|
The documentation (http://download.macromedia.com/pub/documentation/en/flex/2/flex2_appdev.pdf)
for localization states that property files can be encoded as Latin-1 or
Unicode (\udddd). However, when I try to compile a UTF-16 property file, I get
the error: [compc] DSHB_Strings_properties(14): col: 23 Error: End of
input reached before closing quote for string literal [compc] [compc] __propObj["■ [compc] ^ [compc] [compc] DSHB_Strings_properties(17): col: 2 Error: Expecting
rightbrace before end of program [compc] [compc] package I thought perhaps the BOM was getting in the way, so I
removed it in a hex editor, but this made no difference. It looks as though the
compiler is choking on the double-byte characters. If I encode the properties file as UTF-8, I get a runtime
error stating that the resource could not be found. I think this is due to the
BOM. If I put the string on the second line of the file, I don’t get the
runtime error, but the string is corrupted (Japanese characters rendering as
garbage Latin-1 characters.) Any ideas?
Tobias. Creo Inc., a subsidiary of Kodak Tobias Patton | Software Developer | Tel: +1.604.451.2700
ext: 5148 | mailto:[EMAIL PROTECTED] | http://www.creo.com -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
- [flexcoders] compc and Unicode properties files Tobias Patton
- Re: [flexcoders] compc and Unicode properties files Paul Hastings
- RE: [flexcoders] compc and Unicode properties files Tobias Patton

