RE: Gobo, XM_CALLBACKS on_content and special characters

I found the problem.  Problem is because the new version unescapes
characters automatically now and I was pre-parsing some content to set
the document text.  So it turned all my '&lt;' into '<', so I was infact
then passing '<' the second time around so naturally it failed.  In the
previous version it did not automatically unescape the content so I
never had this problem.  To fix I now make sure to escape all the
content on the first parse.

Thanks for your help.

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Franck Arnaud
> Sent: Friday, May 13, 2005 10:46 AM
> To: [email protected]
> Subject: RE: [gobo-eiffel] Gobo, XM_CALLBACKS on_content and 
> special characters
> 
> 
> 
> > You should expect to see the STRING: "if 4 < 5"
> 
> Yes, but note you may get it in pieces, eg: 
> 
>  on_content ("if 4 ")
>  on_content ("<")
>  on_content (" 5") 
> 
> The parser is entitled by contract to split content 
> wherever it sees fit. I've not checked but it's likely it 
> does it currently on escape characters.
> 
> See XM_CONTENT_CONCATENATOR if you wish to get atomic 
> events.
> 
> 
> 
> To Post a message, send it to:   [email protected]
> To Unsubscribe, send a blank message to: 
> [email protected] 
> Yahoo! Groups Links
> 
> 
> 
>  
> 
> 
> 



To Post a message, send it to:   [email protected]
To Unsubscribe, send a blank message to: [email protected] 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/gobo-eiffel/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/