Gengo works best when you send simple text for translation. This doesn't mean you can't localize your site or app with us. If your text contains some HTML code, or any other element that do not need translating, simply apply a few workarounds and you'll be set. 

Excluding Texts

First, make sure to use the triple-bracket method to exclude texts from the word count. For HTML, they're not counted by our system so you can leave them as is. 

Sending File Jobs

If you send us a file to translate, whatever the content looks like will be the exact same thing the translator will see. So if it contains a lot of HTML or if it's grabbed straight from an XML file, translators may not recognize what needs to be translated. File jobs work best for key-value pairs. For example, take a spreadsheet and put key on column A and values on column B. If necessary, hide column A so our system doesn't charge you for them.  

Sending Text Jobs

Text jobs work best if you have a little bit of HTML in your content. When you send plain texts for translations, our translators use our in-house workbench. Here, HTML is deflated and replaced with bracketed numbers. For example:

What you send us:  I like <strong>cheese</strong>

What the translator sees:  I like {1}cheese{/1}.

Translation: 私は{1}チーズ{/1}が好きです

What you get back: 私は<strong>チーズ</strong>が好きです


For content pulled from XML, YAML, or any other similar format, trying to hack it together to order through Gengo can be tedious. If so, you might find greater success through our partners below, who specialize in extracting translatable content and forwarding it to us:





If you have a site powered by WordPress and are looking for a Gengo plugin to make translations easier, have a look at two of the most used below.


Transfluent Wordpress plugin


Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk