[Top][All Lists]

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

Re: a few unintended translations of command names

From: Benno Schulenberg
Subject: Re: a few unintended translations of command names
Date: Mon, 02 Nov 2015 19:34:39 +0100

On Mon, Nov 2, 2015, at 16:41, Chet Ramey wrote:
> On 10/19/15 3:07 PM, Benno Schulenberg wrote:
> > 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.

??  But they *should* be in the POT file, at least most of them.
What I'm saying is:

> > 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?

When the BUILTIN string in a def file equals the SHORT_DOC string in
the def file, there is no need to gettextize that string, because
apparently the command does not take any argument.

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

Well, that would be suboptimal: the strings would still be in the
POT file, they just wouldn't get used.  The change I meant was as
in the attached patch (not adjusted for whitespace).


http://www.fastmail.com - mmm... Fastmail...

Attachment: 0001-don-t-mark-as-translatable-commands-that-take-no-arg.patch
Description: Text Data

reply via email to

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