-
Notifications
You must be signed in to change notification settings - Fork 385
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
CLDR-17339 Fix problem in ChartDeltaDtds that was skipping keyboard3 #3536
Conversation
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.
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? |
I don't think there's any value to comparing to v44 here.
I don't think it's being called 2.0 now.
It's somewhat of the third revision, with 2.0 being CLDR-10926 (2018). |
&& VersionInfo.getInstance(current) | ||
.compareTo(VersionInfo.getInstance(firstVersion)) | ||
< 0) { |
There was a problem hiding this comment.
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
if (last != null | ||
&& (firstVersion == null | ||
|| VersionInfo.getInstance(last) | ||
.compareTo(VersionInfo.getInstance(firstVersion)) | ||
>= 0)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same
Ok then this should work
…On Tue, Feb 27, 2024, 16:28 Steven R. Loomis ***@***.***> wrote:
Question for you, @srl295 <https://github.com/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
<https://unicode-org.atlassian.net/browse/CLDR-10926> (2018).
—
Reply to this email directly, view it on GitHub
<#3536 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJLEMAI4UJAD3IOWAMH2ADYVZ23BAVCNFSM6AAAAABD5BR73OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRXHE3DIMJQHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
CLDR-17339
ALLOW_MANY_COMMITS=true