FAQ

DVX2 updates

DVX updates

7.5.338

Improved performance of IDML filter
Fixed issue with Line Separator (U+2028) in XLIFF filter
Number-only segments copied from the source by Assemble, Scan or Pretranslate now marked as Fuzzy Renumbered (instead of Assembled)
Improved handling of non-numerical digit strings (e.g. 1.2.3)
Improved handling of normal spaces used as thousand separators (instead of non-breaking spaces)
Fixed issue with marker extraction in FrameMaker MIF filter
Fixed issue with footnote extraction in Microsoft Word DOC/RTF filters
Fixed issue missing text in OpenDocument filter
Includes workarounds for various bugs in v3 and v4 of the RichEdit control in Windows Vista and Windows 7
Fixed issue with reimporting certain Trados WB External View files
Fixed problems with exporting of Trados WB files with Word 2010
Fixed a problem with lexicon searches when portions contain wildcard characters
Workaround for malformed font tables in RTF files
Fixed a problem with deleting large numbers of duplicates in TMs
Fixed bug in handling of embedded HTML markup in Java .properties files
Improved AutoSearch performance with TeaM Server TMs (the full fix requires updating the TeaM Server binaries too)
Fixed bug in handling of empty attributes in TeaM Server terms
Added official support for Adobe InCopy ICML files
Added official support for Visio XML (VDX) files
Improved performance when searching for number-only segments
Exact-propagated rows are no longer overwritten with fuzzy-propagated translations
Improved handling of CDATA sections in SGML/XML filter
Improved handling of PHP scripts in HTML filter
Fixed segmentation issues in InDesign IDML filter
 

7.5.335

Added support for Adobe InDesign CS5 IDML
Added support for Office 2010
Performance improvements to SGML/XML filters (including Adobe InDesign INX and Office 2007/2010)
Performance improvements to DOC/RTF filter
Performance improvements to XLIFF filter
Improvements in MIF filter handling of markers and character sets
Number-only segments present in the TM are now retrieved correctly
Fixed bugs in XLIFF filter
Fixed performance issues when using TeaM Server with AutoSearch enabled
Fixed a bug in match sorting for AutoSearch/Assemble
Fixed a bug where PowerPoint 2007/2010 slides were imported in the wrong order
Fixed issues with missing spaces in Office 2007/2010 files
Fixed bugs in AutoSearch
Fixed bugs in Assemble
Fixed bugs with renumbered matches
Fixed issues with incorrect characters in External Views
Fixed bugs in the Alignment Wizard grid
 

7.5.316

Added new filter for working with XLIFF files, including SDL Trados Studio 2009 SDLXLIFF
Added support for FrameMaker v9.0 in FrameMaker MIF filter
Added support for InDesign CS4 in InDesign INX filter
Microsoft Windows 7 officially supported
Microsoft Office 2010 (current at Beta 2) officially supported
Improvements in the RTF filter, including reduced extraneous codes and improved performance
Fixed issues with curly brackets in PO filter
Improvements in the XML filter, including better handling of large CDATA sections and improved performance
Improvments and fixes in the MIF filter, including better handling of index entries, footnotes and text insets
Various fixes to the SDL IDT filter
Fixed issues with exporting satellites
Improvements in number handling (particularly in Propagate) and case conversions
Fixes issues with filter on selection
Fixed various issues with mouse/keyboard focus
Fixed various issues with TMX import/export
Fixed various issues with MultiTerm import
Fixed various issues with TM import/export
Fixed various issues with TD import/export
Fixed issues with alternate portion handling when work with a separate edit area
Fixed issues with search and replace in TM and project
 

7.5.303

Fixed issues with squares appearing in Assemble and repaired fuzzy matches
Fixed issues with renumbering propagated and assembled segments
Improved compatibility with 7.0 COM+ servers
Fixed issue with locked rows being overwritten when importing new files
Improved handling of malformed tags in HTML filter
Fixed issues with certain types of nested tags in HTML.
Added support for Unicode (QuickSilver 3.0) in Interleaf filter
Added support for Unicode (FrameMaker v8.0) in FrameMaker MIF filter
Fixed issues with exporting HTML and XML with the 7 bit US-ASCII encoding
Fixed issues with importing and exporting TMs/TDs and DVPNGs under certain Windows locales
Fixed issue with common "Application Data" path in some versions of Windows 2000
Fixed issue with number checks
Fixed issue with CDATA handling in the InDesign INX filter
Improved round-tripping of embedded CRLFs in SGML/XML filter
Fixed issue with NCRs in non-translatable text in InDesign INX (SGML/XML) filter
Fixed issue with Find & Replace in TM view
Fixed issue with "(COM+)" indicator not being displayed in AutoSearch Sentence window
Fixed issues with alternative portion handling
Fixed issues with External View missing/extra spaces
Fixed issues with duplicate detection External View
Improved support for Windows Vista UAC
Fixed issues with installing on pre-installed OEM version of Windows Vista
Fixed issues with Undo grouping
Fixed issues with large ITD files
Fixed performance issues with TM/TD export
 

7.5.302

Fixed importing/exporting TMs
Fixed a bug in Ctrl+Space keyboard shourcut
Improvements in the SDLX ITD filter
Improvements in the PowerPoint filter
Improvements in INX filter
Improvements in Excel 2007 filter
Fixed importing some japanese characters
Fixed a bug which prevented proper MultiTerm import
Fixed a bug in Word 2007 filter
Fixed a bug in TTX filter
Fixed a bug which prevented proper External View export for TTX filter
Improvements in assemble feature
Improvements in propagate feature
Handling of AutoSearch/Assemble portions with punctuation
Sorting/priority of matches in AutoSearch/Assemble
Fixed some issues in terminology check
TDB Browse and TDB Lookup windows display multiline text attributes correctly
 

7.5.297

Added compatibility with Windows Vista
Added new filter for working with Office 2007 files
Added new filter for working with InDesign CS2 - INX files
Added new filter for working with OpenOffice 2.0 files
Added new filter for working with RESX files (.NET resources)
Added new filter for working with SDLX ITD files
Added new filter for importing SDLX translation memories
Added new filter for importing MultiTerm terminology databases
Added new filter for exporting a project (External view) to Trados RTF format
Improvements in assemble feature
Improvements in propagate feature
New add/remove databases UI
Terms are sent to all the terminology databases with F11
Various fixes to Autosearch and Scan
Excel cells with more than 1000 characters are now imported properly
Fixed importing XML not embeddable tags
Fixed using Autotext feature in the editing separate text area
Fixed removing embedded codes with Ctrl+Space
Fixed importing some japanese characters
Fixed exporting \\n characters in Excel and PO files
Improvements in Word filter
Fixed exporting a project to an External View without duplicates
New menu entry for QA functions
Fixed changing properties in the C++/Java filter
Fixed displaying source sentence in context (F6)
Fixed locating a sentence in a MDB
Fixed selecting the encoding in a XML file
Fixed sorting alphabetically empty MDBs
Fixed a bug with leading 0 in Trados Workbench External View
Fixed reimporting empty translations in Trados Workbench External View
Fixed exporting backslashes in HTML External View
Fixed filtering segments with SQL statements - Source/Target Comments
 

