Support localising of config.xml permission strings
See original GitHub issueNSLocationWhenInUseUsageDescription
NSLocationAlwaysUsageDescription
NSCameraUsageDescription
etc
should also be localised.
So instead of automatic detecting of what needs to go into InfoPlist.strings
I’d suggest to have 2 translation files for each language, one for config.json
and one for app.json
. Everything from config.json
goes into InfoPlist.strings
.
What do you think?
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Localize your app - Android Developers
This document describes best practices for localizing Android apps. ... Put the app's default text in res/values/strings.xml .
Read more >Config.xml - Apache Cordova
config.xml is a global configuration file that controls many aspects of a cordova application's behavior. This platform-agnostic XML file is arranged based on ......
Read more >Using Locale to force Android to use a specific strings.xml file ...
Will this work? I.e., can we control which strings.xml file it uses via Locale , even if the device has no native support...
Read more >Working with resource strings | Kentico 12 Service Pack ...
Users with the Global administrator privilege level; Users who belong to roles with the Localize strings permission for the Localization module.
Read more >Config Plugins - Expo Documentation
Note: The Expo Go app doesn't support custom native modules, and config plugins ... that adds camera permissions to the Info.plist and AndroidManifest.xml....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Good point there. i have unpublished 0.1.4 and bumped the version to 1.0.0
I’ve been using 1.0.1 for my project, and it seems to work ok so far. Closing this issue for now.