CLDR-17147 In dateTimePattern examples with short date, use abbreviated not full zone #3730
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
macchiati
previously approved these changes
May 17, 2024
pedberg-icu
force-pushed
the
CLDR-17147-fix-dateTimePattern-examples-with-short-date
branch
from
0043749 to
a962368
Compare
|
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
|
@macchiati Thanks, but needs re-stamp due to spotless format fixes. |
DraganBesevic
approved these changes
May 17, 2024
pedberg-icu
deleted the
CLDR-17147-fix-dateTimePattern-examples-with-short-date
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CLDR-17147
In the dateTimePattern examples that were originally added per CLDR-15622, change the examples that combine short date with full time to instead use long time (abbreviated zone) per Mark's review comment on the PR for that original ticket, PR #2977
(The ticket for this current PR is a clone of the original ticket specifically to address this issue)
ALLOW_MANY_COMMITS=true