UIImagePickerController is not localized
Opened this issue · 10 comments
the control buttons in the UIImagePickerController specially in the camera is showing the locale key of the strings .. any idea?
I believe those are a part of the system, so they cannot be localized.
I think you can get them directly from view hierarchy am set their caption,
however you may face compatibility issues with newer/older versions.
On 29 aug. 2015, at 15:44, Mohamed Emad Hegab notifications@github.com
wrote:
the control buttons in the UIImagePickerController specially in the camera
is showing the locale key of the strings .. any idea?
—
Reply to this email directly or view it on GitHub
#1.
that's sad.. it works fine depending on the localization of the device if i remove your code.. the only solution now is to use another third party camera ..
I think you shouldnt bother, there are many more controls that behave like
that (camera, mail, contacts, date/time etc)...
On 29 aug. 2015, at 15:58, Mohamed Emad Hegab notifications@github.com
wrote:
that's sad.. it works fine depending on the localization of the device if i
remove your code.. the only solution now is to use another third party
camera ..
—
Reply to this email directly or view it on GitHub
#1 (comment)
.
Checkout my fork. I fixed the issue with system frameworks not using localized strings or not using the language set using setLanguage:
very nice.. it's actually fixed .. good job... I think @cmaftuleac should have a pull request to merge it with the original pod 🎯
Glad to hear it fixed your issue as well. I did file a pull request with @cmaftuleac ... #2
@jbolter thank you for your contribution! I will merge, but want to do some testing first.
Setting "AppleLanguages" in user default will require application restart. This way I believe this is a partial fix, because if you change the language system frameworks will not change until restart, right?
I noticed its crashing on iphone 4s with ios 9. Is that common?
@cmaftuleac Sorry for the late reply... never saw your comment previously. Yes that's really the best we can do I think since the system frameworks won't change until the next launch of the app. @cupnoodle glad it helped!