What's the problem exactly?
http://fr.php.net/manual/fr/function.eval.php In the example and in the screen output, the word "caf�" is displayed instead of "caf�", that's the problem.
Yes, that's because you used entities in CDATA sections, which is wrong. In CDATA sections you should use chacters from the current charset in which the document is written. I do not want to add a hack for this.
The problem is, and we already discussed about it, is that Damien uses a Mac, so when he uses accents, all I get is ^M^Z.. If you don't want to add a hack for this, should I ? or should we buy a new computer for Damien ?
If you need to include special chars with entities in CDATA sections, then you need to drop the CDATA and use the "old method", which involves escaping of XML special chars.
What do you mean by this ? Can you give me a small example ? I really would like to fix this problem for the new coming year :)
> If someone adds some decoding of entities
in CDATA sections that we are going to violate the XML spec, and our validating tools will be fooled... An option might be to create a precommit script for Damien to run before he commits files, which converts the special chars to use proper codes, so all of you will be happy with file contents.
I don't like this idea too much, but if it's the only solution.. I'll look in this direction when I understand how we should replace the CDATA's parts.
PS : I love when a personnal discussion gets forwarded to a mailing list...
Since this is a somewhat general problem, it is nice to have records of it in the archives for future upcoming translation workers to point to...
never mind (lack of sleep)
didou
