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

Plural-Forms Croatian #596

Closed
milotype opened this issue Aug 3, 2019 · 5 comments
Closed

Plural-Forms Croatian #596

milotype opened this issue Aug 3, 2019 · 5 comments

Comments

@milotype
Copy link

milotype commented Aug 3, 2019

Could you please check the "code" for the croatian plural forms.
In the MacOS Poedit Version 2.2.3 (5738), when saving a po-file this is being writen in the file:

nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : 2);

But on http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html?id=l10n/pluralforms it is defined as:

nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);

As I understand it, it doesn't matter if hr or hr_HR, wright?

@vslavik
Copy link
Owner

vslavik commented Aug 4, 2019

Can you please provide specific example(s) of phrases where the current expression is wrong, showing the difference with explanation?

Poedit uses (much as like GNU gettext itself does, except that has some hardcoded legacy expressions like this one) CLDR data for the expressions. CLDR is generally a comprehensive and reliable source, but neither it nor TranslateHouse are infallible, and the difference may be something subtler that doesn't affect "%i something" expressions (although given the kind of difference of the expression, I doubt that's the explanation).

Serbian, Belarusian, Ukrainian and Russian appear to be in the same boat.

@milotype
Copy link
Author

milotype commented Aug 4, 2019

Well I don't know if it's wrong, because I don't know what (n%100<12 || n%100>14) or (n%100<10 || n%100>=20) do. And according to the specs it should be the second one.

I just noticed it, because someone updated one of my translations and ther where these differences. Please take a look at the file "man/hr.po", and you can see the difference at:
https://gitlab.com/inkscape/inkscape-docs/documentation/merge_requests/27/diffs#diff-content-7b9227c12d5822fa66961c34da2255d324c5d8cd
At the bottom of the page you'll see "This diff is collapsed. Click to expand it."
Then you can see the diffs.

@vslavik
Copy link
Owner

vslavik commented Aug 4, 2019

And according to the specs it should be the second one.

Sorry, what "specs"? You didn't link to any "spec", you linked to an unofficial reference document, which took this form from GNU gettext manual (not "spec" either). The closes thing to a "spec" for a language is precisely the CLDR dataset I am using.

The only thing that is specified here is the syntax of the plural forms field and the meaning of it. See the manual. The very reason why it exists is that a file can set the rules in itself.

If you think the default expression from Poedit is wrong, please back it up with some linguistic explanation. I can't just randomly change things if two mostly-reliable sources disagree, I need to understand which one is correct for the language.

@vslavik
Copy link
Owner

vslavik commented Aug 4, 2019

Actually, scratch that: the two expressions are equivalent. They evaluate to the same values and are just slightly different ways of writing the same thing (one by human, one generated).

@vslavik vslavik closed this as completed Aug 4, 2019
@milotype
Copy link
Author

milotype commented Aug 4, 2019

OK, if it doesn't matter I'm fine with that.
Maybe "spec" was the wrong word, sorry. I was refering to the two links I found on
https://poedit.net/trac/wiki/Doc/PluralForms

http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html?id=l10n/pluralforms
and
https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html

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