fluent-syntax-selectors

Fluent select expressions route translations by runtime values and CLDR plural rules, ensuring correct plural forms across locales. You create a select expression in FTL that chooses a translation variant based on a numeric count and includes a mandatory default variant for reliable fallbacks.

Cardinal plurals in Fluent handle standard counting quantities like one or many, while ordinal plurals handle positional forms like first or third. Both use CLDR rules to match numeric selectors, ensuring correct language-specific forms are selected for the appropriate context.

Nested selectors in Fluent allow modeling complex localization logic by placing select expressions inside other variants. This handles scenarios where multiple runtime values or CLDR categories simultaneously drive the final translation output across different languages.

Yes, Fluent FTL supports combining exact numeric matches and string selectors within the same select expression. This enables precise routing for language-aware translations by matching both specific numbers and arbitrary string values to dedicated variants.

Fluent enforces a single default variant to ensure reliable fallbacks across locales when no specific selector or CLDR category matches. This mandatory default prevents missing translation errors and guarantees language-aware output even without exact runtime value matches.

Term-attribute selectors in Fluent grammar use attributes from defined terms as the selector value within a select expression. This allows routing translations by dynamic attributes, integrating complex localization logic and CLDR rules directly into multi-language app definitions.