• State Suggested Answer
  • Replies 9 replies
  • Answers 2 answers
  • Subscribers 285 subscribers
  • Views 15924 views
  • Users 0 members are here
Options
Related

WordprocessingML v. 2

Chiara Mariani

Hello,

I am having a problem with WordprocessingML v. 2 as the one described by Chiara Terraneo on April 13.

When I open a Word (.docx file) in Trados Studio 2015, the file is described as "Translatable", but then in the following steps of the New Project procedure, it cannot be converted.

I think the problem lies in the fact that it has been created with this WordprocessingML v. 2 filter - which it seems I don't have on my PC, I don't know why.


Can anyone help me?

Thank you.

Chiara Mariani
Rate translation
×
Suggest better translation
×
Parents
  • 0
    When you add the file to the project, you should be informed which file type is used. So please check this first. If "WordprocessingML v.2" is shown there, so you have this file type and are using it. If in this case the file is not converted, you will get an error message (you need to select the file and then the message). Please post the wording of the message 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.

  • 0 in reply to Jerzy Czopik
    Hi Jerzy, thank you for your reply. When I create a New Project and add the file I have to translate, the file type displayed is WordprocessingML v.2, so I probably have it.... But going on with the next steps of the procedure (after uploading the TM, the termbase, etc.), I cannot complete it: when Trados tries to convert my .docx document into a translatable format, a white X with a red background is displayed and I cannot go on. The error message is: "Object reference not set to an instance of an object".
  • 0 in reply to Chiara Mariani
    OK, this is a quite tricky error, not necessarily connected with the file.
    Please try the following:
    - Reset the file types in the project template you are using. Go to FIle -> Setup -> Templates, select the template and chose Edit, then click File Types and press "Reset" in the lower left part of the window.
    - Try now.
    - If that does not work, open the file in Word and save under a new name, then try again.

    Should all that not work and the file is Word 2013 or earlier, deselect the WordprocessingML file type and select the Word 2007-2013 instead in your template and then try again.

    _________________________________________________________

    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.

  • 0 in reply to Jerzy Czopik
    Dear Jerzy, following your instructions I succeeded in opening the file :-)

    I had to go to the last instructions you provided, i.e. to deselect the WordprocessingML file type (2007-2016) and select the Word 2007-2013. This way the New Project wizard completed the creation of the Project and it converted the file into a translatable format.

    I opened the file and translated a couple of sentences, just to try. I saved the file to see if saving was allowed, and it was all OK.
    But then I tried to Generate Target Translation - the button I normally use to convert the translated file in the original format - and unfortunately it does not work :-( It does not show any error nor warning during this operation, but when I open the Word file it generates, it does not open and a Microsoft Office Word error message is displayed: "Cannot open file xyz due to problems with its content -- Details: unspecified error. Position: Part/word/footnotes.xml, Row: 112 Column: 268" ...and of course I don't understand anything of this message :-((

    Anyway, I want to THANK YOU since your instructions helped me a lot - now I can open and translate the file in Trados, which is definitely the biggest problem two hours ago. Unfortunately it seems that I cannot export my translation in the original format, so I will inform my customer about this problem and hope he will do it himself at the end of my translation.

    Maybe I should try and check again the WordprocessingML file type checkbox before clicking the Generate Target Translation button???
  • 0 in reply to Chiara Mariani
    So it looks like the Word file is the culprit here. This is quite unusual, as typically Word DOCX files are better in processing. In any case - if you save the Word file after translation and it is unusable, then the whole process makes no sense. Hence we should find another solution.
    Please save the file as DOC instead of DOCX and check, if it does not get damaged in Word. If not, take this one for processing and forget the DOCX file at the moment.
    If you wish, you can also send me the Word file for checking off forum - jerzy at czopik dot com.

    BTW, checking the WordprocessingML file type in an already created project will not change anything. All the settings like file type are used BEFORE the file is converted. Once converted, it is already done. It is like tea: before you pour water over the teabag, you can change teabag and take another one. But once in water, you tea has already the flavor of the teabag used and you cannot now switch from Earl Grey to Vanilla or so :)

    _________________________________________________________

    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.

Reply
  • 0 in reply to Chiara Mariani
    So it looks like the Word file is the culprit here. This is quite unusual, as typically Word DOCX files are better in processing. In any case - if you save the Word file after translation and it is unusable, then the whole process makes no sense. Hence we should find another solution.
    Please save the file as DOC instead of DOCX and check, if it does not get damaged in Word. If not, take this one for processing and forget the DOCX file at the moment.
    If you wish, you can also send me the Word file for checking off forum - jerzy at czopik dot com.

    BTW, checking the WordprocessingML file type in an already created project will not change anything. All the settings like file type are used BEFORE the file is converted. Once converted, it is already done. It is like tea: before you pour water over the teabag, you can change teabag and take another one. But once in water, you tea has already the flavor of the teabag used and you cannot now switch from Earl Grey to Vanilla or so :)

    _________________________________________________________

    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.

Children
  • 0 in reply to Jerzy Czopik
    Hi Jerzy, I was beginning to think that the culprit is the Word file... I already thought to convert it from docx to doc, but before saving it an warning message was displayed saying that some features cannot be kept (I think graphics or things like that). That's why I did not go on with this conversion: I don't want to use a doc file because I am afraid I can damage it. Moreover, it's full of pictures, icons, graphics, and it's really heavy!
    So now I am going to write to my customer and explain the problem, i.e. that his Word file cannot be managed like this. I will tell him to convert it himself in the old Word (doc) and then what I can do is to use HIS new version.

    I thank you once again for your really precious help! :-)
    ciao
    Chiara
  • 0 in reply to Chiara Mariani
    There may be ways to have the Word file saved - which version of Studio do you use? Is this the latest Studio 2015 build 12.2.5099.5? Go to Help menu and look in About SDL Trados Studio. If not, maybe updating will help, as SDL is continuously working on improvements.
    Other idea would be to check, if you are able to save the source file from the DOCX you converted using the Word 2007-2013 file type.
    It is also worth checking, if there aren't any damaged TOC or other links in Word file. To do so, open in Word, press CTRL+A and then F9. If you then find error messages in the file, then you can try to resolve these. Damaged hyperlinks (jumps) are usually not a problem, but a damaged TOC is a big problem. Sometimes vendors do remove the TOC, but do not do that fully and leave just a last piece of the field (because a TOC is in fact a field in Word), which makes trouble when processing in Studio.
    I could tell you more, when I see the file.

    _________________________________________________________

    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.