On Friday 05 September 2014 09:16:48 André Somers wrote: > > This did not extract the string for translation. It needs to be something > > that does extract for translation and does translate to another language > > if a translator was loaded. > > I don't see how it properly could. Both strings would be specialized > anyway for the singular and plural case. The singular version probably > would not even have a placemarker for the number in it. How would that > work in the translation? You could still use a translatable string for > both alternatives, but I think that's completely missing the point. You > either do localization, or you don't. This really sounds like a weird > in-between, non-solution to me.
Fortunately for us, existing implementations have done this successfully for years and prove it's possible. https://techbase.kde.org/Development/Tutorials/Localization/i18n#Plurals -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
