• State Verified Answer
  • Replies 8 replies
  • Subscribers 429 subscribers
  • Views 1411 views
  • Users 0 members are here
Options
Related

Anyone else finding pretranslate locks segments when the lock boxes are unticked in the batch task wizards?

Alison Field

Hi everyone,

I normally set the Wizard to lock content if I 'pretranslate' an SDLXLIFF to introduce corrected content from a TM.

However, this time I don't want anything locked because the huge quantity of large XML files I'm proofreading are extremely slow and opening them to have to unlock them takes AGES.

Thus, I unticked the lock boxes in the pretranslate Wizard (also in my profile settings and each project's settings), which I set to 'all' to update non-proofed files with the dedicated TM containing the content from files I've already proofed and corrected.

Regardless of whether I'm using the 'pretranslate' batch task or the 'create new project' batch task, the entire content of the files is locked when I open them. Thus I have to highlight the entire content of the files containing tens of thousands of words, which takes sooooo long, just so I can unlock everything, which takes even longer, so I can proceed with verification. I have to run the QA check, the tag check, number verifier and terminology verifier individually or the verification fails despite my incredibly tight, bombproof settings. 

My system is faster than the client's systems. They can't process these files unless I've unlocked them. I'm sorting the files out for them because Studio crashes when they try to perform any task on the files.

This is one of those 'bogged down' jobs where I can't see the woods for the trees but I'm convinced I've done everything right...

This is happening since I installed the latest, untested update but I don't know if it would have already happened prior to the update.

I have almost finished the job now so I don't need a solution per se but thought I should raise this in case anyone else is having the same experience.

All the best,

Ali Slight smile
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply
  • +1 in reply to Daniel Brockmann

    Hi again Daniel,

    I ran my tests and found that it occurs in AND and in 2019 also but only with xml files - docx files don't get locked.

    Interesting!

    I don't usually pretranslate but when I do it is always with the locking switched on, so this is the first time I've noticed it happening with xmls. A huge bunch of enormous files that are very repetitive but cannot all be worked on in a virtual merge without crashing. They were translated by different translators so I as a proofreader have to standardise which is where the pretranslation comes in. Normally the locking wouldn't be a problem but these files are so slow that it can take an hour to unlock one file. 

    Anyway, I think it's a complication of this specific format of file generated by the specific client's database and I'm not going to worry about it as it's not only happening in 2021.

    Sorry I raised it, I should have checked with other file formats and tried running the process in 2019 also before reporting it... 

    All the best!

    Thanks,

    Ali Slight smile
Children