7.0.284

Project repairs can handle more errors
Accurate progress bars in compacting and repairing projects, TMs and TDBs
Various fixes to Pack N' Go export
Various improvements to Pack N' Go import
Send terms to TDB from alignment projects
Fixed an issue with duplicate alignment project IDs
Various fixes to Scan
Improvements in guaranteed matching during Pretranslate
Improved handling of duplicate relations in TDB
Correct handling of intralanguage relations in TDB
Lemmas longer than 255 chars no longer result in an error (DVX truncates them)
Fixes IBM TM import (added support for MIF data) into TM
Fixed to Trados TM import into TM
Fixed handling of WHERE filtering in DVMDB export
Correct escaping of certain characters in TMX markup when importing into TM
Correct reindexing of sentences after manual editing in TM
Improved spell check support for TM and TDB
Fixed a bug when adding a sentence to TM while source was sorted alphabetically
COM+ improvements (workaround for bug in RPC marshalling in Windows)
Handling of CR/LF mismatches inside cells in Excel filter
Improved handling of textboxes in Excel
Exported PowerPoint presentations now have the target language set
TTX files now default to UTF16 on export
Empty TUVs in TTX files are handled correctly
Fixed a problem with exporting all languages in a single BIF/TMX file (in a project)
Correct escaping of backslashes in C/Java filter
Fixed extraction of non-textual strings in C/Java
Support for importing comments in C/Java filter
Improved CJK character and font handling in MIF
Improved codepage handling for MIF
Rewritten Trados WB filter
Fixed handling of escaped backslashes in POT files
Missing target language specification no longer results in crash in POT files
Improved codepage detection on import for POT files
Fixed language mapping when exporting RTF files
Improved handling of hidden text in RTF
Correct handling of French quotes in RTF
Improved handling of fields in RTF
Improved handling of HTML in Access/ODBC fields
Improved handling of control types in RC files
Support for extended dialogs in RC files
Correct handling of certain patterns in SGML files
Improved handling of entities in non-translatable text in XML/SGML files
Improved handling of incorrectly defined entities in DTDs
PageMaker and Quark XPress encoding support
Project comments now have unlimited length
Fixed problem when exporting lexicon entries that contain portions
Improved subset restriction handling in satellite export
Splitting and joining no longer allowed in any type of satellite
"Accept all multiple matches" option added (not documented in 273)
No longer reports and error when duplicates are not found
Correct handling of incorrect SQL syntax in project view's row selector
Fixed AutoCorrect handling in long sentences
Improved handling of mismatched curly brackets and backslashes
Significant improvements in number and code handling/repair in Assemble, Propagate and AutoSearch
Improved handling of portions in Assemble
Various improvements to External View
"Suppress embedded codes" and "Export row ID" options now mutually exclusive in External View
The External View export option “Microsoft Word Document” was replaced by “Rich Text Format”, which should solve all the strange font problems in External Views
Correct reporting of errors related to Settings.dvset
Improvements to manual code checking usability
DVX can now run under a normal user account without administrator priveleges (Installation still has to be done with an administrator account)
Fixed some problems with handling of Turkish
Changing options in Tools > Options now clears the cache so that no older portions will be displayed
 

7.0.273

Inserting portions from the MDB will now work correctly again
Alt-down no longer inserts a question mark
Various bug fixes to the Excel Filter
Various bug fixes to the Trados Workbench Filter
Gridlines in the External View now show up correctly
Fixed a number of bugs specific to Windows 98 and Windows Me
Fixed a few things in the MDB import into another MDB
Solved various problems with spellchecking
Fixed a few problem related to the german ß character (Find function and Lexicon)
Various improvements to Assemble
The shortcuts Ctrl-M and Ctrl-Shift-M now work better (for comments)
The fonts in the external view are now again the same as those set in DVX
You can now import and export data from MDBs and TDBs located on a COM+ server
Various improvements to DVPNG and DVSAT satellite export
 

7.0.266

You can now join and split freely in Trados TTX files (imported in any build)
Better handling of different character sets in TTX (please see <A HREF="http://support.atril.com/disparticle.asp?ID=289DOB">the knowledge base</A>) for details.
Splitting and joining now works correctly in Trados Workbench projects <B>created in this build</B>
Fixes to satellite import / export in dvpng format
Bug fixes to all the filters
Bug fixes to the Project Explorer
Bug fixes to TMX import
Fix to Propagation with Multiple Exact matches
Fixes to Fuzzy Propagation
Merging data between DVX Memory Databases is now possible
You have the option of not requiring the Ctrl to insert Autosearch portions (Tools > Options > Environment)
A more robust COM+ mechanism (to improve handling of different DVX versions between the clients and the server)
You can now have global settings for filters (in Tools > Options > Filters)
Added the ability to set per-file import properties in the New Project wizard
When sending a project to a memory database, you can choose to 'Delete all previously sent pairs from this project'
Better handling of translations between the same primary languages (e.g. US English to UK English)
Various improvements to Scan, Assemble and Autosearch
Fixes to problems with satellites and PNG files
Fixes to TDB import/export (date and user fields now supported)
Fixes to MDB import/export
A few new User Interface languages (English, French, German, Dutch and Spanish are now available)
The DVPNG extension is now associated with DVX
A better External View
You can now Accept all Multiple Exact Matches
The Trados Workbench (doc & rtf) filter has been completely rewritten.
The Excel filter has been completely rewritten
Fixes to problems with the Spellchecker
Corrected various glitches in the User Interface
 

7.0.238

