The following case study was provided by the developer of the Chalkboard Math iOS app who used TraductoPro to localize his app.
I would like to disclose up front that part of the costs to translate our next version of Chalkboard Math (version 1.2) were paid by Traducto.
I had always wanted to localize an iOS app and have it support multiple languages, but for one reason or another have never gotten around to doing it. Let’s face it, if it were easy to do – all of the iOS applications that we develop would be localized. It takes work (ie. development time) and costs money if you hire a translator.
When I was approached on having TraductoPro featured on App Tuesday, I decided to put it to the test. Chalkboard Math was selected as the evaluation application, to determine if it was worth offering developers following App Tuesday the chance to win a copy of TraductoPro and translation credits.
In terms of complexity of code, Chalkboard Math is probably of average complexity – which makes it a good candidate for evaluating Traducto Pro.
TraductoPro is not a silver bullet that will magically solve all of your localization problems (time and cost). It’s a bronze bullet that will definitely save you a lot of time and for that reason is a tool worthy of having. Now onto the details of my experience (pros and cons):
Importing Data into Traducto Pro
The first step is to create a new Xcode (iOS) project within the app. One of the first things that it does to help out developers that have never localized an iOS project before (or developers that are experienced in this area – but are either lazy or missed a spot) is to allow the ability to scan through the Objective-C source code to see if there are any static strings in the code that have not been localized.
It will even modify your code, to make the strings localized. That’s a pretty cool feature!
The 2 snags that I ran into were:
1) Chalkboard Math uses a custom plist file to offer words of encouragement (Positive feedback) on both correct and incorrect answers. TraductoPro does automatically import your info.plist file but does not currently support custom plist files.
2) It could not read/open my Storyboard files.
Fortunately, TraductoPro support is very responsive (even when inquiring in the evening and on the weekend).
For the first issue, I was provided a workaround (create a Strings file to place my text into). There may be future support to read custom Property List files. Traducto Pro works with XIBs, Storyboards, and String files and the default Property List file.
The second issue, was because I had an old copy of the Developer tools in my path (/Developer) (that I should have uninstalled a long time ago). I don’t remember which version of Xcode it was, but Apple changed the way that the Developer tools were bundled (and I did not choose the option to uninstall them). Uninstalling the old tools, hasn’t appeared to break anything yet ￼
You probably won’t run into these snags, but if you should run into problems/issues – the support at Traducto is excellent for a software company.
Getting your text Translated
Now comes the fun part! Within Traducto Pro, add the languages that you want your text to be translated into.
For Chalkboard Math: I chose Spanish, French, and Chinese (Simplified). Make sure that the text boxes for the translated text are empty – unless you have already localized the files.
Then you add the languages to your shopping cart, at which point you can see the total cost – if you choose to use their translation service. You do NOT have to use their translation service.
If you happen to be a large company, that has a translator on staff – you could have them manually enter in the translations. Or if you are on a budget – or just want to help local college students – you can obtain the translations from them and enter them in the program. In this case Traducto Pro is more of a database of language translations – and allowing you to manage what needs to be translated / not translated – which still is worth the cost of the tool.
You can also create an AppStore project to translate your AppStore description and keywords into other languages as well. For this you basically copy/paste your description and keywords that you have on the AppStore and enter them into Traducto Pro. You then add the languages that you want, and add them to the cart.
Once you have everything in the cart and are ready to order, you place the order – and then wait for the translation. Even over the weekend, I was able to get my translated text within 24 hours.
Exporting translated text back into Xcode
This part was really cool! Once a given language is 100% translated, all you have to do is click 1 button to Export the translated strings back into the corresponding localized XCode files.
If you did not add that language within your XCode project, you will need to add it. Don’t worry – if you don’t do this you’ll get an error message on the Export specifying exactly which language(s) you need to add.
If you view the localized versions of the file you will see the translated text. At this point you will have an app that is localized. More likely than not, you will have to adjust the width and lengths of your labels (as translated text in my case is longer than the corresponding English words).
Not that this is a realistic capability, but if TraductoPro were able to automatically fix label widths – I would call it a silver bullet in the area of iOS localization.
As Chalkboard Math, speaks a lot of the text/audio (when the user gets an answer correct/incorrect) the next step is to use speech synthesis or voice talent to add audio in the foreign language. At least now I know the words that need to be spoken ￼ Once that’s completed, I should be ready to submit to Apple – and within the next month or so share the results on whether localization improves App Sales.
In summary – Traducto Pro is a bronze bullet that will save you a lot of time in localizing iOS apps and at this point in time the best tool out there in the market.
Article Source: Chalkboard Math