How to handle made up abbreviations Auteur du fil: Olieslagers
|
|---|
Olieslagers
Polynésie française
Local time: 05:26
néerlandais vers français
+ ...
Hello,
I am translating a technical user manual (Dutch>French) which has dozens of made up abbreviations (for example: hoofdventilator = HV, Kachel = KA, etc.). Further in this document, these abbreviations appear in a large number of tables, titles, etc.
So my question is how would you handle this kind of abbreviations? Simply transpose them? But then the reader might get confused as the abbreviations won't correspond to anything. Or "try" to translate those abbreviations (... See more Hello,
I am translating a technical user manual (Dutch>French) which has dozens of made up abbreviations (for example: hoofdventilator = HV, Kachel = KA, etc.). Further in this document, these abbreviations appear in a large number of tables, titles, etc.
So my question is how would you handle this kind of abbreviations? Simply transpose them? But then the reader might get confused as the abbreviations won't correspond to anything. Or "try" to translate those abbreviations (for example: ventilateur principal=VP). But then I might get confused!
Thanks in advance for your help!
Noëlle ▲ Collapse
| | | |
There is no reason for leaving them in their original form. Nobody will understand them if they are not standard abbreviations. Translate them, preferably by properly introducing them at their first occurrence (FO). Keep a running list for yourself if you need to.
Alternatively, you can write out the whole term every time and do away with the acronyms. Sometimes this is doable, but if something occurs many times and space is at a premium (e.g. in large tables), it's not an option.
If... See more There is no reason for leaving them in their original form. Nobody will understand them if they are not standard abbreviations. Translate them, preferably by properly introducing them at their first occurrence (FO). Keep a running list for yourself if you need to.
Alternatively, you can write out the whole term every time and do away with the acronyms. Sometimes this is doable, but if something occurs many times and space is at a premium (e.g. in large tables), it's not an option.
If I come across a weird acronym I often do a search in the document. If it only occurs twice, I just write out the whole term and save myself and the reader a headache. ▲ Collapse
| | | | | Ask the client and agree on a policy | Feb 7, 2014 |
In something like a user manual, consistency is important. What does the client do in user manuals for their other products, and what will they do with updates?
Ask, and agree on how you will translate abbreviations.
If the client already has a policy on abbreviations, they will want you to follow it sooner or later, when they think about it.
| | | |
In my experience, clients that spew out crazy acronyms are unlikely to give you sensible guidance on what to do with them. If they cared about the linguistic aspects of their documents, they wouldn't be generating these acronyms in the first place.
One can always give it a shot, of course.
| | |
|
|
|
Olieslagers
Polynésie française
Local time: 05:26
néerlandais vers français
+ ...
AUTEUR DU FIL
Thank you for your suggestions Christine Anders and FarkasAndras.
I will give it a try and ask them if they have a policy regarding these abbreviations. Even through I have some doubts they do, at least they will have the ball in their court and they can tell me their opinion!
| | | | neilmac
Espagne
Local time: 16:26
espagnol vers anglais
+ ...
Whenever I have to deal with acronyms in a translation, I always remind clients that any abbreviations or similar that are translated in the text will also need to be changed in any accompanying graphic material, such as tables, figures, annexes, etc.
In fact, I take pains to make sure that they understand that any abbreviations or acronyms in their texts are their own responsibility and not mine. It saves me a lot of time wasted researching or brainstorming things when the author who per... See more Whenever I have to deal with acronyms in a translation, I always remind clients that any abbreviations or similar that are translated in the text will also need to be changed in any accompanying graphic material, such as tables, figures, annexes, etc.
In fact, I take pains to make sure that they understand that any abbreviations or acronyms in their texts are their own responsibility and not mine. It saves me a lot of time wasted researching or brainstorming things when the author who perpetrated them can tell you what they stand for at the drop of a hat.
[Edited at 2014-02-08 08:25 GMT]
[Edited at 2014-02-08 08:25 GMT] ▲ Collapse
| | | | Erik Freitag 
Allemagne
Local time: 16:26
Membre (2006)
néerlandais vers allemand
+ ...
| Dutch language and acronyms | Feb 8, 2014 |
Dear Noëlle,
That's a problem that the Dutch language suffers from a lot more than other languages, in my experience at least. The Dutch are especially fond of using acronyms, and use them very frequently. Probably, they're especially good at deciphering them as well.
I'm going a long way to make this easier for the target language readership (German, in my case), who probably don't share the Dutchmen's abilities in this regards. My translations will usually contain an... See more Dear Noëlle,
That's a problem that the Dutch language suffers from a lot more than other languages, in my experience at least. The Dutch are especially fond of using acronyms, and use them very frequently. Probably, they're especially good at deciphering them as well.
I'm going a long way to make this easier for the target language readership (German, in my case), who probably don't share the Dutchmen's abilities in this regards. My translations will usually contain an explanation of an acronym at its first occurrence, even when the source text doesn't contain one. I will usually add such an explanation even when I use a translated acronym. Quite often, I spell the translation of Dutch acronyms out every time they occur.
neilmac wrote:
In fact, I take pains to make sure that they understand that any abbreviations or acronyms in their texts are their own responsibility and not mine.
Neilmac, I envy you for that. That would indeed make my life a whole lot easier, and my productivity would increase big time. I'm not sure though that this is what my customers should expect from me. On the other hand, my customers are usually prepared to explain any acronyms and abbreviations that are not obvious to me. ▲ Collapse
| | | | jldomingo
Espagne
Local time: 16:26
anglais vers espagnol
If there are a table in the document that explains the meaning of abbreviations, that will be enough.
If not, introduce the abbreviation the first time it appears in a way like this:
... the North Atlantic Treaty Organization (NATO) aims to...
From then on, you could use NATO only in the body text.
| | |
|
|
|
Tina Vonhof (X)
Canada
Local time: 08:26
néerlandais vers anglais
+ ...
efreig, you said:
"That's a problem that the Dutch language suffers from a lot more than other languages, in my experience at least. The Dutch are especially fond of using acronyms, and use them very frequently. Probably, they're especially good at deciphering them as well."
So true, and they are never explained, even when they first occur, and (when it's a company or institution) not even on their own websites!!! I have started my own list of acronyms and abbreviations... See more efreig, you said:
"That's a problem that the Dutch language suffers from a lot more than other languages, in my experience at least. The Dutch are especially fond of using acronyms, and use them very frequently. Probably, they're especially good at deciphering them as well."
So true, and they are never explained, even when they first occur, and (when it's a company or institution) not even on their own websites!!! I have started my own list of acronyms and abbreviations I have encountered, which I hope will save me a lot of time searching in the future. ▲ Collapse
| | | | Olieslagers
Polynésie française
Local time: 05:26
néerlandais vers français
+ ...
AUTEUR DU FIL | I have one advantage | Feb 8, 2014 |
At least I know where the abbreviations stand for. All the abbreviations are clearly listed and explained in the overview of the manual. But the question is: shall I keep the Dutch abbreviations or translate them...
At the end of the day, does it makes any difference to the reader? Is it more clear to say: "Stabilisateur de chaleur = WS (the Dutch made up abbreviation) or SC (my own made up abbreviation)"!?
I think I better ask the client as suggested by Christine Anders...
| | | | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » How to handle made up abbreviations | Wordfast Pro | Translation Memory Software for Any Platform
Exclusive discount for ProZ.com users!
Save over 13% when purchasing Wordfast Pro through ProZ.com. Wordfast is the world's #1 provider of platform-independent Translation Memory software. Consistently ranked the most user-friendly and highest value
Buy now! » |
| | Trados Business Manager Lite | Create customer quotes and invoices from within Trados Studio
Trados Business Manager Lite helps to simplify and speed up some of the daily tasks, such as invoicing and reporting, associated with running your freelance translation business.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
Translation news
