I see that this happens when FCKConfig.EnableSourceXHTML is set to true. Example: character "" is converted in "î". Can this be disabled? The text that I'm editing in FCKEditor in entered in a MySQL database and this substitutions affect the way that the database is searched and sorted.
I have the same problem. I need to store the UTF-8 codes, MySQL knows how to handle them, but instead I get HTML special character codes in which every character counts as one. How to disable the automatic entity creation?
But disabling the XHTML, I think you will have the original character. But For me there is still a problem because the HTML attribute are not written between "
exe <FONT COLOR=#FF00000> instead of <FONT COLOR="#FF0000">.
XHTML feature is great especially when you handle HTML code that is suppose to be displayed on a webpage.
As I can see FCK need to convert the original character into a special char to parse correct HTML into XHTML. A solution could be to reconvert them into original char when "ONSUBMIT" event fires.
The original code where the original chars are converted into HTML special chars is in editor\_source\internals\fckxhtml.js and the character conversion map is in editor\_source\internals\fckxhtmlentities.js. Note that this 2 files are the source code so that you can better understant that's going on. The files that keep the code that is executed (when XHTML is parsed) is located in editor\js\fckeditorcode_gecko_1.js and editor\js\fckeditorcode_ie_1.js (one for Geko ant the other for IE).
This are the place where FCK convert the original chars to special chars.
UTF-8 sites validate, so I see no critical need to use the entites. It would be great if next release included a configuration option to switch off the entity creation.
file: editor\_source\internals\fckxhtml.js 1. find Text Node handling code (line ~236 to ~258) and comment all the code that belongs to "case 3:" except the "break" statement. This must be between line 236 and line 258.
2. Uncomment the code on line ~261 [xmlNode.appendChild( this.XML.createTextNode( htmlNode.nodeValue ) ) ;]
RE: central european chars
Thanx.
RE: central european chars
RE: central european chars
exe <FONT COLOR=#FF00000> instead of
<FONT COLOR="#FF0000">.
Hope it helps
RE: central european chars
As I can see FCK need to convert the original character into a special char to parse correct HTML into XHTML. A solution could be to reconvert them into original char when "ONSUBMIT" event fires.
Could this be male on FCK2. Where? How?
RE: central european chars
RE: central european chars
This are the place where FCK convert the original chars to special chars.
RE: central european chars
I will look at these files.
RE: central european chars
RE: central european chars
Here's the fix:
file: editor\_source\internals\fckxhtml.js
1. find Text Node handling code (line ~236 to ~258) and comment all the code that belongs to "case 3:" except the "break" statement. This must be between line 236 and line 258.
2. Uncomment the code on line ~261 [xmlNode.appendChild( this.XML.createTextNode( htmlNode.nodeValue ) ) ;]
3. Re-pack the source using FCKeditor.Packager.exe (http://prdownloads.sourceforge.net/fcke ... p?download). Note that you need NET Framework Version 1.1(http://www.microsoft.com/downloads/deta ... laylang=en) in order to run the FCK packager.
4. Enjoy it!
RE: central european chars
It works great for the accentuated characters. How can I deal with the symbol like the euro one. I get a ? instead of .
RE: central european chars
If I look in the FCKeditor source, the euro symbol is not converted. My further processing of the output string makes this symbol to be modified.