use IO::HTML; # exports html_file by default
use HTML::TreeBuilder;
my $tree = HTML::TreeBuilder->new_from_file(
html_file('foo.html')
);
# Alternative interface:
open(my $in, '<:raw', 'bar.html');
my $encoding = IO::HTML::sniff_encoding($in, 'bar.html');
The algorithm as implemented here is:
The "<meta>" tag can be in one of two formats:
<meta charset="..."> <meta http-equiv="Content-Type" content="...charset=...">
The search is case-insensitive, and the order of attributes within the tag is irrelevant. Any additional attributes of the tag are ignored. The first matching tag with a recognized encoding ends the search.
$filehandle = html_file($filename, \%options);
This function (exported by default) is the primary entry point. It opens the file specified by $filename for reading, uses "sniff_encoding" to find a suitable encoding layer, and applies it. It also applies the ":crlf" layer. If the file begins with a BOM, the filehandle is positioned just after the BOM.
The optional second argument is a hashref containing options. The possible keys are described under "find_charset_in".
If "sniff_encoding" is unable to determine the encoding, it defaults to $IO::HTML::default_encoding, which is set to "cp1252" (a.k.a. Windows-1252) by default. According to the standard, the default should be locale dependent, but that is not currently implemented.
It dies if the file cannot be opened, or if "sniff_encoding" cannot determine the encoding and $IO::HTML::default_encoding has been set to "undef".
($filehandle, $encoding, $bom)
= html_file_and_encoding($filename, \%options);
This function (exported only by request) is just like "html_file", but returns more information. In addition to the filehandle, it returns the name of the encoding used, and a flag indicating whether a byte order mark was found (if $bom is true, the file began with a BOM). This may be useful if you want to write the file out again (especially in conjunction with the "html_outfile" function).
The optional second argument is a hashref containing options. The possible keys are described under "find_charset_in".
It dies if the file cannot be opened, or if "sniff_encoding" cannot determine the encoding and $IO::HTML::default_encoding has been set to "undef".
The result of calling "html_file_and_encoding" in scalar context is undefined (in the C sense of there is no guarantee what you'll get).
$filehandle = html_outfile($filename, $encoding, $bom);
This function (exported only by request) opens $filename for output using $encoding, and writes a BOM to it if $bom is true. If $encoding is "undef", it defaults to $IO::HTML::default_encoding. $encoding may be either an encoding name or an Encode::Encoding object.
It dies if the file cannot be opened, or if both $encoding and $IO::HTML::default_encoding are "undef".
($encoding, $bom) = sniff_encoding($filehandle, $filename, \%options);
This function (exported only by request) runs the HTML5 encoding sniffing algorithm on $filehandle (which must be seekable, and should have been opened in ":raw" mode). $filename is used only for error messages (if there's a problem using the filehandle), and defaults to ``file'' if omitted. The optional third argument is a hashref containing options. The possible keys are described under "find_charset_in".
It returns Perl's canonical name for the encoding, which is not necessarily the same as the MIME or IANA charset name. It returns "undef" if the encoding cannot be determined. $bom is true if the file began with a byte order mark. In scalar context, it returns only $encoding.
The filehandle's position is restored to its original position (normally the beginning of the file) unless $bom is true. In that case, the position is immediately after the BOM.
Tip: If you want to run "sniff_encoding" on a file you've already loaded into a string, open an in-memory file on the string, and pass that handle:
($encoding, $bom) = do {
open(my $fh, '<', \$string); sniff_encoding($fh)
};
(This only makes sense if $string contains bytes, not characters.)
$encoding = find_charset_in($string_containing_HTML, \%options);
This function (exported only by request) looks for charset information in a "<meta>" tag in a possibly-incomplete HTML document using the ``two step'' algorithm specified by HTML5. It does not look for a BOM. The "<meta>" tag must begin within the first $IO::HTML::bytes_to_check bytes of the string.
It returns Perl's canonical name for the encoding, which is not necessarily the same as the MIME or IANA charset name. It returns "undef" if no charset is specified or if the specified charset is not recognized by the Encode module.
The optional second argument is a hashref containing options. The following keys are recognized:
For people who prefer not to export functions, all functions beginning with "html_" have an alias without that prefix (e.g. you can call "IO::HTML::file(...)" instead of "IO::HTML::html_file(...)". These aliases are not exportable.
The following export tags are available:
my $file = do {
# This file may define the charset later in the header
local $IO::HTML::bytes_to_check = 4096;
html_file(...);
};
The HTML 5 specification recommends using the default value of 1024, but some pages do not follow the specification.
Setting it to "undef" will cause the file subroutines to croak if "sniff_encoding" fails to determine the encoding. ("sniff_encoding" itself does not use $default_encoding).
Please report any bugs or feature requests to "<bug-IO-HTML AT rt.cpan.org>" or through the web interface at <http://rt.cpan.org/Public/Bug/Report.html?Queue=IO-HTML>.
You can follow or contribute to IO-HTML's development at <https://github.com/madsen/io-html>.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE SOFTWARE AS PERMITTED BY THE ABOVE LICENSE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE SOFTWARE TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.