[Development] [Interest] Direct-lookup translation, even for English (was Re: get english translation)

[Saether Jan-Arve]

I'm not sure I understand. English does not have paucal (but polish have :), so you would only need singular and plural for such an API. If this is the case, it would be limited to languages that have the same plural rules as English.

We could do that, but I don't see the problem in providing the translation file. Shawn already mentioned many good reasons for why translating the "engineering English" to "end user English" (whatever that is) is a good thing.
(Note - you don't need to provide translations for everything)

Jan Arve



> -----Original Message-----
> From: Kobus Jaroslaw
> Sent: 3. september 2014 08:25
> To: Saether Jan-Arve; Rutledge Shawn; Thiago Macieira
> Cc: development at qt-project.org
> Subject: RE: [Development] [Interest] Direct-lookup translation, even 
> for English (was Re: get english translation)
>> Actually, some of the i18n features of Qt _requires_ you to provide an
>> English translation. This is the case for the plural forms, where the
>> engineer typically
> writes.
> 
>> tr("Found %n item(s)", 0, m_numberOfItemsFound);
>> 
>> And Qt will pick the singular/plural translation (that came from the
>> translation file)  depending on the value of m_numberOfItemsFound.
> 
> Can't we just provide some tr() overload, in which you could also
> specify plural and paucal forms in source code, next to the number? E.g.
> 
> tr("Found %n item" /*singular*/, "Found %n items" /*paucal*/, "Found
> %n items" /*plural*/, m_numberOfItemsFound);
> 
> In this way the English in the source code could be good enough.
> 
> Jarek