I had the same problem. FredCK found the cause of the problem. This is how he replied to me:
"Hi Marko,
I found out a solution for the problem!!!
The only problem is the encoding used to save the JS files. The original files where saved with Western European Codepage 1252 encoding. In this case some characters are not accepted. To solve the problem you just have to save the same file with Unicode encoding. Everything works fine then.
You will find the correct file attached. (I had to zip it because Outlook doesnt allow JS files on attachments for security reasons)
Ive used Visual Studio to save the files. You can define the encoding in the Advanced saving options menu. If you have problems on doing that, just send me the translated files (zip) and I save then in the correct encoding for you.
In any case Ill manage to save all files in Unicode format for the final release.
I use "windows-1250" charset for my webpages. I had tried to save all .js files in "Unicode" codepage encoding (I mean all files like /fckeditor/js/*.js and /fckeditor/fckeditor.js).
It still display incorrect characters in EditorArea window.
Is there any else to do? If I understood well there is an <object> tag that displays the EditorArea.
for php version: The problem is in fckeditor.php. It uses htmlentities function for quotes conversion. But this function convert all characters which have character entity equivalents in HTML. thats why it converts foreign characters in &xxx;. i've change this function to htmlspecialchars() which converts only quotes.
We had similar problems with french special characters (and any special characters i suppose). Our application is in UTF-8. We solved our problem by removing the htmlencode function in the fckeditor.asp wich modify utf-8 character.
For example a "" is store in our database (sqlserver) as "A~" (or something like that) This "A~", if display by IE in UTF-8, is well interpreted and shows as "". But if it passes through htmlencode function it becomes #466#4654 and shows as "A~".
This is why we removed the htmlencode function which is not a good solution for a public application as this function prevent malicious users to insert script or code in a database.
Maybe our master Fred C.K. could tell more about this.
same problem
RE: Internalization - lang. specific characters
"Hi Marko,
I found out a solution for the problem!!!
The only problem is the encoding used to save the JS files. The original files where saved with Western European Codepage 1252 encoding. In this case some characters are not accepted. To solve the problem you just have to save the same file with Unicode encoding. Everything works fine then.
You will find the correct file attached. (I had to zip it because Outlook doesnt allow JS files on attachments for security reasons)
Ive used Visual Studio to save the files. You can define the encoding in the Advanced saving options menu. If you have problems on doing that, just send me the translated files (zip) and I save then in the correct encoding for you.
In any case Ill manage to save all files in Unicode format for the final release.
Thanks,
FredCK"
RE: Internalization - lang. specific characters
It still display incorrect characters in EditorArea window.
Is there any else to do? If I understood well there is an <object> tag that displays the EditorArea.
Any help will be appreciated.
RE: Internalization - lang. specific characters
Bedla
RE: Internalization - lang. specific characters
Bedla (smid@ebrana.com)
RE: Internalization - lang. specific characters
The problem is in fckeditor.php. It uses htmlentities function for quotes conversion. But this function convert all characters which have character entity equivalents in HTML. thats why it converts foreign characters in &xxx;. i've change this function to htmlspecialchars() which converts only quotes.
RE: Internalization - lang. specific characters
Special characters and htmlencode()
For example a "" is store in our database (sqlserver) as "A~" (or something like that) This "A~", if display by IE in UTF-8, is well interpreted and shows as "". But if it passes through htmlencode function it becomes #466#4654 and shows as "A~".
This is why we removed the htmlencode function which is not a good solution for a public application as this function prevent malicious users to insert script or code in a database.
Maybe our master Fred C.K. could tell more about this.
Hope this helps
RE: Special characters and htmlencode()
In fck_config.js , set:
config.EnableXHTML = false ;
RE: Internalization - lang. specific characters
RE: Internalization - lang. specific characters