I wrote (on hyphens): > I think this is fixed in upstream halibut[*] as of r8309. We're emitting > "-" rather than the "\-" you suggest; a little experimentation suggests > that we're doing the Right Thing, as the former tends to come out as > "U+002D HYPHEN-MINUS" (what we want) whereas the latter has minus-sign > semantics and tends to come out as "U+2212 MINUS SIGN".
(Although trying it on NetBSD in a UTF-8 locale for the sake of testing portability, I couldn't find a way to get it to emit a U+002D at all, not that that's your problem. Ugh, it's all horrible.) > rjk also writes: > > Also it uses curly quotes instead of the ascii apostrophe sign in the > > pterm -e example. > > This isn't yet fixed upstream. The options appear to be: > ' Current; "right quote" semantics so tends to generate > U+2019 RIGHT SINGLE QUOTATION MARK > \' "Acute accent" semantics so tends to generate > U+00B4 ACUTE ACCENT > \(aq "Apostrophe quote"; appears to generate what we want, > U+0027 APOSTROPHE > > I'm going to go for generating the latter, but I'm slightly nervous > because that named character is not in the "classical" troff reference, > <http://www.kohala.com/start/troff/cstr54.ps>, so I'm worried about its > portability. Opinions? This is now implemented upstream as of r8322, so upgrading the package to that version or later should be sufficient to fix this Debian bug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
