CMS does not support some foreign languages?

[jvence]

I am trying to create an arabic version of a CMS content file but every time I try to save it, all arabic letters are converted to '?'. It pastes it fine but once saved, everything is converted to questions marks.

My db characterset is utf8 and I am able to manually insert records with arabic data.

I thought that Tiny MCE was to blame but the problem even occurs when I don't use the WYSIWYG editor. Also tried it with different browser where I force it to use Arabic character encoding.

You can test it by trying to paste some content from this site http://news.bbc.co.uk/hi/arabic/news/
and you will see what I mean.

Anyone have any idea on why this is happening?

[soshah]

jvence-

What OS is your Portal server running on?

If you are running Portal on a Windows Box try the following:
-Dfile.encoding=UTF-8 as a JVM parameter to the application server

On Windows JVM the default encoding is not UTF-8. On Linux everything works just fine out-of-the-box

Also see here for any clues: http://jira.jboss.com/jira/browse/JBPORTAL-1727

Thanks

[jvence]

jvence-

What OS is your Portal server running on?

If you are running Portal on a Windows Box try the following:
-Dfile.encoding=UTF-8 as a JVM parameter to the application server

On Windows JVM the default encoding is not UTF-8. On Linux everything works just fine out-of-the-box

Also see here for any clues: http://jira.jboss.com/jira/browse/JBPORTAL-1727

Thanks

Thanks Sohil,

I am running it on Mac OS 10.5.2 with JVM 1.5.0 -
Tried specifying -Dfile.encoding=UTF-8 with no success.
Any ideas,

Thank you,

Jean

[jvence]

jvence-

What OS is your Portal server running on?

If you are running Portal on a Windows Box try the following:
-Dfile.encoding=UTF-8 as a JVM parameter to the application server

On Windows JVM the default encoding is not UTF-8. On Linux everything works just fine out-of-the-box

Also see here for any clues: http://jira.jboss.com/jira/browse/JBPORTAL-1727

Thanks

You are right it works fine on Linux. Must be a Mac issue. I will play with the file.encoding param. Thanks for your help