Tag: best practices

Advertisement
Weglot

Minimum Viable Product: Globalization

Personalization and Design, Translation Technology

Yes, been waiting to get a Silicon Valley-style allusion to MVP (Minimum Viable Product) into a blog post for ages. And now, thanks to Java and Android guru and i18n veteran John O’Conner (@joconner), here it is:

The Absolute Minimum You Need to Know About Internationalization

A simple, straightforward and understandable list of the key things that developers, designers and product folks need to know to make a product ready for successful global launch. What a contrast to those hectoring tl;dr i18n tomes we’ve had to deal with at times (and we wonder why nobody heeds the advice?)

We’ve come a long way since this example of major #i18nfail I encountered in 1996 (a real case with content changed to protect the starry-eyed innocents of the day):

I18n challenge 1996-style. A real-world example.

I18n challenge 1996-style. A real-world example. Example from the AGIS 2009 Conference Internationalization and Translatability for Beginners workshop.

But not far enough.

Let’s see more posts like John’s to remind us about what’s important and to make it less scary for emerging technologies and startups to understand and integrate internationalization requirements into their processes.

Tags:, , , , , , , ,
+ posts

Ultan Ó Broin (@localization), is an independent UX consultant. With three decades of UX and L10n experience and outreach, he specializes in helping people ensure their global digital transformation makes sense culturally and also reflects how users behave locally.

Any views expressed are his own. Especially the ones you agree with.

Advertisement

Related News:

Advertisement

Don't Translate, Won't Translate

Translation Technology

How do you indicate non-translatable parts of a translatable string? I’m interested in your best practises and advice.

Let’s assume the file format concerned is XML, and XLIFF at that. And let’s also assume these source strings are in English and must be optimized for as much translation automation as possible (MT, TM, other string leveraging techniques, and so on).

I would have thought the obvious solution was to do something like use the mrk element in the source segment. For example:

<source>Please translator, do not translate the word <mrk mtype=”protected”>Groovy</mrk>. The word <mrk mtype=”protected”>Groovy</mrk> refers to an agile dynamic language for the <mrk mtype=”protected”>Java</mrk> platform and should remain in English.</source>

How would you do it given the assumptions above?

Tags:, , ,
+ posts

Ultan Ó Broin (@localization), is an independent UX consultant. With three decades of UX and L10n experience and outreach, he specializes in helping people ensure their global digital transformation makes sense culturally and also reflects how users behave locally.

Any views expressed are his own. Especially the ones you agree with.

Related News: