Today’s web and mobile app localization industry relies on numerous standards, libraries and file formats to facilitate the exchange between developers and translators. While some formats are somewhat sophisticated, others lack even the most basic features, like pluralization and contextualization. And most can’t offer support for more advanced localization features, like language cases. The most common localization formats include Gettext PO, PHP Arrays, Android XML, YAML, .Net RESX, iOS Strings and many others. A typical developer today works with many frameworks - for instance a Laravel backend app (PHP Arrays) with Ember front end (i18n JS) and iOS mobile app (Strings). Since all standards have distinct syntax, in many cases translations cannot be shared across applications. Translation Markup Language (TML) aims to solve both these problems by introducing a powerful extensible cross-platform syntax that offers support for pluralization, language contextualization, language cases, reusable decorators and much more. TML libraries are available for all major web and mobile platforms. TML allows translators to do in-context translations - where they can translate right from within the apps. TML libraries also eliminate the need for developers to ever deal with the resource files, as all extractions and translation substitution is done realtime and the resource files are only used as a transport between the apps and the Translation Exchange platform. Translation Exchange stores all translations in Universal Translation Memory (UTM), a graph database which stores all translations with their context, tone, rank and other attributes for accurate matching. This allows translations to be shared across all apps in the Translation Exchange Network. The translation memories of each app are extracted from the UTM graph and are managed by their individual localization teams. During this presentation we will look at some of the features of TML and how it can be used to quickly translate a Ruby on Rails application into any number of languages using in-context translation tools. We will also look at how the data is stored and shared across applications using UTM.

1. translationexchange.com
Powered by Translation Exchange
Translation Markup Language
for Ruby on Rails

2. Michael Berkovich
michael@translationexchange.com
@translationx
translationexchange.com

3. Localization is cumbersome
translationexchange.com

4. There are many
standards, but little
guidance.
“

5. 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

6. 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
Rails YAML .yaml
Subtitles .srt
MicroDVD .sub
Subviewer .sub
Mozilla Web L10N
Text .txt
CSV Spreadsheet
Excel Spreadsheet
Word Document

7. 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

8. 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

9. How can we make it
BETTER FOR
EVERYONE

10. 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

11. あ
A
Translation Management
Service
Global CDN
Local Cache
Application
with SDK
A Better Way
A truly automated and continuous localization

12. Translation Caching
static and dynamic cache adapters for
storing translations in your application
Inline Translation Tools
Translation can be done in context of the
application
Access Professional Translators
Connect your application to thousands of
professional translators around the world
Open Source
all SDKs are available on github
Multiple Platforms
support for Rails, Node, PHP, Python, iOS,
Android and more
Universal Translation Memory
Translations are shared across all
applications
translationexchange.com
Core Benefits

13. Getting Started
translationexchange.com

14. gem 'tml-rails'
Integration
# Gemfile
translationexchange.com

15. Configuration
# initializers/tml.rb
Tml.configure do |config|
config.application = {
key: “YOUR_APPLICATION_KEY”
}
end
translationexchange.com
# layouts/application.html.erb
<%= tml_scripts_tag %>
<%= tml_language_selector_tag(:flags) %>

16. Translation Markup Language
Developer friendly syntax for marking up application content.
Supports language context rules and language cases, making translations
significantly more accurate for any language.
translationexchange.com

17. Hello World
<%= tr('Hello World') %>
translationexchange.com
Translation Markup Language

18. tr('Eats shoots and leaves', 'a panda')
Eats shoots and leaves
tr('Eats shoots and leaves', 'a violent restaurant patron')
Translation Markup Language
Description & Context

19. Hello Michael
translationexchange.com
Translation Markup Language
Data Tokens & Interpolation
<%= tr('Hello {name}', {name:'Michael'}) %>

20. Hello Michael
<%= tr('Hello [bold: {user}]', {
user: current_user
}) %>
translationexchange.com
Translation Markup Language
Decoration Tokens

21. Hello Michael
<%= tr('Hello <strong>{user}</strong>', {
user: current_user
}) %>
translationexchange.com
Translation Markup Language
Decoration Tokens

22. Hello Michael
<%= tr('Hello [bold: {user}]', {
user: current_user,
bold: '<strong>{$0}</strong>'
}) %>
translationexchange.com
Translation Markup Language
Decoration Tokens

23. You have 5 messages
<%= tr(You have {count || message}', {
count: 5
}) %>
translationexchange.com
Translation Markup Language
Pluralization

24. Michael uploaded 3 photos
<%= tr('{user} uploaded {count || photo}', {
user: current_user,
count: 3
}) %>
translationexchange.com
Translation Markup Language
Pluralization

25. Michael liked Anna’s post
<%= tr('{actor} liked {target::pos} post', {
actor: current_user,
target: other_user
}) %>
translationexchange.com
Translation Markup Language
Language Cases

26. This is your second warning
<%= tr(This is your {count::ord} warning', {
count: 2
}) %>
translationexchange.com
Translation Markup Language
Language Cases

27. Michael completed 3 miles on his last run.
<%= tr('[link: {user}] completed [bold: {count || mile}]
on {user | his, her} last run.', {
user: current_user,
link: { href: user_path },
count: 3
}) %>
translationexchange.com
Translation Markup Language

28. Demo
❏ Use TML SDK to localize an online recipes application
❏ Demonstrate crowdsourced localization tools
❏ Deploy translation release and update application realtime
❏ Download release snapshot and run Foody independently from the
service
translationexchange.com

29. How is Translation Done?
translationexchange.com
Machine Translation
provided by Google,
Microsoft and Yandex.
Translations are ranked to
get the best result.
Crowdsourced Translation
Some developers may
choose to use their own
users to translate their
content, similar to how
Facebook and Twitter
translated their sites.
Professional Translation
Order are received and
processed by our partners
and are made available in our
system within hours.

30. Caching Options
translationexchange.com
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.
$ bundle exec rake tml:cache:generate
Dynamic Cache
Redis, Memcached (and others) updated
from CDN release. Cache is shared
across all processes. Can be deployed
without restarting servers.
$ bundle exec rake tml:cache:upgrade

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

32. Thank You
Find out more at translationexchange.com
translationexchange.com