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.
Just out of curiosity, why is there an "\0" at the end of the UTF8 string in
your implementation? If I remember this correctly, the length of the UTF8
string gets encoded.
- Christian
Quoting "John R. Hogerhuis" <[EMAIL PROTECTED]>:
> On Thu, Feb 28, 2008 at 8:40 AM, Casey Hagen <[EMAIL PROTECTED]> wrote:
>> I just want to point out where the null character is, since it's not
>> visible in the code Gordon sent.
>>
>> The null character trails the verion string in the ReaderFirmwareVerion
>> XML tag.
>>
>> <ReaderFirmwareVersion>3.0.1.240\0</ReaderFirmwareVersion>
>>
>> Thanks,
>>
>> Casey
>
> Actually that was me, not Gordon. But, good point. Looks like LTKPerl
> discards the null when it converts the binary message to XML.
>
> Not sure whether to consider that a bug or a feature (of LTKPerl).
>
> -- 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
