Technical forums » Déjà Vu support »
Déjà vu x2 Workgroup refusing to export 75% of translated files
Thread poster: Pavel Tsvetkov
Pavel Tsvetkov
Pavel Tsvetkov  Identity Verified
Bulgaria
Local time: 01:18
Member (2008)
English to Bulgarian
+ ...

Moderator of this forum
Jan 23, 2013

Dear All,

1. I have Déjà vu x2 Workgroup (the latest version) installed. The project consists of 4 files. I have translated them and must deliver them ASAP.

2. Unfortunately, Déjà vu x2 Workgroup refuses to export 3 of the 4 translated files, just informing me of the fact, and not giving a reason.

3. It seems that the creator of the *.doc files has placed some kind of a password protection against editing them. I only noticed it after running the files ... See more
Dear All,

1. I have Déjà vu x2 Workgroup (the latest version) installed. The project consists of 4 files. I have translated them and must deliver them ASAP.

2. Unfortunately, Déjà vu x2 Workgroup refuses to export 3 of the 4 translated files, just informing me of the fact, and not giving a reason.

3. It seems that the creator of the *.doc files has placed some kind of a password protection against editing them. I only noticed it after running the files through Code Zapper, and then not being able to open them without the password in Word. So I had to start translating the original files, and not the 'zapped' ones.

4. Could that be the problem (the security feature of the files)? How can the problem be solved? Any help and suggestions are appreciated.

Kind Regards,
PTs ▲ Collapse
 
Grzegorz Gryc
Grzegorz Gryc  Identity Verified
Local time: 00:18
French to Polish
+ ...
Password removing from Word XML... Jan 23, 2013

Pavel Tsvetkov wrote:

(...)

4. Could that be the problem (the security feature of the files)?

Exactly.
DVX tries to write in password protected sections and obviously fails.
Every CAT would fail (except Transit, AFAIK).

How can the problem be solved? Any help and suggestions are appreciated.

At this stage, you have a problem.
You should have done it before importing the file in a CAT too...
So, you must remove the password first, reimport, then pretranslate.

In Word 2003 you can save as Word XML , then use a decent text editor kinda Notepad++ or similar to replace the password hash with "00000000" (eight zeros), then open in Word and unprotect the document using a blank password.
I.e. search for the string "w:unprotectPassword", then you have a eight
number value you should replace with zeros.

If you have Word 2007-2010, the section will look like that:
<w:documentProtection w:edit="readOnly" w:enforcement="1"
w:cryptProviderType="rsaFull" w:cryptAlgorithmClass="hash"
w:cryptAlgorithmType="typeAny" w:cryptAlgorithmSid="4"
w:cryptSpinCount="100000" w:hash="YbweVdqHWHz3FAf+fO6/QmtaEgM="
w:salt="SbxiUfQet+xZRZaKmHU8PQ=="/>
You shoull remove the entire section in the Word XML file.

Then save back the file as .doc.

Sorry I'm in extreme hurry, I just paste fragments of my older posts.
It may not work for some document protection types but, at least, you have some suggestion...

BTW.
I love this kind of password protection.
One has a sophisticated safebox and leaves the key under the carpet

Cheers
GG
 
Pavel Tsvetkov
Pavel Tsvetkov  Identity Verified
Bulgaria
Local time: 01:18
Member (2008)
English to Bulgarian
+ ...

Moderator of this forum
TOPIC STARTER
Thanks and problem solved (but in a different way) Jan 23, 2013

GG,

Thank you for your time.

A. I tried implementing your solution with Notepad++, but could not locate the string you mention.
B. Therefore, I proceeded with another workaround:

1. I was able to get rid of the problem (which was some sort of a read-only protection, if you do not have the password) by first saving the files as .rtf and then running Code Zapper on them, to check that the protection was not triggered. It wasn't.
2. I added the fil... See more
GG,

Thank you for your time.

