Translating plural forms

iNaturalist Next Discussion
1

This is a bit wonky and primarily for people who provide translations via Crowdin: we’re using Fluent syntax for translations in iNat Next, which is both more flexible for translators (good) and more complicated (bad). One of the complications is that translators need to know how to pluralize in Fluent syntax. For example, you might find something like this in the source:

{ $projectCount } { $projectCount ->
   [one]  project
  *[other] projects
}

but to support other plural forms, you would need to know that all of the following forms are available:

{ $projectCount } { $projectCount ->
   [zero] projects
   [one] project
   [two] projects
   [few] projects
   [many] projects
  *[other] projects
}

Would it help to include all of those forms in the source, even though most of them are unnecessary in most languages? I feel like that will result in fewer errors because translators don’t have to worry about the code, just the words, but it will result in unnecessary work because most translators won’t be aware that they only have to support the forms their language requires.

3

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.