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-17339 Fix problem in ChartDeltaDtds that was skipping keyboard3 #3536

Merged

Conversation

macchiati
Copy link
Member

CLDR-17339

  • This PR completes the ticket.

ALLOW_MANY_COMMITS=true

@macchiati macchiati requested a review from srl295 February 28, 2024 00:15
@macchiati
Copy link
Member Author

Question for you, @srl295 . There was a keyboard3 in v44. The change here fixes a bug, but also only goes back to v45 (eg no comparison to v44). That's ok if we want to forget about the v44 dtd.

If we want to retain the comparison we would change the following to have 44.

    keyboard3("keyboards/dtd/ldmlKeyboard3.dtd", "45.0", null, "../keyboards/3.0"),
    keyboardTest3("keyboards/dtd/ldmlKeyboardTest3.dtd", "45.0", null, "../keyboards/test");

Second question is: we are sometimes calling this Keyboard 2.0 (since it is a breaking change), but we have keyboard3. Should we publicly call it Keyboard 3.0?

@srl295
Copy link
Member

srl295 commented Feb 28, 2024

Question for you, @srl295 . There was a keyboard3 in v44. The change here fixes a bug, but also only goes back to v45 (eg no comparison to v44). That's ok if we want to forget about the v44 dtd.

I don't think there's any value to comparing to v44 here.

If we want to retain the comparison we would change the following to have 44.

    keyboard3("keyboards/dtd/ldmlKeyboard3.dtd", "45.0", null, "../keyboards/3.0"),
    keyboardTest3("keyboards/dtd/ldmlKeyboardTest3.dtd", "45.0", null, "../keyboards/test");

Second question is: we are sometimes calling this Keyboard 2.0 (since it is a breaking change),

I don't think it's being called 2.0 now.

but we have keyboard3. Should we publicly call it Keyboard 3.0?

It's somewhat of the third revision, with 2.0 being CLDR-10926 (2018).

Comment on lines +155 to +157
&& VersionInfo.getInstance(current)
.compareTo(VersionInfo.getInstance(firstVersion))
< 0) {
Copy link
Member

Choose a reason for hiding this comment

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

good catch, needed to be a version compare not a lexical compare

Comment on lines +179 to +183
if (last != null
&& (firstVersion == null
|| VersionInfo.getInstance(last)
.compareTo(VersionInfo.getInstance(firstVersion))
>= 0)) {
Copy link
Member

Choose a reason for hiding this comment

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

same

@macchiati
Copy link
Member Author

macchiati commented Feb 28, 2024 via email

@macchiati macchiati merged commit c1c3887 into unicode-org:main Feb 28, 2024
10 checks passed
@macchiati macchiati deleted the CLDR-17339-Update-charts-for-BRS-(2) branch February 28, 2024 00:32
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