Why does studioViews segmentation override our modified segmentation settings?

Dear All,

We are having some trouble while splitting projects with studioViews.

This is how we work:

  • Studio projects are created using a complete version (uncut) of a text; we also use translation memories that have, for example, the following modified settings:

> we have modified the segmentation to exclude colons (:)

> we use a modified list of abbreviations in English: it contains, for example, "para." (for "paragraph").

  • A coordination team is responsible for allocating the translation of long texts to several translators. This team identifies passages in the original text where the "splitting" must be done.

  • Then, the coordination team identifies the segment numbers (ids) in the Studio project, where the splitting is to be done. The team launches the studioViews "split" using the "Split by segments ids" option (note: we can't use either "Split by word count" or "Split by equal parts" options).

 This is the time that our problem arises: once the splitting is done, we find that segmentation is different from the one that would be predictable. Two examples:

> studioViews splits after the colon and so creates 2 distinct translation units;

> studioViews splits after the abbreviation "para." and so creates 2 distinct translation units.

 Thus, the segmentation is modified in both the sdlxliff file and "split" files. The segment ids are no longer the same after the split. We have made several tests and the result is always the same: it seem that studioViews applies Studio default (built-in) settings. Therefore, the "split" parts of the project no longer correspond to the passages identified by the coordination team.

This is a problem for the allocation to translators of the parts of the original to be translated.

This our Trados Studio version: 2021 SR2 - 16.2.12.9338

Any feedback would be much appreciated. Thanks in advance!



It's a question, not a discussion.
[edited by: Paul at 11:07 AM (GMT 0) on 13 Mar 2024]
emoji
Parents Reply Children
No Data