Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #11814

Re: a few unintended translations of command names

Show all headers | View raw

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().

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

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: a few unintended translations of command names Chet Ramey <chet.ramey@case.edu> - 2015-11-02 10:41 -0500

csiph-web