Danilo Lopes Barbosa 

From what I see the source was a PDF. So the problem seems to be the PDF conversion and not Studio. To avoid such problems, ask for the proper source file or convert the PDF in a better way. The problem with PDF is always the same, a conversion done automatically will never fulfil the real need. It is always better to get the proper source or to convert PDF manually.

Thank you for your answer, but the source file is actually an MS Word document (.docx), not a PDF. 

Danilo Lopes Barbosa 

Can you tell me how do you see extra paragraph breaks in your document? In your screenshot I do not see any paragraph breaks, as non-printable characters are not shown.

For example, in screenshot 2, compared to screenshot 1, there are 2 extra blank lines between "CONTROLES" and "VOICE", 2 extra blank lines between "VOICE" and the paragraph below it ("Aumenta a resposta de harmônicos..."), 2 extra blank lines between "GAIN" and the paragraph below it ("Aumenta a saturação global no sentido horário..."), etc.  

Danilo Lopes Barbosa 

Please visualize the non-printable characters. Only then you really can count paragraph breaks. There can be different characters there, causing the layout to change. Your target text is not exactly as long as the source and this causes changes.

Danilo Lopes Barbosa 

Perhaps it would be helpful to see the sdlxliff you have translated.  Can you share that?  If not and you can only share screenshots please show a screenshot of the Editor View with non-printable chars showing, and also using the All Content filter instead of the All Segments.

Danilo Lopes Barbosa

I've taken a closer look on your second screenshot. It seems the spacing of your line formatting has changed. Might be the standard format style has been overridden in the source file and restored in the target file. Anyway, without seeing the non-printable characters no one can tell what happened there. Please also make the column and page breaks and also text frames visible.

I've attached the original source word file, the Trados source preview word file and the sdlxliff file.

I've attached the original source word file, the Trados source preview word file and the sdlxliff file.

Danilo Lopes Barbosa 

Thank you for sending the files though.  I have to say I think this is a bug.  The original file looks like this:

In Studio it looks like this (showing All Content):

Then just copying source to target and saving I get this in the target file:

For some reason Trados Studio is adding a soft and a hard return after the text and hard breaks, but only inside some of these text boxes.  I'm not sure why.

Danilo Lopes Barbosa 

Even stranger is that if I then translate the target file that has these additional breaks the target created from that is perfect... still includes the additional breaks but it doesn't duplicate them.

Danilo Lopes Barbosa 

This is strange, as the lines are already in the source file, when I open it in TS. I have never seen something similar before. However, the formatting of the source file is bad and makes the impression, it was converted from PDF. Unfortunately, I cannot help. The only solution I see here is to remove the paragraph breaks in the target file. I have no explanation where do they come from.

The original source docx file was indeed obtained by converting a PDF with OmniPage Ultimate, however that doesn't explain why it looks different when i open it directly in Word versus when I open it in Trados Studio and then save it to docx, right? Studio shouldn't alter the formatting of the document.   

Danilo Lopes Barbosa 

I have no explanation for it. As Paul  already stated, this might be a bug. A very strange one, as in all the years of using Studio since very early 2009 I have never seen something similar.

Does this happen with other files on your side too or is this the only file with such strange behavior?

Danilo Lopes Barbosa 

I think I found the problem... but I don't know why!  If I delete the large image and then process the file the target is perfect:

That is the target after roundtripping in Trados Studio.

So probably easy to solve by removing the image and translating the file, then put the image back afterwards.  Why it happens... I have no idea.  But certainly PDF conversions can do odd things that we probably never tested for before.

I'll log it with the support team so they can put it into the system to be resolved.  In the meantime you have a workaround, and it might be a problem you never ever see again!

 Danilo Lopes Barbosa Jerzy Czopik 

In fact the problem is even easier than that!

Danilo Lopes Barbosa said:

The original source docx file was indeed obtained by converting a PDF with OmniPage Ultimate

I don't know much about that application but I think the DOCX format it creates is not an upto date DOCX... at least not in all parts of the standard (whatever that is).  If I simply open your original source file and then save it into a new folder first I get prompted with this:

If I say yes and save it I then get a file that is a little larger, but it now processes perfectly well.

So I don't think I can give this to the support team because the first thing that will happen is that they need to ensure the DOCX is a valid DOCX based on what we would receive when created with Word.

So the solution is to simply do that... open the file in Word, save the file into a new folder upgrading it on the way and then translate the file  in Trados Studio.  It will no longer have this problem.

One last thing... it's worth checking what version of Word you are using as it might be your Word that causes the problem instead of OmniPage.