You are currently working on UAT
I have had to merge segments – and now find that while everything looks good in the source and target in Trados, when I hit preview [source or target] the rest of the sentence – except the first line, or the orgignal first segment – has disappeared: any ideas how to fix this?
[IE] 3 merged segemnts, for example, forming one full sentence in both source and target in Trados, only display the first line [presumably the initial segment] for both source and target in both html and embedded preview.
Is this a refresh issue? What happens if you close the file, switch projects, then come back to this one again and preview it?
Would also be good to know what type of file this is and maybe share a screenshot too (you can simply copy/paste into the forum)?
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
It's a regular sdlxliff file sent containing a single .docx
But from my experience edit source does not cause ANY problems in ANY format, while merging will damage some.
It will if you use the edit source to remove the content and copy into another segment Jerzy. You can end up with markup files that are missing content where it must be there.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
I read the multifarious article earlier - but it didn't mention text [visible in the xliff file when open in Trados] disappearing - both source and target text - in the preview and in the target file...
It didn't mention the preview effect as this was something I wasn't aware of either until your post. But the problem is clear and mentioned. This image shows exactly what the problem can be:
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Well, it seems to be a very special case here.
Would the source be XLF or XML, the whole merging over paragraph breaks is not a good idea.
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Ironically, I tried it and it worked! I unlocked the second [erstwhile merged] segment, and cut and pasted from both the source and the target... now it looks fine [except that the 3rd merged segment shows as a blank line]... but what a complete waste of time!
I do not leave the source segments empty, but place XXX there. The translation is then two spaces. It worked until now in 100% of all cases.
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
I do not leave the source segments empty, but place XXX there. The translation is then two spaces. It worked until now in 100% of all cases.
It wouldn't work in all cases though Jerzy. If it was important for the target application to take the content of the, now empty elements (spaces are empty), and use this in a specific location it would now fail to be suitable for purpose. It would require additional work from a localization engineer to fix them.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
C'mon, this is a rare problem. Try to work with any other tool and then compare this "waste of time" with what you can or cannot do there. You've spent hours on discussing this "problem" here, which most probably will not occur in the vast majority of other Word docx files. Same can happen to you on a motorway: you'll drive it for years, until one day there will be a nail and you will waste time replacing your tyre...
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Then this will be the price he has to pay for preparing a file with not translatable content. Broken segments may not harm in English, but can lead to huge problems in other languages.
Try to translate this into English:
<p>Mit der Maschine können</p><br>
<ul><li>Dosen</li><br>
<li>Flaschen</li><br>
<p>produziert werden</>
What do you put in the last segment?
Now imagine, you have confirmed this translation and stored in your TM. And then you go for this:
<p>Mit der Maschine können</p><br>
<ul><li>Dosen</li><br>
<li>Flaschen</li><br>
<p>abgefüllt werden</>
This is a typical example of a badly written and formatted text. If that is Word, an empty segment will not harm. But if as you say, an empty segment makes a problem in another format, the author MUST not produce such crap. Otherwise he'll pay afterwards, if his content does not work As simple as that.
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
This is a typical example of a badly written and formatted text. If that is Word, an empty segment will not harm. But if as you say, an empty segment makes a problem in another format, the author MUST not produce such crap. Otherwise he'll pay afterwards, if his content does not work As simple as that.
Agreed. Source content has an important part to play in the whole process, and it's often misunderstood.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
It's a Word document: why "try to work with any tool " at all? Trados has not helped me in any way. I only use it if I have to. For this very reason. Not only do I waste hours trying to fix problems I wouldn't have if I just used Word, I can't even physically see the Word document - or it shows problems I can't fix in the xliff file that I could fix if it was a simple word file. Why send ac xliff for a single word doc in any case? This one has no charts/tables etc. ... And I'm not seeking to discuss anything - I just want the answer, to fix what shouldn't be happening.
And as Jerzy alludes to, the TM is completely pointless when the German text is chopped up into 'untranslatable' segments that can't be merged properly: it defeats the purpos of using Trados at all.
It's a Word document: why "try to work with any tool " at all? Trados has not helped me in any way. I only use it if I have to. For this very reason. Not only do I waste hours trying to fix problems I wouldn't have if I just used Word, I can't even physically see the Word document - or it shows problems I can't fix in the xliff file that I could fix if it was a simple word file. Why send ac xliff for a single word doc in any case? This one has no charts/tables etc. ... And I'm not seeking to discuss anything - I just want the answer, to fix what shouldn't be happening.
And as Jerzy alludes to, the TM is completely pointless when the German text is chopped up into 'untranslatable' segments that can't be merged properly: it defeats the purpos of using Trados at all.
Come on guys... we concluded at the start this is a bug. We need to fix it... that's all there is to it.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
And as Jerzy alludes to, the TM is completely pointless when the German text is chopped up into 'untranslatable' segments that can't be merged properly: it defeats the purpos of using Trados at all.
Yes, but note that this is a source document problem and should be resolved there. We can't expect a CAT tool to take content and handle it perfectly when it's been prepared without any thought towards localization.
If you handle it in Word you are effectively working in the source application, so of course that will help to avoid any problem over segmentation isues.
The preview issue is something else. We need to fix this.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Well clearly this is way above my pay grade, but, as I mentioned, even when I preview the SOURCE, the same (merged) segments only display the first page line, which I assume is the first (premerged) segment... If it was just a preview issue rather than a problem with the original file, wouldn't the issue be resolved (which it's not) when I generate the target file (F12)?
I still can't understand why it looks perfect with the xliff open, but the target file comes out bad...
(By the same token, if I had been able to generate a source document in the same way, it would also have ce out with only partial merged segments)
To generate source: File -> Advanced Save -> Save source as...
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Can you provide a sample from the source fle? You could do this:
This will no longer contain any recognisable content to worry about an NDA but the structure should be fine so we can reproduce the problem and get it fixed.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Without anything merged? Ie as I received it?
Correct. But tell me which parts you merged.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
I can provide a sample from the source fle, tomorrow, since I have more paid work to do right now... but I have never deleted content from an xliff file before, nor pseudotranslated , nor do I know how to "save the target" - beyond hitting F12, for instance - or do you mean just hitting CTRL S, for the paragrahs pseudotranslated?
Well, I could not find out how to delete content [ie entire segments] so , instead, here's a link to the entire xliff, as sent to me for post-editing:
https://www.dropbox.com/s/s6ckizmk8oe42de/xxx.docx%20-%20Copy.sdlxliff?dl=0
The segments merged are those seen in the screenshots, for example 74-76, 77-8, also from 921 to 941 I did multiple merges, all with the same result - lloking great in the editor screen, but preview - and "save target" only show the first line...
for Target preview - not bad
for Source preview - not so good
Translate
