“Go global by going local.” That phrase, or some variation on it, gets tossed around a lot – it’s almost become its own buzzword (buzzphrase?) – but it’s a crucial concept in localizing website and apps. Imagine walking into a grocery store, where all the items are labeled in English, but the prices are listed in rubles. Well, that’s helpful.
Localizing your app or website – currencies, dates, time, temperatures, addresses, etc. – helps your business blend seamlessly into the user’s online experience. It also helps avoid ambiguity, like this date: 6/7/2011. You probably read it as June 7th, 2011, but other nationalities read it as July 6th, 2011. You don’t want the user to wonder which date is the right one; you want them to trust that you’ve given them the best user experience possible – and that means localization.
Simplifying Localized Content
Say you want to swap a paragraph. All you need to do is tag the resource HTML with “SL_swap” and a unique ID.
<p>This is a swap. What happens to it?</p>
<span class=”SL_swap” id=”localize_text”><p>This is a swap. What happens to it?</p></span>
Smartling’s Translation Delivery Network will ingest the content and place it into the Localized Content section of the dashboard. Nice and tidy.
Choose the language from the drop-down menu to localize for that language. So, in this case, I’ll pick French. I’ll change my text to whatever I’d like:
Now, I’ll click Save to save the change and send it to be translated.
What if I don’t want the content to be translated? Maybe it’s an image, or content that’s been translated already. In that case, I’ll select Do Not Translate, then click Save, to save the change without sending it to be translated. Done.
Now, go forth and localize! You know, the simple way.