Alex Sergeyev wrote:
When AxKit process page by XSP processor it changes '|' characters :)) to '\|' sequence but did not change this sequence to '|' back...Looks like over-escaping. A lot of the code generated by XSP uses q|| as its quoting mechanism, and it thus escapes | in the content. It looks as if some recent patch might have caused escaping to happen twice. Can you tell us which version you're using and provide us with a dump of the generated code? This could be specific to a taglib as well.
Probably I do something wrong...
But my result with '|' char displayed as '\|' and '|' was changed to '\|' too!
--
Robin Berjon <[EMAIL PROTECTED]>
Research Engineer, Expway http://expway.fr/
7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
