Hi Paul, 

Here's the sdlxliff screenshot.

with the merge option grayed:

Part of pdf generated from the InDesign file:

Thanks,
David

(Sorry for the delay in responding. The Notification function doesn't appear to be working.)

Hello David,

These are all paragraph segments.  Your problem is that the xliff file presents these segments as paragraph segments in Studio.  So you have this:

To be able to merge them you would need to see this:

As I said, Studio 2017 will allow you to do this technically but I'd be very interested to see what this would look like when the file gets back to memoQ.  I can test this for you if you can send me the original source file to test in a memoQ -> Studio 2017 -> memoQ workflow.

Regards

Paul

As I said, Studio 2017 will allow you to do this technically but I'd be very interested to see what this would look like when the file gets back to memoQ.  I can test this for you if you can send me the original source file to test in a memoQ -> Studio 2017 -> memoQ workflow.

We are doing this for Transit projects for several years now. Previously I edited the source, merging paragraphs this way "virtually". In target I entered a double space then. This way there were no meaningful entries in TM, as the broken segments have been translated to spaces. I do not remember now, if MemoQ did accept these segments to update the TM, but I think it was so.

Now, since Studio 2017 is around for testing, I used segment merging instead. This leaves the merged segments empty. And in MemoQ it does result in empty segments, which are reported as MemoQ cannot update the TM with these segments. So in MemoQ I do split them manually back to what they were before or just leave empty - depends on what happens with the file next. But in the end of the day the process works perfectly both ways.

As I said, Studio 2017 will allow you to do this technically but I'd be very interested to see what this would look like when the file gets back to memoQ.  I can test this for you if you can send me the original source file to test in a memoQ -> Studio 2017 -> memoQ workflow.

We are doing this for Transit projects for several years now. Previously I edited the source, merging paragraphs this way "virtually". In target I entered a double space then. This way there were no meaningful entries in TM, as the broken segments have been translated to spaces. I do not remember now, if MemoQ did accept these segments to update the TM, but I think it was so.

Now, since Studio 2017 is around for testing, I used segment merging instead. This leaves the merged segments empty. And in MemoQ it does result in empty segments, which are reported as MemoQ cannot update the TM with these segments. So in MemoQ I do split them manually back to what they were before or just leave empty - depends on what happens with the file next. But in the end of the day the process works perfectly both ways.