Colin Watson dixit: >Heh, you managed to find a case where it actually *was* a man-db bug >after all! I did say "almost never", I guess ...
Happens ;-) >This is triggered by your use of UTF-8 characters that aren't just >recoded versions of ISO-8859-1 characters in comments at the top of the >manual page. Ah, okay. >The Debian Policy Manual documents the current situation: > > Due to limitations in current implementations, all characters in the > manual page source should be representable in the usual legacy ^^^^^^^^^^^^^^^^^^ Interesting twist if this appears to comments as well. (But with your fix, I believe this won’t be necessary any more ☺) > encoding for that language, even if the file is actually encoded in > UTF-8. Safe alternative ways to write many characters outside that > range may be found in groff_char(7). >You can work around this bug by replacing those characters with some >plain ASCII, perhaps something like this: > >-.\" * ` generates b-.\" * ' generates b-.\" * - generates b+.\" * ` generates >U+2018 in groff, so use \` >+.\" * ' generates U+2019 in groff, \' generates B4, so use \*(aq >+.\" * - generates U+2010 in groff, \- generates U+2212, fixed in >tmac/mdoc/doc-groff I think your mail arrived here in a broken state. >After this fix, you still have a "warning: `aV' not defined", but that's >a genuine problem in your pages rather than in either groff or man-db. Interesting too. I will have to look at how GNU groff’s mdoc implementation defines the .Nx, .Ox &c. macros then. (MirBSD uses AT&T nroff (and offers GNU groff via ports) with the (a bugfixed) UCB mdoc implementation for both *roff processors, so that this issue has not appeared there yet.) Thanks for this quick fix and the coöperation! bye, //mirabilos -- [...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but what about xfs, and if only i had waited until reiser4 was ready... in the be- ginning, there was ffs, and in the middle, there was ffs, and at the end, there was still ffs, and the sys admins knew it was good. :) -- Ted Unangst über *fs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
