Think about Loose Coupling | |
PerlMonks |
Re^3: Problems parsing UTF16 fileby graff (Chancellor) |
on Aug 11, 2012 at 18:19 UTC ( [id://986915]=note: print w/replies, xml ) | Need Help?? |
I should mention that if you open the input file like this:
(that is, without the "LE" in the encoding spec), then you won't need this line: because the "unmarked" version of UTF-16 encoding requires that a stream-initial BOM be provided on input, and the initial BOM is stripped from input as a result. For output of UTF-16, if you're trying to match a particular byte order, it'll be best for the code to state this explicitly, because the "default" output order might be different, depending on your machine and environment. Of course, whenever a file is written with 'UTF-16' encoding, the initial BOM is always included, which should make it possible for any other process to read the file correctly - but of course, not all processes that expect UTF-16LE (or BE) will live up to that specification. Anyway, when you do decide to be explicit about byte order for an output file, then you should also be sure to include the initial BOM (because it won't be supplied by default). So if you try out the snippet below, see whether there's any difference in the output when you comment out the "UTF-16" open statement and uncomment the two lines that use "UTF-16LE" instead:
In Section
Seekers of Perl Wisdom
|
|