Markdown

Markdown comes in many flavors. The one that is supported by Smartling is the GitHub flavor of markdown. If you’re unsure which flavor of Markdown you are using, someone on your technical team should know.

Before uploading your Markdown file to Smartling, be aware of the following:

Markdown translation is accomplished by transforming content into HTML so that it can be manipulated in translation tools and viewed in context with ease. Once translation is complete, the content is converted from HTML back into Markdown while the translated content is downloaded. As a result, your original Markdown document may differ in some ways from what is downloaded in the translated documents.

During the translation process, Smartling will try to maintain the same visual layout of your file but can’t guarantee that there won’t be some noticeable differences. Some post processing may be required to return the same formatting as the original document.

Below are some examples of known differences in the translated document.

Examples:

Alternate Codes

Most Markdown styling can be represented by different Markdown code sequences (or character sequences). One code sequence will be consistently returned for any given style. For example:

H1 and H2 headers:

Original

Downloaded

# Header 1## Header2

Header 1=======Header 2-------------

Italic and bold:

Original

Downloaded

Text with _Italic_, __bold__, *Italic* , **bold**

Text with *Italic*, **bold**, *Italic* , **bold**

Formatting of code blocks is returned with an indentation style:

Original

Downloaded

```public void main(){// body}```

public void main(){// body}

Escaping

The following characters are escaped with a backslash '\' in the downloaded file if they’re in the translated text: