Bug 244499 – app-portage/eclass-manpages should support UTF-8

• Product: Portage Development
• Status: RESOLVED FIXED

[Description Ulrich Müller 2008-10-26 18:44:38 UTC]

GLEP 31 says that UTF-8 should be used as character set in eclasses. However, app-portage/eclass-manpages doesn't support UTF-8 (which is mainly an issue for the @MAINTAINER block).

Setting severity to "enhancement" since I don't have a good idea how to achieve this without having support for UTF-8 input in groff.

(One solution would be to convert characters listed in groff_char(7) to their groff input names, e.g. "ü" -> "\[:u]" or "Ł" -> "\[/L]" but that looks very clumsy to me.)

[Comment 1 SpanKY 2008-10-26 20:22:36 UTC]

i dont see how eclass-manpages itself cares about the format at all.  this sounds like a man/groff problem which we already have bugs open for.

[Comment 2 Ulrich Müller 2008-10-30 14:58:05 UTC]

(In reply to comment #1)
> i dont see how eclass-manpages itself cares about the format at all.
> this sounds like a man/groff problem which we already have bugs open for.

I can find only bug 126361 (which isn't exactly "open") and a lot of duplicates. But you are right, the underlying problem is with groff, so let's hope that their upstream doesn't need another five years to fix it.

[Comment 3 SpanKY 2008-11-01 06:21:12 UTC]

you're right, but unless there's something that needs changing in eclass-manpages, i guess we can close this out ...

[Comment 4 Ulrich Müller 2011-02-08 08:36:06 UTC]

Could a coding tag be added to the man pages, so that preconv(1) will reliably recognise the encoding?

[Comment 5 Ulrich Müller 2011-02-08 08:37:02 UTC]

Created attachment 261795 [details, diff]
patch for files/eclass-to-manpage.awk

[Comment 6 SpanKY 2011-02-10 02:19:13 UTC]

feel free to commit that

[Comment 7 Ulrich Müller 2011-02-10 07:38:47 UTC]

Committed.