-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[iOS/HybridGlobalization] No space between time and AM/PM designator #102250
Comments
Tagging subscribers to this area: @dotnet/area-system-globalization |
@mkhamoyan, in
https://developer.apple.com/documentation/foundation/nsdateformatterstyle/nsdateformattershortstyle https://developer.apple.com/documentation/foundation/nsdateformatterstyle/nsdateformattermediumstyle should return formats with the space. Is it possible that we format it on the fly? Or might it be a behavioral change between iOS's ICU version? |
We see bahavioural change as there was a fix in ICU flow ( see #83589) and now runtime/src/libraries/System.Private.CoreLib/src/System/Globalization/CultureData.Icu.cs Line 338 in 0c64e66
runtime/src/libraries/System.Private.CoreLib/src/System/Globalization/CultureData.iOS.cs Line 79 in 0c64e66
I will open a PR to use same function for both flows. |
@matouskozak fyi |
I am not able to reproduce this issue in the .NET 8 repo (works as expected on .Net 9 also). |
I can still reproduce this with .NET 8. I am using |
Thanks! I can reproduce with |
In .NET 9 It appears that recent ICU versions have introduced a change where I will open a PR to handle these cases properly. |
Description
When using hybrid globalization on iOS and using the short time specifier, there is no space in front of the "AM" or "PM".
Reproduction Steps
Expected behavior
3:15 PM
Actual behavior
3:15PM
Regression?
No response
Known Workarounds
No response
Configuration
macos 14.2.8053/8.0.100 SDK 8.0.200
ios 17.2.8053/8.0.100 SDK 8.0.200
iOS 17.2
Other information
The same problem happens when using the long time format specified ("T").
The space is present as expected when not using hybrid globalization
The text was updated successfully, but these errors were encountered: