I've found that PhoneGap Build's template project for iOS contains localizations for 4 strings in 4 different languages. These localizations cause the App Store to report my App supports those 4 languages, when it doesn't. I've fixed this by including my own locale folder with appropriate languages, like so:
locales
|-en
| |- local.strings
|-de
| |- local.strings
The problem is that when I include this locales folder, the PhoneGap Build template localization is not merged with my localization - meaning that I need to include them manually.
Instead of the current behavior, I'd like it if the build server merged it's localizations with the custom localizations, while removing template localizations that aren't included in the custom package. In essence, if I include the locales folder above, the generated IPA should include en.lproj and de.lproj. The lproj folders should contain both my localizations and the default localizations.
Let me know if this is possible. Thanks!
locales
|-en
| |- local.strings
|-de
| |- local.strings
The problem is that when I include this locales folder, the PhoneGap Build template localization is not merged with my localization - meaning that I need to include them manually.
Instead of the current behavior, I'd like it if the build server merged it's localizations with the custom localizations, while removing template localizations that aren't included in the custom package. In essence, if I include the locales folder above, the generated IPA should include en.lproj and de.lproj. The lproj folders should contain both my localizations and the default localizations.
Let me know if this is possible. Thanks!
- 8 Posts
- 0 Reply Likes
Posted 7 years ago
- 8261 Posts
- 263 Reply Likes
Hello there,
Sorry for the late response however the localization on Build doesn't work that way. The folder structure above only helps Appstore to identify supported language while the translation itself have to be done via Javascript or some other way (load from local/remote storage, etc..)
Anyway, lets change this topic to and Idea so other people can vote for your suggestion.
Thanks
Sorry for the late response however the localization on Build doesn't work that way. The folder structure above only helps Appstore to identify supported language while the translation itself have to be done via Javascript or some other way (load from local/remote storage, etc..)
Anyway, lets change this topic to and Idea so other people can vote for your suggestion.
Thanks
- 8 Posts
- 0 Reply Likes
I understand what you are saying, but I feel as though you've missed my main point: When I include the above folder structure which "helps the Appstore identify supported language[s]", it wipes out the template's localization, thus making parts of my app not localize, when they once did.
For instance, if I include locales>de>local.strings with a dummy string in it (that I can't even use, according to you), then I would expect that the following strings would be merged from the template: https://github.com/phonegap/phonegap/...
I'd call this a bug, unless your intention was to cause this feature to remove localizations included in the template by default.
For instance, if I include locales>de>local.strings with a dummy string in it (that I can't even use, according to you), then I would expect that the following strings would be merged from the template: https://github.com/phonegap/phonegap/...
I'd call this a bug, unless your intention was to cause this feature to remove localizations included in the template by default.
- 8 Posts
- 0 Reply Likes
Amir - Thanks for your response. I don't seem to be communicating the issue very clearly, so I'm going to prepare some samples tonight to illustrate my point.
- 8 Posts
- 0 Reply Likes
Amir - here are two repos, one that uses your "official hack":
https://github.com/artlogic/CaptureAudio
https://github.com/artlogic/CaptureAu...
1. Build both of these for iOS with PhoneGap Build
2. Turn on voice over in the accessibility settings.
3. Switch the phone's language to German.
4. Start CaptureAudio, click on "Capture Audio".
5. Tap the record button (to get the accessibility text) - the voice over for the record button is in German, as it should be.
6. Start CaptureAudioGerman, which uses the "official hack", click on "Capture Audio".
7. Tap the record button (to get the accessibility text) - the voice over for the record button is in English. This is obviously incorrect.
Ideally, when I specify the language for my app using the "official hack", I would expect that it wouldn't disrupt strings already localized.
https://github.com/artlogic/CaptureAudio
https://github.com/artlogic/CaptureAu...
1. Build both of these for iOS with PhoneGap Build
2. Turn on voice over in the accessibility settings.
3. Switch the phone's language to German.
4. Start CaptureAudio, click on "Capture Audio".
5. Tap the record button (to get the accessibility text) - the voice over for the record button is in German, as it should be.
6. Start CaptureAudioGerman, which uses the "official hack", click on "Capture Audio".
7. Tap the record button (to get the accessibility text) - the voice over for the record button is in English. This is obviously incorrect.
Ideally, when I specify the language for my app using the "official hack", I would expect that it wouldn't disrupt strings already localized.
- 8261 Posts
- 263 Reply Likes
Hi Artlogic
Sorry for the late response. Now I'm fully understood the situation. I have create a bug report for this and please bookmark / watch / comments to get status update.
https://github.com/phonegap/build/iss...
Thanks you for your valuable feedback!
Cheers
Sorry for the late response. Now I'm fully understood the situation. I have create a bug report for this and please bookmark / watch / comments to get status update.
https://github.com/phonegap/build/iss...
Thanks you for your valuable feedback!
Cheers
- 8 Posts
- 0 Reply Likes
Thanks for sticking with this. I'm glad to see it's going to get fixed.
- 1 Post
- 0 Reply Likes
You should try localizing your iOS app with another localization tool such as this one: https://poeditor.com/. I never had such problems with my apps, and on top of that it has really useful features and a good price.
- 8 Posts
- 0 Reply Likes
POEditor is a great product, but it wouldn't help in this scenario. This is a problem with PhoneGap Build itself.
- 3500 Posts
- 40 Reply Likes
Hi,
This issue is now closed due to the inactivity.
Create a new issue if you wish to bring up the current situation or have any other problem with PhoneGap Build.
We seek your kind coorperation.
This issue is now closed due to the inactivity.
Create a new issue if you wish to bring up the current situation or have any other problem with PhoneGap Build.
We seek your kind coorperation.
This conversation is no longer open for comments or replies.
This conversation is no longer open for comments or replies.
Related Categories
-
PhoneGap Build
- 15111 Conversations
- 275 Followers


