Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2020.1.0b7
2020.2
Issue ID
1243754
Regression
No
Time pattern uses '.' as a TimeSeparator instead of ':' when the OS language format is set to Norwegian
How to reproduce:
1. Change the OS date and time format to Norwegian Bokmål (in Windows 10: Control Panel -> Clock and Region -> Change date, time, or number formats -> Formats -> change the format to Norwegian Bokmål).
2. Open the attached project (case-1243754.zip)
3. Enter Play Mode
Expected result: the date printed in the Console window is of format dd.mm.yyyy hh:mm (colon in the time)
Actual result: the date printed is of format dd.mm.yyyy hh.mm (dot in the time)
Reproducible with: 2018.4.22f1, 2019.3.13f1, 2020.1.0b8, 2020.2.0a9
Not reproducible with: 2017.4.40f1 (CurrentCulture always set to English)
Notes:
The issue would seem to occur when OS date format is set to be separated by '.' symbols and time to be separated by ':' symbols. However, the issue only occurred with the Norwegian language format and not with other similar formats (for example, Russian).
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Builder Data Path Source List starts flickering and scrolling when trying to select the last item in the list
- Crash on ProcessSceneBeforeExport when analyzing selected Addressables rules in a specific project
- HDR images are compressed incorrectly with default settings on Android Platform
- Crash with multiple stack traces when painting detail on Terrain with a highly detailed Prefab
- Crash on mono_object_handle_isinst_mbyref_raw when SerializedReference points to a struct implementing ISerializationCallbackReceiver whose first field is a UnityEngine.Object
Resolution Note:
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this issue.