Make datetime styles (lengths) map to skeletons instead of patterns
The XML for datetime styles/lengths currently looks something like this:
Under the dateFormatLength element, I would like to propose changing `<pattern>` to `<skeleton>`. In this case, we would end up with something like,
The skeleton can then be mapped to the pattern using `<availableFormats>`, in this case with an exact match.
What are the next steps on this issue, given that the data submission deadline is rapidly approaching?
Who owns the next action item for this issue?
Need test that supplied skeleton generates the pattern from the exiusting availableFormats
Just add skeleton field …
That sounds like a good migration path. By adding a unit test that the skeleton produces the pattern, we can ensure that they are in sync in each release.
That would also go for those locales that don’t have any availableFormat data; we would add the 4 mappings from skeleton to pattern to ensure that they are in sync.
For the future, we can migrate to only collecting the availableFormat data, and eventually we could remove the stock pattern data.