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

[Niko Tyni]

On Sat, Dec 03, 2016 at 12:21:39PM -0800, Russ Allbery wrote:
> Niko Tyni <ntyni at debian.org> 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 supported anyway.
> 
> Yeah, I think we're at the point where we should just go ahead and do this.

Agreed, so I already did it in the last upload, 5.24.1~rc4-1 :)

Sorry for not following up on the discussion.

> > I think my only problem with this is that upstreaming it properly would
> > be somewhat difficult due to the incompatibilities noted here. I suppose
> > I shouldn't let that be a blocker. Dominic, any opinion?
> 
> > (Possibly a manual Configure option like -Dmanutf8, maybe even
> > enabled by default on Linux, would be acceptable upstream. No idea how
> > an automatic Configure probe for the UTF8 compatibility would work.)
> 
> The upstreaming part is really my fault, since I've been intending for
> ages to start a thread on pod-people and perl5-porters about the best
> approach in general but haven't gotten to it (or, more to the point,
> haven't made sure I had the resources to participate in the thread and act
> on the results).  This is definitely on my to-do list to do.

Thanks. I decided to just go ahead and worry about upstreaming later
to make sure we get fixed man pages in stretch. So it's now on my to-do
list as well, but I'm very happy if you get there first :)
-- 
Niko