Support for ngettext about jsxgettext HOT 7 CLOSED

We definitely should, I just don't have enough resources right now though :(

from jsxgettext.

Ah, cool. We could try help out on this if you like? We just need to know how you would like things to look from the user's perspective.

For example, there is currently a keyword option to look for a different symbol than 'gettext', but that'd need to change once we add ngettext and friends. We could either add a keyword option for each (which sounds a little weird I think), or instead change keyword to look up the object that the gettext methods were called on. So, for example, if keyword was _, we would look for _.gettext, ..., _.ngettext.

Let me know me what you think :)

from jsxgettext.

I'd say we should look for 'n' + keyword and 'd' + keyword when we add those. Also it looks like they'll need somewhat different parsing logic than the current gettext implementation so I think they should be in their respective functions.

from jsxgettext.

Hi, i'm not sure how much further you've got with adding this functionality, however i've implemented rudimentary support for ngettext this afternoon on my local project.

The solution I went with with regards to the keywords debate above was to follow the keyword spec syntax that xgettext itself uses. For example, this would specify a standard translation keyword of "tr" and a plural translation keyword of "trn":

['tr','trn:1,2']

Obviously this hasn't proceeded any further than the rudimentary support that I need but hopefully i've done it in such a way that makes the logic easy to extend for adding context support, etc.

I've pushed the changes into my fork at https://github.com/TeaSeaLancs/jsxgettext if you care to take a look :)

from jsxgettext.

So, gettext plurals doesn't work currently in jsxgettext?

from jsxgettext.

Yup, unfortunately :(

On Fri, Feb 20, 2015, 11:39 Serj Lavrin [email protected] wrote:

So, gettext plurals doesn't work currently in jsxgettext?

—
Reply to this email directly or view it on GitHub
#51 (comment).

from jsxgettext.

that's nice, thanks!

from jsxgettext.