Salesforce

Are.*ts files (Video Transport Stream files) supported in WorldServer?

« Go Back

Information

 
TitleAre.*ts files (Video Transport Stream files) supported in WorldServer?
URL Name000022925
SummaryVideo Transport Stream files in *.ts format are not supported per default in WorldServer or Trados Studio. However, depending on the content of the files, a file type configuration can be created to segment these files. This article provides some instructions.
Scope/EnvironmentWorldServer
Question
Does World Server support *.ts (Video Transport Stream) files?
Answer
Video Transport Stream files in *.ts format are not supported per default in WorldServer or Trados Studio. However, depending on the content of the files, you can follow these steps:
  1. Build a custom Regular Expression Delimited Text file type filter in Trados Studio. A basic filter (which can process simple .ts documents) is attached to this article. You can further customize this filter if needed. You can also build a different type of filter in Trados Studio, for instance, an XML 2 file type configuration where you leave only source elements as translatable and set others if needed as not translatable.
  2. Once you have tested your filter configuration in Trados Studio and confirmed that all the translatable content is being extracted, export the File Type configuration to an *.sdlftssettings file and import the File Type configuration into your WorldServer environment.
  3. Once the configuration is imported, add a Mime Type for the *.ts file. You can do so by going to Management > Administration > Customization and in the drop-down menu next to Custom component type: selecting Mime Types. The Mime Types page will open.
  4. Click on Add to add a new Mime Type as displayed in this screenshot. Once done, click OK
User-added image

If you need assistance with configuring your File Type to segment your *.ts file correctly, please resort to our Professional Services department for them to provide a fully customized and supported solution.
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by