You are currently working on UAT 

Merged segments not showing merged text

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.

  • This is entirely a Studio problem, since

    1. a) the original source xliff/project was made by Studio and
    2. b) the target file, also produced by Studio, is also coming out wrong when segments are merged.

    Sorry man, but this clearly indicates that you have no idea about the technicalities behind the whole story and therefore make totally wrong conclusions.

    I don't disagree with you that the source is poor, but in general I agree with John and I think we should be able to handle this better.  I don't think it is the job of translators to understand the technicalities in the same a way a seasoned localization engineer would.  If Studio was sold as a tool designed only for these specialists I think you might have a point, but it's not.  So I personally think we should 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

  • I beg to disagree a bit. The translators must know, how the tool works and they MUST know, what happens with a PDF file, when it is simply thrown on Studio without taking care about the post processing. The life has changed and we live in 21st century. But TBH the "translators not understanding technicalities" was never valid. Even as we translated from paper, you had to know how formatting in Word works. Now things got more complicated and we have to deal with many more formats than just plain paper. Understanding how your tool works is a necessary prerequisite to deliver high quality translation. Otherwise you deliver crap - even if the translation as such is lingusticaly OK.

    There is no excuse for translator not to know the tool used. Exactly as there is no excuse to a nurse not knowing how to enter the data of the patient in her computer. If other processions can learn using computer to their need, I do not see why should translators be excused here.

    _________________________________________________________

    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 beg to disagree a bit. The translators must know, how the tool works and they MUST know, what happens with a PDF file, when it is simply thrown on Studio without taking care about the post processing.

    Well, this is an interesting twist ;-)  Translators telling us we don't need to fix something!!

    It is certainly a good idea for everyone to learn as much as they can about their software, but that doesn't excuse the software from being able to make this easier and reduce the effort required to mirror the source files provided.  Just because the source files are a poor conversion does not excuse the software from being able to handle them.  We can extract the text ok, so it seems logical that we should be able to preview it and save the target too.

    Let's keep this to a discussion on this specific problem... I doubt we disagree about the rest.

    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

  • IMO, SDL made a kind of mistake when they implemented this "easy for translator" process for translating PDFs.
    Something what perhaps originally looked like a competitive advantage turned very quickly to a pain-in-the-ass...

    If I would be a product manager, I would seriously think about removing this feature....

  • Translators telling us we don't need to fix something!!

    But well, there is really nothing to fix... everything works just fine, as I just showed...

    it seems logical that we should be able to preview it and save the target too

    But you DO show it in preview and you DO save it in the target too...
    It's all about just the bad formatting of the source and the VISUAL(!!!) result...

  • If I would be a product manager, I would seriously think about removing this feature....

    I doubt this would happen as there is a healthy volume of these type of files coming through the software and prior to this capability it was always one of the most requested features.  I think a text only extract might be a good idea so we strip out all formatting and leave it to the user to reformat in Word to get the look and feel prior to translation... if they have the time to do 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

  • I fully agree that we don't disagree.

    Just a last remark: if the problem is caused by a fixed line or table cell height, than it is NOT in slightest way a problem of Studio, but entirely the problem of a badly formatted source and in the end the problem of the user not being able to notice and correct this in the target file. Any CAT tool MUST retain the source formatting, otherwise it will be useless.

    _________________________________________________________

    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.

  • If you strip all formatting from the PDF after the conversion, the vast majority of the users producing the target file will not even be able to format it... And here is the whole problem: people cannot use the software they are expected to use.

    _________________________________________________________

    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.

  • it was always one of the most requested features

    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...

  • Former Member
    0 Former Member in reply to Paul Filkin
    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