New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistency over "=encoding" requirement for Latin-1 #13886
Comments
From @fbriereThis is a bug report for perl from fbriere@fbriere.net, There doesn't seem to be a consensus on the need to specify an =encoding Flags: Site configuration information for perl 5.18.2: Configured by Debian Project at Sat Mar 1 14:00:24 UTC 2014. Summary of my perl5 (revision 5 version 18 subversion 2) configuration: Locally applied patches: @INC for perl 5.18.2: Environment for perl 5.18.2: |
From @andk"fbriere@fbriere.net (via RT)" <perlbug-followup@perl.org> writes:
Interesting links about the topic in rejected ticket -- |
The RT System itself - Status changed from 'new' to 'open' |
From @fbriereOn Fri, May 30, 2014 at 08:29:57PM -0700, (Andreas J. Koenig) via RT wrote:
Thanks, this didn't come up in my initial search. I must admit to being a bit more confused after reading those tickets If this is correct, then my two gripes would be: - perlpod(1) should make it clear that the lack of =encoding for - Pod::Check should be aware of this and report it -- if not as an |
From @khwilliamsonOn 05/31/2014 10:50 AM, Frédéric Brière wrote:
I have now added text to blead to indicate that there is a risk if you If you think more is needed, let me know
Yes |
Migrated from rt.perl.org#121993 (status was 'open')
Searchable as RT121993$
The text was updated successfully, but these errors were encountered: