Live website localization

Good afternoon! Thank you for giving me the opportunity to talk about live website localization.

@mathjazz

If you want to stay in touch with me after this workshop, here's my twitter handle.

Slovenia

I come from Slovenia. People mix Slovenia with Slovakia, but it's really easy to distinguish one from another.

sLOVEnia

There's love in Slovenia and there's no love in Slovakia.

Matjaž

My name is Matjaž. This is how my name is spelled. But it might not be so all the time.

Matja

Here's another example of my name that I see quite a lot.

Matjaž

And another. Seeing such mistakes with my name and my country's name is what actually got me interested in localizing the web.

Mozilla

10 years ago I got involved with Mozilla by localizing Mozilla Application Suite. Since last year I work for Mozilla, spending most of my time developing the website localization tool I'm about to demonstrate.
Mozilla is a global non-profit dedicated to putting you in control of your online experience and shaping the future of the Web for the public good.
Mozilla is not only Firefox. It's a non-profit organization, shaping the future of the Web and putting you in control of your online experience. We have thousands of volunteers, localization is 100% volunteeer-driven.
Yes, we also have a community on Antarctica.

Existing Approach

We normally localize websites by extracting strings, giving them to localizers, and when they are done, we integrate them back into the website.
First we have to extract the original strings (text) from the websites.

Localize

#: resources/static/shared/messages.js:150

msgid "Become a Test Pilot!"

msgstr "Postani testni pilot!"

Then we give these strings to localizers who have to translate them.
When localizers are done with translations, we integrate translations back into the website which is than translated.
There are two problems with this approach. Localizers don't see the context and they don't know whether their translations will fit the space available.
There are two problems with this approach: 1. Localizers don't see the context (BUTTON or MENU ITEM). 2. Localizers don't know if their translation will fit the space they have (BUTTONS HAVE LIMITED SPACE).

The way ahead

SOLUTION: localize on the page itself or what we call LIVE LOCALIZATION.
There are two problems with this approach. Localizers don't see the context and they don't know whether their translations will fit the space available.
Let's see an example of live localization. We have the text and we localize it right now, right here.

pontoon-dev.
mozillalabs.com

Pontoon is a tool we develop at Mozilla that can turn any website into editable mode, which enables live localization on the page itself. Let's check out the demo. 1. FRONTPAGE: To enable localization of your site, paste the snippet, then go to Pontoon site, enter url, pick the target language and localization starts (click demo). 2. TOOLBAR_: Click on the info icon (i), tell them about subpages menu, progress bar etc. 3. LOCALIZATION: Hover over strings, edit one, translate it, show the progress bar update. 4. ADVANCED: What if I want to translate the title tag? Explain it's like Verbatim or Transifex, show auto translation, translation memory. 5. DOWNLOAD: Login using BrowserID, Download as e.g. PO