Thank you, Michal. I will need to think a bit about this... Emre
Emre Akkaş Chief Technologist - Globalme US/CAN 1.855.438.5106 On Wed, Nov 25, 2015 at 5:02 AM, Michal Čihař <mic...@cihar.com> wrote: > Hi > > I'm afraid that using context will not scale as well, but will give > translators better chance to translate correctly (the gender doesn't > have to be same in all languages). > > You can see example here: > > https://github.com/phpmyadmin/phpmyadmin/blob/master/po/cs.po#L9354 > https://github.com/phpmyadmin/phpmyadmin/blob/master/po/cs.po#L9349 > https://github.com/phpmyadmin/phpmyadmin/blob/master/po/cs.po#L9336 > https://github.com/phpmyadmin/phpmyadmin/blob/master/po/cs.po#L9367 > https://github.com/phpmyadmin/phpmyadmin/blob/master/po/cs.po#L9371 > > The source strings is always same here ("New"), but is translated > differently based on gender of the thing it is about. > > -- > Michal Čihař | http://cihar.com | http://blog.cihar.com > > Dne 25.11.2015 v 08:45 Emre Akkas napsal(a): > > Hello Michal, > > > > Thanks for the response. To give you a bit of a background, the content > > is strings for unit tests. The source tsv contains strings ids and the > > text. We have been translating this file traditionally (CAT/TM etc.) and > > then adding the necessary gender variations etc. as additional columns > > in Excel (so the TM only contains the neutral form). Developers then > > consume this input and generate variations of the unit test files for > > different forms if additional columns exist. > > > > Obviously this format is very hard to manage and is not scalable. I > > would appreciate if you can elaborate on your suggestion of context. > > > > Thanks, > > Emre > > > > > > Emre Akkaş > > Chief Technologist - Globalme > > US/CAN 1.855.438.5106 > > > > > > > > On Tue, Nov 24, 2015 at 11:23 PM, Michal Čihař <mic...@cihar.com > > <mailto:mic...@cihar.com>> wrote: > > > > Hi > > > > Dne 25.11.2015 v 02:30 Emre Akkas napsal(a): > > > What is the best way of handling gender and formal/informal > variations > > > in Weblate. Could one use an approach similar to how plurals are > being > > > handled? Any pointers would be greatly appreciated > > > > There is currently no direct support for this. Also the only > translation > > format which handles this is IMHO Mozilla's l20n. However all it's > > features make it more a programming language than simple format for > > translations.... > > > > If you want to make something easy, you can use context for > > differentiating the variations. > > > > -- > > Michal Čihař | http://cihar.com | http://blog.cihar.com > > > > > > _______________________________________________ > > Weblate mailing list > > Weblate@lists.cihar.com <mailto:Weblate@lists.cihar.com> > > https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate > > > > > > > > _______________________________________________ > Weblate mailing list > Weblate@lists.cihar.com > https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate > >
_______________________________________________ Weblate mailing list Weblate@lists.cihar.com https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate
