Re: Translation of numeric values (application gnome-schedule)



Hello guys,

De: "Christian Rose" <menthos gnome org>
> Then I suggest you expand the sentence fragments a bit so that you don't
> just mark "3rd" and so on for translation. I.e.:
>
>         /* Translators: This gets put into the "Run this application..."
>            sentence. */
>         N_("every first minute")
>         /* Translators: This gets put into the "Run this application..."
>            sentence. */
>         N_("every second minute")
>         /* Translators: This gets put into the "Run this application..."
>            sentence. */
>         N_("every third minute")
>
>         ...
>
>         /* Translators: This gets put into the "Run this application..."
>            sentence. */
>         N_("every first hour")
>         /* Translators: This gets put into the "Run this application..."
>            sentence. */
>         N_("every second hour")
>
>         ...
>
>         /* Translators: This gets put into the "Run this application..."
>            sentence. */
>         N_("every first day of the month")
>         /* Translators: This gets put into the "Run this application..."
>            sentence. */
>         N_("every second day of the month")
>
>         ...
>
>         /* Translators: In this sentence, the strings inserted are the
time
>            strings translated elsewhere. It's one of the minute strings,
one
>            of the hour strings, and one of the month day strings, in this
order.
>            Example: "Run this application every second minute every third
hour
>                      every 20th day of the month."
>            If you need to reorder the arguments to suit your language, you
can
>            do it with the printf parameter reordering syntax.
>            Example: "Run this application %2$s %1$s %3$s."
>            In this example, the hour string will be placed before the
minute
>            string.
>         */
>         _("Run this application %s %s %s.",
>            _(minutestring), _(hourstring), _(monthdaystring))
>
> Note the translator comments²: They're absolutely essential here so that
> the translator will know how the sentence fragments are used.
>
> Also note that in almost all cases it's better to expand to full
> sentences marked for translation instead of doing something like this,
> even if it means many more strings marked for translation -- this is
> just an exception because otherwise the total number of strings would
> grow absurdly in this case, since the number of possible combinations is
> so huge.

Now I'm speaking as a translator.

I liked Christian's suggestion, and I prefer to have to translate the same
words hundreds of times (using Ctrl+C, Ctrl+V, of course) than having to do
malabarisms to translate or even don't translate.

I read Philip's reply for Christian's message and I know what he wants to do
as a possibly temporary solution. If he preferred to write the same phrases
hundreds of times with just a slight difference between them it would be
better for translating on most languages (I think).

The way the POT file is now in CVS, in this case, doesn't cause problems for
Portuguese translations. But I know it does cause for other languages, so I
don't matter having to spend more time translating to Brazilian Portuguese
if the modifications which caused it will make translation for other
languages possible.

I also prefer to translate by editing just a PO file than having to edit a
Python program too.

Raphael Higino



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