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-16943 kbd: Normalization #3285

Merged
merged 7 commits into from
Oct 4, 2023

Conversation

srl295
Copy link
Member

@srl295 srl295 commented Sep 27, 2023

  • remove , add
  • dtd and spec update

Co-authored-by: Marc Durdin [email protected]

CLDR-16943

  • This PR completes the ticket.

ALLOW_MANY_COMMITS=true

- remove <info normalization>, add <settings normalization>
- dtd and spec update

Co-authored-by: Marc Durdin <[email protected]>
@srl295 srl295 requested a review from mcdurdin September 27, 2023 00:21
@srl295 srl295 self-assigned this Sep 27, 2023
@srl295 srl295 requested review from miloush and a team September 27, 2023 00:21
@@ -596,7 +585,7 @@ An element used to keep track of layout specific settings. This element may or m
**Syntax**

```xml
<settings [fallback="omit"] [transformFailure="omit"] [transformPartial="hide"] />
<settings fallback="omit" normalization="mixed" />
Copy link
Contributor

Choose a reason for hiding this comment

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

The brackets were denoting an optional attribute. You kept them above in the info element, it should be unified.

> The implementation will apply normalization as appropriate when matching transform rules and `<display>` value matching.
> Output from the keyboard, following application of all transform rules, will be normalized to implementation or application-requested form.
>
> However, it is recognized that there may be some keyboards which, for compatibility or legacy reasons, need to manage their own normalization. The implementation in that case will do no normalization at all. The keyboard author must make use of transforms in the keyboard to any required normalization.
Copy link
Contributor

Choose a reason for hiding this comment

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

This needs to specify that normalization="mixed" is the attribute to enable this mode.

Perhaps it should be normalization="disabled" -- that seems clearer given the description

Copy link
Member Author

Choose a reason for hiding this comment

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

that makes some sense

@srl295 srl295 requested review from miloush, mcdurdin and a team October 3, 2023 15:53
@srl295 srl295 merged commit a315290 into unicode-org:main Oct 4, 2023
5 checks passed
@srl295 srl295 deleted the cldr-16943/kbd/normalization branch October 4, 2023 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants