On terça-feira, 8 de março de 2016 19:14:08 PST André Somers wrote:
> > When Nokia used Qt, we used to call this translating from "Engineering
> > English" to "proper English". In some projects, the source strings always
> > started with "!!", which helped identify what wasn't yet translated in
> >
Op 08/03/2016 om 20:08 schreef Jason H:
Sent: Tuesday, March 08, 2016 at 1:14 PM
From: "André Somers"
To: interest@qt-project.org
Subject: Re: [Interest] Translating plural with is/are
Op 08/03/2016 om 18:17 schreef Thiago Macieira:
On terça-feira, 8 de março de 2016 09
> Op 08/03/2016 om 18:17 schreef Thiago Macieira:
> > On terça-feira, 8 de março de 2016 09:06:14 PST Frédéric Marchal wrote:
> >> If for instance I write tr("%n whatever rubbish I type here", "",
> >> n) and the translator decides to translate "%n whatever rubbish I
> >> insert here" with "One m
> Sent: Tuesday, March 08, 2016 at 1:14 PM
> From: "André Somers"
> To: interest@qt-project.org
> Subject: Re: [Interest] Translating plural with is/are
>
>
>
> Op 08/03/2016 om 18:17 schreef Thiago Macieira:
> > On terça-feira, 8 de março de 2016 09:0
Op 08/03/2016 om 18:17 schreef Thiago Macieira:
On terça-feira, 8 de março de 2016 09:06:14 PST Frédéric Marchal wrote:
If for instance I write tr("%n whatever rubbish I type here", "", n)
and the translator decides to translate "%n whatever rubbish I insert
here" with "One message was saved"
On terça-feira, 8 de março de 2016 09:06:14 PST Frédéric Marchal wrote:
> If for instance I write tr("%n whatever rubbish I type here", "", n)
> and the translator decides to translate "%n whatever rubbish I insert
> here" with "One message was saved" for singular and "%n messages were
> saved" for
2016-03-07 20:16 GMT+01:00 Jason H :
>> > Ok I'm getting there, but how do I specify this string (a) or that string
>> > (b)?
>> > What's the qsTr() line look like?
>> > qsTr( ? )
>>
>> http://doc.qt.io/qt-5/i18n-plural-rules.html
>>
>> and
>>
>> http://doc.qt.io/qt-5/i18n-source-translation.html
Em segunda-feira, 7 de março de 2016, às 20:37:24 PST, Jason H escreveu:
> I now understand that is wrong, that it is just looking it up in a
> translation table, and that "(s)" does not specify the string alteration. I
> would assume then that the 3-parameter tr() call is what signifies that it
>
It is up to the person filling the
> translation file with translations (including the one for English) to
> make sure that both versions of the definitive string are provided in
> the .ts file.
>
> André
André and Thiago, thanks for clarifying that.
I figured there was some type of string
Op 07/03/2016 om 20:25 schreef André Somers:
Op 07/03/2016 om 19:56 schreef Jason H:
If you provide a translation file, the message with %n will be
translated
according to the language's plural rules. For English, you'll have two
translations for the same source message.
"At least one
Op 07/03/2016 om 19:56 schreef Jason H:
If you provide a translation file, the message with %n will be translated
according to the language's plural rules. For English, you'll have two
translations for the same source message.
"At least one upper case character is required" (a)
Em segunda-feira, 7 de março de 2016, às 20:16:48 PST, Jason H escreveu:
> Please provide the tr line as even after re-reading I don't think it (is/are
> selection) can be done, and please reference where the docs cover that
> syntax.
>
> To put it in s more documentation example way:
> Example:
Em segunda-feira, 7 de março de 2016, às 19:56:04 PST, Jason H escreveu:
> > If you provide a translation file, the message with %n will be translated
> > according to the language's plural rules. For English, you'll have two
> > translations for the same source message.
> >
> > "At least one
Il 07/03/2016 20:16, Jason H ha scritto:
I do not see how I can supply a plural and non-plural string, or a string that
works in both contexts and included is/are or was/were, respectively.
By then using lupdate to extract translations, linguist to provide them,
lrelease to compile them, and
> > Ok I'm getting there, but how do I specify this string (a) or that string
> > (b)?
> > What's the qsTr() line look like?
> > qsTr( ? )
>
> http://doc.qt.io/qt-5/i18n-plural-rules.html
>
> and
>
> http://doc.qt.io/qt-5/i18n-source-translation.html
>
> -> chapter Handling Plurals
Yeao, read
> Am 07.03.2016 um 19:56 schrieb Jason H :
>
>
>>
>> If you provide a translation file, the message with %n will be translated
>> according to the language's plural rules. For English, you'll have two
>> translations for the same source message.
>>
>>"At least one upper case character i
>
> If you provide a translation file, the message with %n will be translated
> according to the language's plural rules. For English, you'll have two
> translations for the same source message.
>
> "At least one upper case character is required" (a)
> "At least %n upper case chara
Em segunda-feira, 7 de março de 2016, às 18:44:17 PST, Jason H escreveu:
> > Sent: Monday, March 07, 2016 at 12:38 PM
> > From: "Thiago Macieira"
> > To: interest@qt-project.org
> > Subject: Re: [Interest] Translating plural with is/are
> >
> > Em
> >
> > Supply a translation file for en_US.
>
> I'm not sure I follow. I don't see anything that allows me to tell it to
> select one for singular or the other? I think I'm missing something?
I'd like to **NOT** have a redundant pluralisation check, which might not
match the language's plura
> Sent: Monday, March 07, 2016 at 12:38 PM
> From: "Thiago Macieira"
> To: interest@qt-project.org
> Subject: Re: [Interest] Translating plural with is/are
>
> Em segunda-feira, 7 de março de 2016, às 18:23:20 PST, Jason H escreveu:
> > While Qt handles certa
Em segunda-feira, 7 de março de 2016, às 18:23:20 PST, Jason H escreveu:
> While Qt handles certain phrases like:
> "Use %n upper case character(s)"
>
> adequately, if phrased slightly differently:
>
> "At least %n upper case character(s) is required"
> breaks because the translation is:
> 1. "At
While Qt handles certain phrases like:
"Use %n upper case character(s)"
adequately, if phrased slightly differently:
"At least %n upper case character(s) is required"
breaks because the translation is:
1. "At least 1 upper case character is required"
2a. "At least 2 upper case characters is requ
22 matches
Mail list logo
