Saturday 25 March 2006 10:19:33 am - 11 replies
Modified on Saturday 25 March 2006 10:20:44 am by Gabriel Ambuehl
Xavier Dutoit
Tuesday 28 March 2006 8:08:01 am
It looks like a bug to me. Any news on that topic ?
X+
http://www.sydesy.com
Gabriel Ambuehl
Tuesday 28 March 2006 11:43:32 am
Yes but it seems to happen during serializing back to text, the dom tree itself is working fine.
Visit http://triligon.org
Tuesday 28 March 2006 11:06:18 pm
So that's the toString method that doesn't play nicely with & then. Right ?
Wednesday 29 March 2006 12:28:58 am
I'd say so.
I got around it with some more hacking of my own (which breaks the use of & in XHTML documents but that doesn't really matter much to me as & should work, too).
Kirill Subbotin
Friday 31 March 2006 2:20:51 am
hm... probably toString function need to have some parameter like convertSpecialChars as well... Will this solve a problem?
Friday 31 March 2006 3:35:04 am
It might solve the problem (it's mostly what I tacked on it, but it's not entirely clean I think).
Another issue with ezxml is that it silently discards of special chars (like German umlauts, Euro sign etc)
Friday 31 March 2006 4:41:55 am
I'm not sure this bug is related.
http://ez.no/bugs/view/8068
Friday 31 March 2006 5:35:06 am
It's likely somehow related.
It's essentially what I saw with my examples.
Valentin Doroschuk
Tuesday 11 April 2006 5:54:29 am
- Added convertSpecialChars parameter into toString().
Wednesday 12 April 2006 1:47:20 pm
Hi,
It that on pubsvn ? What version ?
Thursday 13 April 2006 12:35:23 am
stable/3.7 rev. 15624, trunk rev. 15625
You must be logged in to post messages in this topic!