El Loco Blog

Blog | El Loco Updates for May 31, 2016

El Loco Updates for May 31, 2016

By Adam Yagiz — May 31, 2016

Here are the latest updates and improvements to the Web Portal and El Loco app.

Web Portal [v1.2 (2805)]

This update:

  • Fixed overlapping screens and rendering issues with large form factors in Visual Context Editor.

  • Fixed false-positive overrun indicators in Visual Context Editor.

  • Updated reporting for translators and developers.

  • Added the ability to pause/resume El Loco subscriptions.

  • Improved performance and other bug fixes.

El Loco App [v1.0.2542.0]

This update:

  • Improved Swift file parsing and support.

  • Fixed El Loco library integration error when Swift bridging header is present.

  • Fixed customer reported issues.

  • Improved stability, error handling, and other bug fixes.

Happy localizing!
The El Loco Team

How Secure Is My Use Of El Loco?

By Kee Nethery — February 9, 2016

How Secure Is My Use Of El Loco?


Let’s start with what El Loco does not do; El Loco does not upload your app, or its source code, into the El Loco servers. Your source code and your compiled app stay on your development machine.

What does El Loco upload to its servers?

Two things:

  1. The strings that need to be translated, pulled from your code and from your xib b files; and

  2. The definition of the screens viewed in the iOS Simulator.

That’s it. What goes up into the El Loco servers from your development machine is less than what a user gets when they download your app onto their iOS device.

Worst case scenario, if someone guesses your password, they would be able to see screens from the next version of your app. You do create strong passwords, correct?

More Details Please…

El Loco provides you with the El Loco app for your OS X development machine. The purpose of it is to help you organize your code for the localization process. Specifically, the El Loco app:

  1. organizes source files into .lproj folders if needed,

  2. identifies for your review, and then on your command wraps strings in your code,

  3. gathers the screen definitions used by translators when you run your app in the Simulator,

  4. manages the upload of what needs to be translated to the El Loco servers,

  5. manages the download and integration of translations back into your app,

  6. keeps track of localization type changes as you develop the app, and,

  7. manages the frequent upload, translate, integrate cycle so that your app is completely translated the day the code is complete.

The El Loco app installs an El Loco iOS library into your app that collects screen data while you are running the app in the iOS Simulator. As screens get displayed, the library captures what is displayed, and provides that data to the El Loco app for upload.

Instead of waiting until the end of the development cycle to localize your updated app, you upload translatable strings and screens captured via the iOS Simulator to the El Loco web site initially to do the bulk of the localization, and then periodically for the few changes that happen during your continued development.

Those strings and screens are the only data from your app that are ever on the El Loco web site; everything else that happens on your development machine, stays on your development machine.

See For Yourself

Download El Loco for OS X , analyze your app, and see just how localization ready you are.

App Store Says My Non-English App is in English

By Kee Nethery — January 12, 2016

App Store Says My Non-English App is in English

The App Store looks in your app for .lproj folders and uses those to see what languages your app supports. It does not matter what you tell the App Store, it looks inside the app to determine which languages your app supports. Without an .lproj folder the store typically defaults to English.

A properly named empty folder in your source code is all it takes to have the App Store know the language of your app.

There are several formats for naming the folder that indicates your app’s language:

  1. <ISO 639-1 two letter language code>.lproj

    For example, en.lproj indicates generic English, fr.lproj generic French, ja.lproj Japanese, and ko.lproj is Korean.

  2. <ISO 639-2 three letter language code>.lproj

    For example, eng.lproj indicates generic English.

  3. <ISO 639-1 or 639-2 language code>-<iso 3166-1 two letter region designator>.lproj

    For example, en-AU.lproj to indicate Australian English or fr-CA.lproj for Canadian French.

  4. <ISO 639-1 or 639-2 language code>-<iso 15924 four letter script code>.lproj

    For example, zh-Hant.lproj for Traditional Chinese or zh-Hans.lproj for Simplified Chinese.

For the App Store to correctly report the language of your app, there needs to be a properly named .lproj folder. An app supporting multiple languages will have an .lproj folder for each language.

The following links provide extensive lists of the ISO codes referenced above:

El Loco App To The Rescue

A key feature of the El Loco app is how it automatically cleans up and organizes your code into properly named folders. No more tedious searching and moving around of files. This alone can save you a bunch of time and allows you to focus on more important things… like actually developing your app!

Download El Loco App Today