Re: Certain msgs crashing TOT fire

Graham Booker <[email protected]> Thu, 3 Jun 2004 01:04:53 -0500
Newsgroups gmane.network.fire.devel
Message-ID <[email protected]>
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 &#x4; 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).

On Jun 2, 2004, at 11:10 PM, brett wrote:

> It some sort of add on program where the users sends a command like 
> "/skiss" and it makes a kissing sound - assuming both parties have the 
> program - of course we just end up receiving the dodgy msg with hidden 
> characters.   I found a little bit of info at the end of this page 
> about what its sending
>
> http://www.messengertools.net/?page=tipstricks#msnplusinfo
>
> If u view this page with safari ull see a little box character, 
> copying that character and sending it to fire will crash fire.  U can 
> also send the character from fire and it crash itself
>
>
> On 03/06/2004, at 12:47 AM, Graham Booker wrote:
>
>> Believe it or not, the devs have actually hit this bug before, but we 
>> have been unable to track it down.
>>
>> It would help greatly if you could tell me the EXACT messages that 
>> were SENT!  Then I can track this down.  I suspect that it is an xml 
>> encoding issue.
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> From Windows to Linux, servers to mobile, InstallShield X is the one
> installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> fire-development mailing list
> fire-development-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/fire-development
>
>


------------------------------------------------------------------
Graham Booker                   Texas A&M University
[email protected]    Graduate Student in ELEN
------------------------------------------------------------------
smime.p7s (application/pkcs7-signature, 2.3 KB) - not displayed