By Trados AppStore Team




Sometimes there is a need to be able to extract some segments from a file, or multiple files, and send them as a single file to others. Sometimes there is a need to open all the files in a virtual view and then save them as a single file to share with others. Sometimes you don't want to open the files at all, but you might want to split them or merge them to send to others.


The solution to all of these requirements is studioViews. This application will not only allow you to export from the files view, filtered selections in the Editor view, or plain and simple segment selection, but it also allows you to import the translated file you exported back into your project and will update your files accordingly. The exported file is an SDLXLIFF and fully supports all the features of SDLXLIFF (segment statuses, match values, tracked changes etc.).

To learn how to use this application, please check the Documentation tab.

Technical details - Trados Studio 2022 (SR1)


  • Introduced a new service to calculate the Word counts at a segment level
  • Removed dependency on Toolkit

Checksum: f5bead4f08c385f9c5011c7a306af0acd3e70059e37743851011fcbc05d0736d

Release date: 2023-09-26 - Trados Studio 2022


  • Resolved a bug where referenced sub segments were not included in the exported split files

Checksum: 61c3593e0c71e821b16494b6b1b7984660fa35d303fb54f01475f0e5f08f632c

Release date: 2023-07-24 - Trados Studio 2021

No related information.


After installing the plugin you gain access to it in two different places, the Files View and the Editor View which are addressed below.  

Files View

You can select one or more files and right-click (the image below is shortened for convenience) where you will find two menu items:

  • Import into the selected files
  • Split the selected files

Split the selected files

In practice you would most likely use the "Split into selected files" first and this brings up the following menu:

If you have used the "Spit and Merge" application from the SDL AppStore these options will be familiar for you. The "Split" operation allows you to do two important things:

  • split the selected files by wordcount, by equal parts or by segment ids
  • merge the selected files

split the selected files by wordcount, by equal parts or by segment ids

"Split by word count": you specify the maximum number of words you want in each file and the application will split the files to the nearest segment.

"Split by equal parts": you specify how many files you'd like the selected file(s) to be split into and the application will split the files to the nearest segment.

"Split by ids": you specify the segment ID numbers separated by a comma, for example with an 800 segment file you could use this list of ids:


The application will split the file(s) into five files.






merge the selected files

There is no obvious option for merging so this requires additional explanation. If you have multiple files in your project you could merge them all into one SDLXLIFF by entering "1" into the "number of equal parts" field:

This effectively allows you to merge files after the project has been created, so it's not only something you have to consider when the project is initially created.

The naming convention for the output is managed with a simple mask feature, the default being:


You define the mask and the location for the "split" files in the Output panel here:

