-
Notifications
You must be signed in to change notification settings - Fork 44
Plurals using "one" not parsed, only "=1", Localizely generated files don't work properly #31
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
Comments
The parsing would be in intl_translation, not this package. And it should understand "one", at least it's in the grammar. So there's probably something more complicated going on. Note that it's possible to add your own parsing if you need to work around issues or use a different format. See intl_translation_format. |
Here is the issue I created for Flutter repo: flutter/flutter#84291 |
Yes, but I don't think that's the same issue. See also #215 |
I'm not using intl_translation, I'm only using intl with the |
Closing in favor of #215 and/or the flutter issue. |
This has been an annoyance for one of my projects for over a year now, hope
it can get fixed soon. It's worth noting that a major third party
translation tool, Localizely, exports arb files that depend on this, and as
such I have to manually process each file I get back from it, every time we
update translations.
…On Wed, 16 Nov 2022 at 22:54, Moritz ***@***.***> wrote:
Closed dart-lang/i18n#31 <#31> as not planned.
—
Reply to this email directly, view it on GitHub
<#31>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATCQWAFPYKVZJNCPVQOODDWIT7SDANCNFSM5EAS7BXQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
So Localizely generates entries like this:
and if I use that with
intl
, then I get generated code like this:Note that it's missing the
one
field.On the other hand, if I use this format:
it works fine, generating this code:
It would be really nice if this package could understand this format. Right now I have to manually edit every arb file that Localizely creates, and that's really not scalable. Unless I'm mistaken, this format does seem to be part of the arb specification, so it should work - I assume this is a bug?
The text was updated successfully, but these errors were encountered: