[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: a few unintended translations of command names

From: Chet Ramey
Subject: Re: a few unintended translations of command names
Date: Mon, 2 Nov 2015 10:41:02 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0

On 10/19/15 3:07 PM, Benno Schulenberg wrote:
> Hi,
> In bash-4.4-beta the command names 'true' and 'false' have been
> mistakenly translated in the Greek, Italian, Slovak and Indonesian
> PO files.  The latter two also mistakenly translate 'times'.
> As the command synopses are gettextized only in order to allow
> translators to translate possible arguments, there is no need to
> gettextize them when a command takes no options nor arguments.

Well, the short docs are marked with N_ in the generated builtins.c,
but I guess the gettext tools aren't smart enough to not put them in
the pot files.

> Would it be possible to change the script that converts the *.def
> files into a builtins.c in such a way that when $BUILTIN == $SHORT_DOC
> the $SHORT_DOC is not gettextized?  It would prevent these mistranslations.
> (Or, if it's not possible to leave out the call to gettext, to add a hint
> instead: /* TRANSLATORS: This is a command name. Do not translate. */?)

That's a C program.  It might be better to just not run the short doc
through gettext in builtin_help().

``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]