XLIFF

entity_escaping

• auto (default) 
• true
• yes 
• false
• no

(case-insensitive)

Controls whether base characters ( > < & " ) are "escaped" into entities when delivering translations. This can be set universally for the whole file via API, or by setting the directive at the top/start of the file. The directive can also be placed inline to control the behavior of specific strings.

For example, your translation might look like this:
This is an <hr> & " example string4

By default, using the "auto" setting, we will assume this is HTML from the <hr> tag.

When the translated file is downloaded, the translated string will be escaped as:
This is an <hr> &amp; &quot; example string4

Using <!-- smartling.entity_escaping = false --> will allow is above string to appear unescaped.

entity_escaping_type

• html4 (default)
• html5

(case-insensitive)

By default, all html4 entities are unescaped, except the basic set: &lt; &gt; &amp; &quot;.

When this directive is set to html5, all html5 entities will be unescaped as well.

<!-- smartling.entity_escaping_type = html5 -->

entity_escaping_strategy

• none (default)
• propagate

(case-insensitive)

Used to retain entity escaping for all non-base entities. For example, normally we turn &copy; into © but if we use this new directive the translation will automatically update to use escaping from the source. For each entity character, we'll check to see if it was escaped in the source and try to match (propagate) it in the target.

If HTML5 entities are required as well, you must use the entity_escaping_type=propagate directive.

Numerical entities are not considered at all with this directive, and are treated normally.

<!-- smartling.entity_escaping_strategy = propagate -->

If the same character is both escaped and unescaped in the same string, propagate will return the characters in the translation escaped in the same order as they were in the source. However, if there are a different number of characters in the translation where the translation process removed or added some and the escaping is inconsistent among them, propagate will escape all entities for that character.

This does not affect source content at all - so using it will not result in new strings.

propagate will only affect non-base entities - all named entities except &amp; , &quot;, &lt;, &gt;. Base entities continue to be controlled by HTML detection and the entity_escaping directive.

placeholder_format

• NONE
• C
• IOS
• PYTHON
• JAVA
• YAML
• QT
• RESX

Used to specify a standard placeholder format.

<!-- smartling.placeholder_format = IOS -->

Specifies iOS-style placeholders for the file.

placeholder_format_custom

• Custom (Java Regex)
• NONE - disables any current custom placeholders.

Specifies a custom placeholder format. Any text in your file matching the regular expression you provide will be captured as a placeholder.

See Placeholders in Resource Files for more on placeholders.

<!-- smartling.placeholder_format_custom=\{([^}]+)\} -->

Any characters surrounded by curly brackets, e.g., {first name}, will be treated as a placeholder.

pseudo_inflation

Integer values between

0 - 100

Sets the percentage by which original strings are inflated when downloading pseudo translations. If this directive is not set, pseudo translations are 30 percent longer than the original strings.

<!-- smartling.pseudo_inflation = 80 -->

Downloaded pseudo translations will increase the length of original strings by 80 percent.

• NONE
• HTML
• PLAIN_TEXT
• MARKDOWN

Control trans-unit level HTML parsing.  If this is set to HTML a single trans-unit can be ingested by Smartling as multiple strings, depending on block level tags. 

<!-- smartling.string_format=html -->

<trans-unit id="HTML string1">
 <source>&lt;p>&lt;div>String1 div1.&lt;/div>&lt;div>String1 div2&lt;/div>&lt;/p></source>
</trans-unit>

<!-- smartling.string_format=html -->
<trans-unit id="HTML string2">
 <source>&lt;p>&lt;div>String2 div1&lt;/div>&lt;div>String2 div2&lt;/div>&lt;/p></source>
</trans-unit>

<!-- smartling.string_format=none -->
<trans-unit id="HTML string3">
 <source>&lt;p>&lt;div>String3 div1.&lt;/div>&lt;div>String3 div2&lt;/div>&lt;/p></source>
</trans-unit>

<p><div>String1 div1</div><div>String1 div2</div></p>

String2 div1

String2 div2

<p><div>String3 div1</div><div>String3 div2</div></p>

whitespace_trim

• on (default)
• yes
• true
• off
• no
• false
• leading
• trailing

A whitespace is any character or series of characters that represent horizontal or vertical space in typography. When rendered, a whitespace character is not a visible mark, but does occupy an area or space on a page.

Although whitespaces are necessary within a string (typically to separate words), unnecessary whitespaces can be found at the start of a string (leading) and at the end of a string (trailing).

With this directive, you can manage whitespace trimming.

By default, the leading and trailing whitespaces are trimmed.

You can choose to disable trimming or specify trimming for leading or trailing whitespaces.

The directive can be used inline or as the API request parameter.

<!-- smartling.whitespace_trim=on-->

Smartling will trim leading and trailing whitespaces (default)

<!-- smartling.whitespace_trim=off -->

Smartling will not trim leading or trailing whitespaces

<!-- smartling.whitespace_trim=leading -->

Smartling will trim only leading whitespaces

<!-- smartling.whitespace_trim=trailing -->

Smartling will trim only trailing whitespaces

Content inside the listed custom tags will be captured as a placeholder. 

<!-- smartling.xliff_tags_to_placeholders = g, mrk, ept, bpt -->

g, mrk, ept, and bpt will be captured as tags.