Translation Markup Language and Universal Translation Memory

Translation Markup
Language
Universal Translation Memory
and

Michael Berkovich
michael@translationexchange.com
@translationx

1990 (pre internet)
OS introduced support for multiple languages and ability to switch
between them
Localization is based on resource files and language bundles
2016
Progress has been made in better file resource management but
localization complexity still exists.
We still live in the same localization paradigm.

Content Translation
Date & Time Conversion
Number Formatting
Currency Conversion
User Interface Adjustments
{COMPLICATED
It’s

There are many
standards, but little
guidance.
“

Every i18n framework has its own “right way”
of doing things, with a different syntax and file
format.
Developers often hack together their own
solutions to try and simplify the process.
No universality
in the current
standards

Android .xml
Apple .strings
Apple .plist
Gettext .po
Gettext .pot
Java .properties
Java .xml
Microsoft .resx
Microsoft .resw
Microsoft .resjson
Microsoft .aspx
FILE FORMATS
Lots of translation
Microsoft .rc
PHP .ini
PHP .conf
Babel Flash .xml
Blackberry .rrc
NSIS .insh
QT Linguist .ts
Latex .latex
Docbook .dbk
TBX .tbx
TMX .tmx
XLIFF .xliff
YouTube .sbv
YAML .yaml
Subtitles .srt
MicroDVD .sub
Subviewer .sub
Mozilla Web L10N
Text .txt
CSV Spreadsheet
Excel Spreadsheet
Word Document

Extract content into
files
Upload files to a TMS
or an LSP
Wait... Download translated
files
Put translations back
in your app
Repeat when new content is added or changed
BOTTLENECK
File management is a

File Management
● Not DRY (Don’t Repeat Yourself)
● Requires content extraction, sync with a TMS or an LSP
● Mini “waterfalls” in the agile process
● Slows down development cycle and releases
● High upfront cost and maintenance

Some companies build their own
CUSTOM TOOLS
WhatsApp Facebook AirBnB Twitter LinkedIn Evernote

How can we make it
BETTER FOR
EVERYONE

What would an ideal solution
look like?
● Consistency
Provide tools that offer a clear and
consistent way for internationalizing
content across all frameworks
● Adaptability
Tools must be extensible and adaptable
and should be able to solve any arising
internationalization and localization
problem
● Contextualization
Allow translators to translate in context
from within the application
● Agility
Keep the development cycle agile -
localization must not add significant
overhead for developers - it must be done
in parallel to the development process

What are the
Proxy Servers
Smartling, Easyling
Javascript based
solutions
Localizejs, Bablic,
Transifex Live
SDK based
solutions
Translation Exchange
ALTERNATIVE SOLUTIONS

● Depends on external servers uptime
● Search engines penalize content in
ranking (from external DNS)
● Increase response time
● Does not work for dynamic content
Proxy Server Solutions
● Easy to configure
● updated automatically
● Changes can be applied outside of
source code and developer’s time
Good Bad

● Easy to implement
● Content is all in one place
● Automatic updates
● Served from your domain
● Bad for SEO (only Google does any JS)
● Adds time in rendering
● Flicker effect
● Depends on external server uptime
Javascript Solutions
Good Bad

● Easy to install
● No manual content extraction
● Content is under developer’s control
● All content is in one place
● Served by your servers
● Good for SEO
● Translations can be done in context
● Supports agile methodology
● Same syntax across all frameworks
● Translations are reused across all apps
● Supports context rules
● Does not depend on external uptime
SDK Solutions

あ
A
Translation Management
Service
Global CDN
Local Cache
Application
with SDK
SDK Flow

Caching Translations
Static Cache
● File based cache
● Loaded into the process memory
and must be deployed with the
source code
● Each process contains the entire
translation cache
Dynamic Cache
● Redis, Memcached (and others)
updated from CDN release
● Cache is shared across all
processes
● Can be deployed without
restarting servers

Translation
Tools
Developer friendly syntax for marking
up application content.
Supports language context rules and
language cases, making translations
significantly more accurate for any
language.

<?php tre('Hello World') ?>
<%= tr('Hello World') %>
TML.translate('Hello World')
TMLLocalizedString('Hello World')
Ruby on Rails
PHP
Java
Objective C
TML Basics
Hello World
Python, Javascript, Node.JS, Ember, Angular, etc...

Descriptions
tr('Eats shoots and leaves', 'a panda')
Eats shoots and leaves
tr('Eats shoots and leaves', 'a violent restaurant patron')

Data Tokens
tr('Hello {name}', {name: 'John'})
Hello John

Data Tokens
tr('Hello {user}', {user: [user_object, :name]})
Hello John
Passing an object

Decoration Tokens
tr('Hello [bold: World]', {bold: '<strong>{$0}</strong>'})
Hello WorldWorld

Decoration Tokens
tr('Hello <bold>World</bold>', {bold: '<strong>{$0}</strong>'})
tr('Hello <strong>World</strong>')
With HTML Syntax
Hello WorldWorld
or

Decoration Tokens
tr('Hello <link>World</link>', {link: {‘href’:‘www.google.com’}})
link: ‘<a href=”{$href}”>{$0}</a>’
With Predefined Default Decorators
Hello WorldWorld
where link is a default decoration defined as

Decoration Tokens
TMLLocalizedString('Hello <bold>World</bold>', @{
@”bold”: @{
@"font": [UIFont fontWithName:@"ChalkboardSE-Bold" size:14]
}
})
Using iOS Native Decoration Methods
Hello WorldWorld

Nested Tokens
Hello JohnJohn
Nesting Tokens
tr('Hello [bold: {name}]', {name: 'John', bold: '<strong>{$0}</strong>'})

Nested Tokens
Hello MichaelMichael
tr('Hello [bold: {user}]', {user: [current_user, :name]})
tr('Hello [bold: {user}]', {user: current_user})
or
Passing Objects

<%= tml_source('common/navigation') do %>
<ul>
<li><%= tr('Home') %></li>
<li><%= tr('Features') %></li>
<li><%= tr('Languages') %></li>
<li><%= tr('Pricing') %></li>
<li><%= tr('Docs') %></li>
</ul>
<% end %>
Sources are arbitrary groups of related strings
Sources & String Grouping

<%= trh(source: 'common/navigation') do %>
<ul>
<li>Home</li>
<li>Features</li>
<li>Languages</li>
<li>Pricing</li>
<li>Docs</li>
</ul>
<% end %>
Translation Blocks
Entire blocks can be translated without markup.

<%= trh(source: 'common/navigation') do %>
<nav>
<ul>
<li>You have <a href=’/messages’>unread messages</a></li>
<li><a href=’/logout’>Logout</a></li>
</ul>
</nav>
<% end %>
Blocks
You have [link: unread messages]
You have unread messages

http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html
CLDR Pluralization Rules
(Common Locale Data Repository)

labels:
messages:
one: You have 1 message
other: You have {count} messages
<%= t('labels.messages', {count: 5}) %>
:rule => lambda { |n| n == 1 ? :one : :other }
Rails Code
en.yaml
messages.en.yaml
Pluralization in Rails using YAML
English

Rails Code
ru.yaml
messages.ru.yaml
Pluralization in Rails using YAML
Russian
labels:
messages:
one: У вас есть 1 сообщение
few: У вас есть {count} сообщения
other: У вас есть {count} сообщений
<%= t('labels.messages', {count: 5}) %>
:rule => lambda { |n|
n % 10 == 1 && n % 100 != 11 ? :one :
[2, 3, 4].include?(n % 10) &&
![12, 13, 14].include?(n % 100) ? :few : n % 10 == 0 ||
[5, 6, 7, 8, 9].include?(n % 10) ||
[11, 12, 13, 14].include?(n % 100) ? :many : :other
}

Pluralization in Rails using TML
English
<%= tr('You have {count || message}', {count: 5}) %>
You have 5 messages

Pluralization in Rails using TML
Russian Translation
'У вас есть {count || сообщение, сообщения, сообщений}'
У вас есть 5 сообщений

Data Token Full Definition
{count:number::ord || one: message, other: messages}
name context value options based on context ruleseparatorcase

Simplification through Configuration
{count:number || one: message, other: messages}
{count || message, messages}
{count || message}

Pluralization with TML
translations: [
{label: “You have one message”, context: {count: {number: ‘one’}},
{label: “You have {count} message”, context: {count: {number: ‘other’}},
]
<%= tr('You have {count} messages', {count: 5}) %>Rails Code
English Translations
Expanded Translations

Pluralization with TML
<%= tr('You have {count} messages', {count: 5}) %>Rails Code
Russian Translations translations: [
{label: “У вас есть {count} сообщение”, context: {count: {number: ‘one’}},
{label: “У вас есть {count} сообщения”, context: {count: {number: ‘few’}},
{label: “У вас есть {count} сообщений”, context: {count: {number: ‘other’}},
]
translations: [
{label: “‫אחת‬ ‫הודעה‬ ‫לך‬ ‫,”יש‬ context: {count: {number: ‘one’}},
{label: “‫הודעה‬ ‫שתי‬ ‫לך‬ ‫,”יש‬ context: {count: {number: ‘two’}},
{label: “‫הודעות‬ {count} ‫לך‬ ‫,”יש‬ context: {count: {number: ‘other’}},
]
Hebrew Translations
Expanded Translations

Numeric Rules Definition
English Rules:
Russian Rules: one: (&& (= 1 (mod @n 10)) (!= 11 (mod @n 100)))
few: (&& (in '2..4' (mod @n 10)) (not (in '12..14' (mod @n 100))))
other: (|| (= 0 (mod @n 10)) (in '5..9' (mod @n 10))
(in '11..14' (mod @n 100)))
one: (= @n 1)
other: (true)

Contextualization by Gender
Michael uploaded 3 photos
tr('{user} uploaded {count || photo}', {user: user, count: 3})
user = {name: ‘Michael’, gender: ‘male’}

Michael загрузил 3 фотографии
'{user || загрузил, загрузила} {count || фотографию, фотографии, фотографий}'
Russian Translation
dependant on gender of user dependant on value of count
male onefemale few many

<%= tr('{user} uploaded {count || photo}', {user: user, count: 3}) %>
Rails Code
Russian Translation (1 line)
'{user || загрузил, загрузила} {count || фотографию, фотографии, фотографий}'
Simplified

<%= tr('{user} uploaded {count || photo}', {user: user, count: 3}) %>
Rails Code
Russian Translations (by context)
translations: [
{label: “{user} загрузил {count} фотографию”, context: {count: {number: ‘one’}, user: {gender: ‘male’}},
{label: “{user} загрузил {count} фотографии”, context: {count: {number: ‘few’}, user: {gender: ‘male’}},
{label: “{user} загрузил {count} фотографий”, context: {count: {number: ‘other’}, user: {gender: ‘male’}},
{label: “{user} загрузила {count} фотографию”, context: {count: {number: ‘one’}, user: {gender: ‘female’}},
{label: “{user} загрузила {count} фотографии”, context: {count: {number: ‘few’}, user: {gender: ‘female’}},
{label: “{user} загрузила {count} фотографий”, context: {count: {number: ‘other’}, user: {gender: ‘female’}}
]
By Context

Possessive Case
Michael liked Anna’s post
“{actor} liked {target::pos} post”

Dative Case
Михаилу нравистся пост Анны
“{actor::dat} нравится пост {target::gen}”

Ordinals
This is your 2nd reminder
‘This is your {count::ord} reminder'

{date} = ‘{month_name} {days}, {years}’
Dates
English Date Format
tr('{user} was born on {date}', {user: user, date: user.birthday.tr(:verbose)})
%B = {month_name}
%d = {days}
%Y = {years}
Alex was born on July 4, 2002
verbose = ‘%B %d, %Y’ #July 4, 2002

Dates
Russian Date Format
Alex родился 4 Июля, 2002
“{user || родился, родилась} {date::gen}”
‘%d %B, %Y’ #4 Июль, 2002
{date} = ‘{days} {month_name}, {years}’

tr('[link: {user}] completed [bold: {count || mile}] on {user | his, her} last run.',{
user: [user, :name],
count: 3,
link: {href: ‘/profile’}
})
Mixing it all together
Michael completed 3 miles on his last run.

Mixing it all together
Russian Translation
Michael пробежал 3 мили в своем последнем забеге.
'[link: {user}] {user | пробежал, пробежала} [bold: {count || милю, мили, миль}]
в своем последнем забеге.'

Framework
Support
Translations can be shared across
multiple platforms and frameworks.

● Translations should be reusable across
multiple projects
● Each translation key can have many
translation options for a language based
on context
● Translation keys and translations are
unique and are only stored once in the
entire system
What is UTM?

Translation
Rankings
● Ranks are derived from user input
● Translators have ranks and voting powers
that change based on their input and
acceptable translations
● Translation usability score is derived from
how often the translation has been
locked in other projects
¡Hola Mundo!
hola mundo!
Hello Mundo
Hola World
Yo Mundo!
Que Paso, Mundo?
@!*#&
+45
+2
-2
-17
-55
-58
-99
Hello World!

+45
+22
+1
-99
Translator
Rankings
Translators have ranks and voting powers
that change based on their input and
acceptable translations.
Jenny Smith
Admin
Jeremy Swanson
Proofreader
Jessica Sawyer
Translator
Jake Stephens
Translator

Hello World Hola Mundo
안녕하세요
Привет Мир
Hallo Welt ‫עולם‬ ‫שלום‬
你好，世界
UTM Graph

Resources
SDKs https://github.com/translationexchange
Documentation http://translationexchange.com/docs
Blog http://blog.translationexchange.com
Sample App https://github.com/translationexchange/tml-rails-samples-foody
Live Sample App http://foody.translationexchange.com
Facebook https://www.facebook.com/translationexchange
Twitter @translationx
Feedback feedback@translationexchange.com

Translation Markup Language and Universal Translation Memory

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (8)

Destaque

Destaque (14)

Semelhante a Translation Markup Language and Universal Translation Memory

Semelhante a Translation Markup Language and Universal Translation Memory (20)

Último

Último (20)

Translation Markup Language and Universal Translation Memory