Deja Vu X: Unable to export file
Thread poster: tanyazst

tanyazst
Belarus
Local time: 15:55
English to Russian
+ ...
Jun 5, 2006

Hi all!

I encountered a very unpleasant problem.
After a I finished my translation and tried to export it to MS Word, the tool reported a message: Deja Vu X was unable to export the following files: \[file name]. It did create a target folder, and even created a file, but the file was empty.

I checked the embedded codes, checked that the path is not too long, and removed images from the original text.

Still nothing helped

Does anyone have a clue as to what I can do besides copy-pasting the translation to Word??? (which would take me forever since there are dozens of tables in the doc... )

Thanks in advance for all your help!


Direct link Reply with quote
 

Victor Dewsbery  Identity Verified
Germany
Local time: 14:55
German to English
+ ...
Various possibilities Jun 5, 2006

For example the position of the codes:
- Are the codes in source and target in the same order?
- Does anything come in front of codes which are at the start of the segment in source?
- Does anything come after codes which are at the end of the segment in source?

I suppose you have done the automatic code check (by going to the start of the file, pressing CTRL-Shift-F8, and if DVX finds problems, looking at the error comment at the very bottom left of the DVX window).

Have you introduced extra line breaks into the target text?
Have you entered curly brackets { or } as characters in the text?

Sometimes I find that export problems are fixed if I close DVX and Word (and perhaps even reboot the computer), then start up, open the DVX project and try again. (In such cases, it is Word that has gone on the blink, not DVX).

***
A more radical solution is to save the source file in a slightly different format under a different name (e.g. "save as" Word 6.0/95, or open it in OpenOffice, change some insignificant detail like adding a space at the end of a line, then save as Word). Then import the changed file and pretranslate with CTRL-P. Pretranslating will find almost entirely exact matches; the rest you will have to fix manually, but that is miles better than copy/pasting the whole translation from DVX to Word.
(If you do this, it is worth checking that any numbers and/or brackets at the end of exact match segments are right, just in case)

I hope you manage to fix your export quickly. I know the feeling - it's not common, but this problem very occasionally comes up.


Direct link Reply with quote
 

Yolanda Broad  Identity Verified
United States
Local time: 08:55
Member (2000)
French to English
+ ...

MODERATOR
Word files will export as blank when Word program is open Jun 5, 2006

Make sure you've closed all Word files (and the Word window) before exporting.

Direct link Reply with quote
 

Piotr Sawiec  Identity Verified
Local time: 14:55
English to Polish
+ ...
export in two columns Jun 5, 2006

It occurred to me several times that I could not export the finished translation. In such cases I use the option of exporting in two columns. You will have then a table, where there are original fragments in the left column and corresponding translations in the right. Then you remove the left column, convert a table to text and apply the original formatting to the document. It also can take a lot of time, but (as the method above), can save you some effort.

Piotr


Direct link Reply with quote
 

Ilde Grimaldi  Identity Verified
Local time: 14:55
Member (2003)
English to Italian
+ ...
Is the source file still were it was at time of importing? Jun 6, 2006

Just a guess.
Is the source file still in the path where it was at time of importing? Did you rename some part of its path?
Ilde


Direct link Reply with quote
 

Victor Dewsbery  Identity Verified
Germany
Local time: 14:55
German to English
+ ...
Only for certain file types Jun 6, 2006

Ilde Grimaldi wrote:
Is the source file still in the path where it was at time of importing? Did you rename some part of its path?
Ilde


I believe this only applies to Excel and PowerPoint files.
They not only have to be in the same place, they even have to be unchanged.

But for Word files, it does not matter where the source file is. And the restriction on path length (which tanyazst mentioned in the question) was an issue with DV3, but not with DVX.
So the problem lies elsewhere.


Direct link Reply with quote
 

Endre Both  Identity Verified
Germany
Local time: 14:55
Member (2002)
English to German
Try exporting the source file Jun 6, 2006

