Re: Assume CP1252

On Mon, 2015-01-05 at 21:58 -0800, David E.Wheeler wrote:
> Pod Peeps:
> 
> perlpodspec says:
> 
>    *   Since Perl recognizes a Unicode Byte Order Mark at the start of files
>        as signaling that the file is Unicode encoded as in UTF-16 (whether
>        big-endian or little-endian) or UTF-8, Pod parsers should do the same.
>        Otherwise, the character encoding should be understood as being UTF-8
>        if the first highbit byte sequence in the file seems valid as a UTF-8
>        sequence, or otherwise as Latin-1.
> 
> I suggest we switch from Latin-1 to CP1252.

I also agree this is a good idea.  None of the Latin-1 control
characters that CP1252 replaces with printable characters should be
appearing in POD anyway.

Regards
Grant