ah.. found it

It is not related with the Merge

It is the problem of "some kind of MS Word vertical arrangement", I guess..

It is a TABLE, the height of CELL has restriced with unknown reason.

Just let it go, then you will be happy again

Bye..

Paul Filkin said:

Thanks for the "sample" file.  I created the sort of file I was looking for from your file by saving the source, editing the source and then using that.  File attached so you can see what I was getting at:

Woo..

You wrote "448 words" and I have failed to find Your solution for this problem.

Did I miss something ?

If so, can you please tell me that a little bit more briefly ? 

regards

Jerzy Czopik said:

Any CAT tool MUST retain the source formatting, otherwise it will be useless.

I agree... and as you can see the content perfectly well in the source we must be able to do this in the target too.  This means not taking the approach we do today (in my opinion) as we simply add text into a row where it won't fit.

So it's perhaps not so much of a bug, but rather a problem with the way in which we have resolved this issue of not being able to merge across paragraph breaks.  It might even be something that we cannot avoid with the current capabilities, but let's see what the development team have to say about this first as the change may not be trivial to achieve this.  If this is the case it probably won't get fixed at all since this is (as you mentioned earlier) a rather rare occurrence and definitely avoidable by preparing files for translation properly.

Evzen Polenka said:

Sure... from people which don't have the faintest idea about why it's 'not possible'... from people who don't understand that PDF is NOT just another document format... from people who hardly have an idea about the technicalities behind.

I believe that "one of the most requested features" from, let's say, often traveling salesmen is a teleport ;-)... but still no transportation company does not do any research or implementation in this regard...
...simply because someone sensibly evaluated the request and found it unreal or not worth the trouble...

You did make me laugh... but hardly the same thing.  At the end of the day people receive PDF files for translation and they just want a better way of handling them.  A perfectly reasonable request given the source of their income is coming from people who definitely don't have a clue.

Unknown said:

Woo..

You wrote "448 words" and I have failed to find Your solution for this problem.

Did I miss something ?

Yes.  There isn't one!  At least not without correcting the source file first.

no

you'd better do not touch the source

and most of the time, it is NOT allowed

Unknown said:

no

you'd better do not touch the source

and most of the time, it is NOT allowed

In this case of course it is.  The whole problem comes from converting the original source, a PDF in a really poor way.  If you read the rest of my post you surely see the problem?

You didn't notice that the source is a Word file converted from PDF... which is a source not only allowed to touch, but actually required to touch.

so, what you have said is just one line.

"I will talk to tech part and wait/see" Right ?

Paul Filkin said:

If you read the rest of my post you surely see the problem?

no there are no problem at all.

and

there are no solution at all too.

Yeah, the example was a bit extreme ;-)

I just disagree here...nonsensical requests are still nonsensical, no matter if they are made by people paying me.

"A better way of handling PDF" was known for ages - get the source format from which the PDF was created. Period.
And only if there is really really REALLY REALLY no chance to get the source, use the convert-to-word workaround, clearly understanding that it's just an emergency workaround with lot of drawbacks, not an easy-peasy day-to-day process.

That should be the message from big localization players towards the clients... because they don't believe poor translators, they believe only to big companies.

If the poor translators had their backs covered by such clear statements from big players, they would be able to argument with the ignorant clients... and won't be pushed to corner by "translate this PDF, or I'm going to ask someone else" requests.

EDIT::
Actually, getting back to the teleport example - I'm pretty sure that the salesmen most probably even DON'T request the teleport, simply because it's widely and publicly known that it's not possible.

Yeah, the example was a bit extreme ;-)

I just disagree here...nonsensical requests are still nonsensical, no matter if they are made by people paying me.

"A better way of handling PDF" was known for ages - get the source format from which the PDF was created. Period.
And only if there is really really REALLY REALLY no chance to get the source, use the convert-to-word workaround, clearly understanding that it's just an emergency workaround with lot of drawbacks, not an easy-peasy day-to-day process.

That should be the message from big localization players towards the clients... because they don't believe poor translators, they believe only to big companies.

If the poor translators had their backs covered by such clear statements from big players, they would be able to argument with the ignorant clients... and won't be pushed to corner by "translate this PDF, or I'm going to ask someone else" requests.

EDIT::
Actually, getting back to the teleport example - I'm pretty sure that the salesmen most probably even DON'T request the teleport, simply because it's widely and publicly known that it's not possible.