As part of our support
for Windows Vista in Déjà Vu
X 7.5, we are including a new version of the dongle drivers,
both for 32 bit (x86) and 64 bit (x64) editions of Windows.
The new dongle drivers
required some changes in Déjà Vu
X 7.5 which make it incompatible with previous versions of the
drivers, so if you are using Déjà Vu X with a dongle,
you must update the dongle drivers to the latest version. In
order to update them correctly, follow these steps:
1. Unplug the dongle.
2. Uninstall the drivers installed in your computer. To do so, open the Start
menu, click on Run and copy and execute the following line:
"C:\Program Files\ATRIL\Deja Vu X\Dongle\setupdrv.exe" /u
If you installed Déjà Vu X in a different location, you will
need to change this path.
3. Restart your computer.
4. Install the drivers by double-clicking on the setupdrv.exe file in the folder "C:\Program
Files\ATRIL\Deja Vu X\Dongle\"
5. Turn off your computer.
6. Connect the dongle to your computer.
7. Turn on your computer.
8. Your dongle will be recognized by Windows and you will be ready to use Déjà Vu
is possible to use Déjà Vu on a net. You can share
your memory database, terminology database, project (files), and
Déjà Vu's settings. When sharing, it is possible
for more than one translator to use the same memory and terminology
databases, to work in the same project/file, and to share the
same settings file.
In the Configuration window (Project
Parameters tab), set source and output directories using a
server's net name (or computer's net name. E.g.: \\myserver\translation\clientA).
In the Languages tab, you should point
to your memory and terminology databases using your server's
net name. E.g.: \\myserver\translation\dvmemories).
Be sure to share all relevant directories/folders.
We recommend to share Déjà
Vu's settings as well (list of clients, subjects, etc.).
To share DVX settings:
Place settings file (Settings.dvset) in a shared directory
Go to Tools > Options and select the General tab.
Under "Miscelaneous", in "Shared settings
location:", point to the shared settings file.
Note: Apart from the network being 100 mbps, it is advisable to
use switches rather than hubs. The Workgroup edition of DVX will
include the possibility of accessing databases via COM+, which
results in higher overall speed.
If you open DV and there is no access to its settings file, DV
will present an error message asking to reinstall it. Close DV,
and make sure you have access to the appropriate computer/directory.
be sure "Prevent segmentation" is not selected in the
this is not the case, remember: (Judy Ann Schoen's explanation)
Macintosh systems, lines of text are terminated with a carriage
return, ASCII character #13. On Unix systems, lines are terminated
with the new line character #10. On Windows, they're terminated
by both: CR LF.
Mac or UNIX files are converted into Windows files, those paragraph
markers act funny. They look like proper paragraph markers,
but are not. You can search for the ASCII 13 or 10 character
and see, what you actually got in your file.
find a carriage return, type ^013 inside
the find box; to find a new line, type ^010.
Replace them with normal paragraph marks.
Endre Both modified a couple of fonts to
be used in DV. To download them, click
The fonts Veronika Sans DV and Veronika
Serif DV are adapted from the Bitstream Vera Sans and Bitstream
Vera Serif fonts, respectively. Please read Bitstream's original
copyright notice in the enclosed copyright.txt file.
The following modifications have been applied:
1. The space character (unicode no. 0020) has
been replaced with the middot character (unicode no. 00B7, the
character used in Microsoft Word for displaying spaces when the
option "Tools/Options/View/Formatting marks/Spaces"
or ".../Formatting marks/All" is checked).
2. The non-breaking space character (unicode
no. 00A0) has been replaced with the degree character (unicode
no. 00B0, the character used in Microsoft Word for displaying
non-breaking spaces when the option "Tools/Options/View/Formatting
marks/Spaces" or ".../Formatting marks/All" is
N.B. Both the dot in the space character and
the degree sign in the non-breaking space character are placed
lower than the original middot and degree signs to facilitate
differentiation between them.
Please send comments and suggestions to "abo
at endreboth dot com"
http://www.atril.com/dvx/builds/284/dvxEngine.5.zip It seems the patches above are not cumulative, but the patch below
"To install it, locate the file dvxengine.dll (usually located
folder "C:\Program Files\ATRIL\Deja Vu X") and overwrite
it with the
The above patches are not cumulative, you use one or another,
on top of each other.
Patches from 3 and upwards AFAIK address specific problems and
meant for public use (could someone please fill in what they solve?).
Patch 2 should AFAIR solve or alleviate certain assembly problems.
not perfect, but seems to improve things, at least here.
IMNSHO, openness about the patches, what they're supposed to solve,
public official announcements of them no matter how small or special
targeted problem may *seem*, would be hugely beneficial to everyone.
You can only export your whole file to External View if you have
DV's Workgroup edition. If you do not have it, DV will export
translated cells, propagated cells, and cells containing a comment.
That is, if you have translated the whole file and want somebody
else to edit it, it is possible to export it to External View
independently of the DV's edition you have. If you want somebody
to translate the whole file in External View, you should have
DV's Workgroup edition.
If you do not have the Workgroup edition and still need to export
everything to External View, you have to place a comment in each
blank or populated cell of your project.
When you first open the document, it looks
ok. By the second time you do not see anything OR you see hidden
hollow fonts (as above). To solve the problem, when you first
open the document, Save As a Word file (.doc). Get rid of the
RTF and use only the new saved document.
Another tip about external view: if the file is large, importing
it back into the project might take a very long time, but if you
save it as rtf and import it as such, it would take just a few
The first time you open the doc, copy the whole table to a new
I find by far the fastest way to select (highlight) one or more
words to be put into the TDB or Lexicon is to double-click on
the fist word (which includes the trailing space) and then hold
down shift+control and press right arrow to select the following
word or words (including the final trailing space).
It's much more reliable than using the mouse (if your not careful,
you quite often cut off the first or last letter(s) in the portion).
Yves Maurer's TIP: The trailing space will
be cut off before sending it to the TDB, so you don't have to
worry about that. Just check inside the text boxes in the "Add
Term Pair" window -- the trailing space is not there.
This has been said here before, but this information might be
useful for new users.
"Shift+F11" doesn't do the same as "F11".
The term is saved *without* the attributes "subject"
I try to use the mouse as little as possible, so I don't even
double click on the first word. I just position the cursor in
front of the first word I want to highlight and hold down Shift+Control
and then press the right arrow to select the rest of the words.
you aware that in Déjà Vu you can use asterisks
in your searches?
example, you can type con* fil* in
target, select the text, right-click and select 'Scan as source'
from the context menu. Déjà Vu will return MDB pairs
which contain words beginning with 'con' and 'fil', such as:
Before working in two
different computers... (MS Jet Engine Versions)
Herbert Eppel (and Atril's Team)
Be sure all your computers are using the same MS Jet Engine version.
If all computers are using the same DV version, this is normally
not a problem. Different Jet Engine versions can corrupt your
database. Check Microsoft's
To understand how the subject affects DVX, read
this message and corresponding thread.
You can leave the associated files behind, and only copy the
files .dvmdb and .dvtdb, but if you do you mustrepair these databases later on before you use them.
The associated files (extensions dvmdb; dvmdx; and [lang.
code.]dvmdi) contain the indexes for the databases, and
the repair function can generate them again.
You must also ensure that the databases are not read only, otherwise
access from Déjà Vu X will be impossible; needless
to say, you cannot access them from Déjà Vu X if
they are still on the CD.