Skip Menu |

This queue is for tickets about the Unicode-String CPAN distribution.

Report information
The Basics
Id: 14638
Status: resolved
Priority: 0/
Queue: Unicode-String
People
Owner: Nobody in particular
Requestors: jtwang [...] mit.edu
Cc:
AdminCc:
Bug Information
Severity: Important
Broken in:
  • 2.06
  • 2.07
Fixed in: 2.08

History Show all quoted text
  Sun Sep 18 19:29:41 2005 Guest - Ticket created
Subject: Does not conform to RFC 2781 for UTF-16
Unicode::String does not conform to RFC 2781 specifying UTF-16 encoding. Unicode::String should support the utf-16le and utf-16be identifiers to determine byte ordering of the input string. Furthermore, Unicode::String should process the BOM in the first two bytes of strings marked as utf-16 to determine the byte order for the remainder of the string, stripping the BOM in the resulting output.
  Sun Sep 18 19:31:39 2005 Guest - Correspondence added
From: jtwang [...] mit.edu
[guest - Sun Sep 18 19:29:41 2005]: Show quoted text
> Unicode::String does not conform to RFC 2781 specifying UTF-16 > encoding. Unicode::String should support the utf-16le and utf-16be > identifiers to determine byte ordering of the input string. > Furthermore, Unicode::String should process the BOM in the first > two bytes of strings marked as utf-16 to determine the byte order > for the remainder of the string, stripping the BOM in the resulting > output.
I apologize - RFC 2781 actually specifies that programs processing strings marked as utf-16 MUST be able to process the BOM. So this bug is actually quite critical.
  Mon Oct 31 09:55:39 2005 GAAS [...] cpan.org - Status changed from 'new' to 'resolved'
  Mon Oct 31 09:56:33 2005 GAAS [...] cpan.org - Fixed in 2.08 added