You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As shown in the picture above, with the previous library WheelPickerCompose, we could confirm that the text for the month was applied according to the Locale settings. (Locale.KOREAN applied)
However, in the current library that supports Kotlin Multiplatform, these Locale properties are not applied, causing the month's text to always be displayed in English.
For some reason, the kotlinx-datetime library doesn't seem to support Java.util.Locale provided by Java (I might be mistaken about this), so Locale is not being applied.
Could you possibly explain why this is the case? Also, I'm curious if this is a limitation of Kotlin or the kotlinx-datetime library.
The text was updated successfully, but these errors were encountered:
You're right, Locale isn't working for this lib yet. Here's why:
When I migrated the original lib to multiplatform, I didn't include support for localization (L10N). That's why you're seeing month names based on the Month enum instead of localized names.
I originally skipped L10N partly because Kotlin-Datetime didn't have built-in Locale support. So, I decided to put L10N on the back burner for a while.
Long story short, I'm the one who limited the L10N. But I'm actively working on adding proper L10N support soon.
As shown in the picture above, with the previous library WheelPickerCompose, we could confirm that the text for the month was applied according to the Locale settings. (Locale.KOREAN applied)
However, in the current library that supports Kotlin Multiplatform, these Locale properties are not applied, causing the month's text to always be displayed in English.
For some reason, the kotlinx-datetime library doesn't seem to support Java.util.Locale provided by Java (I might be mistaken about this), so Locale is not being applied.
Could you possibly explain why this is the case? Also, I'm curious if this is a limitation of Kotlin or the kotlinx-datetime library.
The text was updated successfully, but these errors were encountered: