On Sun, Apr 29, 2007 at 02:54:27PM +0200, David Philippi wrote: > msgid "Friendly unit sighted" > msgid_plural "$friends friendly units sighted" > > They'll have only a translation for the singular string to be > used in all cases. Now the problem is: the singular string doesn't have a > $friends and the number is lost. > There's a workaround for translators: declare english plural rules and use > the > same translation for both cases adding $friends in the second case and a 1 > for the first case depending on taste and custom. But I don't like to define > the plural variants wrong just to work around a limitation of Wesnoth. > Rewriting those strings would obviously mean to include the variable and thus > 1 in the singular case for untranslated usage.
It's much simpler: Such languages such declare 0 plural rules and adapt the singular msgstr to match both singular and plural strings. This should be really simple as singular and plural strings occur always together and not separated in the PO file. A proper translation of msgid "Friendly unit sighted" msgid_plural "$friends friendly units sighted" would that's why msgstr "$friends Friendly unit(s) sighted" It the task of the translator to create a proper message from the singular and plural pair and works this way really trivial. PS: This reminds me that the German strings are sometimes very different from the English ones. IIRC an explanation was that this is a workaround to avoid too long messages. The proper way is of course a fix in the framework (scrollable text, dynamic text sizes, ...). I don't know the current status but I doubt that the situation has changed Jens _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