A. I tried implementing your solution with Notepad++, but could not locate the string you mention.
B. Therefore, I proceeded with another workaround:

1. I was able to get rid of the problem (which was some sort of a read-only protection, if you do not have the password) by first saving the files as .rtf and then running Code Zapper on them, to check that the protection was not triggered. It wasn't.
2. I added the files to the project, pretranslated the first one and manually edited the different segments (a few new codes at unexpected places).
3. I checked if the file could be exported correctly. It could.
4. I repeated steps 2 and 3 for the last two files.
5. When I tried opening the translated .rtf files in Word a message came up warning me that I should either supply a password, or open the files in read-only. I opened them in read only and saved them under a new name in the original Word 2003 format.

Thank you all, GG and Selcuk Akyuz, for all your kind help in solving this!

Best regards,
PTs ▲ Collapse
 
Grzegorz Gryc
Grzegorz Gryc  Identity Verified
Local time: 00:18
French to Polish
+ ...
Maybe it's my mistake... Jan 23, 2013

Pavel Tsvetkov wrote:

A. I tried implementing your solution with Notepad++, but could not locate the string you mention.


Ooops, maybe I was not enough precise in the Word 2007-2010 related part.
The section starting with the documentProtection statement may vary depending of the document.
And probably I did a stupid mistake.
I.e. I don't remember if I did it for Wrd XML or for unzipped DOCX file.

Sorry for being imprecise
I'm really in hurry today...

Cheers
GG
 
Pavel Tsvetkov
Pavel Tsvetkov  Identity Verified
Bulgaria
Local time: 01:18
Member (2008)
English to Bulgarian
+ ...

Moderator of this forum
TOPIC STARTER
2 years later: a similar problem and an identical solution Apr 25, 2015

Dear All,

Fast forward 2 years and I am having a similar problem (check the thread here:

http://www.proz.com/forum/déjà_vu_support/285041-the_name_in_the_end_tag_of_the_element_must_match_the_element_type_in_the_start_tag.html

...and I used a solution, simil... See more
Dear All,

Fast forward 2 years and I am having a similar problem (check the thread here:

http://www.proz.com/forum/déjà_vu_support/285041-the_name_in_the_end_tag_of_the_element_must_match_the_element_type_in_the_start_tag.html

...and I used a solution, similar to the one I described above: saving the original (source) file into .rtf, translating it, exporting it, opening it in Word and saving it back as .docx.

Voilà!

Even the Microsoft Fix-it tool failed where this simple method succeeded...

Best regards,
Pavel Tsvetkov ▲ Collapse
 
mikhailo
mikhailo
Local time: 02:18
English to Russian
+ ...
re Apr 27, 2015

I had the same problem a long time ago. Solution was simple — always export rtf with segment ID column.
 
mikhailo
mikhailo
Local time: 02:18
English to Russian
+ ...
re Apr 30, 2015

Seems first time I had not understand problem correctly

Do You know trick with putting "}" in the end of last segment (until DV exports)?
It' works. But resulted file always corrupted to some extent. This can be corrected manually.
Hope this way will take less time to you.


[Редактировалось 2015-04-30 07:53 GMT]
 


To report site rules violations or get help, contact a site moderator:

Moderator(s) of this forum
Pavel Tsvetkov[Call to this topic]

You can also contact site staff by submitting a support request »

Déjà vu x2 Workgroup refusing to export 75% of translated files






Trados Studio 2022 Freelance
The leading translation software used by over 270,000 translators.

Designed with your feedback in mind, Trados Studio 2022 delivers an unrivalled, powerful desktop and cloud solution, empowering you to work in the most efficient and cost-effective way.

More info »
CafeTran Espresso
You've never met a CAT tool this clever!

Translate faster & easier, using a sophisticated CAT tool built by a translator / developer. Accept jobs from clients who use Trados, MemoQ, Wordfast & major CAT tools. Download and start using CafeTran Espresso -- for free

Buy now! »