Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@pedberg-icu
Copy link
Contributor

@pedberg-icu pedberg-icu commented Feb 11, 2021

Checklist

In fa, which has a bunch of ASCII <LRM> which were probably intended to be actual \u200E characters:

  • If the <LRM> immediately precedes a strong L character (ASCII letter or µ), then just remove it, it would have zero effect if converted to \u200E
  • In the other cases, convert the <LRM> to an actual \u200E character. Most of these are before a / in a per pattern, which makes sense. Two of them precede a space which is followed by a strong L character; these are probably mistakes but they would have an effect in a R-L context so I did convert them.

In ko, there was one bogus < in Japanese era name, removed it.

I will split off a separate ticket to add tests for a future Survey Tool phase.

@pedberg-icu pedberg-icu changed the title CLDR-14477 fa, remove explicit <LRM> or replace with \u200E; ko, remove a bogus > CLDR-14477 fa, remove explicit <LRM> or replace with \u200E; ko, remove a bogus < Feb 11, 2021
@AEApple
Copy link
Contributor

AEApple commented Feb 11, 2021

Isn't this actually ticket CLDR-14476?

@FrankYFTang
Copy link
Contributor

Peter, this should be 14476 not 14477

@FrankYFTang
Copy link
Contributor

Copy link
Contributor

@FrankYFTang FrankYFTang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gee.. it is hard to review invisible characters but I made it.
Please change the commit subject to CLDR-14476

Copy link
Member

@macchiati macchiati left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only issue is the ticket number.

@pedberg-icu pedberg-icu force-pushed the CLDR-14476-fa-fix-explicit-ASCII-LRMs branch from 04ad398 to 726d195 Compare February 11, 2021 02:18
@jira-pull-request-webhook
Copy link

Hooray! The files in the branch are the same across the force-push. 😃

~ Your Friendly Jira-GitHub PR Checker Bot

@pedberg-icu pedberg-icu changed the title CLDR-14477 fa, remove explicit <LRM> or replace with \u200E; ko, remove a bogus < CLDR-14476 fa, remove explicit <LRM> or replace with \u200E; ko, remove a bogus < Feb 11, 2021
@pedberg-icu
Copy link
Contributor Author

gee.. it is hard to review invisible characters but I made it.
Please change the commit subject to CLDR-14476

Thanks, I fixed the commit message, and also the ticket ID in this PR, please re-approve

@macchiati
Copy link
Member

gee.. it is hard to review invisible characters but I made it.

I filed a ticket for that: https://unicode-org.atlassian.net/browse/CLDR-14496?filter=10033

@pedberg-icu pedberg-icu merged commit 21386c2 into unicode-org:master Feb 11, 2021
@pedberg-icu pedberg-icu deleted the CLDR-14476-fa-fix-explicit-ASCII-LRMs branch February 11, 2021 02:49
jefgen added a commit to microsoft/icu that referenced this pull request Mar 5, 2021
…00E; ko, remove a bogus &lt

This change cherry-picks fixes from the upstream CLDR repo to fix data
issues in the fa and ko locales. The CLDR-MS was regenerated after
picking up the fix. This change is the update to the MS-ICU data
files from the updated data.

Upstream PR:
unicode-org/cldr#1025

Upstream tickets:
https://unicode-org.atlassian.net/browse/CLDR-14476
https://unicode-org.atlassian.net/browse/ICU-21485
jefgen added a commit to microsoft/icu that referenced this pull request Mar 5, 2021
…00E; ko, remove a bogus &lt

This change cherry-picks fixes from the upstream CLDR repo to fix data
issues in the fa and ko locales. The CLDR-MS was regenerated after
picking up the fix. This change is the update to the MS-ICU data
files from the updated data.

Upstream PR:
unicode-org/cldr#1025

Upstream tickets:
https://unicode-org.atlassian.net/browse/CLDR-14476
https://unicode-org.atlassian.net/browse/ICU-21485
jefgen added a commit to microsoft/icu that referenced this pull request Mar 5, 2021
…00E; ko, remove a bogus &lt (#71)

This change cherry-picks fixes from the upstream CLDR repo to fix data
issues in the fa and ko locales. The CLDR-MS was regenerated after
picking up the fix. This change is the update to the MS-ICU data
files from the updated data.

Upstream PR:
unicode-org/cldr#1025

Upstream tickets:
https://unicode-org.atlassian.net/browse/CLDR-14476
https://unicode-org.atlassian.net/browse/ICU-21485
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants