CLDR-19756 Use latest (Jul 23) version of ICU4J - #6093
Conversation
|
What is triggering the error? I am not familiar with what triggers a "Error: Process completed with exit code 1." I didn't see any more specific errors? |
I am not sure either. @srl295 , any ideas what could cause this? |
It's in the error logs. Yet again more static initialization !!!!!!!!!!!!!!!!!!! Prohibits us from seeing the error in a reasonable context. FYI @eggrobin
|
|
FYI @eggrobin
Caused by: java.lang.IllegalArgumentException: Unescaped
Pattern_White_Space in UnicodeSet string literals is prohibited until ICU
81. Escape U+000A. [©®‼⁉™ℹ↔-↙↩↪⌚⌛⌨⏏⏩-⏳⏸-⏺ Ⓜ▪▫▶◀◻-◾☀-☄☎☑☔☕☘☝☠☢☣☦
☪☮☯☸-☺♈-♓♠♣♥♦♨♻♿⚒-⚔⚖⚗ ⚙⚛⚜⚠⚡⚪⚫⚰⚱⚽⚾⛄⛅⛈⛎⛏⛑⛓⛔⛩⛪ ⛰-⛵⛷-⛺⛽✂✅✈-✍✏✒✔✖✝✡✨✳✴
Where is the full UnicodeSet expression? I don’t see a UnicodeSet string
literal here (there would be some {}).
Interesting that CLDR uses string literals with ignored spaces…
|
|
Ah, this monster of a UnicodeSet, whose line-wrapping breaks families! cldr/common/supplemental/attributeValueValidity.xml Lines 122 to 128 in 3d70c0b |
|
So break the lines outside of the {} and all will be well, and as a bonus those couples and families will be reunified and marginally more legible. Also remove stray spaces that keep 👩 ❤👩 and others apart. |
Where in the error logs? I searched for it and didn't see it?
Okay, but the error is not formatted like the others. Is it possible to have it formatted the same? 
Usually it is formatted as "Error:" in bright red. |
|
Robin, while we can take care of this in cldr, is this a client
incompatibly that we are comfortable in ICU?
…On Fri, Aug 28, 2026, 20:05 Annemarie Apple ***@***.***> wrote:
*AEApple* left a comment (unicode-org/cldr#6093)
<#6093 (comment)>
What is triggering the error? I am not familiar with what triggers a
"Error: Process completed with exit code 1." I didn't see any more specific
errors?
I am not sure either. @srl295 <https://github.com/srl295> , any ideas
what could cause this?
It's in the error logs.
Yet again more static initialization !!!!!!!!!!!!!!!!!!! Prohibits us from
seeing the error in a reasonable context.
FYI @eggrobin <https://github.com/eggrobin>
Caused by: java.lang.IllegalArgumentException: Unescaped
Pattern_White_Space in UnicodeSet string literals is prohibited until ICU
81. Escape U+000A. [©®‼⁉™ℹ↔-↙↩↪⌚⌛⌨⏏⏩-⏳⏸-⏺ Ⓜ▪▫▶◀◻-◾☀-☄☎☑☔☕☘☝☠☢☣☦
☪☮☯☸-☺♈-♓♠♣♥♦♨♻♿⚒-⚔⚖⚗ ⚙⚛⚜⚠⚡⚪⚫⚰⚱⚽⚾⛄⛅⛈⛎⛏⛑⛓⛔⛩⛪ ⛰-⛵⛷-⛺⛽✂✅✈-✍✏✒✔✖✝✡✨✳✴
Where in the error logs? I searched for it and didn't see it?
What is triggering the error? I am not familiar with what triggers a
"Error: Process completed with exit code 1." I didn't see any more specific
errors?
I am not sure either. @srl295 <https://github.com/srl295> , any ideas
what could cause this?
It's in the error logs.
Yet again more static initialization !!!!!!!!!!!!!!!!!!! Prohibits us from
seeing the error in a reasonable context.
FYI @eggrobin <https://github.com/eggrobin>
Caused by: java.lang.IllegalArgumentException: Unescaped
Pattern_White_Space in UnicodeSet string literals is prohibited until ICU
81. Escape U+000A. [©®‼⁉™ℹ↔-↙↩↪⌚⌛⌨⏏⏩-⏳⏸-⏺ Ⓜ▪▫▶◀◻-◾☀-☄☎☑☔☕☘☝☠☢☣☦
☪☮☯☸-☺♈-♓♠♣♥♦♨♻♿⚒-⚔⚖⚗ ⚙⚛⚜⚠⚡⚪⚫⚰⚱⚽⚾⛄⛅⛈⛎⛏⛑⛓⛔⛩⛪ ⛰-⛵⛷-⛺⛽✂✅✈-✍✏✒✔✖✝✡✨✳✴
Okay, but the error is not formatted like the others. Is it possible to
have it formatted the same?
Image: Screenshot 2026-08-28 at 8 03 12 PM (view on web)
<https://github.com/user-attachments/assets/fb817274-975a-47e7-b7d5-6f17fd1f7331>
Usually it is formatted as "Error:" in bright red.
—
Reply to this email directly, view it on GitHub
<#6093?email_source=notifications&email_token=ACJLEMDIR4SVGUTDLYE6LOD5MJB7PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBVHE4TIOBUGM3KM4TFMFZW63VQOJSXM2LFO5PXEZLROVSXG5DFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5459948436>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJLEMCUKJTSRJDKL3YVPGT5MJB7PAVCNFSNUABFKJSXA33TNF2G64TZHMYTAMZZGQ4DMNZSHNEXG43VMU5TKMRYGMYDKMBQGA3KC5QC>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/ACJLEMHCU366P2ZATXOIS535MJB7PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBVHE4TIOBUGM3KM4TFMFZW63VQOJSXM2LFO5PXEZLROVSXG5DFMSSWK5TFNZ2KUZTPN52GK4S7NFXXG>
and Android
<https://github.com/notifications/mobile/android/ACJLEMAPMVXMDEV26IMDMBT5MJB7PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBVHE4TIOBUGM3KM4TFMFZW63VQOJSXM2LFO5PXEZLROVSXG5DFMSSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>.
Download it today!
You are receiving this because your review was requested.Message ID:
***@***.***>
|
It was a very conscious decision in ICU, complete with a transition period, see https://docs.google.com/document/d/1MsXcCEggqTGRDcyO2l3Hv88ZPoQL0hhKUEKXhJfvaRQ/edit?tab=t.0#bookmark=id.ud0rlosxly8t and https://docs.google.com/document/d/1MsXcCEggqTGRDcyO2l3Hv88ZPoQL0hhKUEKXhJfvaRQ/edit?tab=t.0#heading=h.gq09ahjle3k6. The pre-79 behaviour was neither documented by ICU nor expected by anyone. |
|
Ah, yes. I agree (and had agreed earlier) that
https://docs.google.com/document/d/1MsXcCEggqTGRDcyO2l3Hv88ZPoQL0hhKUEKXhJfvaRQ/edit?tab=t.0#bookmark=id.ud0rlosxly8t
was
the right approach.
I didn't realize that the problem here was from having the characters
within {}.
…On Sun, Aug 30, 2026 at 3:04 PM Robin Leroy ***@***.***> wrote:
*eggrobin* left a comment (unicode-org/cldr#6093)
<#6093 (comment)>
is this a client incompatibly that we are comfortable in ICU?
It was a very conscious decision in ICU, complete with a transition
period, see
https://docs.google.com/document/d/1MsXcCEggqTGRDcyO2l3Hv88ZPoQL0hhKUEKXhJfvaRQ/edit?tab=t.0#bookmark=id.ud0rlosxly8t
and
https://docs.google.com/document/d/1MsXcCEggqTGRDcyO2l3Hv88ZPoQL0hhKUEKXhJfvaRQ/edit?tab=t.0#heading=h.gq09ahjle3k6
.
The pre-79 behaviour was neither documented by ICU nor expected by anyone.
—
Reply to this email directly, view it on GitHub
<#6093?email_source=notifications&email_token=ACJLEMEU6WG7XVS2RVMECXL5MSQF3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBXGE2TGMRZGA3KM4TFMFZW63VQOJSXM2LFO5PXEZLROVSXG5DFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5471532906>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJLEMBQJ3ZYWGNNH7WKPLT5MSQF3AVCNFSNUABFKJSXA33TNF2G64TZHMYTAMZZGQ4DMNZSHNEXG43VMU5TKMRYGMYDKMBQGA3KC5QC>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/ACJLEMBR3W7DVZDJRB6XAXD5MSQF3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBXGE2TGMRZGA3KM4TFMFZW63VQOJSXM2LFO5PXEZLROVSXG5DFMSSWK5TFNZ2KUZTPN52GK4S7NFXXG>
and Android
<https://github.com/notifications/mobile/android/ACJLEMEA2SN7TYW6LIUB5K35MSQF3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBXGE2TGMRZGA3KM4TFMFZW63VQOJSXM2LFO5PXEZLROVSXG5DFMSSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>.
Download it today!
You are receiving this because your review was requested.Message ID:
***@***.***>
|
|
BTW, I was thinking that almost nothing in attributeValueValidity.xml is
obsolete and not needed anymore, except for
<variable id='$language…' ...
I just confirmed that by deleting everything else and running all the
tests. Dragan, you can go ahead and make a spot fix to unblock yourself.
I'll file a ticket to clean up that file.
Mark
…On Sun, Aug 30, 2026 at 8:38 PM Mark Davis Ⓤ ***@***.***> wrote:
Ah, yes. I agree (and had agreed earlier) that
https://docs.google.com/document/d/1MsXcCEggqTGRDcyO2l3Hv88ZPoQL0hhKUEKXhJfvaRQ/edit?tab=t.0#bookmark=id.ud0rlosxly8t was
the right approach.
I didn't realize that the problem here was from having the characters
within {}.
On Sun, Aug 30, 2026 at 3:04 PM Robin Leroy ***@***.***>
wrote:
> *eggrobin* left a comment (unicode-org/cldr#6093)
> <#6093 (comment)>
>
> is this a client incompatibly that we are comfortable in ICU?
>
> It was a very conscious decision in ICU, complete with a transition
> period, see
> https://docs.google.com/document/d/1MsXcCEggqTGRDcyO2l3Hv88ZPoQL0hhKUEKXhJfvaRQ/edit?tab=t.0#bookmark=id.ud0rlosxly8t
> and
> https://docs.google.com/document/d/1MsXcCEggqTGRDcyO2l3Hv88ZPoQL0hhKUEKXhJfvaRQ/edit?tab=t.0#heading=h.gq09ahjle3k6
> .
>
> The pre-79 behaviour was neither documented by ICU nor expected by anyone.
>
> —
> Reply to this email directly, view it on GitHub
> <#6093?email_source=notifications&email_token=ACJLEMEU6WG7XVS2RVMECXL5MSQF3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBXGE2TGMRZGA3KM4TFMFZW63VQOJSXM2LFO5PXEZLROVSXG5DFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5471532906>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ACJLEMBQJ3ZYWGNNH7WKPLT5MSQF3AVCNFSNUABFKJSXA33TNF2G64TZHMYTAMZZGQ4DMNZSHNEXG43VMU5TKMRYGMYDKMBQGA3KC5QC>
> .
> Triage notifications, keep track of coding agent tasks and review pull
> requests on the go with GitHub Mobile for iOS
> <https://github.com/notifications/mobile/ios/ACJLEMBR3W7DVZDJRB6XAXD5MSQF3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBXGE2TGMRZGA3KM4TFMFZW63VQOJSXM2LFO5PXEZLROVSXG5DFMSSWK5TFNZ2KUZTPN52GK4S7NFXXG>
> and Android
> <https://github.com/notifications/mobile/android/ACJLEMEA2SN7TYW6LIUB5K35MSQF3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBXGE2TGMRZGA3KM4TFMFZW63VQOJSXM2LFO5PXEZLROVSXG5DFMSSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>.
> Download it today!
> You are receiving this because your review was requested.Message ID:
> ***@***.***>
>
|
5 participants
CLDR-19756
Updates
icu4j.versionintools/pom.xmlfrom the mid-March snapshot to thelatest published one:ALLOW_MANY_COMMITS=true