rdmenezes/easl

Automatically exported from code.google.com/p/easl

easl's Issues

Byte Order Mark

The byte order mark is not properly handled at the moment. Currently the 
library assumes big-endian format. It could be useful to have a utility 
routine that can check for a BOM. It's not worthwhile having the BOM on 
every single string.

Original issue reported on code.google.com by [email protected] on 4 Jan 2009 at 11:39

Data types

Currently the types char8_t, char16_t and char32_t are defined as char, 
short and long respectively. The sample code from Unicode.org found at 
ftp://www.unicode.org/Public/PROGRAMS/CVTUTF/ specifies their equivalent 
types as unsigned.

The names of the types were chosen based on those from the new C++0x 
specification. I've not heard of the char8_t type being defined, but it's 
good for the sake of clarity.

It would be useful to have these types defined as the as how they will be 
defined in the new C++0x spec.

Original issue reported on code.google.com by [email protected] on 2 Jan 2009 at 6:59

Patch for /trunk/easl/source/getbom.h

temp should be assigned with the incoming str

Original issue reported on code.google.com by [email protected] on 27 Apr 2014 at 9:40

Attachments:

• getbom.h.patch