CLDR-15113 json: move datetimeSkeleton to a parallel location

[srl295]

CLDR-15113

• This PR completes the ticket. (yet again!)

Change from the previous stopgap format in #1552 to:

"dateFormats": {
  "full": "EEEE, MMMM d, y",
  "long": "MMMM d, y",
  "medium": "MMM d, y",
  "short": "M/d/yy"
},
"datetimeSkeleton": {
  "full": "ahmmsszzzz",
  "long": "ahmmssz",
  "medium": "ahmmss",
  "short": "ahmm"
},

@macchiati this is slightly different than your proposal in #1552 (comment) - I made the object name datetimeSkeleton to match the actual element name in CLDR, and the structure would allow a timeSkeleton etc if such was needed.

[macchiati]

I was proposing

dateFormats: {...}
dateSkeletons: {...}

Which also leads to the corresponding:

timeFormats: {...}
timeSkeletons: {...}

It is a bit hard to see what your code is producing, so can you check to see that it matches the above?

[srl295]

@macchiati What I produce is in the head comment above, since datetimeSkeleton better matches the element name in XML. But I can change it to dateSkeletons exactly, will do.

[jira-pull-request-webhook]

Notice: the branch changed across the force-push!

• tools/cldr-code/src/main/resources/org/unicode/cldr/json/pathTransforms.txt is different

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

[srl295]

actually i missed the timeSkeletons before.

@macchiati as of 72536cc the output is now:

            "dateFormats": {
              "full": "EEEE, MMMM d, y",
              "long": "MMMM d, y",
              "medium": "MMM d, y",
              "short": "M/d/yy"
            },
            "dateSkeletons": {
              "full": "yMMMMEEEEd",
              "long": "yMMMMd",
              "medium": "yMMMd",
              "short": "yyMd"
            },
            "timeFormats": {
              "full": "h:mm:ss a zzzz",
              "long": "h:mm:ss a z",
              "medium": "h:mm:ss a",
              "short": "h:mm a"
            },
            "timeSkeletons": {
              "full": "ahmmsszzzz",
              "long": "ahmmssz",
              "medium": "ahmmss",
              "short": "ahmm"
            },

[srl295]

@macchiati this is the full diff for output files: (i skipped changing the version this time) unicode-org/cldr-json@a18f696

[macchiati]

Looks good now