This space is intended for freelancers and customers working together with PRODOC

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

PRODOC projects on the memoQ server are generated by templates. They have some common settings which are described here.

Customer-specific information applies to all projects. This information is handed over with the corresponding order.

Table of contents

Table of Contents

Related pages

Content by Label
showLabelsfalse
max5
spacesPMG
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel in ("settings","memoq","projekt") and type = "page" and space = "PMG"
labelssettings memoq projekt

A detailed description of the memoQ software can be found on the Kilgray website.

Here, only a short overview is given with PRODOC-specific information.

Elements created with each project

LiveDocs


Excerpt

  •  Screenshot requires update

With each project a LiveDoc with the following naming rule is created: projectnumber_project_references

The LiveDocs are corpora used as references for Translation.

They are bilingual documents, PDF files, or the result of aligned older translations, . 

We provide PDF files as a reference for most translations.

LiveDoc hits appear in the translation grid with a special icon.


Translation memories

  •  Screenshot requires update

Working TM

There is always a Working-Translation Memory per language, whose hits are translated segments of the current project.

Naming rule for Working-TMs: Working-projectnumber-languagepair

Hits from the Working-TM must be checked before using them, they are not proof-read.

Master-TM

Master-TMs providehits from earlier translations (Projects) and are reviewed. There may be several Master-TMs assigned to a project.

Naming rule for Master-TMs: customername-Master-customerdepartment-languagepair

Hits from the Master-TM can be used without further content checks, they are proof-read.

Transit-TMs

Transit TMs providehits come from converted Transit language pairs. They are reviewed.


There are 2 different kinds of Transit TMs:

Transit_Refs

These TMs contain all translations that have been made for a customer in a specific language combination. They have context information and may produce 101% hits.

However, since they contain older translations too, there might be different translations for the same source text due to corrections being made over time.

Naming rule for Transit-Refs: customername-Transit-Refs-languagepair

Hits from Transit-Refs must be checked for correct terminology, even if they are 100% or 101% hits.

TMX_Transit_Refs

These TMs contain only the most recent translations that have been made for a customer in a specific language combination. They do not have context information and cannot produce 101% hits.

Naming rule for TMX_Transit-Refs: customername-TMX_Transit-Refs-languagepair

Hits from Transit-Refs must be checked for correct terminology, even if they are 100% hits, because these TMs are no longer maintained..

Term bases

  •  Screenshot requires update

Term bases contain terminology to be used. They are set by the project manager and can be viewed in the Term bases pane.

Term bases are ordered by the term base rank. You see entries from term bases with a higher rank on top of the others.

Term base entries are highlighted with a light blue background in the translation grid:

In the translations results pane they have a blue tag:

Default term bases for projects

NameMeaningToDos
customer_checkThe term base contains obligatory terms provided by the customer.

These terms

must

MUST be used.

Never change any of these terms!

Never add any term to these term bases!

customer_von_customerThe term base contains terms provided by the customer.

These terms should be used, if possible. See also the customer info section.

Never change any of these terms!

Never add any term to these term bases!

customer_von_prodocThe term base contains terms that are entered during translation work by PRODOC staff or by freelancers

These terms should be used, if possible.

Never change any of these terms!

You may add new terms to these term bases!

 

If you do not agree with any of the terms provided, please let us know!

Additional term bases

There might be more term bases added to a project, especially term bases representing software GUIs.

Info
titleAdditional information per customer available

If there are more term bases for a specific customer, their function and use are explained in the customer info section