Elizabeth Jean Leah Peters

I don't think you can move images (a tag I guess) around in the source segments. Why don't you keep it in the same segment in the target as well, save the target and then move the image in the resulting Word file?

Daniel

Thank you for your response, Daniel. Yes, I have tried that as well. No matter where I place the image (tag) in the target segment, I keep getting the same error and I am unable to produce the resulting Word file. I'm at a loss...

Anyway, thank you again for your input! I appreciate your help :-) 

Dear Elizabeth Jean Leah Peters,

For each PDF file you work on in Studio, you will find a DOCX file in the source language folder of your project. This file is created by Studio when you read in the source file.

I think it would be best that make a copy of that file, rename it to some other name and then add it to your Studio project. Then, try immediately to save a target file. If this fails, remove the problematic image from the source file and add it to your project again.

Good luck!

Best

Annette (from Manfred's account)

Dear Annette, 

I can't thank you enough! I've just done everything you said and it worked brilliantly! You are right, I had forgotten that a Word document is created in the Source folder when you upload a PDF file. I took that file and saved it to a separate folder, then added it to my project and voilá :-) I'm happily into revision stage and I'm confident I'll get the file to my client on time. 

Thank you again, Annette! You're a lifesaver!!!

Sincerely, 

Elizabeth 

Regardless the source, such error is caused by merging segments across paragraph breaks. One of the paragraphs has contained an image before merging. After the merging the image/illustration is moved to another paragraph. Usually you could see that due to new tags appearing in such merged paragraph.

When merging segments across paragraph breaks you always should try to generate a target file immediately after merging to make sure this works. And you should also try to open such target file in Word immediately - because even if target will be created it is also possible, that Word will not open it anymore.

Hi Jerzy, 

Yes! You are right. I've been merging many segments in this document and this was definitely the source of the problem. I will take your advice for future PDF files, and I will try immediately generating the target file after merging segments to see if it works.

In this particular case, however, I left the two problematic segments unmerged because I am in a bit of a time crunch and I didn't have time to experiment ;-) 

Nevertheless, I appreciate your feedback and advice greatly, Jerzy. Take care and have a wonderful day!

Sincerely, 

Elizabeth 

I have a similar problem, but this solution for me needs to spend a lot of time to edit segmentation in the new file. there is not any other solution?

Hi Jerzy – thanks for the correct diagnosis, found your comment useful when searching for this. Just to check – is there no way, as far as you know, of undoing the incriminating merge? For example by dividing the segments again?

Undo does not work then—because Studio was heavily crashing after such operations, SDL decided to limit Undo and make it unavailable after segments have been merged over paragraph breaks. So you cannot undo the action.

Splitting segments does not restore the original file structure. When merging over paragraphs, two different XML nodes are brought together, so the resulting xml has a different structure. When splitting, the remaining node is split into two—resulting in even more changes in the xml. This is not an exact description, but a very simplified one. Nonetheless, splitting will not help.

Ah, you are right, I remember the crashing, and of course I’ve tried undoing now, in vain. I was hoping you might have a trick up your sleeve. A bit of a bummer that you don’t, as I am half way through a 5000-segment book.

I am torn between cursing Trados for all these little faults that add hours of work, and pondering in awe bout XML-node-level magic they must figure out.

Thanks for going out of your way to reply, Jerzy.