Just because it's so sadly hilarious, i have to add this gem: Ingo Schwarze wrote on Fri, Oct 24, 2014 at 05:57:40PM +0200:
> And even if stunnel(8) exclusively targets groff, it's not > up to the job: > > $ pod2man -u stunnel.pod | preconv -eutf8 | groff -mandoc -Tps \ > > stunnel.ps > <standard input>:85: warning: can't find special character `u00A0' > > ... and the resulting PostScript file has "-fdN" without a blank > in the SYNOPSIS line. > > $ pod2man -u stunnel.pod | preconv -eutf8 | groff -mandoc -Tascii > $ pod2man -u stunnel.pod | preconv -eutf8 | groff -mandoc -Tlatin1 > > don't give you the blank, either, even though it's seemingly easy > enough to translate a blank to ASCII. You think at least UTF-8 will work out of the box? No way: $ pod2man -u stunnel.pod | groff -mandoc -Tutf8 gives you gibberish. Try looking at it with uxterm(1), $ export LC_CTYPE=en_US.UTF-8 and less(1) -R. You have to jump through hoops to handle what the stunnel(8) people are doing even if you *do* want UTF-8 output. Here is what you have to do: $ pod2man -u stunnel.pod | preconv -eutf8 | mandoc -Tutf8 | less $ pod2man -u stunnel.pod | preconv -eutf8 | groff -mandoc -Tutf8 | less -R $ pod2man -u stunnel.pod | preconv -eutf8 | groff -mandoc -Tutf8 -P -c | less Anybody still claims the stunnel(8) manual is *not* broken? Yours, Ingo
