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.)
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.
(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.
you're right, but unless there's something that needs changing in eclass-manpages, i guess we can close this out ...
Could a coding tag be added to the man pages, so that preconv(1) will reliably recognise the encoding?
Created attachment 261795 [details, diff] patch for files/eclass-to-manpage.awk
feel free to commit that
Committed.
