Embed Size (px)
Citation preview
memoQ
workarounds
memoQ Fest 2016
Budapest
Angelika Zerfaß
Agenda
Source language Check
Standard segments
QA
Term check
EN-DE-JP review
Collecting sample sentences during term extraction
Translation comparison
Pseudo-translation for filter settings check
Source language check
Standard segments
To check if the source document uses
standard sentences (for example in
copyright notices or chapters with
warning messages or other text that
appears often and should not change)
create a TM of standard sentences.
Source and target language segments
will be the same.
Source language check
Standard segments
Create a project where the target language is your actual source language (to be able to use the spellchecker) and add the list of standard sentences.
Copy source to target.
Update the TM
Use this TM to pre-translate new documents Either pre-translate twice (Good Matches and lock everything
then all matches)
Or insert matches from about 80% (change the TM settings for Good Matches).
Filter for unlocked segments
Set up sorting for segments with higher match values first and scroll down to the ones that are below 95%
Check what kind of changes have been made.
Run spellchecker on the target language, if appropriate
Source language check
QA
Frequent question from larger LSPs or
translation departments inside
companies.
How to use QA and term check on the
source language and produce a clean
source language document for
translation and as feedback for the
authors.
QA and term check
for the source language
Create a project (target language should be the actual source language of your files)
Copy source to target
Check the target with QA feature
Export clean document
And here is what you need to consider…
QA and term check
for the source language
You cannot set up a project where source and target language are exactly the same.
Choose the source language of the document as the target language of the project (for use of the correct spellchecker and punctuation rules in the QA checker).
Choose a source language that uses the same format for numbers (delimiters for decimal numbers and grouped numbers) and the same punctuation rules.
Set up auto-translation rules to correct things like non-breaking spaces between numbers and measurements or correct use of measurement symbols (20°C instead of 20° C)
For forbidden terms, create a new entry in the term base. The "source language" contains the forbidden term, so that it can be found in the "source language", the target language contains the term to be used.
QA and term check
for the source language
Do not create projects with only language variants (DE-DE with DE-CH), as term recognition might not work correctly.
Forbidden
term
Forbidden
term
Correct
term
Incorrect display with
language variants
If you choose language variants for the project, the term check might give you confusing results:
Although there is no entry in the term base that shows monitor (EN) – monitor (EN-US) or PC-PC, it still appears in the list!
No such issue with different languages (Malay – EN-US)
Incorrect display with
language variants
Apologies for the misinformation in the previous slide.
The screenshot was taken at a time when the following option, to treat sublanguages as different languageswas not available.
It is now possible to use sub-languages,just use the checkboxshown on the right.
Translation DE-EN-JP
A translation DE-EN exists.
A translation DE-JP exists.
A reviewer is supposed to check the Japanese translation, but does not know German.
How can the reviewer see the English segments for the Japanese translation?
Solution 1: Fake TM
The reviewer uses a project DE-JP
Fake TM
The DE-EN TM is exported to TMX
The language ID for EN is changed to JP
The TMX file is imported to a DE-JP TM
The results list will now show the DE-
JP and DE-EN segments.
Solution 1: Fake TM
The results list will now show the
DE-JP and DE-EN segments.
You could also use the LiveDocs instead of a fake TM.
This solution can also be used via WebTrans.
Solution 1: keep in mind…
Set the TM with the DE-EN content to "read-only" so that the reviewer does not save changes to the fake TM.
Also, the document to be reviewed (DE-JP) should have the same segmentation as the other translation (DE-EN) and there should not be any empty segments (to avoid matches from the fake TM being inserted. You could also deactivate the insertion of matches in the translation settings.)
Solution 2: Using a view
Import the TM DE-EN as a translation
file for DE-JP (change the language
IDs in the TMX file)
Open the document and lock all segments
Import the translation file DE-JP
Create a view of both documents
Sort the view by frequency
Solution 2: pro and con
You will see the segments in the
translation editor, which is easier to
handle than always checking the
results list.
But you will be working in a sorted list,
so not in the natural sequence of the
sentences in the document.
Solution 3: preview table
Export the two documents (DE-EN and DE-JP) to RTF tables.
Create a table with 3 columns and copy to Excel
Create a project with 2 target languages (EN and JP)
Use the multilingual delimited text filter
The preview shows all 3 languages
Solution 3: keep in mind…
The table approach only works if the segmentation of the two translation files is identical.
The reviewed/changed segments have to be applied from the TM to the DE-JP translation file afterwards (use the QA Check for inconsistencies between document and TM to find changed segments).
Term Extraction with multilingual
sample sentences
A term list contains terms in several
languages, but is missing the context
sentences.
To avoid having to search (the
bilingual TMX files) for the same term
multiple times, the TM Search tool is
used.
Term Extraction with multilingual
sample sentences
Set up the TM Search tool with all TMs
Run the search for a term
Copy the context sentences
Comparing 2 TMs
The statistics tell you how similar the source segments are, but not how good the translations are.
A client TM was not fully usable.
Some matches could be used, others had to be changes.
Updating the matches was done during translation.
How do you find out how much had to be changed (to calculate a price for updating the TM)?
Comparing 2 TMs
Step 1 (to see the list of changes) Create a project with the client's TM as
translation file (TMX) and the translator's TM attached.
Run QA with inconsistency setting
Comparing 2 TMs
Segments where the translation in the document and the translation from the best match are not identical, show a QA warning.
Comparing 2 TMs
Step 2 (to get match statistics on the
changes in the target segments)
The TM of the translator is exported to TMX.
Create a project with the reverse language
pair.
Attach the original client TM to the project.
Add the TMX file from the translator as
translation file.
The analysis shows a comparison of the TMs
Comparing 2 TMs
Client
TM
DE-EN
Translator
TM
DE-EN
Translation
document
Match from the TM
Translation used as is
Translation
changed
New translation
Same source
segments - but
maybe different
translations
Comparing 2 TMs
TMX from
translatorExport to TMX
Translator
TM
DE-EN
Create new project
with opposite
language direction
memoQ project
EN-DE
Run
analysis
Client
TM
DE-EN
Attach the
client TM
Import as
translation
document
in memoQ
Comparing 2 TMs
If there is a 100% match from the client TM this means that the translator used the segment from the client TM.
If there is a fuzzy match means that the translation from the client TM had been changed.
A no match means that the translation from the client TM was neither used nor changed, but a new translation was created.
Pseudo-Translation for filter
settings check
When creating a filter for a text- or xml-
based file, we want to make sure that
all translatable text has been
accessed.
Pseudo-Translation can make it easier
to find not yet defined text in these
files.
Pseudo-Translation for filter
settings check
Pre-translate using
machine translation
Pseudo-Translation for filter
settings check
Check the resulting file either in the preview or export and view in a text/XML editor to find text that your filter did not catch.
Thank you for
your attention
