Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Pluralizer ignores the domain of a TranslationString that is passed in #31

Open
ztane opened this issue Jun 8, 2016 · 0 comments
Open

Pluralizer ignores the domain of a TranslationString that is passed in #31

ztane opened this issue Jun 8, 2016 · 0 comments

Comments

@ztane
Copy link

ztane commented Jun 8, 2016

Pluralizer ignores by default the domain of TranslationString that is passed in, whereas Translator doesn't. This is rather silly, since if a TranslationString is passed in to Pluralizer instead of a str/unicode, it is exactly because a TranslationString knows its domain.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ztane