|
Instructions
for Quality Control in You
will receive a project in a pack and go file. ____________________________________________________ PROCESSING A PACK AND GO FILE When
you receive the satellite or EV file rename it
changing "to translator" to "from translator" if it is
not already named like that. Ideally
you should have a subfolder named "Providers" within the project
folder to avoid confusions when handling multiple files; place all files sent
and received to providers in this subfolder. 1
Select
FILE | OPEN. 2
In
the OPEN dialog, navigate to the location of your Pack & Go Package,
select ALL DEJA VU X FILES or PACK & GO
PROJECTS, and select the .dvpng file. 3
Click
OPEN. 4
The
Pack & Go
Import Wizard starts. 5
Click
NEXT and create a project to host your Pack & Go package. 6
Select
NEXT. 7
The
wizard displays the current settings. 8
Click
FINISH. The wizard shows you the import progress and notifies you when the
import process is finished. 9
Déjà
Vu X Workgroup displays the open project. To translate a project created from a Pack &
Go package Once
the file is open, you can start to work in it right away. It may be a good
idea, however, to first re-adjust the settings of the current project. 1
Select
PROJECT | PROPERTIES. 2
On
the General tab, make sure that the client and subject
setting is set to match the configuration of your
subjects and clients. 3
On
the Databases tab, make sure that the project is mapped
to databases on your computer or network. When
you are done with your work on the project file, you can create a new Pack
& Go package and return it to the project owner. 1
Open
the project that you would like to export into a Pack & Go package. 2
Select
FILE | EXPORT | PACK & GO. 3
The
Select Location of "New Pack & Go
Package" dialog appears. 4
Click
on SAVE after you have selected the folder where you
want this file to be stored and have named the file. 5
The
Pack & Go Export Progress
dialog appears. 6
When
the export is finished, a new file with the extension .dvpng
will have been placed in the specified folder. You will notice that the size
of the .dvpng file is significantly smaller than
the originating project file. 7
Send
the file to us. ____________________________________________________ quality control Once
you receive and import the External View files there are several things to do
for each language. It is important
that you follow the next steps in the same order describe here. General Quality Control ·
Make sure the spaces between words are the same
in the source and target columns. ·
There
must not be blank spaces after
or before codes in the TARGET column if they are not present in the
SOURCE column. That is, spaces should be the same before and after codes in
both source and target versions. ·
Make sure the capitalization of the first word in the
source and target columns match, unless the target language requires a
different capitalization. You may need to consult with the translator if
there are any doubts. ·
If
the text in two consecutive cells in the SOURCE column seems to belong to a
single sentence split in two consecutive cells, place the cursor in the
SOURCE column and put a note in each row pressing CTRL + M. This does NOT apply to sentences divided by
a semicolon (;) or colon (:). For example, if there is a single sentence
split in three rows put a note in each row column: in the first row put JOIN
1, in the second row put JOIN 2, etc. Also, mark these rows as DO NOT SEND
and LOCKED so they are not sent to the translation memory or accidentally
modified. You should assume these rows are ALWAYS prone to be incorrect;
consequently, send to the translator for review. Of course, you should
provide them with surrounding context in an EV
file. Code Consistency Checks It is extremely important that you understand how
codes work in Déjà vu. Codes indicate
changes in format (usually at the beginning and end of a word or
fragment) and therefore should be located in similar locations in the target
language. For example, a code (like {123}) can indicate change of normal font
to italics and another (like {124}) can indicate change of format back to
normal font. Therefore, you can change their relative position in the target
but must maintain sequential order for
each pair of codes representing a certain format. To
check whether there are any discrepancy between embedded codes in source and
target: ·
Select
Ctrl+Home (or Ctrl+PgUp)
in the selection mode to go to the beginning of your open file or project. ·
Press
CTRL + SHIFT + F8 (Or, on the TRANSLATION
menu, click CHECK EMBEDDED CODES) ·
Déjà
Vu X Workgroup will jump to the next occurrence of a discrepancy between
embedded codes in source and target. ·
Pay
attention to the message appearing at the bottom
of the screen. It is particularly important to fix problems related to
"the codes in the target do not
match those in the source" or "the codes in the target might not be correctly placed" ·
You
can quickly fix the codes by pressing Ctrl+F8. This will copy all missing
codes to the end of the current target segment. You will then have to
reposition them in the right places. However, if you are not sure about their
position consult with the translator regarding font formatting. ·
If
you cannot fix the codes this way, cut the problem sentence, paste into a
text editor (like Word or Notepad), fix the codes and copy and paste again
into the proper row in Déjà vu. ·
Make
sure that the codes are now located in the correct position. ·
Continue
to check for code errors and fix them until you reach the end of the open
file or project. To find the next numeral discrepancy: ·
Select
Ctrl+Home (or Ctrl+PgUp)
in the selection mode to go to the beginning of your open file or project. ·
Press
CTRL + SHIFT + F8, or on the TRANSLATION
menu click CHECK NUMERALS. ·
Déjà
Vu X Workgroup will find the next numeral discrepancy and display a red
exclamation mark in that row (or a light violet exclamation mark if there is
already a target comment on that row). Sending the Project to the TM and Pretranslating ·
Create
a translation memory where you can store the language pairs ·
Send
the project to the TM pressing ALT + F12 ·
Pretranslate the rest of the
project pressing CTRL + P. Select ALL FILES and ACCEPT ONLY EXACT MATCHES.
Make sure ASSEMBLE FROM PORTIONS is not checked. Nothing else should
be checked. ·
Make
sure there are no empty targets selecting ALL EMPTY ROWS in the Rows Selector. If there are empty
rows complete them using the TM or consult with the translator. Finding and Processing Fuzzy Matches ·
In
the Rows Selector choose FUZZY MATCH ROWS. ·
Go
row by row checking for discrepancies between source and target versions in
bullets, relative code position, capitalization, numerals, punctuation
symbols, etc. ·
If
you have doubts about how to fix a particular row mark as pending and make a
note to send to the translator. ·
If
you want to stop the work and resume later you can put a mark pressing CTRL +
F2 (and delete afterwards also pressing the same keys). To find the bookmark
just press F2. Translation Consistency Check You
can check consistency finding duplicate sentences with different
translations: ·
Select
PROJECT | FIND DUPLICATE SENTENCES. ·
Select
"Find sets of duplicate source sentences with different
translations" and mark (select) ignore
case, ignore numerals, ignore embedded codes. ·
Switch
between natural and
alphabetical views, selecting VIEW | TOGGLE SORTING and select DUPLICATE ROWS in the Rows
Selector. ·
The
duplicated rows with different translations are now displayed on top of each
other. You can now enter your corrections if necessary. You can easily see
discrepancies between translations, even if you don't know the target
language. ·
You
can uniform duplicate sentences with different translations pressing SHIFT +
F9. This propagates and overwrites other perfect matches in the same file.
Just make sure you do not accept to overwrite sentences that are not perfect
matches. For this function to work, the rows to be overwritten must be unmarked. ·
Verify
that all instances match and correct discrepancies if you can. If you cannot
correct discrepancies make a note in each row to be sent in an EV file to the translator. You can also mark these rows
as pending and export only those. You
can also check consistency for specific short phrases or words: ·
Highlight
the source in question, right-click, and select FILTER ON SELECTION. ·
You
will see only the source phrase or word you selected and its corresponding
translation. ·
Verify
that all instances match and correct discrepancies if you can. If you cannot
correct discrepancies make a note in each row to be sent in an EV file to the translator. ·
Right-click
in the source column and select UNFILTER. ____________________________________________________ exporting and importing an external view You might need to send a satellite or an external
view file to a translator if there are unsolved issues. Preparation for Export You
can export a satellite file (if you have DV
Workgroup Edition) or export the project (or part of it) as an External View
file. ·
Mark
fuzzy matches, rows with codes you don't know how to
position, etc. as pending so the translator can verify code position,
capitalization, etc. ·
Mark
rows with split sentences also as pending to send to the translator (see
above). Exporting an External View File Export
an External View (Rich Text Format) file for each language, making sure you
select: ·
Rich text format ·
All files ·
All rows or Only pending rows (depending on
your needs you might want to send all rows so the translator has context) ·
Natural ·
Include row ID ·
Include row status ·
As color It
is a good practice to highlight in red the codes in the export view files in
order to help the translators distinguish them from the rest of the text. 1
Go
to menu EDIT | REPLACE 2
Select
MORE 3
In
the FIND WHAT box type "{" 4
Select
SPECIAL | ANY DIGIT 5
Type
"}" 6
Place
the cursor in the REPLACE WITH box 7
Select
SPECIAL | FIND WHAT TEXT 8 Select
FORMAT | FONT | FONT COLOR | RED 9 Click
OK 10 Click
RELACE ALL 11 Repeat
steps 4-10 adding an extra digit
(step 4) until no occurrences are found. The
name of each exported External View should be the same as the original, but
with the extension for each language (_DE for German, _IT for Italian, etc.).
If you are exporting the whole project into a single EV
file, then name the file as "Project Number_to
translator_Language Code.rft", where Project
Number is the number of the project, and Language Code is the code for each
language. For a list of Language Codes click here. These exported versions
should be uploaded to the intranet's folder PROVIDERS | FROM ALTER | PROJECT
NUMBER, where PROJECT NUMBER is the number for the project. Once you receive the EV
file rename as explained above ("from translator") and import. ·
Mark
all pending rows as finished. ·
Check
consistency if needed. ·
Check
codes and numerals again. ____________________________________________________ returning THE PROJECT Return
the project to us as a satellite (preferably as a pack and go file). For
instructions to return as a pack and go see PROCESSING A PACK AND GO FILE
above. To
return the project: ·
Export
the satellite or pack and go file ·
Use
the same name in the pack and go file you received from us changing
"to" in the file name with "from". ·
Save
to the same folder where the DV file and Office
files are located in your hard drive. ·
Upload
to the intranet folder PROVIDERS | TO ALTER | PROJECT NUMBER (here the
project number will be the one for each language; for example
"SP-22_EN_DE" means project SP-22 from English to German). ·
Notify
us. Project completed! ____________________________________________________ ADDITIONAL INFORMATION You
can use the DISCUSSIONS link at the left of the intranet to post questions
and answers relative to your project in the respective forum. If there is no
forum for your project you can ask us to create one. Using the forum you can
collaborate and interchange information with other translators in this
project and with us. |