develooper Front page | perl.perl5.porters | Postings from December 2014

Re: [perl #121993] Inconsistency over "=encoding" requirement forLatin-1

Thread Previous
From:
Karl Williamson
Date:
December 31, 2014 04:59
Subject:
Re: [perl #121993] Inconsistency over "=encoding" requirement forLatin-1
Message ID:
54A382A7.8000705@khwilliamson.com
On 05/31/2014 10:50 AM, Frédéric Brière wrote:
> On Fri, May 30, 2014 at 08:29:57PM -0700, (Andreas J. Koenig) via RT wrote:
>> Interesting links about the topic in rejected ticket
>> https://rt.cpan.org/Ticket/Display.html?id=79232
>
> Thanks, this didn't come up in my initial search.
>
> I must admit to being a bit more confused after reading those tickets
> and messages than before.  If I understand correctly, this is meant to
> be a warning, but due to limitations in Pod::Simple, the difference
> between warnings and errors is rather moot, and this "warning" will
> therefore show up under "POD ERRORS", make Test::Pod fail, etc.
>
> If this is correct, then my two gripes would be:
>
>   - perlpod(1) should make it clear that the lack of =encoding for
>     anything other than ASCII is, if not forbidden, at least strongly
>     discouraged.

I have now added text to blead to indicate that there is a risk if you 
have non-ASCII without an =encoding.  Commit
a0879bf8a3066bd055931dcc51f2c4f80ec01ffb

If you think more is needed, let me know
>
>   - Pod::Check should be aware of this and report it -- if not as an
>     error, then at least as a warning.  (Although if Pod::Parser is
>     indeed to be replaced with Pod::Simple, I guess this issue will
>     resolve itself automatically.)

Yes


Thread Previous


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About