[Build] Current localization method overwrite PhoneGap default localization template

[amirudin]

@hardeep introduce the following localization method on Build:
Ref: http://community.phonegap.com/nitobi/topics/problem_with_binary_details_ios_localization_builded_with_phonegap_build#reply_6687343

- locales --- en ---- local.strings --- fr ---- local.strings

However, it seems to overwrite default localization available set by PhoneGap itself:
The following default template default template the become empty (blank).

https://github.com/phonegap/phonegap/tree/master/lib/ios/bin/templates/project/__TESTING__/Resources

[artlogic]

More information is available here: http://community.phonegap.com/nitobi/topics/custom_localization_overwriting_build_template_localizations_on_ios#reply_12906539

[hardeep]

Hey Amir,

This is the intention of the feature, it's to allow users to modify the localization settings when submitting to the apple app store.

By default the PhoneGap project has a set of locales that are auto generated by having specific string files in their project, this feature allows a user to over ride the locales.

Hardeep Shoker

[artlogic]

Hardeep,

I've copied and pasted a summary of the problem from the support ticket:

Amir - here are two repos, one that uses your "official hack":

https://github.com/artlogic/CaptureAudio
https://github.com/artlogic/CaptureAudioGerman

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.

This is the core of the problem - if I choose for my app to be localized only in German, I would expect the strings already localized by phonegap build to be carried over.

[shawnmckay24]

Thank you for submitting an issue. The PhoneGap Build team has triaged your request and labeled it:

1.   bug
   

2.   medium priority
   

We've added your request to the team's backlog. Due to high volumes, there may be a delay in addressing your request. Rest assured, we haven't lost track of your request. Your feedback is very valuable to us, so please keep it coming.

If you have any questions, please ask us over on our support community. We love to help!

Cheers,

The PhoneGap Build team

[networksolution]

Hi. It is not possible to have the photoshooting UI (Camera plugin) in iPhone in Italian like the rest of the phone and the app?

[wildabeast]

@networksolution yes it is possible, i've outlined how here

[networksolution]

Sorry but at the link you provided, the forum stripped away the tags from your reply...
Where to insert the string "it" in config.xml? It is not specified.

Also, here they told me it is not possible yet. http://community.phonegap.com/nitobi/topics/native-ui-elements-are-in-english-on-an-italian-phone

[wildabeast]

Thanks for pointing that out -- here's how it should read:

<gap:config-file platform="ios" parent="CFBundleLocalizations" mode="replace"> 
    <array>
      <string>it</string>
      <string>fr</string>
    </array>
</gap:config-file>

Throw that in your PGB config.xml and when you change your iPhone to italian or french, the camera plugin should render in that language.

[artlogic]

@wildabeast Forgive me because it's been nearly 18 months, but does this fix solve the root issue here, or is that still a problem?

[wildabeast]

@networksolution's question was actually a different issue.

@artlogic I can look into the main issue here, if it would still be of any value to you..

[artlogic]

@wildabeast If you have a few spare moments it would be nice to get it fixed, but frankly, it was @networksolution's question that even got me thinking about it again. I haven't had a user complaining about it for awhile now.