Upon further investigation, I found that dumptorrent is capable of dumping more than one torrent with a single command. Dumping both a torrent containing a centered dot and torrent containing the EN DASH to a single file does indeed yield a mixed encoding. At this point, I don't know if this is due to different encodings used in different torrent files, a problem with dumptorrent, a problem with the bencode library, or a problem with the Windows APIs. I found that I could read the data correctly by trying to decode raw input as UTF-8 and, if that fails, decoding it as cp1252. This seems to work for all torrent files I have encountered so far: 

use strict;
use warnings;
use Try::Tiny;
use Regexp::Common qw /number/;
use Encode;

my $linecount = 0;
        
open(DATA, qq(dumptorrent.exe "$ARGV[0]"|));
binmode(DATA, ":raw");
binmode(STDOUT, ":encoding(UTF-8)");
foreach my $line (<DATA>)
{
    $line = DecodeRawLine($line);
    # Discard the 5 lines of output before the list of filenames
    if (++$linecount > 5)
    {
            last if (length($line) == 0);
            $line =~ s/^ *//;
            $line =~ s/ +\(${RE{num}{real}}[KMG]\)$//; # e.g. " (8.22M
+)" 
            my $sizeindex = rindex($line, ' ') + 1;
            my $filesize = substr($line, $sizeindex);
            # Ignore zero-length files in torrents. 
            if (defined $filesize && length($filesize) > 0 && $filesiz
+e > 0)
            {
                # Remove the extra spaces between the file name and si
+ze
                (my $filekey = $line) =~ s/ +(\d+)$/ $1/;
                print "$filekey\n";
            }
    }
}

sub DecodeRawLine
{
    # IMPORTANT! Any arguments in @_ that are needed in 'try' must be 
+COPIED!
    my $line = substr($_[0], 0, length($_[0])-2); # remove CR-LF
    try
    {
        $line = Encode::decode('UTF-8', $line, Encode::FB_CROAK);
    }
    catch
    {
        $line = Encode::decode('cp1252', $line);
    };
    return $line;
}

[download]

In reply to Re^5: What is the proper way to read non-ANSI data by freonpsandoz
in thread What is the proper way to read non-ANSI data by freonpsandoz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.