Tags: -1 - patch
On Mon, May 23, 2011 at 04:05:11PM -0700, Russ Allbery wrote:
Niko Tyni nt...@debian.org writes:
It's clearly still true, and I can't see any fix for it other than
adding =encoding utf8 lines in the POD files where necessary.
However, I think all the documents that are
forwarded 492037 http://rt.perl.org/rt3/Public/Bug/Display.html?id=78332
thanks
On Sun, May 22, 2011 at 09:01:23AM +0300, Niko Tyni wrote:
On Sat, May 21, 2011 at 03:56:16PM +0100, Dominic Hargreaves wrote:
As far as I can see, pod2man --utf8 now exists, but will not render
all documents
Niko Tyni nt...@debian.org writes:
It's clearly still true, and I can't see any fix for it other than
adding =encoding utf8 lines in the POD files where necessary.
However, I think all the documents that are rendered incorrectly with
--utf8 are already rendered incorrectly now, albeit in a
On Sat, May 21, 2011 at 03:56:16PM +0100, Dominic Hargreaves wrote:
As far as I can see, pod2man --utf8 now exists, but will not render
all documents correctly - possibly =encoding UTF8 is needed for this
to work.
Is this statement still true, or has any progress happened since the
last
On Wed, Oct 01, 2008 at 02:10:53AM -0700, Russ Allbery wrote:
Niko Tyni nt...@debian.org writes:
Any estimate on how widespread this POD problem is? Is the hardcoded
'pod2man --utf8' in the Lenny perldoc going to cause more grief than
it's worth?
I'm leaning on reverting that and
On Fri, Oct 03, 2008 at 01:49:16PM +0100, Colin Watson wrote:
Due to groff's inability to take Unicode input in most cases at the
moment, man needs to know the language of the manual page in order to
recode it back to a legacy encoding for formatting by groff. It does
this either by relying
Niko Tyni [EMAIL PROTECTED] writes:
OK, it's your call of course.
Both patches have the one important property: they can't break anything
when the utf8 option isn't used. I don't see any point in diverging,
so I think the attached patch (based on yours but cleansed of the
unrelated stopword
On Thu, Oct 02, 2008 at 03:59:45PM -0700, Russ Allbery wrote:
Niko Tyni [EMAIL PROTECTED] writes:
So the output is ISO-8859-1 where possible and UTF-8 elsewhere.
Russ, I think the binmode($output, :utf8) really belongs in pod2man
instead of Pod::Man.
It turns out, at least based on the
Niko Tyni [EMAIL PROTECTED] writes:
I see. The Perl internal encoding is UTF-8, but there are ways to get
invalid UTF-8 in there, for example by using :utf8 on binary input.
This invalid UTF-8 will then be output as-is with if :utf8 is set on
output.
I can't really think of a case where
On Fri, Oct 03, 2008 at 02:19:52AM -0700, Russ Allbery wrote:
Niko Tyni [EMAIL PROTECTED] writes:
I don't think there's any need to touch the filehandles of people using
parse_file().
I would prefer not to touch the filehandle, but I don't think it's
acceptable to say that if you're
On Fri, Oct 03, 2008 at 03:28:28PM +0300, Niko Tyni wrote:
Colin, I can't really get man to work with cyrillic documents. As an
example, the attached ru.pod from #492037 looks fine after 'pod2man
--utf8', but 'man -l ru.man' just drops all the cyrillic characters.
Any ideas? Is this supposed
On Wed, Oct 01, 2008 at 11:26:23AM -0700, Russ Allbery wrote:
Niko Tyni [EMAIL PROTECTED] writes:
I think that for lenny you may want to back out of the --utf8 change and
give it some time to settle.
Are you referring to backing out the whole Pod::Man update (#480997)
or just the
Niko Tyni [EMAIL PROTECTED] writes:
Thanks, we're on the same page then. I'll revert the perldoc change.
Does this documentation patch for lenny look OK to you?
Yup, this looks good to me.
(I suppose it should be duplicated in pod2man.PL too.)
Yes.
--
Russ Allbery ([EMAIL PROTECTED])
On Wed, Oct 01, 2008 at 11:26:23AM -0700, Russ Allbery wrote:
Niko Tyni [EMAIL PROTECTED] writes:
I think that for lenny you may want to back out of the --utf8 change and
give it some time to settle.
Are you referring to backing out the whole Pod::Man update (#480997)
or just the
Niko Tyni [EMAIL PROTECTED] writes:
Hm, this is looking worse the more I stare at it.
I spent four and a half hours on this the other night before producing the
patch that was in my previous message, so I'm sympathetic. :) It gets to
be more and more of a headache the more you work through
On Tue, Sep 30, 2008 at 08:22:35PM -0700, Russ Allbery wrote:
You got it exactly right. Basically, podlators has been papering over
this bug incorrectly, but in a way that happens to do the right thing with
a common POD problem.
So if you're using UTF-8, starting the POD with:
Niko Tyni [EMAIL PROTECTED] writes:
Any estimate on how widespread this POD problem is? Is the hardcoded
'pod2man --utf8' in the Lenny perldoc going to cause more grief than
it's worth?
I'm leaning on reverting that and reopening #492037 until the issue is
sorted out in Pod-Perldoc
On Wed, Oct 01, 2008 at 02:10:53AM -0700, Russ Allbery wrote:
Niko Tyni [EMAIL PROTECTED] writes:
Any estimate on how widespread this POD problem is? Is the hardcoded
'pod2man --utf8' in the Lenny perldoc going to cause more grief than
it's worth?
I'm leaning on reverting that and
On Wed, Oct 01, 2008 at 02:10:53AM -0700, Russ Allbery wrote:
Niko Tyni [EMAIL PROTECTED] writes:
Any estimate on how widespread this POD problem is? Is the hardcoded
'pod2man --utf8' in the Lenny perldoc going to cause more grief than
it's worth?
I looked at this some more, and there's
Niko Tyni [EMAIL PROTECTED] writes:
I think that for lenny you may want to back out of the --utf8 change and
give it some time to settle.
Are you referring to backing out the whole Pod::Man update (#480997)
or just the hardcoded 'pod2man --utf8' in perldoc (#492037) ?
Sorry, I meant only
On Wed, Oct 01, 2008 at 11:26:23AM -0700, Russ Allbery wrote:
Niko Tyni [EMAIL PROTECTED] writes:
Are you referring to backing out the whole Pod::Man update (#480997)
or just the hardcoded 'pod2man --utf8' in perldoc (#492037) ?
Sorry, I meant only the pod2man --utf8 change in perldoc. I
found 500210 5.10.0-15
thanks
On Fri, Sep 26, 2008 at 02:04:55PM +0300, Niko Tyni wrote:
On Thu, Sep 25, 2008 at 11:37:21PM +0200, Gerfried Fuchs wrote:
Package: perl-doc
Version: 5.10.0-14
Severity: normal
When running perldoc perlrun I have strange characters in the output of
it,
Colin Watson [EMAIL PROTECTED] writes:
For me, this fixed the case where a 0xA0 byte is embedded essentially
accidentally in the middle of a UTF-8 stream (as happened with debconf's
Russian translations), but it broke the case where 0xA0 is actually
being used as a non-breaking space. Note
Package: perl-doc
Version: 5.10.0-14
Severity: normal
Hi!
When running perldoc perlrun I have strange characters in the output of
it, and I managed to pin it down to a short POD snippet like this:
#v+
=head1 SYNOPSIS
Bperl S[ B-sTtUWX ]
#v-
The S[ ] does strange stuff with the
tag 500210 patch fixed-upstream
thanks
On Thu, Sep 25, 2008 at 11:37:21PM +0200, Gerfried Fuchs wrote:
Package: perl-doc
Version: 5.10.0-14
Severity: normal
When running perldoc perlrun I have strange characters in the output of
it, and I managed to pin it down to a short POD snippet like
25 matches
Mail list logo
