Re: Full mandoc locale support committed.

[Kristaps Dzonsons <kristaps@bsd.lv>]

>> With this last commit, initial [full] locale support has been fitted
>> into mandoc!  Attached is eye-candy: a manual full of random Unicode
>> input (\[uNNNN]) first with -Tascii, then with -Tlocale.
>
> Unicode escapes work for me, but does that mean that existing localized
> manpages can't be used? Tried several ja and ru from debian 6, all of
> them make mandoc die with "FATAL: line scope broken, syntax violated"
> (-Tlint talks a lot about "ERROR: skipping bad character: ignoring
> byte").

Yuri,

Groff doesn't actually accept multi-byte input: it translates with 
preconv from the localised form to the Unicode escapes.  This is hidden 
away with the `-k' groff option.  See:

  http://manpages.ubuntu.com/manpages/lucid/man1/groff.1.html
  http://manpages.ubuntu.com/manpages/lucid/man1/preconv.1.html

(Why doesn't groff have its own manuals online instead of just the 
texinfo?  I bet it's cause grohtml doesn't look so good... ;))

We'll worry about doing preconv-style translation later.  For this 
release, the push is for the Unicode support itself.

>> The check-ins:
>>
>>     (1) http://mdocml.bsd.lv/archives/source/0920.html
>
> A small typo here in Makefile's comment - USE_CHAR.

Fixed---thanks.

> Checked on Solaris 11 and Illumos - both do not export the symbol,
> though commenting out #undef USE_WCHAR in term_ascii.c makes -Tlocale
> work.

Great news!  (The Internet agrees, as there are bug reports regarding 
Solaris and 10646.)  I'm still trying to figure out a good way to let 
the lack of this symbol be ignored when it's supported anyway (as in 
Solaris' case).  For the release itself, I'll probably let USE_WCHAR be 
authoritative and set or unset by downstream.

Thanks again,

Kristaps
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv