I ran a small series of checks for well-formedness, validity, if ascii, and if cp1252 using:

String::UTF8
Search::Tools::UTF8

#!/usr/bin/perl

use strict;
use warnings;
use Search::Tools::UTF8;
use String::UTF8 qw(:all);

my $text = 'There are those of you out there stuck with Latin-1.';
print my $str =
is_utf8($text), "\n", #check if well-formed 
is_valid_utf8($text), "\n",
is_ascii($text), "\n",
looks_like_cp1252($text), "\n";

[download]
It outputs: 
1
1
1
0

[download]
It's well-formed, valid utf8. It's also ascii but not cp1252. The well-formed test comes from String::UTF8, while the other methods come from Search::Tools::UTF8. Does this help?

In reply to Re: What's the best way to detect character encodings, Windows-1252 v. UTF-8? by Khen1950fx
in thread What's the best way to detect character encodings, Windows-1252 v. UTF-8? by Jim

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.