Here is an example (an empty one): http://2fd6db98ea.url-de-test.ws/
I missed "ngetexted" strings, because was not sure of "ngetext_th" syntax and even existence. Don't guarantee but suppose that all instances of "getext" replaced.
The .po project is 83% comleted and what is left belongs to admin pages.
When able I'll update github repository. And I'm almost ready to submit core translation for Russian lang for v 1.4.9.
Also I'm going to find a way of supporting translation with poedit given than gettext_th is used instead of gettext (think it should be simple).
As far as I can see on that site all is properly translated and is kept that way when I switch between English and Russian.
Syntax of ngettext() is explained here:
http://www.zenphoto.org/news/translating-tutorial#how-doeszenphotos-translation-work
It's the same for the theme/plugin based one, except the suffixes _pl/_th.
Setting up Poedit is quite easy, you just have to add the gettext_th/gettext_pl calls to the catalog settings under additionall keywords (not sure how it is named right now as my Poedit is in German). You cannot disable the normal gettext calls, only add additional ones if I understand right.
A Russian core translation will be very welcome. If you submit set the internal version to the next version (so in this case 1.4.10).
Glad that proper functioning is confirmed so far. Tested it different browsers - seems OK.
The source repository is updated, but I don’t generate a pull request because not sure. Maybe both “gettext” and “gettext_th” versions should exist separately. Anyway, the translation itself (.po, .mo) is almost valid now.
As for other points, info is quite timesaving. Now don’t have to guess, search.
[quote]Maybe both “gettext” and “gettext_th” versions should exist separately.
[/quote]
Not sure what you mean by that exactly. The core translation of course should not cover _pl/_th calls from a third party theme or plugin. Only official themes and plugins are and should be covered by a core translation.
I wanted to say that generally there are two ways of localizing site running zenphoto. The first and the default way is translating zp_core, with the third party theme path included into zenphoto.po project.
The plus managing all string in one place.
The disadvantage is that the admin will have to maintain modified project (quite extensive) with each zenphoto version upgrade.
The other way is to modify the theme so that it’s translation can be maintained separately through ”_th” functions and “themename.po” file.
The plus is that core upgrades come easy.
The disadvantage is that theme version upgrade becomes a bit complicated (if the author holds to using “gettext”).
The second way seems more preferable for me, but others may have their own reasons.