If you haven't tried yet, you may want to make a copy of your project file (you should not try this in your actual project file), mark all segments and populate them (F5).

Try to export the file; if the problem persists, chances are that you have done nothing wrong during translation, and the problem lies with DV's import procedure.

Conversely, if the populated file exports fine, there must be something wrong with the codes in your project as described in detail by Victor.

Endre


Direct link Reply with quote
 

tanyazst
Belarus
Local time: 15:55
English to Russian
+ ...
TOPIC STARTER
Excellent suggestions! Jun 7, 2006

I tried to export the project in columns, as Piotr had suggested (I assume it was the File -> Export -> External View, but maybe there is another way??), and it worked just as he had described.

I went through all the codes again, following Victor's advice, but everything was fine there. I guess DejaVu just failed to digest the complex graphs in the source file.... :-\ Oh well...

This topic sure helped A LOT and I will keep it for future reference Thanks everyone!!!

P.S. Endre, how do you make a copy of the project file in DejaVu?


Direct link Reply with quote
 
bobazu
Local time: 14:55
solved exporting issue [Deja Vu X was unable to export the following files: ...] Dec 6, 2011

tanyazst wrote:

Hi all!

tried to export it to MS Word, the tool reported a message: Deja Vu X was unable to export the following files: \[file name].


The issue can be caused by characters in the filename of the imported file, which are not supported by the OS.

Two approaches can be used:

(Never tried this myself)
1. change default language for the applications not supporting Unicode (under Control Panel > Region and Language settings > Advanced (or Administration) > Default Language for applications not supporting Unicode) [change to the code page you thing your file is named in], restart PC, try exporting again.

(this worked for me - 5 minutes issue)
2. under project explorer change Translation Memory and Terminology Database to a blank new files, resolve the whole project with the memory and database, exit. Rename the input file using English alphanumeric characters without diacritics, open DejaVu, create new project importing the renamed file using the memory and database created above. Pretranslate. Export. It should work.

Regards


Direct link Reply with quote
 

Lbenito_atril
Local time: 14:55
Check Embedded Codes Dec 7, 2011

Did you use DVX's "Check Embedded Codes" function? Without it it is unlikely you will find all instances of incorrectly placed embedded codes unless the project you are working with is short and simple.

You can run this check by accessing the menu option QA>Check Embedded Codes, or by pressing the key combination Control+Shift+F8. When you do this DVX will start checking the current row, and go down, row by row, until it finds a target cell with incorrectly placed embedded codes, and it will show a message on the status bar (at the bottom left-hand side of the DVX window) about the problem it has found. If it does not find anything, it will show a message on the status bar to that effect.

The check only runs from the current row downwards, and only in the segments currently displayed on the grid, so if you want to run the check o the whole project you should display the whole project (by double-clicking on the project name in the File Navigator), select "All Rows" in the Row Selector and then place the cursor in the first segment.

For more information about what to do when a file fails to import you can read the article called "I cannot export a file from Déjà Vu" in Atril's Knowledge Base: http://helpdesk.atril.com

[Edited at 2011-12-07 09:13 GMT]


Direct link Reply with quote
 


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 »

Deja Vu X: Unable to export file

Advanced search






LSP.expert
You’re a freelance translator? LSP.expert helps you manage your daily translation jobs. It’s easy, fast and secure.

How about you start tracking translation jobs and sending invoices in minutes? You can also manage your clients and generate reports about your business activities. So you always keep a clear view on your planning, AND you get a free 30 day trial period!

More info »
BaccS – Business Accounting Software
Modern desktop project management for freelance translators

BaccS makes it easy for translators to manage their projects, schedule tasks, create invoices, and view highly customizable reports. User-friendly, ProZ.com integration, community-driven development – a few reasons BaccS is trusted by translators!

More info »



All of ProZ.com
  • All of ProZ.com
  • Term search
  • Jobs