Przemyslaw Czerpak wrote:
Yes, it is. I also think about it. The same problem I have when I want to use Polish as base language. I'm thinking about adding our own extension for it, sth like: hb_gettext( { <cForm1> [, <cFormN>] } [, <cContext>], <nCount> ) or: hb_ngettext( <nCount>, { <cForm1> [, <cFormN>] } [, <cContext>] ) So it will be possible to use also non English languages as base. In such case programmer will have to set plural index rule at application startup. The default one will be: iif( n == 1, 1, 2 ) If there is translation with corresponding plural index but at least one exists then we can use the 1-st one. In such case it will not be necessary to repeat the same translations when the translated one has only one form in given language. In .pot file we may store base strings as: msgid "single form" msgid_plural "plural form 1" msgid_plural2 "plural form 2" so as long as someone will use only two forms it will be gettext compatible. msgid will be still main hash index and msgid_plural* will be used only as optional results when nCount is given and and index created from nCount has corresponding msgid_plural* entry.What do you think about it?
Hi, that would be great! GNU gettext developers should hear you. Regards, Mindaugas _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
