WebVTT

< (less-than)

&lt;

> (greater-than)

&gt;

& (ampersand)

&amp;

' (apostrophe or single quote)

" (double-quote)

Parse the strings in the VTT file based on sentence markers, instead of by timestamp entry.

00:27:44.430 --> 00:27:46.680 align:middle line:84%
You can either keep
it an endurance push

00:27:46.680 --> 00:27:50.250 align:middle line:84%
for the rest of this, take
it to your max and hold,

00:27:50.250 --> 00:27:52.500 align:middle line:90%
or you can add little bits.

00:27:52.500 --> 00:27:53.910 align:middle line:90%
What are we not doing?

00:27:53.910 --> 00:27:54.820 align:middle line:90%
Going to 50.

If vtt_mt_mode=on each sentence will be parsed as one string, resulting in three strings in Smartling. This allows the content to be machine translated and generates translation memory leverage. 

If vtt_mt_mode=off each timestamp entry will be parsed as one string, resulting in five strings in Smartling. 

• 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.

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.

The default is none which is the current behavior, which recognizes HTML4 entities only - if HTML5 entities are required as well, you must use the entity_escaping_type=propagate directive.

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.

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.

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.

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. 

If you choose to set this directive to html5, you must also use the entity_escaping_strategy=propagate directive

smartling.entity_escaping_type = html5

force_inline_for_tags

A comma-separated HTML tag list

This parameter forces the HTML parser to treat the listed tags as inline. The difference between block and inline tags is that block tags are used to split HTML into strings, whereas inline tags are included in strings.

smartling.force_inline_for_tags = external_link,reference

Any <external_link> or <reference> tags will be parsed as inline tags. Smartling will not create separate strings for content in these tags.

vtt_key_type

• time_range (default)
• id 

This directive can change the key detection type.

time_range = time range is treated as a key.

ID = cue id or caption will be treated as a key.

If the value is id, but the caption for a cue is not present - the key for the cue is null.

smartling.vtt_key_type = id

smartling.vtt_key_type = time_range

vtt_variant_type

A comma-separated HTML tag list

This directive can change the variant detection type.

time_range = time range is treated as a variant.

ID = cue id or caption will be treated as a variant.

If the value is id, but the caption for a cue is not present - the variant for the cue is null.

smartling.vtt_variant_type = id

smartling.vtt_variant_type = time_range

whitespace_trim

on|yes|true or off|no|false or leading|trailing

The default value is on.

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 trim whitespaces, as it enables or disables whitespace trim management for the ingested strings.

Whitespace is optionally trimmed from content then re-inserted on download for convenience so that translators do not have to manage the extra spaces. However, content owners may want to retain surrounding whitespace so that translators can
manipulate it during translation.

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 only be used 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