Preparing & Translating Supported File Types

WebVTT

Extension .vtt
Smartling Identifier vtt
Example File subtitle.vtt
Resources W3.org - WebVTT

 

File directives for API Service configuration parameters are listed below. Inline directives are not supported.

 

Markup (HTML tags and formatting) is now supported for VTT translation in the CAT Tool. The file must contain the code of the tags as follows; <b></b> for the Bold tag, <i></i> for the italics tag and <u></u> for the underline tag. Any variations will fail. The translation VTT file will include the tags, unescaped.

Directives

File directives are supported, both inline and via our APIDirectives are specified in comments within the files, in the following format:

Inline File Format

smartling.[directive_name] = [value]

API Parameter

smartling.[directive_name] = [value] 

Here are some examples of [directive_name], along with example values or paths.

vtt_key_type

Value  id | time_range
Description 

Change the key detection type.

Default: time_range

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.

Examples 

smartling.vtt_key_type = id

smartling.vtt_key_type = time_range

 

vtt_variant_type

Value  id | time_range
Description 

Change the variant detection type.

Default: time_range

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.

Examples 

smartling.vtt_variant_type = id

smartling.vtt_variant_type = time_range

 

whitespace_trim

Values 

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

The default value is on

Description 

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 be used inline or as the API request parameter.

Examples 

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

 

entity_escaping_type

Exact delivery depends on file type.

Values

html4 (default)|html5

(case-insensitive)

Description

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.

Examples

smartling.entity_escaping_type = html5 

 

entity_escaping_strategy

Values propagate | none
Description

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 directive can be placed inline, in the API or in a template (consult your SA about configuring directive templates).

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.

Examples

To use inline:
smartling.entity_escaping_strategy = propagate

XML Characters (always escaped)

Character (name) Escape sequence

< (less-than)

&lt;

> (greater-than)

&gt;

& (ampersand)

&amp;

' (apostrophe or single quote)

&apos;

" (double-quote)

 &quot;

 

Video Tutorial: Translating Video Subtitles in Smartling


Timestamps:

Step 1: Create a .srt or .vtt file 00:06
Step 2: Check the segmentation
00:51
Step 3: Upload the subtitle file to Smartling
02:06
Step 4: Upload the video as visual context
02:45
Step 5: Authorize the job
03:34
What your linguists see
03:45
Step 6: Download the completed translations
04:14
Step 7: Add the translated subtitles to your video
04:32
   a. Closed captions
04:41
   b. Open captions
04:56
Help & Support
05:08

Was this article helpful?