Contents
- If the files import, but the result is not what it should be
- If Déjà Vu hangs during the import
- If Déjà Vu shows a window saying that the file could not be imported
- If Déjà Vu shows a specific error message during the import process
If the files imports, but the result is not what it should be
There are many possible causes for this, depending on what file format is being imported, and the particular characteristics of the document being imported. It is also possible that a particular file is being imported correctly, but its particular features make the result of the import look unusual. Some examples of things you may notice follow:
- When importing a Word 2007 document:
- The import finishes but when you open the file in the project you find there is no text.
- There a lot of tags, or some letters or groups of letters are absent from the imported text, and appear to be replaced by tags:
- Tags contain formatting information from the original file, things like the font used, the style of the paragraph, graphics, etc. They are what allow Déjà Vu to preserve the formatting of the original document when it exports the translation you have created in the project. Documents that have very complex formatting will result in a lot of tags being added to the project.
Occasionally, however, a seemingly simple document will appear with a lot of codes when it is imported. This happens because the document contains a lot of unnecessary formatting information, in the sense that removing this formatting would not noticeable change the layout of this document. This can be alleviated with Déjà Vu:- With Déjà Vu X2: you can select the option Run CodeZapper when you import Word documents. This opens the document in Word before importing it into DVX2 and runs the well-known CodeZapper macro that simplifies formatting in Word documents while keeping the layout almost intact. Using this option is particularly helpful with documents that contain a lot of unnecessary formatting that is not visible to the naked eye. A good example of the kind of document that benefits from this is a Word document converted from a PDF using OCR technology.
- With Déjà Vu X3: by default, the Microsoft Office Live filter is used to import Office documents. This filter does a better job than the older filters of simplifying a document's layout without affecting it visually, thus producing a project that has fewer tags.
- Some Word documents contain Smart Tags in places. These are often not even visible in Word, particularly with the newer versions, but they will be imported by Déjà Vu nonetheless, and they may appear in unexpected places, sometimes causing translatable text to be stored in a tag rather than imported into the translation grid. If your version of Office allows it, you can remove the Smart Tags from a document before importing it. Using Code Zapper can also help get rid of these tags.
- Tags contain formatting information from the original file, things like the font used, the style of the paragraph, graphics, etc. They are what allow Déjà Vu to preserve the formatting of the original document when it exports the translation you have created in the project. Documents that have very complex formatting will result in a lot of tags being added to the project.
If Déjà Vu hangs during the import
This may have any of several causes:
- Déjà Vu was importing the files correctly, but it was taking a longer time than you expected and you thought it had hung.
- If you were importing an Office document with Déjà Vu X or X2, perhaps Déjà Vu was waiting for Office to finish. Older versions of Déjà Vu cannot import an Office file directly. What they do is open an instance of the appropriate Office application and run a macro in it that converts the document you want to import into a format that Déjà Vu can work with. Sometimes the macro itself will not finish. When this happens:
- Maybe the Office application itself has hung. In that case, you can close it from the Windows Task Manager, and Déjà Vu will start working again and output a message saying that the import failed. You can then try the import again.
- Maybe the Office application has output a dialog window informing you of something, and the dialog window has to be closed in order for Office to continue. Déjà Vu opens Word and Excel in such a way that you do not see their window (although the Task Manager will show that they are running, if you look). However, if something happens like, say, Excel outputs a dialog window complaining that the options you have set for macro security may not allow the current macro to run, an icon representing Excel will appear on the Windows Taskbar, and if you click on it you will see the Excel windows and the dialog, and you can then close them.
More information is available here.
- There are Addins for Microsoft Word that interfere with Déjà Vu's CodeZapper. They cause a Save File dialog to be created by Word whenever the CodeZapper macro runs, and the CodeZapper macro will not finish running until this dialog window is closed. More information here.
If Déjà Vu shows a window saying that the file could not be imported
There are many possible causes for this, depending on what file format is being used, and the particular characteristics of the document being imported.
- If you are importing a TTX document and Déjà Vu immediately fails, telling you that the document could not be imported, make sure that the TTX file has been pre-segmented in Trados TagEditor first. Déjà Vu only supports TTX files that have been segmented. More information here.
- If you are trying to import an Office 2003 document with Déjà Vu X or X2, and Déjà Vu tells you the import failed, you may have the execution of macros deactivated. Déjà Vu X and X2 need to run a macro in Office to convert Office 2003 files, but if the execution of macros is disabled this will either cause Office to give a warning that prevents Déjà Vu from continuing or, if Office is configured to block macros without a warning, the import will simply fail. If this happens, you need to reduce the Macro Security setting.
- If you are importing one of the many XML based formats that Déjà Vu supports, you may find that you cannot import the document if it has XML errors. These errors mean that the document has features that do not conform with the XML standard. If a document has XML errors, Déjà Vu will not be able to process the XML, and the import process will end immediately and unsuccessfully. More information here.
If Déjà Vu shows a specific error message during the import process
If you see an error warning dialog window, you can check the Knowledge Base to see if there is an article that corresponds to the error number you are being shown. If so, read the article and follow its advice.
If there is no specific article for the error number you are seeing, open a new ticket in the Helpdesk and enter into it the following:
- The information shown in the error message.
- The document or documents you were attempting to import.
- The project you were attempting to import into.
Comments