The [####] will create a number with four digits when the files are "split". So if I split the files I selected into three files I would have three files like this:




I could rename them as I see fit so if I wanted the name to be different and the number to only have three digits and have it at the start I could create a mask like this:


Import into the selected files

This feature allows you to import the updated SDLXLIFF files you previously "split". The older Split and Merge application physically split the files and then merged them back together again. studioViews doesn't take this approach and is more robust as a result. studioViews replaces the updated segments in the original project files with the ones that were updated from the split files. All supported features are retained:

  • match values
  • statuses
  • locked segments
  • tracked changes
  • etc.

When you select the import feature you will be presented with this window:

It doesn't matter whether you have selected the exact files you "split" originally to import into or not. You can select all the files in your project and right-click to import. The application is smart enough to know which segments you are updating and will only update the appropriate segments in the appropriate files. You can also choose to ignore the updates to segments based on statuses, type of matches or locked. You do this by adding the criteria into the "Ignore Existing Segments" part. The image above shows "Locked" which is the default setting. This will prevent changes made to locked segments in the "split" files from being imported into locked segments in the original.

Once the import is successfully completed you should see a "Task Result" window similar to this:

The report that is created is a simple log file that provides information on which files were imported and some statistics around what was updated, for example:

The original project files are also saved by appending the original files with .Backup_####.sdlxliff so you can always revert to the original if you're unhappy with the result.

Editor View

The Editor View provides a similar, although in many ways more functional approach to the features in the Files View. First of all you need to activate the View for studioViews by clicking on the icon in the View menu when you have opened a file in the Editor View:

This will open a new view to Trados Studio which you can position wherever you wish. For example:

This view has two tabs:

  • Export
  • Import


The Export tab allows you to export selected or visible segments to an SDLXLIFF file in a location of your choosing.

Selected segments

These would be segments that you have selected in the Editor by holding down the Ctrl or Shift key (or by using the keyboard). For example, here I have selected segments #3, #5, #7, #8, #9 and #12:

It doesn't matter how many files you have opened in the Editor, you can select whatever you wish.

Visible segments

These would be segments that are currently visible in the Editor view. So if you have filtered on this using the Advanced Display Filter for example then you may have something like this:

Here I filtered on 10 of the 82 segments in my two files that are open in the Editor. If I Export the visible segments I will create an SDLXLIFF with just these 10 segments in it because these are the ones that are visible.

Whether you use the selected segments or the visible segments once you run the Export you should see a message box similar to this summarising what you have done and where the file has been saved:

You also have a log file which again explains which files the filtered set was taken from and the name of the file that was saved:


The exported file can be imported at the files level as explained above, but you can also do this in the Editor view.

The options are similar. You just set the criteria for any segments in the original source that you would like to be exempt from updating, select the sdlxliff and click on Import. This feature will provide the "Task Result" as before, but you will also see the updated segments change in the file you have open in the Editor:

In this case I signed-off and locked the segments in the file I imported and these are now changed in the file you can see open under the message window. And of course you have a record through the log file.

The original project file is also saved by appending the original files with .Backup_####.sdlxliff so you can always revert to the original if you're unhappy with the result.


As with most of the plugins created by the SDL Community Developers you can always find your way to help by using the TellMe feature in Trados Studio. It's a quick way to get some help if you need it!

Important Notes

Content formatting, placeholders and spaces are not included in the exported document

Structural elements such as content formatting, placeholders and spaces that are external to segment pairs are not included in the document that is exported by studioViews. This ensures that those elements are preserved when the translations are being re-imported. The only exception to this rule are formatting tags located at the paragraph unit level.

Considering the example below:

  • The following formatting will not be included in the exported content
  • The space between segment 2 and segment 3.
  • The formatting bold=true and color=FF000 associated with segment 8

  • The following formatting will be included in the exported content
  • The formatting bold=true & italic=true associated with segment 5
  • The formatting italic=true associated with segments 7 & 8


Segment Split/Merge Support

When the exported document is changed

Support for identifying alignment differences to the segment pair structure within and across paragraph units.

Consider the following workflow:

  1. A Project Manager creates a new Trados Studio project with document a.A section of document a is exported to document b using studioViews and distributed to a linguist for translation.The linguist creates a new Trados Studio project with document bThe linguist opens document b in the editor and performs structural changes to the segments (e.g. split and/or merge), before providing translations.The linguist delivers document b back to the Project ManagerThe Project Manager Imports the translations from document b into document a

Given this workflow, the segmentation of the paragraph units from document b are no longer aligned with those of the original document a, as the linguist performed additional segmentation and/or merged existing segments. The latest release provides full support in recognizing segment pair structural differences and automatically aligns the segments to be imported.

Best Practice

  • Avoid updating the segment structure of the original document, before importing translations back from an exported document.  It is expected that structural changes to the segmentation may exist in the exported document, but not in both.  If structural changes to the segmentation exist in both, then those from the document being imported take precedence.
  • Avoid changing the source content of the original and/or exported document, before importing translations back from an exported document.  We use the source content to aid in aligning the segmentation and/or merging differences.  Any changes to the source content other than removing or adding spaces will affect the alignment procedure.

Checkout other plugins from this developer:
XLIFF Manager for Trados Studio


XLIFF Manager for Trados Studio

By Trados AppStore Team

The ProblemYou need to share files for translation or review and the people you are sharing with don't use Studio, they can't support SDLXLIFF, and they want to use a CAT tool. You also do so much of this you need to have a better way of managing the process. You want to be able to share one XLIFF on a multi-lingual project and have the translators complete the target language.The SolutionThe XLIFF Manager is the solution to this problem as it provides the following core features:- export your Studio projects as vanilla XLIFF 1.2 files- export your Studio projects as Google Polyglot XLIFF files- choose whether the target language should be set or not on export- choose whether you export all the segments in your files or not- import the translated XLIFF files back into Studio and update your Studio projects- map unsupported languages from your clients system in support of the import- generate reports of the changed work- be in control of the end to end process with a project management view in StudioPlanned Enhancements for the future updates- progress bars while waiting for the export/import. Useful for large projects- support for tracked changes in the import- add support for an XLIFF 2.1 export- add support for an SDLXLIFF export (to help with the management of an SDLXLIFF file workflow outside of a package)- we're open to suggestions in the RWS Community!To learn how to use this application, please please check the Documentation tab.