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
{{ message }}
This repository has been archived by the owner on Apr 25, 2019. It is now read-only.
We currently use FilePicker for an iOS app we’ll be releasing soon. We will be releasing US, German, French, Spanish and Simplified Chinese localizations of our app. We were very relieved to see the following on Ink's website:
Do you support internationalization?
Yes, we have implemented internationalization for filepicker dialog. Together with our clients we are creating language resources for Filepicker dialog UI. If you would like to co-create the translation to any language, please contact us.
But then were thoroughly disappointed when we realized that ios-picker has zero support for internationalization. None of the strings use NSLocalizedString, there is conditional logic based on the presence of English strings, number formatting is not locale-friendly, the user interface files are not setup for localization, etc. Is anyone working on this? Has there ever been any discussion around it?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We currently use FilePicker for an iOS app we’ll be releasing soon. We will be releasing US, German, French, Spanish and Simplified Chinese localizations of our app. We were very relieved to see the following on Ink's website:
But then were thoroughly disappointed when we realized that ios-picker has zero support for internationalization. None of the strings use NSLocalizedString, there is conditional logic based on the presence of English strings, number formatting is not locale-friendly, the user interface files are not setup for localization, etc. Is anyone working on this? Has there ever been any discussion around it?
The text was updated successfully, but these errors were encountered: