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
My guess is that the preview is based on the original file which is held inside the sdlxliff and the updated text, whilst part of a merged segment is actually linked to the first segment in the merged group. So the other merged parts are not seen and as segments #75 and #76 are now removed (since the merge is really an automated hack) the preview misses them out altogether.
This looks like a bug in the preview, but the target file should be fine. Press Shift+F12 to quickly create a target file and tell me if everything is ok?
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
Nope ... target file is identical to the preview ... text missing
Is the text part of a table? Do the merged paragraphs belong to the same document structure level? Are there any tags (possibly invisible?)?
_________________________________________________________
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.
No tags[tried all that, toggling to see if theere were any, even removing all formatting]; logically, the merged paragraphs would appear to belong to the same document structure level since they are all the same sentence; as seen from the images, there would appear to be no visible table involved - all i got was a single sdlxliff file.
Even if there was some invisible table, surely the merge would have merged the segments - i.e. the cells? Again, the source AND target text both only show the first line of text after merging... so the merge function seems to have removed the text in segments 2 and 3, for example - both in the preview and in the F12 target file - ...even though it all looks good if the sdlxliff file is opened in Trados...
[I should add, it all works fine elsewhere in the document - i.e other merged segments show ALL the text, both source and target, both embedded and Word previews...
No tags[tried all that, toggling to see if theere were any, even removing all formatting]; logically, the merged paragraphs would appear to belong to the same document structure level since they are all the same sentence; as seen from the images, there would appear to be no visible table involved - all i got was a single sdlxliff file.
Even if there was some invisible table, surely the merge would have merged the segments - i.e. the cells? Again, the source AND target text both only show the first line of text after merging... so the merge function seems to have removed the text in segments 2 and 3, for example - both in the preview and in the F12 target file - ...even though it all looks good if the sdlxliff file is opened in Trados...
[I should add, it all works fine elsewhere in the document - i.e other merged segments show ALL the text, both source and target, both embedded and Word previews...
How do you check the source? And what will happen, if you NOT merge the segments, but use "Edit source" and put all the text from the broken segments in the LAST segment?
And does the text appear in target without merging?
_________________________________________________________
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.
Even if there was some invisible table, surely the merge would have merged the segments - i.e. the cells? Again, the source AND target text both only show the first line of text after merging... so the merge function seems to have removed the text in segments 2 and 3, for example - both in the preview and in the F12 target file - ...even though it all looks good if the sdlxliff file is opened in Trados...
If you merged across parapgrah segments this could be the cause of the issue... because it's a hack. That's where Jerzy is coming from by asking about table cells for example. There was a reason why Trados never supported merging across paragraph breaks for years and the eventual implementation was an automation of simply taking the text out of the subsequent source segments and copy/pasting into the first one.
If there are tags between they will be left where they are and the content between them will now be missing. This is explained here:
https://multifarious.filkin.com/2016/11/21/bridging-the-divide-merging-segments/
So for some filetypes it's not a good idea to enable merging across para segments. In this case, woth word, it's fne. But it seems the preview is broken as mentioned before.
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
Oh, even in Word you must be careful. It is enough, that an anchor point is in one of the merged segments or - even worse - was between these! In that case you can create target, but won't be able to open it in Word.
As for the method of merging - this was possible since 2009 or at least 2011, afair. Simply as soon you allowed to edit source. But from my experience edit source does not cause ANY problems in ANY format, while merging will damage some.
_________________________________________________________
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 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 looks like I'll have to unlock the empty, locked "merged" segments and try and cut and paste lines of the sentence - which kinda defeats the whole purpose of mergining...
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
Translate
