Hi Marc,
Marc Espie wrote on Sun, Apr 04, 2010 at 04:34:53PM +0200:
> On Sat, Apr 03, 2010 at 02:40:23PM +0200, Ingo Schwarze wrote:
>> Nicholas Marriott wrote on Sat, Apr 03, 2010 at 08:10:47AM +0100:
>>> mandoc doesn't understand Spanish, it expects NAME not NOMBRE.
>>
>> In the long run, we might or might not consider adding proper support
>> for section names in national languages. For some sections, it makes
>> a difference because some macros behave differently in some sections.
Just to be clear, for the NAME section, it doesn't really make that
much of a difference right now whether it is recognised as such or not.
The only difference is that a bit more validation is done in
mdoc_validate.c, functions post_sh_head and post_sh_body for NAME
sections than for CUSTOM sections: It warns if NAME doesn't come
first or if it is lacking .Nm and/or .Nd, that's all.
There are other section/macro combinations that trigger special
behaviour, for example, .Nm and .Fd start on a new line in SYNOPSIS,
but not elsewhere, and .In gets an additional '#include' in
SYNOPSIS, but not elsewhere, to name two examples - and such examples
are ugly and fortunately rare.
NAME is not among those sections getting special treatment.
>> For now, just treating section names in national languages as custom
>> sections is probably the way to go (see the patch it sent out).
> I would tend to disagree. Please consider adding section names in national
> languages. makewhatis already does so, it's completely harmless.
>
> Formated.pm: if
> (m/^(?:NAME|NAMES|NAMN|NOMBRE|NOME|Name|\xbe|\xcc\xbe\xbe\xce|\xcc\xbe\xc1\xb0)\s*$/)
> {
>
> (the too last weird sequences correspond to namae in japanese common codings,
> SJIS and EUC if memory serves).
I'm not sure adding a hack like that is needed, at least not right now.
It changes very little.
Yours,
Ingo
