Early Adopter Pricing Announced

On 8th August 2012, the free beta of Locale will end. A limited number of Early adopter accounts are now available.

We’d like to thank the hundreds of beta testers for helping us shape and develop Locale over the past 18 months.

So, before we announce our full plans and pricing in August, we’ve created a special crazy-low-thank-you-beta-tester plan.

Just €12 a month buys ..

  • 5 projects
  • Unlimited locales
  • Unlimited collaborators
  • Unlimited translations
  • Access to this plan for life
  • Our continued development and support of Locale

How to upgrade

  1. Sign in to your Locale account
  2. Visit your profile page
  3. Select the billing tab
  4. Click the upgrade button

You’ll be able to set up a monthly credit card subscription which you can cancel at any time.

Need more than 5 projects?

  • Sign in and get in touch using the help button.

What will happen on August 8th?

  • Projects associated with upgraded accounts will continue to function just as they are now.
  • Projects associated with accounts which have not been upgraded will no longer be available.
  • Project owners should download their translation files before August 8th.
  • During August, we’ll announce our full range of plans and prices, and this plan will no longer be available.

Who should pay?
Project owners with private projects should upgrade today to continue using Locale and keep their projects active.

Who doesn’t need to pay?
Translators and developers who are not project owners will continue to have free access to Locale. Project owners of public projects also don’t need to pay.

Feedback, comments, questions?
Sign in and get in touch using the help button.

Posted in LocaleApp | Tagged , , | Leave a comment

Locale Supports Bi-directional Languages

New today, Locale supports right-to-left text for Arabic, Hebrew and Persian.

Try it for yourself. Add one of these languages to your Locale projects and start translating.

In actual fact, the magic is performed in the browser. Have a quick look at the text fields for these languages and you’ll see: dir=”rtl” lang=”ar”. The browser then decides to display these fields from right-to-left.

One twist is that these languages will often include quotations from left-to-right languages or include numbers. In each case, these are displayed left-to-right within the block of right-to-left text.

That’s why these locales are more accurately described as Bidi, or bi-directional languages.

More information from W3C on the bidi algorithm.

This is our first pass at this feature. Please let us know your thoughts or if there’s anything we’ve missed.

Posted in LocaleApp | Tagged , , , , | Leave a comment

How to migrate Copycopter blurbs to Locale

With Copycopter shutting down on April 15th, how will you manage your blurbs if you don’t want to go back to hand-editing YAML files?

The good news is that there’s a painless and free method of exporting blurbs from Copycopter and importing them to another service – Locale.

Free? Really?

Locale is still in beta – and still completely free to use.

That doesn’t mean it’s flaky and unreliable (it’s running on this cluster of servers, for example), but we’re focused on building out its feature set rather than deliberating over a pricing model.

So that you know we won’t sting you when we do start charging, worst case, we’ll offer similar pricing and features to Copycopter ($9 – $49/month) to all Locale beta users.

How to move your projects from Copycopter to Locale

  1. Create a Locale account and a new project
  2. Uninstall the Copycopter gem from your app and delete `config/initializers/copycopter.rb`
  3. Install and configure the `localeapp gem`
  4. Push your translation files to Locale with `bundle exec localeapp push`

Can Locale do everything that Copycopter does?

Almost. We’re missing the facility right now to have draft and published blurbs – but it’s a feature we will have soon. Aside from that, we think you’ll love using Locale – especially if you’re managing projects with multiple locales.

Is Locale easy to use?

Absolutely. Locale and Copycopter are completely different apps, so the interfaces are different – but we think you’ll enjoy using Locale. We’ve had some great feedback about the UI and we’re still pouring our hearts, souls and development effort into perfecting it.

Will I be tied-in to using Locale?

No. There’s a YAML export from Locale too. You always own your content and we even include YAML for a growing list of apps and gems such as Devise.

Who else is using Locale

There are currently around 500 projects of all sizes using Locale. We use it on one of our own apps – a busy Spanish property portal – to localise it into 9 languages. Here’s what people are saying about Locale on twitter:












Got a question, or need more info?

  1. Locale on Github
  2. Github wiki
  3. You can chat with us directly when you’re signed in to Locale
  4. You can email us at info (at) LocaleApp.com
  5. Twitter @localeapp
  6. .. or leave a reply
Posted in LocaleApp | Tagged , , , , , , | 1 Comment

Update to YAML handling in the localeapp gem

The state of ruby YAML engines

Since ruby 1.9.3-p0, Psych has been the default YAML engine in Ruby. Psych is based on libyaml and fixes a number of issues with the previous YAML library, Sycklocaleapp.com uses 1.9.3 and Psych for all its YAML processing.

localeapp gem v0.4.0

This release increases compatibility with the Psych engine. To update your gem :

bundle update localeapp 

If your project is using ruby 1.9.3

  • Psych is available, so it will be used to generate YAML.
  • After updating to localeapp v0.4.0, the first localeapp pull will convert your YAML files to Psych format.
  • From this point on, YAML exported from localeapp.com will be identical to YAML obtained from localeapp pull.

If your project is using anything under 1.9.3

