-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for ngettext #51
Comments
We definitely should, I just don't have enough resources right now though :( |
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 Let me know me what you think :) |
I'd say we should look for |
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 :) |
So, gettext plurals doesn't work currently in jsxgettext? |
Yup, unfortunately :( On Fri, Feb 20, 2015, 11:39 Serj Lavrin notifications@github.com wrote:
|
that's nice, thanks! |
@BYK Was wondering if you have plans to support
ngettext
(and possiblydgettext
and its other friends)?The text was updated successfully, but these errors were encountered: