|
About the Articles Knowledgebase
|
ProZ.com has created this section with the goals of:
Further enabling knowledge sharing among professionals
Providing resources for the education of clients and translators
Offering an additional channel for promotion of ProZ.com members (as authors)
We invite your participation and feedback concerning this new resource.
|
|
|
|
|
Recent News
Featured Articles
»
Managing Business Risk
|
2nd ProZ.com Conference - Oxford 2004
Presentation Content
|
Recent Articles
»
Ten Things I Learned the Hard Way About Medical Translation
|
The article argues that terminology is the easy part of medical translation, and that what really separates a usable file from a dangerous one is a set of working habits—ten of which make up the body of the piece. Decide who the reader is before translating anything, since clinician-facing and patient-facing documents demand different registers and consent forms carry readability ceilings. Never expand an abbreviation the document itself doesn't disambiguate. Run numbers, units and decimal separators as their own dedicated pass, and don't convert units unasked. On patient-reported outcome instruments, write naturally rather than calquing to flatter the back-translation. Keep a fixed source hierarchy, running from client glossary through regulatory templates and national references down to dictionaries, and follow it. Write queries that do the work for whoever answers them: location, ambiguity, options, recommendation. Flag source errors rather than silently repairing them, especially in certified work. Mark illegible handwriting as illegible instead of guessing a drug name. Use several narrow QA passes rather than one broad one, and read patient-facing text aloud. Decline work outside your subject competence. Closing it out is a case study of a hospital medical record — described structurally only, with no client, patient or clinical content disclosed — covering the six difficulties that job actually presented: a table-heavy composite file that stripped sentence context inside the CAT tool, the tension between layout fidelity and legibility once the target expanded, deciding which institutional identifiers had to stay in the source language for the document to remain verifiable, carrying reference ranges and units exactly as the issuing laboratory reported them, resisting the urge to upgrade non-standard clinical shorthand into polished standard English, and rendering context-free interface strings inside fixed cell widths. The translation itself turned out to be the smallest component of that job, which is more or less the point: this field rewards unglamorous discipline above all.
|
»
Categorization of Translation Mistakes Made by Artificial Intelligence
|
After broaching the primary artificial intelligence issues for translation in the first article of this series, I will delve into the weaknesses at greater length here. The initial article contains a brief description of four categories of errors: style, harmonization, terminology and interpretation of abstractions/references. Those types of mistakes are critical for the stakeholders in the translation process (client/customer, language service provider, and translator). In this article, I will address these in greater depth, while also adding a few other types of flaws.
|
»
Should the Translator Take the Reader to the Author, or the Author to the Reader?
|
Foreignisation and domestication are two fundamental approaches in translation. This article explores how translators balance cultural fidelity and readability, and why the most appropriate strategy often depends on the purpose, genre and target audience of the text.
|
»
Cinq pièges de traduction qui se paient en droit
|
La traduction juridique passe pour une formalité technique. Elle est en réalité un acte de droit : un mot mal rendu déplace une charge de la preuve, périme un consentement, fausse une expertise, fait tomber un moyen. Cinq pièges récurrents, et la manière de les désamorcer avant qu’ils ne se paient — au cabinet, à l’étude notariale, en garde à vue ou devant l’administration.
|
»
Subtitles; here's what AI got wrong
|
Readable subtitles, it's all about reading speed optimization.
|
No articles found.
|
|
printer version