0% found this document useful (0 votes)
70 views2 pages

Translation) Is Acceptable Treatment

The document provides linguistic editing guidelines for translators, including: 1. Translated documents should be in MS Word format and use Track Changes. 2. Translations must include all content from the source document unless otherwise noted. 3. Signatures, stamps, logos, etc. should be designated in italics within brackets and only use the listed terms. Dates, numbers, amounts must be checked carefully for consistency.

Uploaded by

Anwar Gani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
70 views2 pages

Translation) Is Acceptable Treatment

The document provides linguistic editing guidelines for translators, including: 1. Translated documents should be in MS Word format and use Track Changes. 2. Translations must include all content from the source document unless otherwise noted. 3. Signatures, stamps, logos, etc. should be designated in italics within brackets and only use the listed terms. Dates, numbers, amounts must be checked carefully for consistency.

Uploaded by

Anwar Gani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Linguistic Editing Guidelines- GEHA

1. Unless otherwise specified by the Project Manager, the file format of the delivery should be a Microsoft Word document.
2. Always use the Track Changes option when proofreading MS Word documents. In MS Word 2007/2010, this option is found under the
Review tab or by pressing Ctrl + Shift + E.
3. The translated document must include or reference everything (including all text, images, graphs, charts and others) from the source
document, unless otherwise noted by the PM.
4. Seals and stamps must be translated and designated as such by placing the translation of the stamp or seal text in italics in brackets. For
example: [Stamp: President of the United States of America]
5. Signatures, initials, logos, or watermarks must be designated as such by placing the word(s) in brackets and in italics, such as [Signature],
[Initials], [Logo: Company Name], or [Watermark: Watermark Text].

The following are the only acceptable designations for the items in 4 and 5, in addition to any text contained therein:
[Logo] [Stamp] [Seal] [Signature] [Watermark] [Initials] [Image] [QR Code] [Barcode] [Fingerprint]
6. Text that is hand-written in the original document should be italicized in the translation.
7. The translated document should be the same page orientation as the source document. All pages should be in letter size.
8. When proofreading and editing English translations, make sure the proofreading language is set to English (U.S.). To do this, select all the
text and click on the Language bar at the bottom left corner of your screen.
9. Read the ENTIRE translated document to make sure it reads well, is grammatically correct, and is comprehensible.
10. All dates should be in U.S. format (Month/Day/Year). The number of digits should be consistent between the translation and the source
(mm/yyyy vs. mm/yy). All times should be in AM/PM. Times that are presented in a 24- hour format should be changed to AM/PM. For
example, 15:40 should be changed to 3:40 PM in the translated document.
12. Fiscal amounts must be in the correct format, marked with commas and decimal points to two decimal places.
For example: $3,149.20 is correct; $3.149,20 is not.
There should be no space between the dollar sign ($) and amounts in USD. For currency outside of the US, there should always be a
space between the currency symbol and the amount.
12. Dates, numbers, and amounts must be checked with extra care to ensure that they are consistent with the source document.
13. Be sure every line of the source document is included. Make sure all the paragraphs are accounted for; if you have doubts, or if text is
missing, please add a comment saying so.
14. All charts, graphs, tables, symbols, logos, and pictures should be included. Screenshots should be used whenever possible.
15. Formatting is not an important quality for this client. Utilize text boxes, screenshots, etc. whenever possible.
16. Pages that are bilingual – please disregard English and translate source text. If the translator feels the existing English text accurately
reflects the corresponding target text, it may be treated as an image.
17. Pages with Target and English Text – Please utilize screenshots of English text and translate target text in the most convenient way.
18. Pages that are entirely in English should be screenshot and pasted into the translation.
19. Pages with majority English and some source text – screenshot the page, and add text boxes over source text with the translation.
20. Duplicate pages should be translated only once upon confirmation of duplicate. Add a note, text box, or comment in the target file to
indicate that a duplicate page has been disregarded.
21. All proper names (company/ facility names, product names, building names) and addresses should remain in the original language (or
transliterated from the original language if the source language does not use the Latin alphabet). The translation may be added in
brackets for comprehension.
22. Any acronyms in the document should have bilingual treatment, never translated. To do so, keep the acronyms in the document in the
source language and add the explanation of what they mean/stand for [In brackets and italicized] in English immediately following the
acronym. For example: SA [Corporation]
For acronyms in the Greek or Cyrillic alphabets, we can retain the source characters of the source acronym. For example, ΔΓΦ [English
translation] is acceptable treatment.
In case the exact definition/meaning of an acronym is not clear, please include this in a translator’s note.
23. If there is any illegible text, please indicate as: [Illegible] - capitalized and italicized in brackets.
Similarly, any cut off text should be indicated as [Cut off], and any text that has been intentionally blacked out or covered so it cannot be
read should be indicated as [Redacted].
24. Anything erroneous, unusual, unclear, or otherwise requiring explanation should be clearly explained using a translator’s note.
Ex: [Translator’s Note: “Presente” is a header put on documents as a formality and has no exact English equivalent.]
25. If the source file presents a clear error, indicate any and all errors by adding [sic] in the translation immediately after the error. Please do
not attempt to translate the text based on assumptions of what the source file should say or is trying to say. The translated document
MUST be an exact and accurate representation of the source document.
For example – if a person’s name is spelled differently across pages – add [sic] after each instance where the name appears.
26. All relevant glossaries, guidelines, and term bases must be followed at all times; provide these to linguists at project handoff.
27. Government entities should be translated for comprehension. Treatment will be at the linguist’s discretion and should be consistent
throughout the project documents
For example: Ministerio da Fazenda [Department of Finance]
28. Legal identification numbers such as statutes/laws and personal ID numbers should match the source text exactly. Do not convert any
decimal points within these numbers to commas, and vice versa.
29. Accent marks should only be retained for proper names of individuals, untranslated corporation/business names, and addresses. Accent
marks should NOT be retained if an English translation is available.
For example: Panamá mentioned on its own, not as part of an address, should be changed to Panama.

You might also like