Matthew S-anonymised 

By default Trados will always group paragraphs within a Paragraph boundary.  Line breaks are not grouped that way.  So for example:

That's two paragraphs.  Each have three sentences, but the first separates the sentences within the paragraph with line breaks.  In Studio you will get this:

You can tell where the paragraphs are because of the 'P' in the document structure column because an SDLXLIFF contains this information.  So any CAT tool that properly interprets an SDLXLIFF and has a way to display it will be able to see this too.  The line breaks are less important structurally because Studio will put them back when the document is translated.

However, these are also available in the SDLXLIFF if another tool correctly interprets and displays them.  If I show "All Content" to look between the segments I see this:

Note I can see the line breaks between, so if it's important for me to know this and I don't want to use the preview, I can see them this way too.  However, in another CAT tool... very doubtful!!

If I merge the segments in the first paragraph I would see this:

The line breaks are retained in the source.  So if Omega-T cannot see that, and if that's a deal breaker for you because your colleagues will only use Omega-T then you better use it too!!  We have no influence over their tool. 

Matthew S-anonymised 

By default Trados will always group paragraphs within a Paragraph boundary.  Line breaks are not grouped that way.  So for example:

That's two paragraphs.  Each have three sentences, but the first separates the sentences within the paragraph with line breaks.  In Studio you will get this:

You can tell where the paragraphs are because of the 'P' in the document structure column because an SDLXLIFF contains this information.  So any CAT tool that properly interprets an SDLXLIFF and has a way to display it will be able to see this too.  The line breaks are less important structurally because Studio will put them back when the document is translated.

However, these are also available in the SDLXLIFF if another tool correctly interprets and displays them.  If I show "All Content" to look between the segments I see this:

Note I can see the line breaks between, so if it's important for me to know this and I don't want to use the preview, I can see them this way too.  However, in another CAT tool... very doubtful!!

If I merge the segments in the first paragraph I would see this:

The line breaks are retained in the source.  So if Omega-T cannot see that, and if that's a deal breaker for you because your colleagues will only use Omega-T then you better use it too!!  We have no influence over their tool. 

Thanks for the answer - the issue is that the paragraph and line breaks were distinct in OmegaT for the first sdlxliff.

But the second sdlxliff (which was also much larger, 200kb vs 130kb), in which I'd merged some segments, did something to the file that hid the paragraph breaks from OmegaT. The puzzle is to work out what Trados did to the file - to hopefully prevent that happening.

 Matthew S-anonymised 

Merging segments in Studio changes the structure of the xliff in the end. The segmenting changes and depending if the merge was over paragraph breaks or not it may cause a huge difference in the target file. The segments may appear empty in the other tool (for example in memoQ) and you may have no chance to edit this there. I do not know OmegaT, but in case of such problems I would NOT merge anythin in Trados Studio.

Matthew S-anonymised 

If you were to provide a small example file(s)... which surely isn't beyond your capabilities to create, then it would be much easier to see what you mean.

The biggest problem will be if you merged over paragraph breaks, otherwise there should be no problem.  And if you had to do this this then I reckon your source files would benefit from editing before you put them through any CAT tool.

Surely isn't beyond my capabilities??

The source files were run through the document cleaner in the TransTools plugin for MS Word, then loaded into Libreoffice and saved from there. I find this two-step method a very reliable way of removing junk tags from a source file. But editing would not help with my problem - I translate many academic texts from the humanities. And CAT tools are messy when importing citations, which of course include many colons and full stops:

So, I want to be able to merge each footnote (or each whole citation, depending on the context) into a single segment. And I'm assuming that this must be done manually, and that there's no special tool for specifying segmentation rules just for academic citations.

I can share the file that has been causing me problems. But via email or some other direct method - out of respect for my client, I cannot post it here on the open internet. Let me know how I can get the file to you.

Matthew S-anonymised 

I understand your way of working and also the need to merge such texts. From what I see these are NOT separated by any breakds, but simply segmented on punctuation marks. Does this cause also problems in OmegaT? Maybe a way to work could be generating a XLF file in OmegaT and translating this in Studio? I do not know, if that will work, as I do not use OmegaT. However, working with Transit files (via memoQ) and memoQ files in Trados Studio causes usually no problems. So maybe this way round will be easier?

Matthew S-anonymised 

Matthew S-anonymised said:

Surely isn't beyond my capabilities??

Maybe worth explaining after reading this next:

Matthew S-anonymised said:

I can share the file that has been causing me problems. But via email or some other direct method - out of respect for my client, I cannot post it here on the open internet.

From the sounds of it you need to create a Word file containing:

• a few segments with any old text... what it says is not important at all
• a few footnotes or academic citations
• maybe some separate sentences with line breaks

So one page in Word with just a little bit of text to represent the problem you are trying to solve.  That is something you could share here and it would help everyone who would like to help you.