Hi, Kristaps Dzonsons wrote on Thu, Jan 12, 2012 at 02:55:42PM +0100: > Stuart Henderson wrote:
>> The non-english manpages are broken, all the non-ascii characters get >> stripped when you view them. These should either be fixed or disabled. >> Check output in e.g. "man -m /usr/local/man/es scrotwm". >> >> You probably want to build them with nroff for now, as was done with >> the (commented-out) Russian manpage. Use -c on the nroff command line >> to avoid the nasty ESC sequences for coloured output which mess up >> the display in less(1). >> >> mandoc will warn you about manpage problems if you build with >> 'make WARNINGS=yes' (or add WARNINGS=yes to mk.conf). I would suggest >> that porters set this, it gives a good early indication when manpages >> need further investigation. Sure; however, most problems shown by 'WARNINGS=yes', which actually runs 'mandoc -Tlint', should be fixed upstream, and only a small fraction needs porter action. > Note that mandoc(1) actually can render Unicode escapes (\u[N]) with > -Tutf8 or -Tlocale (assuming you have a UTF-8 shell and the > appropriate LC stuff set): > > % cat >foo.1 <<! > .TH FOO 1 > .SH NAME > \[u041F]\[u0440]\[u0438]\[u0432]\[u0435]\[u0442]! > ! > % mandoc -Tlocale foo.1 > > However, scrotwm's manuals would need to be preprocessed to convert > UTF-8 (or whatever) into the Unicode escape form. There's an > upstream utility to do just that, > <http://mdocml.bsd.lv/preconv.1.html>. groff has a similarly-named > utility. mandoc's isn't in OpenBSD, however. > > In theory the functionality can be pulled directly into mandoc, but > I haven't do so to avoid bloat. Eventually, i think that should be included. > Plus, to date, nobody has complained to me about mandoc's locale > stuff, so it's not a priority to me. Well, it does come up now and then. I think right after unlock would be a good time to work on this. Yours, Ingo
