-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Russ Allbery wrote: [...] > What I was trying to get at earlier is that I believe groff can't handle > UTF-8 input. So fixing B, if I'm correct, is certainly not local to > man-db. I believe that fixing groff to handle multibyte character sets > property is a substantial amount of work. I've heard rumors from time to > time that upstream intended to do this for 2.0, but the work is mostly > stalled.
The standard encoding for Japanese man pages is EUC-JP, which is multibyte; and poking around in my man directories, there are some man pages there which are correctly declared as UTF-8. (Take a look at /usr/share/man/it.UTF-8, for example.) So it's obviously possible. Whether there aren't any other horrible gotchas I couldn't say. Incidentally, all I originally wanted to do was just be able to spell upstream's name correctly, so I can live without it for the time being; but it would be nice to get this fixed. (BTW, I don't suppose anyone would be interested in sponsoring the package in question? ufiformat, a USB external drive floppy formatter, something which Debian doesn't appear able to do otherwise...) - -- ┌── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─── http://www.cowlark.com ─────────────────── │ │ "There does not now, nor will there ever, exist a programming language in │ which it is the least bit hard to write bad programs." --- Flon's Axiom -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGwD+vf9E0noFvlzgRAmMMAJ9hE6/p37rEXMqQc2XedFnyQkwoewCfZkZE AWQiNIjjfGVfOocrEPRR+5w= =4+29 -----END PGP SIGNATURE-----
