• State Verified Answer
  • Replies 8 replies
  • Answers 3 answers
  • Subscribers 432 subscribers
  • Views 6327 views
  • Users 0 members are here
Options
Related

Print preview (CTRL+P) and Preview via Print & View no longer available

Donatella Garosi

Hello,

I have been using Studio 2017 for months, and I have been regularly using CTRL+P to preview the target file. Suddenly, last week, this option became no longer available: nothing happens when I press CTRL+P, and if I select "File>Print & View>View In", the "Print Preview" option is not active (light gray), and the (View in) "Microsoft Word as source" and Microsoft Word as target" options are no longer displayed:

   

I cannot use the Preview tab in the Editor view, either: I get a "There is no preview available" message (anyway, I have never been able to use Real-Time Preview: I think this is due to the Office 365 Click to Run installation). This means that every time I want to look at the the target file is to save it and then open it in Word - which is very annoying and time-wasting.

Has anybody encountered this issue and is there a workaround?

Many thanks,

Donatella
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Paul
    Hi Paul,

    thank you for your prompt reply. It is a WorldServer Package, probably created with Studio 2015. However, the Preview worked fine until last week (I translated 65k words out of approx. 150k words) on that very project/file (let's call it Project 1), so this may not be the problem.

    I tried to re-open the original package creating a new project (Project 2), and then the Preview worked, but the sdlxliff file was obviously untranslated. I thought I had inadvertendly changed some options in the Project Settings of Project 1, so I copied the partially translated sdlxliff file of Project 1 in the new Project 2, replacing the empty sdlxiff file, and the problem came up again in Project 2: no Preview available, even if I had changed no project setting. So, I think the sdlxliff became corrupt somehow. I could leverage my TM and pre-translate the new, empty sdlxliff file, but I would lose all the match percentages: all the segments would become 100% Match or Context Match.

    I also tried to create a new single-file project (Project 3) opening the Project 1 sdlxliff file for translation. The file opens, but the following message appears:
    "This file was created using a file type definition that does not exist on your system (Word 2007 v 2.0.0.0. (WS: Word 2010-2013 - No links). The following functionality will be restricted or unavailable: Saving, Verification, Quick Tags, Preview."

    I think this is a file type definition created by my client, who does not want hyperlinks to be translated (they do not even appear in the sdlxliff file).

    In fact, in Project 3 the only Print Preview option available is Side-by-side preview - no Word target file preview and, most importantly, I cannot save the Word target file (Failed to save target content: Cannot find file type definition with id Word 2007 v 2.0.0.0 (WS:Word 2010-2013 - No links).

    Any ideas of what might have happened to my file?

    Many thanks,

    Donatella
  • 0 in reply to Donatella Garosi
    Hi Donatella,

    It does sounds as though the problem is with your sdlxliff. Can you recall if the problem arose prior to the SR3 update? I don't know if this is the reason for the issue but would be interesting to know. Other things might be that you have some security software that corrupted the embedded word file while you were working on it, so the file was still available for translation but things like preview, quick inserts were no longer available to you. Really hard to know for sure, but it sounds as though your best way forward now is to pretranslate the file in the new project from your TM and more forward.

    Regards

    Paul

    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

    Hi Paul,

    the original package was created in January, before the SR3 update; anyway, I am working with Studio 2017 and I have not even downloaded the SR3 update for Studio 2015, so I don't think this is the problem.

    I will follow your suggestion and pre-translate the file in the newly re-created project - this seems the safest thing to do.

    Regards,

    Donatella
  • 0 in reply to Donatella Garosi
    Hi Donatella,

    You mentioned you thought the package was created with 2015... although if it's a WS package then this seems unlikely really.

    Hope it goes well for you now.

    Regards

    Paul

    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
    Hi Paul,

    I replaced the corrupt sdlxliff file in the original project with a backup sdlxliff file dated March 20th, before the problem arose, verified that the Print&View feature worked and applied pre-translation. This way, pre-translation was applied only to the segments I worked on from March 21st onwards and the percentage and match source info were retained for the previously translated segments. Not the best possible solution, but it worked.

    Thank you again!

    Donatella