Hi, I can do it. But I'm not that familiar with Pylons/Pyramid right now. So this will basically take some time. But, yes ;) Thomas Wichert Akkerman wrote:

On 05/17/2012 10:42 PM, Thomas Massmann wrote:

...

Hi,

I added the plural form support (see a corresponding ticket here: https://bugs.launchpad.net/zope.i18n/+bug/161985) in a separate branch: https://code.launchpad.net/~thomas-massmann/zope.i18n/plural. This code was mainly implemented during the 2012 Plonekonf in Munich.

It is already in "production" since 3 months in a project I'm developing right now. Please note that zope.i18nmessageid needs to be taken from this branch to work: https://code.launchpad.net/~thomas-massmann/zope.i18nmessageid/plural.

Extracting plural messages is supported by xgettext by default. Zope tools like i18nduder have to be adjusted (they don't support ungettext right now). I already adjusted lingua by Wichert Akkerman (https://github.com/tmassman/lingua) - the pull request is still open.

If I remember correctly that pull request is waiting for someone to add plural support to translationstring as well. Are you willing to implement that?

Wichert.

Ok, repo forked. I'll dig into it... ;) Thomas Wichert Akkerman wrote:

On 05/18/2012 10:07 AM, Thomas Massmann wrote:

...

Hi,

I can do it. But I'm not that familiar with Pylons/Pyramid right now. So this will basically take some time. But, yes ;)

translationstring is a very simple package that doesn't have any Pylons/Pyramid dependencies itself. It shouldn't be hard to do if you've already handled zope.i18n :)

Wichert.