Assemble sometimes failed to replace terms when repairing a fuzzy match.
Various problems in the SGML/XML filter and the filter editor.
Mismatched rows when exporting PPT files. The filter has been rewritten almost from scratch - it ungroups shapes in all master slides, processes the title master (it previously only processed the slide and note masters) and is considerably faster.
Grouped shapes in an Excel file no longer cause the filter to import a partial file (the problem was actually caused by yet another bug in Excel's VBA). Needless to say, shapes are now ungrouped so that text can be extracted from them.
COM+ problem: sending entire projects and problems with the dongle DLL.
Problems with reimporting satellites and PNGs, and packaging translated satellites back into PNGs.
Various problems in the RTF filter.
Freezing of Find dialog when working with separate edit boxes.
Focus issues in the Scan and Lookup windows.
In some cases, when typing in a translation, the cursor would alternately jump between the beginning and the end of the sentence.
A very minor bug where the display of the index number of a portion higher than 10 would be clipped.
Specifying a field to be imported as "User" when importing data into an MDB would sometimes cause a crash.
Trailing end-of-segment mark was selectable in the main grid, which sometimes caused problems if it was deleted.
Switching word order using the keyboard shortcuts sometimes caused problems.
The Access filter would always convert certain characters into HTML entities even if the field was marked as plain text.
 

7.0.232

Improved the performance of a project-wide Replace All operation when in single file view.
Fixed a number of problems with generating Pack N' Go files from projects that contained PowerPoint, Word or Excel files.
Corrected a problem with global replacement of fonts in the MIF Font Mapper UI.
Corrected a problem in the MIF filter to prevent fonts that are not mapped from loosing the FPlatformName tag.
Corrected problems in the alignment of MIF, OpenOffice.org, Excel and PowerPoint files.
Made extensive changes to Propagate.
Made extensive changes to Assemble.
Pressing P or S while editing in the AutoSearch window no longer exits edit mode.
The scoring code no longer reports matches with more than %100 (this was a silly mistake related to special weighting asigned to codes at the beginning or the end of a sentence).
Overwriting a MDB entry no longer sets its date to 00:00:00.
Alt+DownArrow now stops at rows with marked with an X (wrong codes), even if they are marked as finished or exact.
Fixed a number of problems in the spell-checker.
Deleting duplicate rows in an MDB no longer reports '0 duplicates found'.
Search & Replace is now case-sensitive in exactly the same way as Microsoft Word is (so if you want to replace "Word" with "WORD", you need to check the "Match case" checkbox).
Improved the handling of marked sections in the SGML filter, as well as the overall performance of the filter.
Fixed the handling of escaped characters in the MIF filter (the official Adobe documentation was wrong!).
Empty rows can now be locked.
Partially overwriting two consecutive blue underlined portions no longer results in strange behavior.
Fixed a problem with PNG files which affected the export of Word, Excel and PowerPoint files from them.
Fixed the handling of files in the Project Explorer that sometimes caused invisible Drag & Drops. Other improvementes in the PE for Windows 98 and Me.
Fixed a problem that caused data imported into the MDB to be truncated.
Fixed a number of problems in the DOC and RTF filters.
Attributes are no longer lost when repairing TDBs.
On Windows NT, 2000, XP and 2003, in some circumstances you couldn't enter characters that weren't in the default system code page (unless you used an IME). This has now been fixed, so you can enter any Unicode character supported by Windows.
Fixed problems with character conversions in Interleaf. WARNING: If you translate between languages that use different codepages, you MUST change the font in the exported Interleaf file to one that supports the target character set.
Fixed a bug that caused some files to get exported incorrectly.
Fixed a number of problems in the TTX filter, including:
For sentences that are already translated in the original, the handling of codes (in particular mismatched codes) has been greatly improved. Unfortunately, this means that we have been forced to turn off the mechanism that checks for correct codes before exporting (only for TTX files).
The filter no appends duplicate entries at the end of the exported file.
Worked around a problem in Windows 98 and Me where the OS didn't properly support case mappings for certain code pages. This means Find & Replace now work correctly on those OSes.
Fixed a problem that caused the status of some sentences reimported from an External View to be cleared.
Fixed some minor bugs in the fuzzy terminology matching code.
Fixed some minor bugs in the UI.
<B>WARNING</B>: You will need to repair your projects and MDBs (but not TDBs). Otherwise you may experience some inconsistent behavior when working with short sentences and portions in Assemble and Propagate (we've changed the indexing slightly to improve the handling of leading and trailing symbols).

7.0.227

Corrected a bug in the RTF filter.
Corrected a bug in the OpenOffice.org filter.
Improved speed of RTF and Word import when "ignore hidden text" is selected.
Improved the Excel filter.
Corrected codepage problems in filters.
Importing from TMX into a translation memory doesn't crop the last character of the username anymore.
Solved a problem in exporting PowerPoint files under Office 97.
Fixes to XML filter creation process and XML import.
Search and Replace double spaces works.
 

7.0.226

Most filters have been changed extensively to work properly on DBCS platforms.
Fixed problems with fuzzy propagation.
Inserting portions no longer inserts spaces after hyphens, codes, brackets and opening quotation marks.
Case conversions are now only applied when specified.
Three word portions from the MDB are now shown correctly in AutoSearch.
Send Project to MDB correctly overwrites sentences sent manually.
Improved handling of numbers in Propagate and Assemble.
Lexicon entries are now overwritten if necessary.
Consecutive duplicate sets are now marked correctly.
When translating from Chinese or Japanese, Pretranslate no longer uses Assemble unless it is specified.
Importing DV3 AutoText entries into AutoCorrect now works.
The Copy button in the Scan Results window works.
F5 no longer overwrites locked rows.
Non-sequential rows can no longer be joined.
Find works in the source column when the source language is Japanese.
Find now finds text that spans both normal text and alternative portions (blue underline).
All known focus issues have been fixed. Alt+Tab and Ctrl+Tab no longer move the focus away from the grid.
Row selection is now correctly restored when reopening a file.
Cancelling a login request works.
The Aligner window no longer appears in black until resized.
Dragging folders onto the Project Explorer works again.
When pressing Alt+Down at the bottom of the grid, the cursor no longer disappears.
The Lemma field now scrolls horizontally when the text exceeds the size of the text box.
In Tools->Options, the "Delete All" button in the Subjects tab and the "Delete" button in the AutoCorrect tab now work correctly.
Improved handling of numerical character entities in HTML.
Fixes to the Word, HTML, Excel, PowerPoint and OpenOffice.org filters for the Aligner.
The OpenOffice.org filter now works correctly under Windows 98.
Cancelling an MDB export process works.
Solved some problems with FrameMaker MIF export.
Improved support for filenames with characters outside the default system code page (on NT, Windows 2000 and Windows XP).
Fixed some delimiter selection problems in the TDB and Lexicon export.
Fixed problems in the Trados TXT export from MDB (repeated ChU and "0 rows exported").
Reset All Terminology Warnings works in All Files view.
Status is correctly reimported from External View.
Cancelling an SQL Select statement no longer gives a warning message.
 

7.0.219

Fixed a bug with repairing fuzzy matches.
Solved an issue with importing Word/RTF ignoring hidden text.
Fixed a bug with case sensitivity in Find/Replace.
Fixed a problem with client and subject attributes in the target term when pressing F11.
 

7.0.218

Locked rows could still be edited when working with separate edit boxes.
Fixed problems with decimal conversions in Assemble.
Fixed some problems with word deletion and replacement in Assemble.
Fixed a problem with some duplicate rows not being detected if they were the last set in the project.
Fixed screen update issues in the spell-checker.
Fixed a problem in the terminology check that incorrectly reported terms as incorrect even if the databases contained a larger portion that covered them.
After sending selections to the TDB or the MDB, the text is now deselected.
Deleting a translation in the MDB no longer moves the display back to the top.
Deleting all assembled translations no longer deletes assembled rows that were marked as finished.
Exporting an MDB or TDB to a new Access database now works correctly.
Clients and subjects specified when sending to the TDB from the project are now stored correctly.
Fixed some problems with exporting P&G files with database subsets.
Exporting OpenOffice.org documents that contain images now works correctly.
The built-in spell-checkers can now be used for all sublanguages.
 

Is Déjà Vu compatible with

Operating systems ?

Microsoft

Déjà Vu is compatible with Microsoft Office 2000/2003/2007/2010.

Déjà Vu is designed to run in Windows environment. DVX can run in Windows 7 (or older), 32 or 64 bits. DV3 is not designed to run in Windows 7 and such configuration is not supported. It would be preferable for you to upgrade to DVX (for information about the conditions you can contact our sales department:contact@atril.com.

Alternatively, you could come into contact with users that have been able to install DV3 on Windows 7 using a Windows XP compatibility mode through our mailing list.

To register in the dejavu-l list, send an empty email to:
dejavu-l-subscribe@yahoogroups.com

You can access the group page on:
https://groups.yahoo.com/neo/groups/dejavu-l/conversations/messages

Mac

Déjà Vu X is designed to run only on Windows. Anyway, we know many users who have been able to run Déjà Vu X in Mac computers using emulator programs (such as Parallels or VMFusion), but this kind of configuration is not officially supported.

You could come into contact with other users experienced in such configurations through our mailing list.

In order to register in the dejavu-l list, you should send an empty email to:
dejavu-l-subscribe@yahoogroups.com

You can access the group page on:
https://groups.yahoo.com/neo/groups/dejavu-l/conversations/messages

File formats ?

Project Import format list

Whatever type of file you work with, Déjà Vu X presents you with a uniform interface, displaying only translatable text, so you can work comfortably without having to worry about overwriting formatting and layout information.

Déjà Vu X  has built-in filters that allow you to work with:

  • Microsoft Word
  • RTF
  • Microsoft PowerPoint
  • Microsoft Excel
  • OpenOffice.org/StarOffice
  • Microsoft Access
  • ODBC-compliant data sources
  • FrameMaker
  • PageMaker
  • QuarkXPress
  • InDesign
  • Interleaf/Quicksilver
  • Plain Text
  • Help Content (.cnt)
  • HTML (including scripts and ASP)
  • SGML/XML
  • Java Properties
  • RC
  • C/C++/Java source files
  • GNU gettext files
  • IBM TranslationManager
  • Trados Word/RTF
  • Trados TagEditor
  • TMX
  • EBU subtitle files

Other CAT tools?

We at Atril believe in open systems and standards. We have this strange idea that you –and no one else—have the right to choose whichever CAT tool suits you best.

Sure, you have to satisfy your customers by using the resources and databases they provide you, and adapting to their discount scheme. But that doesn't mean you have to buy or use exactly the same tool they used to create or manage those resources.

Besides, in today's competitive software market, no translator or agency can be expected to own all text processing programs, be it Translation Memory tools, DTP programs or simple word processors.

So, when choosing a Translation Memory tool, one important factor in your decision –besides features-- should be compatibility.

TMX formats

How to create a TM from a tmx file

The first thing you need to do if you have a TMX file, is to “transform”/import it to a TM. To create a TM, you go to File>>New>>Translation memory>>etc…

Then, you open the TM you want to import the file into (the new one or an older one) and select File>>Import>>File or Database>>etc…(making sure you select as type of file TMX).

How to export a TMX file from a TM:

You have to open the actual TM in DVX and go to Files>>Export>>File or Database. Then you follow the wizard, making sure that you select the option “TMX”.

TTX

How do I handle TTX (Trados Tageditor) files in DVX?

There are a number of special things about the way TTX (Trados TagEditor) files are handled inside Déjà Vu X.

  1. Preparing the TTX files

    The TTX files should be presegmented by TagEditor or by the tool used to generate them. In Trados, the option "Segment unknown sentences" should be checked when preparing the files, because Déjà Vu X only imports segmented sentences.

  2. Importing TTX files into Déjà Vu X

    Add the files to the project in the usual way (i.e. with the Project Wizard or with the Project Explorer). Just before they are imported, you may be presented with a window asking you to confirm which languages are present in the file(s). It will show the language abbreviation (as present in the TTX file) in the left column and give you an option of changing the language that Déjà Vu X treats it as.

    If, after importing the file(s), you see that they are empty and don't contain any rows, then you should go back to step 1. and make sure that you (or your client) selected "segment unknown sentences". If the file imported successfully, then you should see the source sentences along with some of their translations.

    If there are no useful translations in the original TTX file (because e.g. it was segmented with an empty Trados memory), then you can delete all existing translations in the file by right-clicking in the project area and selecting "Clear all Translations".

    You may also be presented with orange coloured rows, which indicate XTranslated segments.

  3. Embedded codes inside TTX projects

    When importing a TTX file, Déjà Vu X keeps all existing formatting information from the original. Since Trados and other tools do not have the same concept of embedded codes as Déjà Vu X does, this may result in difficulties. If the formatting of a target sentence is different from the source formatting, then the embedded codes in that sentence pair will not match.

    In contrast to what happens with all other file formats imported into Déjà Vu X, you don't need to correct these code mismatches if they are present right after you imported the TTX file.

    You can safely ignore these particular code mismatches.

    However, when you are manually translating a given sentence, you should still try and place the source codes at the appropriate places in the target sentence.

Workbench

Importing Trados resources into Déjà Vu format

Exporting Déjà Vu resources to Trados (or other) format

  • How to import a Trados memory into DV

    Please follow these steps:

    1. From within Trados, open (in exclusive mode) the translation memory you would like to import into Déjà Vu.
    2. Select File/Export. Select the fields you want the exported file to contain. Click OK.
    3. Enter the name of the file to be saved.
    4. Open Déjà Vu's Database Maintenance Program and open the database you want to add the Trados memory to, or create a new database that will contain the Trados memory content.
    5. With the database open, select File/Import.
    6. Below "External database system" select "Trados WB database".
    7. Set the "external files' character set" to Windows, and set the "Language codes available in Workbench database file" to the proper source and target language of the memory.
    8. Select the appropriate .txt file you exported from Trados, and click OK.
  • How to import a Multiterm glossary into DV

    This process is a little more complex, since Multiterm and Déjà Vu have different database structures. Please follow these steps:

    1. From within Multiterm, define an export filter and select the fields you want to import into Déjà Vu. In order to simplify the process, remember to export only the source term and the target term (in the case of a simple, bilingual glossary). At any rate, the resulting exported items must be in the form of a simple table or text delimited list. For more information on this procedure, please refer to the Multiterm Manual.
    2. From Déjà Vu's Terminology Maintenance program, open or create the terminology database you want to import the Multiterm entries to.
    3. From the File menu, select "Import" and follow the usual Déjà Vu procedure for importing glossary lists. You must select the appropriate text delimiters, etc. For more information on this procedure, please refer to the Déjà Vu Manual.
  • How to open and process a Trados pretranslated file with Déjà Vu

    Please follow these steps:

    1. In Déjà Vu, create a new project. Follow the usual steps for creating a Déjà Vu project, but when prompted for the file format of the source files choose "Trados Workbench".
    2. Import the Trados Workbench files as usual into Déjà Vu. Source segments will now appear in the left column. Trados pretranslated segments will appear in the right column.
    3. Confirm/Edit/Translate the target sentences as usual (in the Déjà Vu edit box).
    4. When you finish, export the project as usual.
    5. The translated files will be saved in the target file directory in Trados tagged text format. This file(s) can be "cleaned up" with Trados by your customer, thus updating the original Trados memory.
  • How to export a DV memory to Trados (or other) format

    Please follow these steps:

    1. Open Déjà Vu's Database Maintenance program.
    2. Open the memory database you would like to export to Trados (or other) format.
    3. From the File menu, choose Export.
    4. Below "External database system", select the desired option. If it is "Trados WB database", choose "Windows" as the "External files' character set" and select the language codes to be used by the Trados database.
    5. Select the destination file and the export filter, if necessary.
    6. Click on Export.
  • How to export a DV terminology database for use with Multiterm (or other applications)

    Please follow these steps:

    1. Open Déjà Vu's Terminology Maintenance program.
    2. Open the terminology database you want to export.
    3. From the File menu choose Export.
    4. Below "External database system" choose one of the many open formats available for exporting the database. All of them can be used by practically any database or terminology application in the market, including Multiterm.
    5. Select the destination file and the export filter, if necessary.
    6. Tick on the files to be exported. Defaults are Source Term and Target Term.
    7. Click on Export.
  • How to export a file translated with Déjà Vu to Trados (or other) format

    In order to export a translated file in Trados tagged text format, the source text file has to be processed first in order to tag it into a typical Trados format file. This can be done with Trados (even with the free demo version). The file can then be translated as a regular Trados project in Déjà Vu. Please follow these steps:

    1. Using the appropriate application (e.g., MS Word) first save the file as an RTF file. Save a copy of this file, since the processed Trados-tagged file will overwrite it.
    2. Open Trados (full or demo version) and open one memory (any one, or even an empty, dumb memory --configured with the appropriate source and target language, etc.).
    3. Select "Translate" from the Tools menu. Click on Add and select the RTF file to process.
    4. Tick in the box "Segment unknown sentences". Leave all other default settings and click on Translate.
    5. The RTF file is now tagged the Trados way and can now be translated as a good old Trados project with Déjà Vu.

For more information, you are always welcome to contact support@atril.com.

Excel TM and TDB

How to export a Translation Memory or part of it:

  1. On DVX, File>>Open>> find the specific TM and select “Open”.
  2. When the TM opens, on DVX select: File>>Export>>File or Database.
  3. On the Export Wizard that opens, select “Next”.
  4. Specify the Data Format to “Deja Vu X Translation Memory” and select “Next”.
  5. Press “Select”, select the name and the location of the TM to which you want to export the data and press “Save”. After the TM is selected you can press “Next”.
  6. At this point you can choose the languages you want to export by highlighting the language and selecting “Add ->”. This is the step that enables you, if you wish, to extract the data of specific languages (If you want to export the whole Database you have to select all the languages. If you don’t choose anything it won’t export anything). You can continue by selecting "Next".

    If there is any other criteria, according to which you wish to extract data from the original TM, you should type the conditions in the “Filtering Conditions:” field, in the same format as an SQL WHERE clause. (In the example shown below, the project id “prjid” number can be found on DVX→ “Project”→ “Properties”→ “Project ID: .....”. After you “Validate” the clause, you can select “Next” to continue. In the User Guide for DVX Workgroup, page 565, you can find “Samples of Regular Expressions for Export from Translation Memory and Terminology Database).

  7. You may select “Finish” to export the data into the new TM.

Exporting-Importing Terminology Databases.

Question:

When I export a translation memory subset from a DVX project and then import this subset into another translation memory, I do not encounter any problems. However, when I try to do a similar thing with the terminology subset, I encounter the following problem. DVX format does not appear to be a valid data format, only earlier versions of Deja Vu and other file formats (text, MultiTerm, Access, etc). What am I doing wrong here? When exporting the terminology subset from a DVX project, I am not given an option to export it in one of the supported formats.

Answer:

You are not doing anything wrong. Déjà Vu X does not have the option for exporting Déjà Vu X Terminologies to another Déjà Vu X Terminologies. That's because each Terminology database has different attributes, and each attribute can contain different values, so the configuration of merging two Déjà Vu X terminologies is not a simple work.
We advise you to use Excel as intermediate format for exporting the terminologies and then import the Excel file into the other Déjà Vu X Terminology.

How to export a Translation Memory or part of it:

  1. 1) Open your DVTDB file
  2. File>>Import>>File or database
  3. Select Excel and your Excel file to import
  4. Check "First rows as field names"
  5. Check "Import As" in "Field1", and select "Main Lemma", "French", and "Western European (Windows)
  6. Check "Import As" in "Field2", and select "Translation", "For Field1", "Russian", and "Unicode".
  7. Press Next and Finish.

The entries should be added to the bottom of the DVTDB.

RTF external view

The External View format is a format specifically created for proofing or checking unresolved issues outside of Déjà Vu X Workgroup. This allows you to export translated and commented rows into a tabular Word or HTML format in which proofing can be performed and outstanding questions can be answered.

The main benefit of these formats is that they can be used across platforms and thus even by people who could not install a copy of Déjà Vu X Workgroup.

This format has two major purposes:

  • It allows for proofing outside of Déjà Vu X Workgroup with the subsequent re-import back into Déjà Vu X Workgroup.
  • It allows for the review of comments and questions that the translator, editor, or project manager may have.

The benefit of this format is a complete platform and application compatibility through the use of Microsoft’s Word and in particular HTML format.

To create an External View:

  • Open the project file from which you would like to export an External View file.
  • Select File>Export>External View.

To import an External View:

  • Open the project file from which you would like to import the External View file into.
  • Select File>Import>External View.

Languages ? –(yes, regional settings)

Character Conversion and Supported Languages

Everything that takes place in Déjà Vu X Workgroup happens within Unicode. This means that all the languages supported by Windows are supported by Déjà Vu X Workgroup as source and target (including double-byte and right-to-left languages). This does NOT mean that texts which did not originate in Unicode will be exported into Unicode. Depending on the file type, target language, and your choice of a code page, the translated text will have the same code page as the original, or one that corresponds more closely to the file type/target language in question.

How to enable East Asian languages in Windows.

Déjà Vu X gets the languages from Windows, so if you have enabled support for East Asian languages in Windows, you will have them in Déjà Vu X. In order to enable these languages in Windows, you should open “Control Panel >> Regional and Language Options >> Language” tab and select the two “Supplemental Language Support” options. You should also open “Control Panel >> Regional and Language Options >> Advanced” tab and select all the “Code page conversion tables”. Finally, you should restart Windows and your Déjà Vu X should have all the Windows languages enabled.

Installation

Evaluation version ?

The evaluation version of DVX is the Professional version, activated for 30 days from the day you download it.

To get the evaluation version of DVX, visit our website www.atril.com, register, download DVX and ask for an evaluation code. If you don’t receive an activation code, you won’t be able to access the full functionalities of Déjà Vu Professional.

To get your activation code Déjà Vu, please follow these steps:

  • Open the Déjà Vu interface
  • Click on the “Help” menu
  • Click on “evaluation code”
  • Send your serial number to support@atril.com
  • We will send you your activation code
  • Enter this code in the evaluation code window

What if my Dongle is not recognized?

  • Unplug the dongle.
  • If you have Windows Vista, disable the User Account Control (UAC).
  • Enter an execute "c:\Program files\ATRIL\Deja Vu X\Dongle\setupdrv.exe" /u in the Windows start >> Run… menu for uninstalling your current dongle drivers.
  • Reboot your computer.
  • Enter an execute "c:\Program files\ATRIL\Deja Vu X\Dongle\setupdrv.exe" in the Windows start >> Run… menu for installing only the USB dongle drivers.
  • Turn off the computer.
  • Plug the dongle.
  • Start the computer.
  • Let Windows install the software required by the dongle.
  • Run Déjà Vu X.
  • Enable again the User Account Control (UAC)

My Dongle is lost or broken. How can I replace it?

You need you to send us an e-mail to support@atril.com:

  • The type of license you are using (Standard, Professional or WorkGroup)
  • Your serial number : you find it under help/evaluation code
  • The number written on your dongle

Then you need to send your defected/parallel dongle to ATRIL at the below-listed address:

M. Lorenzo Benito
Atril Language Engineering SL
Calle Cólquide 6, Edificio Prisma, Portal 1, Planta 1
28231 Las Rozas, Madrid
Spain

The dongle replacement costs 100€ + 7€ shipping costs - please follow this link to proceed to the on-line payment.

As soon as we receive your payment, we will send you the new dongle. In the meantime, we are going to send you a temporary activation code to keep on with Déjà vu.

How do I install my network dongle?

Network dongle installation:

These are the steps you need to follow to correctly install the network dongle on the server, and to configure the client machines to use it:

  1. Copy DDNET.exe and SetupDrv.exe from one of the client machines to the ‘dongle server’ (the server machine where the network dongle is plugged in). You can find these files in "C:\Program files\ ATRIL\Deja Vu X\Dongle".
  2. With the dongle unplugged, run SetupDrv.exe to install the dongle drivers on the server (the client machines don’t need to have them installed, since the dongle is not attached locally). Once the drivers are installed, please connect the dongle and let Windows recognize and configure the hardware.
  3. Move the copy of DDNET.exe to a permanent folder (e.g. C:\Program Files\ATRIL\Dongle). We will be configuring DDNET to run as a service later on, so it needs to be accessible.
  4. On the server machine, you will need to create a network share (i.e. share a directory on the server) to which all the workstation machines have *full* access rights. You will need to set these rights not only in the Share Permission tab for the directory, but also in the Security tab for it. This share will be used by the server and the clients to communicate.
  5. Now that we have a path for the network dongle to use, we need to configure the DDNET service. In order to do this, you need to run DDNET.exe with the following command line parameters, DDNET /I<DongleNetworkShare> /s where <DongleNetworkShare> is the local path of the shared folder; please note that there should be no space between the /I and the path (e.g. DDNET /IC:\MyDongleShare /S).
  6. Now, we need to configure the clients. In the \Dongle subfolder of the DVX installation folder of the clients, you will find a file called DV2.INI. You need to edit this file, and change the value of the DinkeyNetPath line to point to the network share you created in step 4.
  7. Once you’ve changed DV2.INI, please copy it to your C:\WINDOWS folder.
  8. Repeat steps 6 and 7 on all the client machines (or just copy the DV2.INI file you modified on the first client to the C:\WINDOWS folder of all the other client machine). On the client machines, DVX should now detect the network dongle correctly.

How do I install the COM+Server?

Déjà Vu X COM+ Server Installation giving permissions to Everyone group:

In order to install Déjà Vu X COM+ Server you should follow these steps:

  • Enable the Windows Option: “Enable network COM+ Access” in “Control Panel Add or remove programsAdd/Remove Windows ComponentsApplication Server”.
  • Create and share a new folder to store the Translation memories and terminology databases. The shared folder should have the following share and security permissions:
    • Share ( “Share” tab of the folder properties):
      • Select “Everyone” and give “Full control” permissions.
    • Security ( “Security” tab of the folder properties):
      • Add “Everyone” and give “Full control” permissions.
  • Install the Déjà Vu X COM+ Server component and activate it. The Déjà Vu X COM+ Server component is downloadable from
    here. In order to activate it you should click on “start >> All Programs >> Déjà Vu X COM+ Server >> Activate Déjà Vu X COM+ Server” and send to support@atril.com the installation serial number. We will send you a code that will permanently activate the Déjà Vu X COM+ Server installation.
  • Set the permissions in the server so the clients could Access to the shared databases using the Déjà Vu X COM+ Server application:
    • Go to “Administrative tools → Component services” and then to “Console Root → Component Services → Computers → My computer → COM Applications” and open the properties of “Déjà Vu X COM+ Server” COM application. Then select "Network Service” in the “Identity” tab.
    • Go to “Administrative tools → Component services” and then to “Console Root → Component Services → Computers” and open “My Computer” properties. Open “COM Security” tab and add the “Everyone” with all the access permissions allowed on:
      • Access Permissions → Edit Limits”
      • “Access Permissions → Edit Default”
      • “Launch and activation permissions → Edit Limits”
      • “Launch and activation permissions → Edit Default”

Client installation:

  • Set permissions in each client computer so the server can access the information that the client is managing with Déjà Vu X Workgroup:
    • Go to “Administrative tools → Component services” and then to “Console Root → Component Services → Computers” and open “My Computer” properties. Open “COM Security” tab and add the “Everyone” with all the access permissions allowed on:
      • ”Access Permissions → Edit Limits”
      • “Access Permissions → Edit Default”
      • “Launch and activation permissions → Edit Limits”
      • “Launch and activation permissions → Edit Default”

Now the client computers should be able to work with Déjà Vu X Workgroup sharing Translation memories and terminology databases (not projects) using the Déjà Vu X COM+ Server component installed on the server.

How do I update my Déjà Vu license?

To download the latest build of DVX, you can visit our website www.atril.com , register and download DVX. If you face any problems, contact support@atril.com for further assistance.

How do I upgrade my license?

You can proceed to the purchase either by:

a. Bank transfer : the bank details are listed on the attached order form
b. Or by credit card on our website www.atril.com

Once we have received your payment we will generate an upgrade code. Therefore you need to follow the below-listed procedure:

You should run the program Ddlook.exe, which displays information about the dongle, and send me a screenshot of the result.

Ddlook.exe is normally found in the folder C:\Program Files\ATRIL\Deja Vu X\Dongle\DDLOOK.EXE (if you have Déjà Vu X installed), or the folder C:\Program Files\DejaVu (if you have Déjà Vu 3 installed).

Alternatively, you may find a copy included with the latest dongle driver package: http://dvx.atril.com\dvx\dd.4.20.7.0.zip.

This program will output some information about the dongle. You should make a screenshot of this and send it to me. To make a screenshot:

  1. Open the window you wish to make a screenshot of.
  2. Press the keys called “ALT” and “Print screen” (sometimes called “Prt. Scr.” or other such names).
  3. Open Windows Paint (Start>Programs>Accessories>Paint), or any Image Editing Software you like to use.
  4. Press Ctrl-V; this will paste the image into Windows Paint.
  5. Click on File>Save As.
  6. Type a filename for the image, and in the “Save as Type” combo box, select “PNG”.
  7. You will now have a highly compressed image file that can be sent by e-mail easily.

With this information and after having received your payment we will be able to generate an upgrade code.

 

 

Errors

Embedded codes

I cannot export file from DVX.

Review all the embedded codes in the Déjà Vu X project. In order to do so, please follow these steps:

  1. Open the Déjà Vu X project and click on the first segment of the project.
  2. Press “Ctrl+Shift+F8” for check the embedded codes: Déjà Vu X will access to the first segment with wrong codes, and it will give you an error message in the status bar (low on the DVX Window).
  3. Fix manually the wrong codes: place them in the same order as in the source segment and, approximately, in the same position. Remember that you must not change the source text.
  4. Go to step 2 and repeat the steps until Déjà Vu X gives you the message in the status bar “No mismatched codes were found”.

If these steps do not work, try to send the project to the translation memory (Alt+F12), reimport the file and pretranslate it. Try to assemble the remaining empty rows (spliting(ctrl+i) or joining(ctrl+j) segments might be necessary) placing the codes properly (almost all the document will be filled with exact matches).

What is considered a missmatched embedded code and how can I search for missmatches?

Missmatched embedded codes are considered the following:

  • wrong order of appearance of the codes
  • there is text (or space) before the first code or after the last code

These are the problems that do not allow the file to be exported. Generally speaking other variations in the placement of the codes, only create problems in the exported file in isolated cases. You can search for missmatched embedded codes by press “Ctrl+Shift+F8”. Déjà Vu X will access to the first segment with wrong codes, and it will give you an error message in the status bar (low on the DVX Window).

Embedded codes cannot be placed in the same place/order because of the difference in the word order between source and target language.

Any code can be put anywhere in the segment, as long as it doesn’t create a conflict that prevents the file from exporting (such conflicts are the wrong order of appearance of the codes and also if there is text (or space) before the first code or after the last code). So generally we place the codes in more or less the same positions as they are in the source, but don’t have to worry too much about them, as most of them do not even contain a format that can be visible in the exported document. Ofcourse, there are cases that it is difficult to place the codes in the exact same place as the source, due to difference in word order between the source and the target language. In this case we respect the order of the embedded codes in the source segment and place them in a way that they are not considered mismatched. Then we export the document and see if we got the desired result or if we need to alter something. In any way, the order in which the codes appear in the source should be respected and not altered arround to follow the different word order.

How to handle embedded codes in a project.

Embedded codes should be placed in the target segment, approximately, in the same position as in the source segment. Remember that you must not change the source segment.

As DVX is concerned, any code can be put anywhere in the segment, as long as it doesn’t create a conflict that prevents the file from exporting (such conflicts are the wrong order of appearance of the codes and also if there is text (or space) before the first code or after the last code). So generally we place the codes in more or less the same positions as they are in the source, but don’t have to worry too much about them, as most of them do not even contain a format that can be visible in the exported document. Ofcourse, there are cases that it is difficult to place the codes in the exact same place as the source, due to difference in word order between the source and the target language. In this case we respect the order of the embedded codes in the source segment and place them in a way that they are not considered mismatched. Then we export the document and see if we got the desired result or if we need to alter something. In any way, the order in which the codes appear in the source should be respected and not altered arround to follow the different word order.

Before exporting a document, we should always check for mismatched embedded codes:

  1. Open the Déjà Vu X project and click on the first segment of the project.
  2. Press “Ctrl+Shift+F8” for check the embedded codes: Déjà Vu X will access to the first segment with wrong codes, and it will give you an error message in the status bar (low on the DVX Window).
  3. Fix manually the wrong codes: place them in the same order as in the source segment and, approximately, in the same position. Remember that you must not change the source text.
  4. Go to step 2 and repeat the steps until Déjà Vu X gives you the message in the status bar “No mismatched codes were found”.

Error 1935

Error number: 1935 – Cannot install DVX.

Error message:

"Error 1935. An error ocurrred during the installation of assembly ‘policy.8.0Microsoft VC80.ATL.processorArchitecture=’x86’, type=’win32.policy’,version=’8.0.50727.762’publickeyToken=’1fc8b3b9a1e1833b’.

Problem cause:

If the user is using windows Vista, the problem will probably be solved if they disable the User Account Control.

Solution:

In order to disable the User Account Control, please follow these steps:

  1. Open Control Panel.
  2. Under User Account and Family settings click on the "Add or remove user account".
  3. Click on one of the user accounts, for example you can use the Guest account.
  4. Under the user account click on the "Go to the main User Account page" link.
  5. Under "Make changes to your user account" click on the "Change security settings" link.
  6. In the "Turn on User Account Control (UAC) to make your computer more secure" click to unselect the "Use User Account Control (UAC) to help protect your computer". Click on the Ok button.
  7. You will be prompted to reboot your computer. Do so when ready.

Other things to try:

  1. Another thing that you could try is to reinstall DVX and run the installation file as administrator. You can do that if you right click on the file and select run as administrator.
     
  2. You can try to install the Microsoft Visual C++ 2005 SP1 runtime manually. You can download it from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=200B2FD9-AE1....
     
  3. Can you confirm that you were able to install the MSVC 2005 SP1 runtime manually and that it was completed successfully? And, if so, do you get the same error as before when installing DVX? We’ve actually seen this error in person before, and can confirm that installing the runtime manually fixes it…
    If you can confirm all the above, another thing that could have created this problem is that certain pre-installed OEM tools might be causing this For example, this problem may be caused by programs such as WinTools, WinEasy, WebSearch, Easy Installer, System Mechanic, and HP Component Manager. (source: http://social.answers.microsoft.com/Forums/en-US/vistaprograms/thread/d7... (which leads to http://support.microsoft.com/kb/902330)).
    In this case, you would have to identify the program that is causing the problem and uninstall it. You can install it back after completing your DVX installation.

Error 2015

Error number: 2015 - Could not get the control's or form's Windows Handle.

Error message:

“Error number: 2015 Location: Module 'fromSplash', Routine 'Form_Activate', Line Number 333 Description: Could not get the control's or form's Window Handle [Extended Info: Band: barAutoSearchSentences, Tool:fromAutoSearchSentences].”

Problem cause:

The error is caused by an incompatible version of the file atl.dll that is installed when a new update from Microsoft is installed on the computer, either manually or by Windows Update.

Solution:

To solve this problem, please download and install the latest build of Déjà Vu X, available from http://www.atril.com/dvx/current/Websetup.exe.

Error 1609

Error 1609 when trying to install DVX.

"Error 1609: An error occurred while applying security settings. User is not a valid user or group. This could be a problem with the package, or a problem connecting to a domain controller on the network.

Check your network connection and click Retry."

Solution:

To complete the installation a Users group must be created. This can be done from Control Panel > Administrative Tools > Computer Management and then expanding System Tools > Local Users and Groups > Groups. Right click Groups and choose New Group, name it "Users".

After doing that, proceed with the installation.

Error 5

Spellchecker problems.

Problem:

On trying to run the spellchecker without an updated dongle, I get error 5, Module ' mSpelling', Routine ' CheckString', Line Number 2128. Invalid procedure call or argument.

Solution:

The problem appears to be related exclusively to the use of the "Spanish (Latin America)" language, which is only partially supported by Windows XP. Until we find a workaround for this problem, I'm afraid the only solution is to use a different variant of the language.

Error 91

Error number: 91 - Object variable or With block variable not set.

Error message:

“Error number: 91 Location: Module 'Settings', Routine 'AddLangDefaults', Line Number 7440 Description: Object variable or With block variable not set.”

Solution:

If this error is a one time thing, you can ignore it and continue working. If the error insists after specific actions, read the following:

The problem can be related to the connection with the Settings file, or with an error in the Jet Engine.

Please, for ensuring, do the following:

  1. Download and install http://www.atril.com/dvx/msjet/Jet40Sp3_Comp.exe.
  2. Go to http://www.microsoft.com/downloads/details.aspx?FamilyID=1e268b39-533e-4... and download and install the version of the Jet Service Pack 8 that corresponds to the language of your OS.
  3. Delete the Settings.dvset file from your DVX installation folder.
  4. Try running DVX again.

Error 339

Error number: 339 – Component ‘Actbar2.ocx’ or one of its dependencies not correctly registered.

Error message:

“Error number: 339

Location: Module 'fromSplash', Routine 'Form_Activate', Line Number 343 Description: Component ‘Actbar2.ocx’ or one of its dependencies not correctly registered: a file is missing or invalid

Problem cause:

The error is caused because during the installation of DVX, the antivirus did not allow for a file to be registered.

Solution:

To solve this problem, you can try running the following commant:
regsvr32 "C:\Program Files\Common Files\Data Dynamics\ActiveBar2\ActBar2.ocx"

If it does not work, try to unregister the file mscomct2.ocx. In order to do it, click on “Windows Start button >> Run...” and write:
regsvr32 –u mscomct2.ocx

If this doesn’t work, you will need to deactivate your antivirus and reinstall DVX through this link:
http://www.atril.com/dvx/current/Websetup.exe

Error 429

Error number: 429 – ActiveX component can’t create object.

Error message:

“Error number: 429 Location: Module 'mMain', Routine 'Main', Line Number 15 Description: ActiveX component can’t create object

Solution:

To solve this problem, try to update Windows (with Windows Update).
If it does not work, open the following link, select the language and download and install the MSXML 4.0 Service Pack 2 Microsoft component:
http://www.microsoft.com/DownLoads/details.aspx?familyid=3144B72B-B4F2-4...

Repairing

TM

  1. Go to “Tools”>>“Repair”>>“Translation Memory”.
  2. On the window that opened, find the translation memory that you have been using, select it and press “Open”.
  3. A new window opened, saying that “Repair was Successful”. You can press “OK” to continue.

Terminology database

  1. Go to “Tools”>>“Repair”>>“Terminology Database”.
  2. On the window that opened, find the terminology database that you have been using, select it and press “Open”.
  3. A new window opened, saying that “Repair was Successful”. You can press “OK” to continue.

Project

  1. Go to “Tools”>>“Repair”>>“Project”.
  2. On the window that opened, find the project that you have been using, select it and press “Open”.
  3. A new window opened, saying that “Repair was Successful”. You can press “OK” to continue.

Defaults settings

How to restore the default settings of Déjà Vu X.

You can see where the settings file is stored in: DVX >>Tools>>Options>>General>>Miscellaneous

How to restore the default layout of DVX.

Close DVX and run this link: http://www.atril.com/dvx/MenuLayoutDelete.reg

This file will restore the default layout of Déjà Vu X.

Alternatively: Open the Start menu, and click on Run. In the window that appears, type "regedit" (without the quotes), and press Return. This will open the Registry Editor. Navigate to the HKEY_CURRENT_USER\Software\ATRIL\DejaVuX registry key and delete the MenuLayout value. This should fix the problem.

How to handle specific file formats through filters?

XML

How to create a DVX SGML/XML filter.

It is very easy to create a Déjà Vu X SGML/XML filter using the SMGL or XML file you are going to translate. You should follow the New SGML/XML Filter Wizard and select the XML document to be translated in the step "Specify location of reference files". Once the wizard has finished you will get a table with the tags and two columns with check boxes: ...<>... and <>...<>

Now I advise to open the XML file using any text editor or Internet Explorer in order to see the structure of the XML document. For example, you have this document:

<?xml version="1.0" encoding="UTF-8" ?>
<document1>
<book ID="1">
<Title>Don Quijote de la Mancha</Title>
<Author>Miguel de Cervantes</Author>
<edition-date>19/02/2008</edition-date>
<Comments>Fully titled <b>The Ingenious Hidalgo Don Quixote of La Mancha</b>, is a novel written by Spanish author Miguel de Cervantes. Cervantes created a <b>fictional origin</b> for the story by creating a fictional Moorish chronicler for Don Quixote named Cide Hamete Benengeli...</comments> </book> <book ID="2"> <Title>1984</Title> <Author>George Orwell</Author> <edition-date>25/06/1975</edition-date>
</book>
</document1>

When using this document for creating the Déjà Vu X SGML/XML filter, Déjà Vu X will extract these tags (in alphabetical order):

Author
book
Comments
document1
edition-date
Title

You should select as "translatable" (<>...<>) those tags that you want to translate. In the example you will select only "Comments". But you also should select the parent tags that contains the tag with translatable text: "book" and "document1". But you have the tag "b" into Comments with also translatable text, so you should select it as translatable.

The problem appears when you import the file in your Déjà Vu X project using the SGML/XML filter: Déjà Vu X splits the text when it finds an XML tag. So it will import the text in this way:

Segment1: Fully titled
Segment2: The Ingenious Hidalgo Don Quixote of La Mancha
Segment3: , is a novel written by Spanish author Miguel de Cervantes. <-- Here Déjà Vu X applies the delimiter rules for segmenting the text
Segment4: Cervantes created a
Segment5: fictional origin
Segment6: for the story by creating a fictional Moorish chronicler for Don Quixote named Cide Hamete Benengeli...

The solution is in the "...<>...": if you check this in the "b" tag, when Déjà Vu X finds it when importing the file, it won't split here the text and you will get only two segments:

Segment1: Fully titled {1}The Ingenious Hidalgo Don Quixote of La Mancha{2} , is a novel written by Spanish author Miguel de Cervantes.
Segment2: Cervantes created a {3} fictional origin{4} for the story by creating a fictional Moorish chronicler for Don Quixote named Cide Hamete Benengeli...

Once you have created your Déjà Vu X SGML/XML filter for importing the file (it will have the extension "dvflt"), you should open your project, access to the "Project explorer" and select the XML file you want to import. In the file Properties you should select the SGML/XML filter in "Filter Definition File" property, and finally you should import the file.

Open Office 2007

To import an Open Office 2007 file, you will need to select the Filter Definition File.

WB (Workbench)

To import Trados Workbench file, you will need to select the Filter (Project Explorer/Properties/Filter)