Hi.

1. XLF files come presegmented by the tool, which created those. So to solve problem 1, contact the customer and ask for the kind of segmentation rules. This is the only decent way to change it. You can however also use the "Split segment" function - but I'm afraid your customer will moan, as they have most probably segmented that way by purpose.

2. Well, in my case there are also "seg-source" tags in the WorldServer files, but these are already present in the files I get from the customer. And they can import them with no problems...

Hi.

1. XLF files come presegmented by the tool, which created those. So to solve problem 1, contact the customer and ask for the kind of segmentation rules. This is the only decent way to change it. You can however also use the "Split segment" function - but I'm afraid your customer will moan, as they have most probably segmented that way by purpose.

2. Well, in my case there are also "seg-source" tags in the WorldServer files, but these are already present in the files I get from the customer. And they can import them with no problems...

Can i send you a sample of the file for your reference in order to try to import it to SDL Studio and see maybe this can be solved?

Yes, but with no guarantee for a success. jerzy at czopik dot com

Thanks,

Just sent you an email with 2 files.

Hi,

The first one is exactly as Jerzy mentioned.  XLIFF files are already segmented.

The second is controlled by a setting as Studio can handle an XLIFF requirement here which other tools cannot.  I think if you make sure you check this option then you won't see this information in the target file:

I have tested your files with the setting Paul mentioned. When you select the "Do not store segmentation information in the translated file", the seg-source tags do not appear anymore in your target. So the problem "2" may be easily solved with this setting.

However, your files are NOT pure XLF files, they are really badly prepared XLFs, as they contain CDATA sections. CDATA is not allowed in XLF, because all tags within such sections are represented by plain text. To make sure your texts will be translated properly, it would be necessary to create a special file type for those files.

In your files you see:

This results in Studio:

When you create a file type, Studio shows:

Best regards, Jerzy

Thanks - it looks better now.

Can you please let me know what are the settings you set int he file type?

I just created a new XML filetype, imported the corresponding XLF, set "source" as not translatable and used the HTML5 embedded content processor. As file identifier you must set *.xliff instead of *.xml - than it works.

I will try that later on today and will let you know...

One other question - it's kind of a tricky one.

If we have a TM from previous work which contains these large segments with their translation, and now we are adjusting the segmentation - can this be done also on the TM? It will be pity to lose the previous translation just because we fixed the segmentation.

I am afraid that changing the TM will be not possible, at least not without editing it externally in TMX for example. But even there it will be tricky. I could imagine exporting TMX to Excel, than splitting the segments there by a macro (or via Word). In that respect I would not do that myself.

OTOH the translator can always use a lower minimum match setting and go for concordance.

Hi Jerzy,

I still have issues with setting the filetype.

Can you please provide a detailed explanation of exactly how to do that?

Thanks