A Story of Intended Consequences and Plural Forms
summary
Shows that project fluent gains automatic ordinal/plural handling by storing formatting options on a Fluent number object and feeding them to Intl.PluralRules via ecma 402 behavior. Claims: English needs six plural categories once ordinals are counted. Tools: icu message format, project fluent, JavaScript Intl APIs. Built: a patchy-but-working Fluent runtime path that routes number-format options into plural selection. Result: it works because ecma 402 permits extra properties on the number format object.
AI-written summary · about
related talks
25mInternationalisation is a Piece of Cake
24mFluent 2: Designing Teams apps that seamlessly integrate experiences across
39mUsing PL Theory to Make People Happier
45mFluent Design: Designing for the Future
24mTypes as a Specification Language for Creativity
43mProgramming Languages for the Future of Design Computation
41mFrom morphemes to manuscripts: how linguistics can make you a better writer
44mInclusive Form Inputs
