Start a new topic

Unsegmented SDLXLIFF files: how are they created?

CafeTran Training wrote:

>As a side note: I must admit that I have no idea about how these unsegmented Studio projects are created. Whenever I create a test project, it's fully pre-segmented. I think this is the default setting.

I received a reply from Grzegorz Gryc at :

> Thing is: Other CAT tools that can process Studio files, need them

> to be pre-segmented. It's my understanding that upon creation of a

> Studio project, the included SDLXLIFF files will be pre-segmented

> automatically.

> However, I keep reading about colleagues who receive SDLXLIFF files

> that obviously haven't been pre-segmented. So my actual question is:

> how did the PMs create these unsegmented files? 

Grzegorz answered:

The SDLXLIFF files are ALWAYS presegmented.

The problem is the way you use this word here 'cause:

- "unsegmented" means "segmented, without target structures"

- "segmented" means "segmented, with target structures"

The "presegmented" file (i.e. without target structures) is created

automatically when importing the source file to a Studio project (and

put, let's say, in the en-US folder), then copied to the target

directory (let's say, pl-PL, fr-FR etc.) and the target structures are

created (including the target language codes etc.).

Your problem is probably the fact it's no target structures in the


If a PM wants to send ONE mail to several translators translating into

several languages, he obviously selects the "unsegmented" source only

file, it's easier and faster for him.

It's not the way the workflow was intended but it happens.

And indeed, most CAT tools are unable to process "unsegmented" source

(in our example, in en-US), but some do (e.g DVX) but it's safer to

process the "segmented" files. 



Login to post a comment