Localize your apps and content more easily – new formats in Translator
      Toolkit
    
    
    
    
    By Chris Yang, Product Manager and Haidong Shao, Software
      Engineer, Translator Toolkit
      
      
      Cross-posted with the Google
      Open Source Blog and the Google
      Translate Blog
      
      At Google, we put a lot of energy into helping localize the world's information to make it
      more useful to more people. It's not just about localizing our own products – we want to
      provide tools that make it easy for translators and developers around the world to localize
      their own apps and content. 
Google Translator Toolkit is our 
online
      translation tool for amateur and professional translators -- it’s built on 
Google Translate and supports
      more than 100,000 language pairs.
      
      This week, the Translator Toolkit team has launched support for four new translation-related
      file formats:
      
 •
 Android Resource (
.xml)
      
 •
 Application Resource Bundle
      (
.arb)
      
 •
 Chrome Extension (
.json)
      
 •
 GNU gettext-based (
.po)
      
      With these new file formats, you can use Translator Toolkit to localize your apps and other
      products and content much more quickly and easily.
      
      For example, to translate your Android application, go into the res/values directory and
      upload strings.xml into Translator Toolkit -- Translator Toolkit will now automatically
      translate it. You can then 
share
      your translations with amateur or professional translators, who can localize the text using
      Translator Toolkit’s 
WYSIWYG
      online editor.
      
      
      
      
      When you’re finished, you can 
export
      your translated application and store it in a locale-specific directory in Android. Voilà --
      easy localization! 翻译起来太方便了!
      
      In addition, we’ve made the Translator Toolkit interface more intuitive for these new file
      formats so users can translate faster and more accurately. For example, you can turn on
      ‘Customized colors’ so translators can annotate the edited segments, ‘Number of characters in
      the segment’ to make sure the text doesn’t run too long (very important for mobile devices),
      and ‘Synchronized scrolling’ so you can scroll the original and translated text at the same
      time, which makes navigation much easier.
      
      
      
      
      With these new file formats and UI features, along with the 
file
      formats we already support (.aea, .srt, .html), we hope Translator Toolkit can help
      you reach more users around the world.
      
      When you’re ready, give Google Translator Toolkit a try and 
suggest any improvements you’d like to see so we can work on
      making it even better.
      
      
      
Chris
      Yang and Haidong Shao are on the Google Translation Toolkit team.
      
      
      Posted by Scott Knaster,
      Editor