Windows once again does wonderful things without being asked:
I am writing unicode to a file, to be read back in again. utf-16le has 2 byte or 4 byte characters, but on windows, if one of these bytes is a CR, it is automatically "corrected" to a CR LF, and I end up with an odd number of bytes, and a mess when I try to read this in with the same encoding.
What a mess. And since I am already using binmode, I don't know how to set it to 'binary'. It does not work to just add a ':raw' or ':bytes' to the encodoing.
$_ = "\x{ff0a}\x{1234}";
open OUT, ">temp.txt";
binmode OUT, ":encoding(UTF-16le)";
print OUT;
close OUT;
# The output file contains FIVE bytes: 0D 0A FF 34 12
open IN, "<temp.txt";
binmode IN, ":encoding(UTF-16le)";
<IN>; # this line causes: UTF-16LE:Partial character at temp.pl lin
+e 12.
close IN;
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|