Tobias Patton wrote: > 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,
no, that should be "escaped" ASCII unicode or as sun calls it "Unicode-encoded" as used in java style resource bundles (rb) NOT utf-anything. > 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. shouldn't be *any* "double-byte characters", it should be "escaped" ASCII unicode. what are you using to create/manage the property files? if you have the JDK installed someplace & your resource bundles are utf-8 or whatever, try using the command-line native2ascii tool to convert the these into proper rb. otherwise get an rb tool. frankly for anything even mildly complex you *should* be using an rb tool like ibm's rbManager (part of the icu4j project). trying to handle what's been translated, managing changes, interfacing w/3rd party translation agencies, etc. with something like notepad will ruin your day. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
