Languages have a source
You know which original a translation was made from.
TRANSLATION IS ONLY THE FIRST STEP
When the original changes, the person managing the translation needs to know too. Link language versions to a specific document revision and to approval.
For companies selling into several countries and for their documentation and service teams.
LANGUAGES / SOURCE REVISION 2.0
WHY IT MAKES SENSE
You know which original a translation was made from.
An older translation is flagged for update instead of looking current.
A draft translation is not automatically an approved service manual.
HOW WE START
We define the original, the revision and the languages needed for specific markets.
Using your own translator, a partner or an agreed tool.
An expert verifies the content. Only then do we offer it in the relevant passport version.
WHAT YOU GET
A register of languages and revisions, a translation queue, approval and alerts on source changes. Machine translation can be connected depending on the chosen tool and its licence terms.
CLEAR BOUNDARIES
Translating a marketing website, an application interface and service documents are different tasks. Foreign-language PDFs and technical translation are not automatically included in the CZ/EN switch.
BEFORE WE TALK
Let's start with what you already use and what slows your people down today.
Yes, as an individually validated integration. We confirm the scope, protection of the transferred data and licence cost in advance. The demo does not use any external translation service.
No. The example uses pre-prepared fictitious language versions. We demonstrate approval and the response to a new source revision, not the quality of machine translation.
We do not recommend it. Approval should be given by a responsible expert according to the nature of the document and the target market.
In the consultation we will go through your data, responsibilities and the system you work with. We confirm the scope and price before work begins.