Re: Certain msgs crashing TOT fire

I changed the string transform for XML escaping to include the 
characters that XML doesn't have to accept.  The unprintable characters 
are changed to a big fat unicode ?.  I think this should handle 
everything the best way.  So, as soon as the changes propagate to ToT, 
you should be able to try it.

On Jun 3, 2004, at 1:04 AM, Graham Booker wrote:

> OK, this helps greatly, now I know what is wrong...  The issue becomes 
> how to fix it!
>
> For those who would like to know:
> The character is 0x4.
> XML is required to accept 0x9, 0xA, 0xD, 0x20-0xD7FF, 0xE000-0xFFFF, 
> and 0x10000-0x10FFFF.
> 0x4 is outside this range, so that is why the parser is breaking.
> (http://www.w3.org/TR/2004/REC-xml-20040204/#charsets)
>
> I thought of encoding it as  but the parser said:
>
> Entity: line 1: parser error : xmlParseCharRef: invalid xmlChar value 4
> <message><span style="color: #0000d5; font: 10px 
> Times">&#x4;</span></message>
>
>
>
> Question that I would like answered:
> So, I am thinking that the best course of action at the moment is to 
> flat out DROP these characters!  What does everyone else think?
>
>
> BTW, something to parse these sounds seems to me like a great idea for 
> a plugin.  Anyone want to write one?  The plugin can read these 
> characters before the XML parser gets to it and drops them.  It can 
> even kill the message so it is never displayed if it so chooses (which 
> would be wanted in this case).
>
>


------------------------------------------------------------------
Graham Booker                   Texas A&M University
[email protected]    Graduate Student in ELEN
------------------------------------------------------------------