Issue
When importing/exporting translation files, the "other" form isn't appearing or being populated.
Answer
This issue most likely applies for Russian, Ukrainian, or Polish languages. This is because of CLDR software and GNU gettext standard differences.
The CLDR software standard contain 4 plural forms, while GNU Gettext supports three--the other form for floating point numbers is not included.
(If your gettext file contains the 4th plural form, it is because you have overridden the default gettext rules, since gettext allows custom languages with custom rules.)
In order to better support GNU gettext files, OneSky will only export 3 plural forms for these languages. We currently do not have plans to support custom languages, but it is something our product team will consider in the future.
Comments
4 comments
"If the other form isn’t appearing in your translations, it might be due to the language’s pluralization rules or the way the translation strings are set up. Have you checked if the correct ICU syntax or placeholders are used? Also, ensure that the project settings support multiple forms for the target language. If the issue persists, try refreshing the translation memory or reaching out to OneSky support for further assistance.
snow rider
Emergency Locksmith Royston "If the other form isn’t appearing in your translations, it might be due to the language’s pluralization rules or the way the translation strings are set up. Have you checked if the correct ICU syntax or placeholders are used? Also, ensure that the project settings support multiple forms for the target language. If the issue persists, try refreshing the translation memory or reaching out to OneSky support for further assistance.
Hello,
This is a clear and concise explanation of the issue with the "other" plural form in translation file imports/exports for Russian, Ukrainian, and Polish languages when using OneSky.
Here's a breakdown of why this is a good answer and some potential minor additions:
Strengths of the Answer:
Directly addresses the issue: It clearly states why the "other" form is missing.
Identifies the affected languages: It specifically names Russian, Ukrainian, and Polish.
Explains the root cause: It correctly points to the difference between CLDR and GNU gettext standards regarding plural forms.
Provides context about gettext customization: It acknowledges that users might have overridden default gettext rules.
States OneSky's current limitation: It clearly explains why OneSky only exports 3 plural forms for these languages. LowesKidsWorkshop
Offers insight into future considerations: It mentions that supporting custom languages is something the product team will consider.
Best Regards
The absence of the "other" plural form during translation file import/export, particularly for Russian, Ukrainian, or Polish, stems from a discrepancy between the CLDR software standard (4 plural forms) and the GNU gettext standard (3 plural forms). Gettext lacks the "other" form used for floating-point numbers. While custom gettext rules allowing a 4th form are possible, OneSky currently standardizes on the 3 gettext forms for these languages to ensure better compatibility. Support for custom language rules is a potential future consideration for their product team.
Please sign in to leave a comment.