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.

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

Plurals in the tag-tanslation files supported? #45

Open
Hufkratzer opened this issue Sep 23, 2019 · 1 comment
Open

Plurals in the tag-tanslation files supported? #45

Hufkratzer opened this issue Sep 23, 2019 · 1 comment

Comments

@Hufkratzer
Copy link
Contributor

README.md explains that plurals can/should be defined with "!=1": like:

{
"tag:barrier": {
"message": "Barrière",
"!=1": "Barrières"
},
...

Is this still correct? Currently en.json doesn't contain any plural definitions, some plurals have been removed here by @Cybereric . Why have they been removed?

I think it would be useful to have them when needed. For example the routes categories contain a hard coded string "Routes". If we had defined

"tag:type=route": {
    "message": "Route",
    "!=1": "Routes"
}, ...

we could use it there. Also in filters plurals would make sense (e.g. "Hotels" instead of "Hotel").

How could plurals be retrieved by the translation functions, e.g. what to use instead of tagTrans('type', "route") to get "Routes" instead of "Route"?

@plepe
Copy link
Owner

plepe commented Sep 24, 2019

No, they are no longer supported. The Weblate application does not support this (at least in this format) and they were removed by it. I'm not too happy about this too. When I would add support for this, I would recover the already existing plurals from the Git history.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants