Bug#840211: perlunicook man page does not display utf8 char beyond ascii

2016-12-03 Thread Niko Tyni
On Sat, Dec 03, 2016 at 12:21:39PM -0800, Russ Allbery wrote: > Niko Tyni writes: > > > No, I don't think we've ever done that. I think it *should* be as simple > > as patching ./installman to pass utf8 => 1 to Pod::Man (the Perl build > > system doesn't use pod2man itself).

Bug#840211: perlunicook man page does not display utf8 char beyond ascii

2016-12-03 Thread Russ Allbery
Niko Tyni writes: > No, I don't think we've ever done that. I think it *should* be as simple > as patching ./installman to pass utf8 => 1 to Pod::Man (the Perl build > system doesn't use pod2man itself). There might be some issues with > cross-building but that's not really

Bug#840211: perlunicook man page does not display utf8 char beyond ascii

2016-11-19 Thread Niko Tyni
On Fri, Nov 18, 2016 at 12:16:49PM -0800, Russ Allbery wrote: > Dominique Dumont writes: > > > Looks like I was not clear. I was thinking of patching perl build system > > to generate perl* man page (perlrun perlunicook...) as utf8 man page. > > > That should not impact the

Bug#840211: perlunicook man page does not display utf8 char beyond ascii

2016-11-18 Thread Russ Allbery
Dominique Dumont writes: > Looks like I was not clear. I was thinking of patching perl build system > to generate perl* man page (perlrun perlunicook...) as utf8 man page. > That should not impact the generation of other man pages (i.e. not in > Debian perl package) using

Bug#840211: perlunicook man page does not display utf8 char beyond ascii

2016-11-18 Thread Dominique Dumont
On Friday, 18 November 2016 10:54:36 CET Russ Allbery wrote: >> Considering [1], we may want to patch Debian's perl to produce utf8 man > > pages even if upstream cannot, due to portability constraints. > > That's not strictly true, which is the reason why I haven't already > switched Linux

Bug#840211: perlunicook man page does not display utf8 char beyond ascii

2016-11-18 Thread Russ Allbery
Dominique Dumont writes: > On Friday, 18 November 2016 09:34:03 CET Russ Allbery wrote: >> Guillem did some more investigation, and sadly it turns out that raw >> UTF-8 in man pages continues to break even completely current man >> implementations on platforms like macOS. >

Bug#840211: perlunicook man page does not display utf8 char beyond ascii

2016-11-18 Thread Dominique Dumont
On Friday, 18 November 2016 09:34:03 CET Russ Allbery wrote: > Guillem did some more investigation, and sadly it turns out that raw UTF-8 > in man pages continues to break even completely current man > implementations on platforms like macOS. That's a constraint we do not have on Debian/unstable.

Bug#840211: perlunicook man page does not display utf8 char beyond ascii

2016-11-18 Thread Russ Allbery
Niko Tyni writes: > I think upstream (Russ and iirc others on p5p too) have been stepping > very carefully here due to compatibility issues with older nroff > implementations and the like. Guillem did some more investigation, and sadly it turns out that raw UTF-8 in man pages

Bug#840211: perlunicook man page does not display utf8 char beyond ascii

2016-11-18 Thread Niko Tyni
severity 401089 normal reassign 840211 perl-doc 5.24.1~rc3-3 forcemerge 840211 401089 forwarded 401089 https://rt.cpan.org/Public/Bug/Display.html?id=68741 thanks On Sun, Oct 09, 2016 at 05:30:23PM +0200, Dominique Dumont wrote: > Package: perl > Version: 5.24.1~rc3-3 > Severity: normal > > Dear

Bug#840211: perlunicook man page does not display utf8 char beyond ascii

2016-10-09 Thread Dominique Dumont
Package: perl Version: 5.24.1~rc3-3 Severity: normal Dear Maintainer, In perlunicook man page, non-ASCII utf-8 char are replaced by 'X' (which is a shame on a man page dealing with unicode and utf8 issue): Compare: $ man perlunicook | grep -A 4 '$measure' my $measure =