The first reply should work fine, unless your script generates other warnings unrelated to character encoding, and if you are simply testing for utf8 vs. some different (single-byte) encoding, then Encode::Guess should do nicely as well. Here's another way, which involves specifically testing that a given file is encoded correctly as utf8 data (with no errors, corruptions, or use of non-utf8 characters): 
use Encode;

my $filename = "whatever";

eval {
    open my $file, "<:raw", $filename or die $!;
    local $/;
    local $_ = <$file>;
    decode( "utf8", $_, Encode::FB_CROAK );
}
die "$filename is invalid utf8: $@\n" if $@;

[download]
For more info on that, check the Encode man page, esp. the section titled "Handling Malformed Data".

In reply to Re: detect incorrect character encoding by graff
in thread detect incorrect character encoding by Errto

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.