According to our method of unit test, we should be able to convert from binary to XML and back again and get the same exact binary packet. Given this, we'd have to escape these characters (as ugly as it may look) rather than delete them.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John R. Hogerhuis Sent: Thursday, February 28, 2008 10:38 PM To: LLRP Toolkit Development List Subject: Re: [ltk-d] Java LTK and non XML characters On Thu, Feb 28, 2008 at 9:33 PM, <[EMAIL PROTECTED]> wrote: > > The issue Casey described resulted because we decided to throw an exception > whenever a illegal XML character (as defined in XML 1.0 > http://www.w3.org/TR/xml/#charsets) appeared in the UTF-8 string. This is now > changed. Illegal XML characters are removed from the UTF8 string. > Yeah, I'm considering what to do about the general issue of non-XML characters in utf8v's for LTK-Perl and LTK-XML. Probably what should happen is that characters that are not legal in XML should get quoted in the XML style, in this case I believe � This way, going to/from LTK-XML there won't be any loss of information on the round trip. -- John. ------------------------------------------------------------------------ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
