<div dir="ltr">Hello Andras, <div><br></div><div>Indeed the localization process in iOS development was quite broken before iOS6. Actually when I set out to build this app, iOS7 was not yet released so I tried my best to keep the app compatible with iOS5 and iOS6. It's now compatible with iOS7 as well but keeping it compatible with iOS5 devices also brings some side effects: </div>
<div><br></div><div>iOS5 doesn't support "base storyboard" (one UI file+one localization strings file for each language) and therefore each time we support a new language, we need to create a separate storyboard (iOS's UI design file) for that. In order to avoid the pain keeping storyborads for different languages in sync, I've used a python script which propagates all UI changes in the English storyboard to all other languages's storyboard and remplace all strings in these storyboards accordingly at the end of each compilation. </div>
<div><br></div><div>So here is how it works for now: </div><div><br></div><div>1. For strings that are displayed programmatically, the Localizable.strings files would be used. For each language, there should be one <u>Localizable.strings</u> file. </div>
<div>2. For strings in the Storyboard, the python script will go through the whole file and extract all the strings in the storyboards. We translate those files from English to another language and then, we build the project again and the python script would take care of replacing all the strings into storyboard files accordingly. Therefore, there would be two files here, <span style="font-family:arial,sans-serif;font-size:13px"><u>iPad_autosize.strings</u> and </span><span style="font-family:arial,sans-serif;font-size:13px"><u>iPhone_autosize.strings</u>.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div>For the time being this solution (or a hack xD) is still a workable solution to keep backward compatibility with iOS5, so it might be worthwhile to keep it that way for now. With future releases from Apple, this might provoke some problems and we can consider dropping iOS5 support then. </div>
<div><br></div><div>However I'm not as experienced in terms of software management and it might be better to just drop the iOS5 support now, so don't hesitate to give me your advice on that. </div><div><br></div>
<div>
<br></div><div>Final word: I will push some updates to the localizations files and hopefully the three localization files that I've underlined would be ready to be uploaded to Pootle. I will send you an email when it's ready. </div>
<div><br></div><div><br></div><div>All the best!</div><div><br></div><div>Siqi</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/11/17 Andras Timar <span dir="ltr"><<a href="mailto:timar74@gmail.com" target="_blank">timar74@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Siqi,<br>
<br>
I'm working on the localization of mobile Impress Remote applications.<br>
Unfortunately I'm a newbie at iOS development. I did not understand<br>
the current directory structure under ios/iosremote, and I'm not sure,<br>
if all localizable strings are extracted. How do you generate .strings<br>
files? Why are there two locations for localizable stuff --<br>
ios/iosremote/en.lproj and ios/iosremote/iosremote/en.lproj?<br>
I ran git grep NSLocalizedString, and it seems that strings from<br>
ios/iosremote/InAppSettingsKit are not in Localized.strings.<br>
<br>
In the end, I think we should have 3 English files:<br>
Localized.strings<br>
iPad_autosize.strings<br>
iPhone_autosize.strings<br>
<br>
I want to upload them to Pootle, then merge back translations into<br>
source, and push to git.<br>
<br>
Thanks for you help in advance.<br>
<span class="HOEnZb"><font color="#888888"><br>
Andras<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>--------</div><div><br></div><div>Cordialement,</div>Siqi LIU<div><br><div>Étudiant Ingénieur, 1ère année</div><div>École Supérieur d'Électricité (Supélec)</div>
</div><div><br></div></div>
</div>