Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLDR-17925 da, update to use “ Hg #4369

Merged
merged 1 commit into from
Feb 12, 2025
Merged

Conversation

cgaarden
Copy link
Contributor

CLDR-17925

  • This PR completes the ticket.

ALLOW_MANY_COMMITS=true

@cgaarden cgaarden changed the title Fix for CLDR-17925 - update to use “ Hg CLDR-17925 - update to use “ Hg Feb 12, 2025
@AEApple AEApple requested a review from a team February 12, 2025 18:05
@pedberg-icu pedberg-icu changed the title CLDR-17925 - update to use “ Hg CLDR-17925 da, update to use “ Hg Feb 12, 2025
@pedberg-icu pedberg-icu force-pushed the cgaarden-patch-CLDR-17925 branch from cde526b to 1d420a3 Compare February 12, 2025 18:15
@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 self-requested a review February 12, 2025 18:17
@pedberg-icu pedberg-icu merged commit 51eb1ff into main Feb 12, 2025
13 checks passed
@stenshamn
Copy link
Contributor

You used the wrong character. You used “, but should have used ″ (double-prime, U+2033)

@pedberg-icu
Copy link
Contributor

pedberg-icu commented Feb 12, 2025

You used the wrong character. You used “, but should have used ″ (double-prime, U+2033)

@stenshamn Thanks for catching this! I did not review carefully enough. I made another PR to fix this: #4372

@AEApple AEApple deleted the cgaarden-patch-CLDR-17925 branch February 13, 2025 17:48
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