> > Sounds complicated indeed. Why would you convert the man page
> > itself to UTF-8, when groff already has an option (-Tutf8) to
> > produce UTF-8 output?
>
> That's not the problem. The problem is it is *impossible* to know
> for sure what encoding is used in the source troff file; there is no
> charset=.... line.
The planned groff 2.0 will use the same syntax as Emacs to define the
input character set, i.e. the first line contains
-*- coding: foo -*-
in a comment. This info will then be forwarded to a preprocessor
which converts the man page to UTF-8.
> > I'd suggest:
> > - Assume the manpages are in traditional format.
>
> But what when utf-8 encoded pages will start to appear ?
As soon as groff supports UTF-8 as an input encoding.
Werner
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
- Re: multilingual man pages Tomohiro KUBOTA
- Re: multilingual man pages Pablo Saratxaga
- Re: multilingual man pages David Starner
- Re: multilingual man pages Bruno Haible
- Re: multilingual man pages Alexander Voropay
- Re: multilingual man pages Pablo Saratxaga
- Re: multilingual man pages Markus Kuhn
- Re: multilingual man pages Tomohiro KUBOTA
- Re: multilingual man pages David Starner
- Re: multilingual man pages David Starner
- Re: multilingual man pages Werner LEMBERG
- Re: multilingual man pages Werner LEMBERG
- Re: multilingual man pages Edmund GRIMLEY EVANS
- Re: multilingual man pages Markus Kuhn
- Re: multilingual man pages Bruno Haible
- Re: multilingual man pages Tomohiro KUBOTA
- Re: multilingual man pages Tomohiro KUBOTA
- Re: multilingual man pages Tomohiro KUBOTA
- Re: multilingual man pages Pablo Saratxaga
- Re: multilingual man pages Bruno Haible
- Re: multilingual man pages Werner LEMBERG
