• State Suggested Answer
  • Replies 50 replies
  • Answers 4 answers
  • Subscribers 433 subscribers
  • Views 11882 views
  • Users 0 members are here
Options
Related

Keep format after retrofit from Word?

Ingrid

Hi !

I have to deal with quite a long file (over 10.000 segments) in which a lot of words should be italicized but aren't. I have looked for a quick way of fixing that, and came up with the following:
- export file for review (as a .docx)
- make all the changes in Word (using find & replace with formatting)
- retrofit after review into SDL

I had great hopes with this method, but they proved wrong: SDL does report every single change, but sticks to the previous formatting and doesn't take format changes from Word into account.

So... does anyone have an idea? Please help before I start italicizing my home and kids just for fun...
Truffe
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply
  • 0 in reply to Ingrid

    Hi  

    Unknown said:
    Paul seems to think it might be a bug, possibly with the latest version though I'm not sure about that, and intends to report it so ti can be fixed.

    As I mentioned earlier:

    - bilingual review does not work for this.  This is a bug we need to fix.

    - retrofit does work

    Your problem is that the file is pretty large and taggy so takes quite some processing to achieve what you want.  I think that even if the bilingual review approach did work you'd probably still have problems with a file this complex.

    Paul Filkin | RWS Group

    ________________________
    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

Children
  • 0 in reply to Paul
    Yes, this is it. The file is clearly too big and awkward to handle. But unfortunately I cannot change that... and the tags have to be set right in Studio for the return package, so I cannot just edit them in Word after editing my target file.
    And as I am in France, Retrofit has gone modern and strikes (at least on my computer).
  • 0 in reply to Paul

    Unknown said:
    Your problem is that the file is pretty large and taggy so takes quite some processing to achieve what you want.  I think that even if the bilingual review approach did work you'd probably still have problems with a file this complex.

    I don't think so, because - according to my experience - importing bilingual review file does not do as much god-knows-which postprocessing as retrofit... AFAIK, it simply imports the file as-is, without all that crazy ages-taking computing of editing differences which is done by retrofit (which is exactly the performace-killer, making retrofit actually useless in real-life projects).

    Plus, importing bilingual review Word file can be replaced by processing using SDL XLIFF Converter (the following guide was created back when Studio 2011 and 2014 were used, but should still work):

    When “Update from External Review” does not work – SDL XLIFF Converter

    If the “Update from External Review” does not work – e.g. because the review Word file was edited using Microsoft Word 2003, so the internal information stored inside the DOCX file structure is corrupted or lost – it’s still possible to import the reviewer’s edits into the project using SDL XLIFF Converter.

    SDL XLIFF Converter is a standalone application installed together with both Studio 2011 and Studio 2014:
    Dropdown menu in Trados Studio showing SDL XLIFF Converter for Microsoft Office selected.

    To mimic a behavior of the Studio’s built-in import it's necessary to set the application settings as follows:
    SDL XLIFF Converter settings window with 'Translation Rejected' selected in the dropdown menu for segment status update.

    Add translated SDLXLIFF file (or use the “Load files from project” button) and reviewed DOCX file and click “Import”:
    SDL XLIFF Converter import window showing source SDLXLIFF file and updated DOCX file ready for import.

    SDL XLIFF Converter should import reviewer’s edits from the review Word file successfully.

    Perhaps using this process the added italic formatting would be imported successfully?!
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 1:54 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Evzen Polenka
    Hi , I tried it with the SDLXLIFF Converter and see exactly the same result. I also tried it using a much older version, Studio 2014. It didn't work in there either. I think this is a more fundamental problem that probably never worked as intended for formatting so I'm wondering whether it was ever intended to at all? might know the answer to this if he has time as he created the original SDLXLIFF Converter for Microsoft Office.

    Paul Filkin | RWS Group

    ________________________
    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

  • 0 in reply to Paul
    The point is that the formatting must be apparently added the very same way which Studio itself marks the formatting in the bilingual Word file created from a particular source file type.
    I.e. in IDML files it's the <italic> 'physical XML tag'... but might be different in other file types, e.g. Word (maybe in Word you need to actual format the text, not add the 'physical tag'... I don't really remember all these details from the top of my head, I simply look at the actual file content and only then see what needs to be done).
    That's something what needs either a lot of more-or-less blind experimenting, or simply a knowledge of how Studio works internally.

    All that of course only if there isn't any additional layer of functionality within Studio which would prevent this from working.... e.g. something added in recent builds to prevent the problems created by one of the CUs where QuickInserts added different tags than those in source segtment (like <b> vs. <strong>, <i> vs. <italic>, etc.), which caused the famous "Multiple tags with the same ID 'Italic' have different..." error.

    I can only say that both the IDML process described in the other thread and also the import using SDL XLIFF Converter work(ed) perfectly.
    BTW, the SDL XLIFF Converter process assumes of course that Changes Tracking is turned ON in the Word file... because that's how the bilingual review import work as well - it looks ONLY for segments with tracked changes; if segment does not contain tracked changes, it's ignored. Hence the explicit instruction in the guide to set the corresponding option in the Converter settings.
  • Former Member
    0 Former Member in reply to Evzen Polenka

    Nop, You Are Wrong.
    The point here is to make Italic with easy.

    If you want your point make clearer, make your own post somewhere else.