From: Tanja Güllicher 
Sent: 14-Oct-02 4:39 AM
To: dejavu-l@yahoogroups.com
Subject: [dejavu-l] Re: Export translated file

When I ran across the same "can't write to" export problem the other day, I
searched the archives, tried all kinds of suggestions and made a list of
them, which I insert below. BTW, what worked for me was the thing Emilio
*always* says to do and where I never believed why that would make such a
big difference: update to latest build ...

Good luck
Tanja

“Can’t write to (filename)” – Possible reasons + solutions

- file name too long
- export path too long
- problem with codes (->run code check with ctrl+shift+C)
- source file is pw protected
- source file has been changed
- source file has been moved
- source file is open
- native application of source file is running (check Task Manager)
- large graphics in the source file
- not enough free disc space

Word-specific problems:

- Word macro security is set on high
- revision marks in the source file
- project needs repairing (create backup copy of project first)
- normal.dot or other word template is interfering -> move templates temporarily to another directory
- problem with word 2000 -> save word file as rtf or w97, reimport, pretranslate

Atril standard answer:
---------------------------------------------------------------------------
There is probably an error in embedded codes which has caused the exported
file to be truncated or invalid.
Move to the beginning of the project and press Ctrl+Shift+C. DVI will stop
at any rows for which target codes do not match source codes or are in
different order. You can quickly fix the codes by pressing Ctrl+Shift+F3.
Press Ctrl+Shift+C again and repeat until you get to the end of the project.

When you check the codes, for each row make sure that:
1. If there is nothing in source before the first code, so there isn't
anything before the first code in target.
2. If there is nothing in source after the last code, so there isn't
anything after the last code in target.

DVI will stop at those rows too.

If the problem persists:

0. Upgrade to the latest build from www.atril.com/en/downloads/uchoices.asp.
1. Send your translation to a new, empty MDB.
2. Import a copy of the file, populate, export, and verify that the exported 'translation' was valid.
3. Delete the 'translation' obtained by populating.
4. Pretranslate.
5. Check the pretranslation.
6. Use Ctrl+Shift+C to detect any problems in codes.
7. Export.