-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
chore(3rdparty): update punic to 3.8.1 #39486
Conversation
|
CLDR 42 added a NARROW NO-BREAK SPACE for some time and date definitions. The idea is to prevent a break between a time definition.
Also from upstream punic/cldr: https://github.com/unicode-org/cldr/pull/2367/files |
bbe5f17
to
aaf249b
Compare
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.
Drone samba failure seems unrelated, test adjustments seem sensible 😊
aaf249b
to
a98668d
Compare
a98668d
to
b1f38b3
Compare
Signed-off-by: Daniel Kesselberg <[email protected]>
Punic 3.2.0 added support for timezone translations and returns UTC instead of GMT+0 now. Signed-off-by: Daniel Kesselberg <[email protected]>
Punic 3.8.0 / CLDR 42 added a narrow no-break space unicode character for the time formats and a new default pattern for datetime. Signed-off-by: Daniel Kesselberg <[email protected]>
b1f38b3
to
68eecca
Compare
Summary
Beware! The Punic and CLDR updates brought some changes to the generated date and time formats. I don't think that's a problem unless we parse those strings somewhere else.
Update punic to 3.8.1.
Major library update. The directory structure changed and thus almost everything is changed.
We are using the Calendar component in
lib/private/L10N/L10N.php
.If we make php-intl a required extension, we could use IntlCalendar and drop punic as a dependency.
TODO
Checklist