Hi,
following problem occurs when I have activated HTMLEntities processing in fckconfig.js.
When entering the EURO sign (€) in text-view and switching to source-view it is translated to ¤. Switching back to text-view shows a square instead of the correct sign.
I had a look at the demo of the editor on this site and had a different result. In the demo the sign is translated to &euro when switching to the source-view.
Any suggestions why in my case the sign isn't translated properly would be highly appreciated.
following problem occurs when I have activated HTMLEntities processing in fckconfig.js.
FCKConfig.ProcessHTMLEntities = true ;
When entering the EURO sign (€) in text-view and switching to source-view it is translated to ¤. Switching back to text-view shows a square instead of the correct sign.
I had a look at the demo of the editor on this site and had a different result. In the demo the sign is translated to &euro when switching to the source-view.
Any suggestions why in my case the sign isn't translated properly would be highly appreciated.
Re: HTMLEntities Translation
is there anybody who has an idea?
Greetings from Germany
Re: HTMLEntities Translation
Greets from Berlin
Attachments:
Re: HTMLEntities Translation
Andre
Re: HTMLEntities Translation
Hey and thanx for helping. Unfortunately we still haven't found a solution for the problem. We tried to disable the
by setting it to
. This is working, but we are not sure about whether this is an option. I think, we will need the processing of the HTML-Entities for other stuff...
Any idea, why it's working in the online demo but not with our local installation?
Another way to check whether your installation has the same "bug" is the following:
1. Open your page with at least one FCKeditor
2. Click on "Source"-Button
3. Enter
4. Click again on the "Source"-Button
5. Now back in WYSIWYG-Mode we still have an Euro symbol
6. Another click on "Source"-Button and the
is now a
in the source code
7. Back to WYSIWYG-Mode we have the wrong symbol...
I don't really get the point where that shi** happens. Anyone an idea? Config? We already tried the original config from the online demo (http://www.fckeditor.net/fckeditor/2.6.1/fckconfig.js) - still the same problem... we also tried to experiment with the meta charset, without any success...
Please help us!
Re: HTMLEntities Translation
Re: HTMLEntities Translation
Not yet - but i can build one on monday... i will let you know
Re: HTMLEntities Translation
Re: HTMLEntities Translation
Maybe, do you have any idea what we should test according this charset problem instead of the meta charset value?
OK, i made the demonstration installation ready for you! You can test this "phenomen" here:
http://donau.kicms.de/fck_test/test.html
Please report any information you could give us!
Re: HTMLEntities Translation
Re: HTMLEntities Translation
Re: HTMLEntities Translation
At least I can't tell, I use Tomcat only.
Re: HTMLEntities Translation
I can tell you what's going on, but you will have to figure out why.
The problem is that the document that hosts the text area containing the source (the one with the class SourceField) is identified using character set ISO-8859-15, which reinterprets the value of code A4, which displayed as ¤ in ISO 8859-1 (Western) and as € in ISO-8859-15:
http://en.wikipedia.org/wiki/ISO/IEC_8859-15
You can see this character set if you install DOM Inspector in FireFox (a standard add-on). If you do a small experiement and switch the encoding of your test page (View > Character Encoding) to Western (ISO-8859-1) and then back to UTF-8, you will see that your problem goes away.
So, it looks to me that one of the editor's pages gets served either with the wrong encoding or with no encoding at all and ISO-8859-15 is assumed.
Andre
Re: HTMLEntities Translation
I looked at your HTTP traffic and can even tell you why this is happening. This request:
GET /fck_test/FCKeditor/editor/fckeditor.html?InstanceName=Test&Toolbar=Test HTTP/1.1
results in this response:
HTTP/1.1 200 OK
Date: Sun, 22 Jun 2008 14:43:41 GMT
Server: Zope/(Zope 2.10.5-final, python 2.4.4, linux2) ZServer/1.1
Content-Length: 11052
Content-Type: text/html; charset=iso-8859-15
Via: 1.1 donau.kicms.de
This is your problem.
Andre
Re: HTMLEntities Translation
Thanx for your help. It's working the way you described it, but now the FCKEditor isn't processing the € symbol at all. I am not sure whether that's good for us...


@A.M.
Another thing is, that when we are looking at the HTTP-Response, i cannot see the wrong encoding. I have just made 2 screenshots which say it's encoded with utf-8
HTTP-Response via Web-Developer (FF-Plugin):
HTTP-Response via Dom Inspector (FF-Plugin):
Even if i use the following page, it results in utf-8 encoding
http://web-sniffer.net
Can you tell me, how you listed your HTTP-Response to see the wrong encoding?
Re: HTMLEntities Translation
Try the URL I mentioned.
Re: HTMLEntities Translation
Re: HTMLEntities Translation
Re: HTMLEntities Translation