Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

UI strings should be localizable #8155

Closed
1ec5 opened this issue Feb 22, 2017 · 2 comments
Closed

UI strings should be localizable #8155

1ec5 opened this issue Feb 22, 2017 · 2 comments
Labels
Android Mapbox Maps SDK for Android Google Maps parity For feature parity with the Google Maps SDK for Android or iOS localization Human language support and internationalization

Comments

@1ec5
Copy link
Contributor

1ec5 commented Feb 22, 2017

Strings that appear in UI built into the Android SDK should be localizable in order to match the user’s system and the surrounding application UI. This file contains several strings that appear in UI. Perhaps we can manage translations in Transifex, where we’re currently managing translations of the iOS and macOS SDKs.

/cc @zugaldia @tobrun @ragaisis

@1ec5 1ec5 added Android Mapbox Maps SDK for Android localization Human language support and internationalization labels Feb 22, 2017
@tobrun
Copy link
Member

tobrun commented Feb 22, 2017

Suggesting to pick up accessibility support in #4857 first to avoid doing double translation work.

@1ec5 1ec5 added the Google Maps parity For feature parity with the Google Maps SDK for Android or iOS label Feb 22, 2017
@1ec5
Copy link
Contributor Author

1ec5 commented Apr 19, 2017

#8556 should’ve implemented the necessary Transifex integration, but we’ll want to do a tx pull -a before the next release to pull in any new translations.

@tobrun tobrun closed this as completed Jul 6, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Android Mapbox Maps SDK for Android Google Maps parity For feature parity with the Google Maps SDK for Android or iOS localization Human language support and internationalization
Projects
None yet
Development

No branches or pull requests

2 participants