On Wed, 2015-04-29 at 23:30 +0200, Gert Doering wrote: > Hi, > > On Wed, Apr 29, 2015 at 08:33:02PM -0000, David Woodhouse wrote: > > > That would mean we either go into autoconf territory to test for groff > > > run-time behaviour, or we use a particular unique sequence and do our > > > own post-processing. > > > > The latter is baaically the approach I took in > > http://git.infradead.org/users/dwmw2/openconnect.git/commitdiff/5f51c83f2 > > So you put "−" in the .8 file, which is converted to "-" for > HTML - but what happens for "man openconnect"? Will groff understand > "−" and output a "proper U+002D HYPHEN-MINUS"? (Not that it's > particular fun to edit such .8 files then...)
No, in the .8 file I left it as \- I then seem to get the desired U+002D output from man(1) in the terminal, and the patch referenced above is fixing up the − which we get in XHTML output, for the web rendition which is used at http://www.infradead.org/openconnect/manual.html Quite why we don't get U+2212 MINUS SIGN in the terminal output too, I don't know. That's just groff being inconsistent. > (There's a famous saying about "it would be much easier to teach them > all English" when it comes to internationalization, charsets, and all > that pain...) Seems rather naïve to assume that sticking solely to English would allow us to stick to ASCII. ∃ lots of reasons to use non-ASCII characters, even when you're sticking to English. ☺ -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
