Re: [poedit-users] Problem with utf-8 encoding

Vaclav Slavik <[email protected]> writes:

> David Bolen wrote:
> > to explain failing to handle even a pure-ASCII case.  One reference
> > commented about the lack of a BOM, but to my understanding a BOM is
> > not required for UTF-8 files
> 
> In fact it _shouldn't_ be present in UTF-8 files, because it doesn't 
> makes sense for UTF-{8,7}. The comment was the other way around: I 
> suspected there was some BOM mark that confused conversion...

Well, I believe it should be legal (although not required) even in
UTF-8 files, at least if I read
    http://www.unicode.org/faq/utf_bom.html#BOM
right.  Clearly not putting it as an actual UTF-8 sequence in a UTF-8
file would confuse things though.

> I _think_ I found the underlying bug in wxWidgets -- it 
> unconditionally uses MB_ERR_INVALID_CHARS, which is documented as 
> available on (w2k-sp4 or xp)+ and UTF-8 is documented as having only 
> this flag allowed, so presumably older versions of Windows check if 
> the flag is 0 and fail...

Based on the test code you sent that does appear to be the problem,
which is good news.  Presumably I can just wait until a subsequent
release of poEdit that includes that update from wxWidgets.

-- David



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642