General Instructions for Translators

1. DOCUMENT FORMAT

Documents should always be returned in an editable format.

 Reason:      The client generally expects to receive an editable document. Where a different format is required, such is always clearly stated.

 2. LANGUAGE SUFFIX AND FILE NAME

On completing the translation of a file, ALWAYS change the final ISO‑language designation of the source file to that of the target language. For example, to return an English translation of a Spanish text, the File‑ES.docx on translation becomes File‑EN.docx

Reason:      1. This avoids an incoming target file with the same original language name and suffix thus overwriting the original file in the InfoMarex Translations database.
2. The ultimate client should be able to recognise the incoming file.

3. IMMEDIATE PAYMENT OF INVOICES

The translator should always return an invoice to InfoMarex Translations with the translated file or with the last translated file of a batch of files for payment by return. Any transfer fee attaching to a Bank transfer, PayPal or Skrill is always paid by InfoMarex Translations.

Reason:  It has been InfoMarex Translations’ policy for years to pay the translator on receipt of a translation. InfoMarex Translations does not keep what is generally called a “creditors’ ledger”.

(A number of translators, however, prefer for their own convenience to invoice their tasks monthly on a single itemised composite invoice. This is ok, if  InfoMarex Translations is told in advance. See also Item 4 as follows. )

 4.  PAYMENT OF INVOICES AT 30 DAYS

On occasions, when there is a team of translators working on multiple files in a project of multiple languages, the translator may be told of payment at 30 days. However, this latter procedure is the exception to the above rule.

Reason:  The translator will readily understand that in this instance within a large project, a file‑by‑file invoice does not work.

5. PURCHASE ORDERS

It is NOT the policy of InfoMarex Translations to issue purchase orders for assigned jobs. A simple email between Infomarex Translators and the translator agrees the job contract, the wordcount, the rate and the delivery date. When the translator accepts InfoMarex Translations’ offer, the offer is deemed to be firm and binding on both parties.

Reason:      A confirming email suffices in Ireland being a binding contract in law.

6. LOGOS, SIGNATURES, EMBLEMS

All non‑text items in legal translations must appear in italics in the translation between brackets or similar, translated into the target language as [Logo], [Emblem], [Shield], [Illegible signature], [Illegible initials], [Fiscal stamp], [Stamp/seal with the words “…”’] or similar.

Please note that a ‘seal’ is the official mark of an entity, while a rubber ink ‘stamp’ is merely a pre‑inked impression placed on a document for the sake of convenience instead of handwriting.

A translator may wish to insert ‘round’, ‘oval’ or ‘rectangular’ before the word ‘stamp/seal’.

Reason:  The target text must appear in both translation and format to be as accurately close and image as possible to its original.

7. SUBJECT LINE

Always keep the same Subject Line, e.g. InfoMarex Translation Job 89001: RU > DE

Reason:      The email Subject Line is filtered into the InfoMarex Translations system. Without the job number, in particular, the file fails to be is filtered to the correct directory and ends up in Spam.

 8. PDF, TIF, JPG, or image files

The translation of text in picture files such as .tif, .jpg, .jpeg files should come back as text inserted appropriately in the target MS document, or in a Comment Box to the side.

Reason
:      The client expects to receive back a document which can be changed or overwritten.

9. TRANSLATOR NOTES

The translator should avoid, whenever possible, putting notes in the footer of a text with the following exception.

 Exception: When the source document is multilingual, and the target translation is monolingual, the visual ‘loss’ of text must be explained to the reader (or Court).

 Example:   [Translator’s note: the original of this document was written trilingually in German, French and Italian.]

 Nota bene: If any one of the above instructions is not clear, please let us know and we shall re‑word the text to improve clarity.