Unless you have the Psych gem installed, localeapp will use ya2yaml to generate YAML. While ya2yaml supports UTF-8, it does write YAML differently to Psych so you will notice differences between exporting directly from localeapp.com and doing localeapp pull on the command line.

Posted in LocaleApp | 1 Comment

News from the library

This week we present a big update to the content in our built in library.

Devise-i18n by popular demand!

The number one requested library was for the devise authentication gem.

This sounded like a simple task but our yak razors ended up seeing some heavy use. Originally there was no central repository for collecting translation data for this project and previous efforts had ended up with many gists and varying version compatibilities.

Our first job was to create the devise-i18n project and pull together the different sources to create the base translations.

Devise 2.0 was released during this period so translations also needed to be updated to the latest version.

Finally, after much fixing, testing, and some great user contributions, we’re happy to offer 1-click inclusion of these translations from the “libraries” page within your Locale projects.

Updates to rails-i18n

Not content with adding devise, we wanted to reinforce our commitment to open source projects.

We used Locale to clean and reformat the official Rails translations for better compatibility with Rails 3 and more completeness. Locale made it easy to edit the 74 different locales together and get these translations squeaky clean.

Translations for Rails 3 are now added automatically to every new project created on Locale. To remove them or to replace them with the legacy 2.3 translations use the “libraries” page in your project.

Other minor updates

Translations for the will_paginate gem have been updated to v3.0.

Want more?

We’d love to hear which libraries are essential to your every day development so we can make your life easier by including their translations in Locale.

Posted in LocaleApp | Leave a comment

Pluralization editor(s)

A much requested improvement to the translation editor has just been released : pluralizations.

Create a pluralized translation in your app either by creating a pluralized key or by including %{count} in the description.

Locale understands the pluralization rules for every available language and will suggest which sub keys apply.

Pluralization Editor

We think this improvement will greatly improve your translation speed and accuracy.

Some additional information and tips are available on the Locale wiki.

Happy pluralizing!

Posted in LocaleApp | Leave a comment

London Ruby User Group i18n Video

Chris McGrath's i18n presentation at London Ruby User GroupOur very own Chris McGrath spoke about all things i18n at the last London Ruby User Group – (40 minute video now available there).

Chris referenced this excellent article about string concatenation – one of the greatest localisation sins we’ve come across (and committed quite a few times).

Chris also deals with the problems of context, language compactness and gender (thanks Bender).

Flushed with success, we’re sending Chris off to Cape Town in South Africa in February to RubyFuza

He’s on a mission about why internationalisation makes a lot of (business) sense – even if your app only supports a single language/locale.

After that, catch the Locale team out in force at Railsberry in April (Krakow, Poland).

Posted in LocaleApp | Tagged , , , , | Leave a comment

Kicking off 2012 in style

Wishing you a very happy new year! To get the year off to a good start, we’ve just released a few great changes to the interface that are sure to make your translation management tasks faster and easier :

The multiline editor is dead; long live multiline edits!

We’ve totally revamped the multiline editor to make it even easier to use.

The ‘multiline’ attribute has disappeared so all translations are created equally.

The editor will now adapt to the size of the content in the same familiar interface so that you can stay focused on your translations.

Keyboard shortcuts

Keyboard shortcuts make you faster and more productive.

We know that a big proportion of our users are keyboard junkies (ourselves included) so we’ve added a few shortcuts to make editing translations even quicker.

For example, pressing the tab key when editing a translation will save the content and move to the next item in the list. We’ve found this to be a huge time saver and it is our preferred way of editing a long list of translations.

You can bring up a reminder of available shortcuts by hitting “?” on the translations screen or by clicking on the “Keyboard shortcuts” icon.

What’s next?

We’ve got a packed development schedule but we’d love to hear your feedback and ideas – just click on the support link at the top of every page.

Posted in LocaleApp | Leave a comment

Locale Beta V2

A new release of Locale has just gone live – here are the highlights.

If you spot any problems, don’t hesitate to contact us – the support links are inside your Locale account.

Improved UI

The new project dashboard crams a lot of information into a small space without being crowded or confusing.

Locale project dashboard

Library support

The biggest complaint we had with the previous version of Locale was related to the way we handled base translations for Rails. We’ve now made the process of including those translations an explicit process – by creating libraries.

Libraries clear up one big confusion people had when they first imported a project into Locale – “missing” Rails translations. They weren’t actually missing, we just didn’t show them if they hadn’t been changed from the default. They’re now fully visible so you can get 100% completion for each locale.

To start with there are just two libraries – the regular Rails i18n library and a list of countries.


We’ll be adding to this collection, so if you want a particular library added – don’t hesitate to let us know.

The advantage of libraries is that it saves you having to reinvent the wheel and re-translate a whole bunch of stuff that most Rails developers need translated.

In time, we’ll make these library projects public so that developers and translators can collaborate on making their libraries available in more and more languages.

Improved Pluralisation

We’ve taken a first pass as combining multiple keys related to a pluralised string. For now that involves using YAML, but we’ll be improving that interface soon.

Here’s an example of a pluralised key from the Rails i18n library.


We’d appreciate your feedback about these new features – and any new stuff you need Locale to be doing for your localised Rails apps.

Posted in LocaleApp | Tagged , , , , , , , , | Leave a comment