Shane F. Carr

I'd prefer to not include the month number because the error-state code path should be as minimal as possible; formatting "M01" is more complicated than "M" (even if only a...

Discussion with @zbraniecki: - MonthCode is available to the formatting function as a TinyStr so we can just echo it. Same with era code. `«M01»`, `«gregory»` - For numeric fields...

> > For numeric fields if the FixedDecimalFormatter is not loaded, load the FixedDecimalFormatter in no-data mode, but still indicate the error using brackets > > Why not use `Writeable...

Suffix suggestions: - `_invariant` - `_root` (wrong: we don't have CLDR root tailorings) - `_uax` (too restrictive: we want to add CLDR tailorings) - `_untailored` (wrong: LineBreakOptions has tailorings) -...

From discussion with @aethanyc @makotokato @Manishearth @nordzilla: It is an enhancement to consume CLDR root.xml tailorings, but not necessarily a bug. We would like to see it done in a...

Okay, for 2.0 purposes, which of the four segmenters requires a locale parameter? 1. Grapheme: Are there locale-specific CLDR tailorings for graphemes? 2. Word: It sounds like people want to...

Discuss with: - @eggrobin - @Manishearth - @hsivonen Optional: - @sffc - @markusicu - @zbraniecki

- @eggrobin - Currently we don't have a locale parameter in Segmenter APIs at all? - @sffc - Currently the complex break engine is used when complex script characters are...

The conclusions from the discussion of this issue with the CLDR design group: - Grapheme clusters should not be language-specific; baked into much low-level processing (e.g., Swift, font mappings) which...

I'm moving this back into 1.5 because the constructor can be drafted and bikeshed ahead of time, and then in 2.0 we can do the minimal change of making the...