> > groff will use iconv as a simple preprocessor. I plan that in
> > future groff will understand only two input encodings: latin1 (for
> > backwards compatibility) and utf8.
>
> Sounds reasonable, but why groff is not in future yet, after more
> than 1 year? Why UTF-8 input was not provided in groff-1.19?
Just guess. Besides Gaius Mulley (how takes care of the grohtml
backend) it's only me who is working on groff, and I have *a lot*
other things to do.
> <rant>Will damn groff someday accept non-latin texts
> or each user have to make its own patch for it?
Some languages will *never* be supported, like Indic scripts.
> In 1.19 a hell of various tmac's is provided except some few which
> are needed for people who are so unhappy that use UTF-8 for
> non-latin scripts!
You are invited to contribute to groff -- take the file input.cpp and
make it 32bit clean.
> Of course, I can filter KOI8-R cyrillic via groff in 8bit mode, but
> such kind of solution is not acceptable for East Asian scripts and,
> in general, is not a right thing for i18n.
Support for East Asian scripts is far more complicated than just
providing a UTF-8 input interface.
Werner
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
