At least in your second example, you are not properly decoding your input.

eval { $sCodepoints = decode( "iso-8859-1", $sLine, Encode::FB_CROAK )
+ };
if ( $@ )
{ # input was not iso-8859-1
    print "> No ISO-8859-1, maybe UTF8 ?\n";
    $sCodepoints = $sLine;
}

[download]

Here, $sCodepoints does not contain properly decoded UTF-8.

I would try a loop over the possible encodings:

for my $encoding_candidate (qw(iso-8859-1 UTF-8)) {
eval { $sCodepoints = decode( $encoding_candidate, $sLine, Encode::FB_
+CROAK ) };
if ( $@ )
{ # input was not $encoding_candidate
    print "> Not $encoding_candidate\n";
    #$sCodepoints = $sLine;
}
}

[download]

In reply to Re: convert files to ansi (8859-1) by Corion
in thread convert files to ansi (8859-1) by Yaerox

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.