Actually, I would be a little surprised to find a BOM in
combination with UTF-8 (as the encoding is just a sequence of
bytes). Normally, you'd find BOMs with the "ucs-2" encodings,
as used by Windows in many places. With those, we have a 16-bit value per char, and thus the internal byte ordering matters.
Anyway, what you could try is something like this (not sure if this
is the most elegant way, but it should work... Update: it isn't :) - apparently there's File::BOM)
sub openfile_unicode {
my $filename = shift;
open my $fh, "<:raw", $filename or die "Cannot open $filename: $!\
+n";
my $bom;
read $fh, $bom, 2;
if ($bom eq "\xff\xfe" || $bom eq "\xfe\xff") { # BOM present?
# if so, determine if little- or big-endian
my $encoding = "ucs-2" . ($bom eq "\xff\xfe" ? "le":"be");
binmode $fh, ":encoding($encoding)";
} else { # otherwise assume UTF-8
# reopen file
close $fh;
$fh = undef;
open $fh, "<:encoding(utf8)", $filename or die "Cannot open $f
+ilename: $!\n";
}
return $fh;
}
my $fh = openfile_unicode("somefile");
while (my $line = <$fh>) {
# ...
}
-
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.
|