<commit_before>---

copyright:
  years: 2015, 2016

---

{:new_window: target="_blank"}
{:shortdesc: .shortdesc}
{:screen:.screen}
{:codeblock:.codeblock}


# Machine translation tips
{: #globalizationpipeline_tips}

*Last updated: 27 March 2016*
{: .last-updated}

Machine translation can be effective at providing an approximation of the source text's meaning. However, the quality and usefulness of machine translation varies greatly depending on the target language and the machine translation engine that you use. One of the key factors in the quality of machine translation is the quality of the source itself. Source text that is loaded with colloquialisms, incomplete sentences, incorrect punctuation, and ambiguous words and phrases might not be translated accurately.
{:shortdesc}

When you are creating your {{site.data.keyword.Bluemix_notm}} app UI, follow a few basic writing guidelines to improve not only your source language, but also the quality of the machine translation.

In addition, ask native language speakers to review and edit the machine translation. Also, gather feedback from your app users; they are perhaps the best judges of the usefulness and accuracy of the translation.

## Writing style tips
{: #writingstyletips}

* **Use short- to medium-length simple sentences (5 - 20 words):** Machine-translation engines often have difficulty translating compound and complex sentences, including sentences with semicolons. Convey one thought per sentence. If a sentence contains two active verbs to convey two thoughts, break the sentence down into two sentences. Machine-translation engines also have trouble parsing sentences that are too short to provide enough context.
* **Avoid phrases:** Use complete sentences whenever possible. Phrases are acceptable for headings and subheadings, but avoid telegraphic headline-style writing. Use complete sentences to introduce lists.
* **Avoid idioms, slang, and jargon:** Replace phrases for which literal translations make no sense. For example, replace "on the fly" with "dynamic," "on the other hand" with "alternatively," and "keep in mind" with "remember."
* **Avoid humor, sarcasm, colloquialisms, emoticons, and metaphors.**
* **Be succinct:** Remove unnecessary text and redundancies. For example, replace "It is useful to remember that large values increase the response time" with "Large values increase the response time."
* **Avoid sentences that are written completely in the upper-case:** Capitalization provides clues to the meaning of the word. For example, if you write "BILL", the machine-translation engine cannot determine if you meant the name "Bill" or the word "bill."
* **Avoid ambiguous words:** For example, do not use "once" in place of "after" or "when." Do not use "while" in place of "although" or "whereas." Do not use "may" when you mean "might" or "can."
* **Avoid pronouns:** Repeat nouns or noun phrases when possible. The pronoun "it" is particularly problematic.
* **Write in active voice when possible:** Active sentences are usually clearer than passive sentences. For example, write "The utility determines which path is most efficient" instead of "The most efficient path is determined."
* **Avoid culturally specific information.**
* **Be aware that machine translation engines might translate product names:** Many countries retain the original English product name, but machine translation engines might try to translate product names, especially if the names contain real words. Before you use a product name, test the translation of it. If you find problems, modify the text or translation accordingly.
* **Ensure that all information is written in one language:** Machine-translation engines might assume that all information is in a single language, even if the text includes one or two words in another language. For example, if the text includes "en route" (French), the machine translation engine still tries to translate those words as if they are English words.
* **Avoid marketing slogans:** Marketing slogans often rely on the audience's understanding of a particular culture. Avoid these kinds of slogans because machine translation engines are likely to have trouble translating them accurately.
* **Ensure that list items are complete and parallel:** For example, if one item begins with a verb, make sure that all items begin with a verb.
* **Avoid using please and thank you:** These words can seem out of place or even patronizing in some cultures.
* **Write dates in non numeric format:** Numeric date formats vary depending on country. Write out the month name, day, and year. For example use 1 September 2003 instead of 9/01/03, which might be interpreted as either 1 September 2003 or as 9 January 2003.
<commit_msg>update "last-updated" time to GA date<commit_after>---

copyright:
  years: 2015, 2016

---

{:new_window: target="_blank"}
{:shortdesc: .shortdesc}
{:screen:.screen}
{:codeblock:.codeblock}


# Machine translation tips
{: #globalizationpipeline_tips}

*Last updated: 12 July 2016*
{: .last-updated}

Machine translation can be effective at providing an approximation of the source text's meaning. However, the quality and usefulness of machine translation varies greatly depending on the target language and the machine translation engine that you use. One of the key factors in the quality of machine translation is the quality of the source itself. Source text that is loaded with colloquialisms, incomplete sentences, incorrect punctuation, and ambiguous words and phrases might not be translated accurately.
{:shortdesc}

When you are creating your {{site.data.keyword.Bluemix_notm}} app UI, follow a few basic writing guidelines to improve not only your source language, but also the quality of the machine translation.

In addition, ask native language speakers to review and edit the machine translation. Also, gather feedback from your app users; they are perhaps the best judges of the usefulness and accuracy of the translation.

## Writing style tips
{: #writingstyletips}

* **Use short- to medium-length simple sentences (5 - 20 words):** Machine-translation engines often have difficulty translating compound and complex sentences, including sentences with semicolons. Convey one thought per sentence. If a sentence contains two active verbs to convey two thoughts, break the sentence down into two sentences. Machine-translation engines also have trouble parsing sentences that are too short to provide enough context.
* **Avoid phrases:** Use complete sentences whenever possible. Phrases are acceptable for headings and subheadings, but avoid telegraphic headline-style writing. Use complete sentences to introduce lists.
* **Avoid idioms, slang, and jargon:** Replace phrases for which literal translations make no sense. For example, replace "on the fly" with "dynamic," "on the other hand" with "alternatively," and "keep in mind" with "remember."
* **Avoid humor, sarcasm, colloquialisms, emoticons, and metaphors.**
* **Be succinct:** Remove unnecessary text and redundancies. For example, replace "It is useful to remember that large values increase the response time" with "Large values increase the response time."
* **Avoid sentences that are written completely in the upper-case:** Capitalization provides clues to the meaning of the word. For example, if you write "BILL", the machine-translation engine cannot determine if you meant the name "Bill" or the word "bill."
* **Avoid ambiguous words:** For example, do not use "once" in place of "after" or "when." Do not use "while" in place of "although" or "whereas." Do not use "may" when you mean "might" or "can."
* **Avoid pronouns:** Repeat nouns or noun phrases when possible. The pronoun "it" is particularly problematic.
* **Write in active voice when possible:** Active sentences are usually clearer than passive sentences. For example, write "The utility determines which path is most efficient" instead of "The most efficient path is determined."
* **Avoid culturally specific information.**
* **Be aware that machine translation engines might translate product names:** Many countries retain the original English product name, but machine translation engines might try to translate product names, especially if the names contain real words. Before you use a product name, test the translation of it. If you find problems, modify the text or translation accordingly.
* **Ensure that all information is written in one language:** Machine-translation engines might assume that all information is in a single language, even if the text includes one or two words in another language. For example, if the text includes "en route" (French), the machine translation engine still tries to translate those words as if they are English words.
* **Avoid marketing slogans:** Marketing slogans often rely on the audience's understanding of a particular culture. Avoid these kinds of slogans because machine translation engines are likely to have trouble translating them accurately.
* **Ensure that list items are complete and parallel:** For example, if one item begins with a verb, make sure that all items begin with a verb.
* **Avoid using please and thank you:** These words can seem out of place or even patronizing in some cultures.
* **Write dates in non numeric format:** Numeric date formats vary depending on country. Write out the month name, day, and year. For example use 1 September 2003 instead of 9/01/03, which might be interpreted as either 1 September 2003 or as 9 January 2003.

{'fraction_non_alphanumeric': 0.06349039773323539, 'fraction_numerical': 0.007765767656627138, 'mean_word_length': 5.050793650793651, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1674046', 'n_tokens_mistral': 2252, 'n_tokens_neox': 2107, 'n_words': 1371}