| Subject: | Pod::Simple and latin-1 encoding |
| Date: | Sun, 26 Aug 2012 20:55:46 +0200 |
| To: | bug-pod-simple [...] rt.cpan.org |
| From: | Slaven Rezic <slaven [...] rezic.de> |
Hello,
Pod::Simple currently (e.g. with version 3.23) complains if a Pod
document has latin-1 characters in it but no =encoding command
specified. I think this is incorrect, both perlpod.pod and
perlpodspec.pod specify that a document without =encoding command is in
latin-1:
perlpod.pod (as of commit 684c7e375f581ccd114b4c6b4e8ea730402b50f3 in
perl):
=encoding encoding
... Most users won't need this; but if your encoding isn't US-ASCII
or Latin-1 ...
perlpodspec.pod (as of commit c85e9b4c9684bc896847f5a80e9e91b478c2fc59
in perl):
... 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.
(Unfortunately perlpodspec.pod isn't quite clear about this when
explaining encoding; the quoted paragraph is from the "Notes on
Implementing Pod Processors" section.
Regards,
Slaven
--
Slaven Rezic - slaven <at> rezic <dot> de