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-16998 Fix Formatting #3581

Merged
merged 2 commits into from
Mar 28, 2024

Conversation

macchiati
Copy link
Member

CLDR-16998

Took the suggestion to use monospacing in two of the suggested sections. The https://unicode.org/reports/tr35/#Key_And_Type_Definitions_ was more complicated, and would benefit less so that wasn't done.

  • This PR completes the ticket.

ALLOW_MANY_COMMITS=true

> replacement="und-alalc97">"
>
> result="ja-Latn-alalc97-fonipa" // note that CLDR canonical order of variants is alphabetical
> result="ja-Latn-alalc97-fonipa"
Copy link
Contributor

Choose a reason for hiding this comment

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

I thought source and result were also supposed to be enclosed?

Copy link
Member Author

Choose a reason for hiding this comment

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

I just changed the items that are fragments of XML syntax; that is more consistent with the rest of the document. Adding a note to the ticket.

@@ -3803,13 +3803,13 @@ A matching rule can be used to transform the source fields as follows

_Example:_

> source=ja-Latn-fonipa-hepburn-heploc
> source="ja-Latn-fonipa-hepburn-heploc"
Copy link
Contributor

Choose a reason for hiding this comment

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

I thought he was also asking for formatting around this line?

>
> replacement="und-alalc97">"
> result="ja-Latn-alalc97-fonipa"
Copy link
Contributor

Choose a reason for hiding this comment

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

and around this line?

Copy link
Member Author

Choose a reason for hiding this comment

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

I left the strings alone, and just changed the XML fragments (for more consistency with the rest of the document)

BTW, we definitely could use a scrub to fix the formatting overall, but that's a big-ticket item!

@macchiati macchiati merged commit 0053bd1 into unicode-org:main Mar 28, 2024
7 checks passed
@macchiati macchiati deleted the CLDR-16998-Fix-formatting branch March 28, 2024 20:58
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.

2 participants