Poll: How do you usually handle terminology consistency across projects? Autor de la hebra: ProZ.com Staff
|
|---|
This forum topic is for the discussion of the poll question "How do you usually handle terminology consistency across projects?".
View the poll results »
| | | |
Enrico Zoffoli 
Italia
Local time: 20:20
Miembro
alemán al italiano
+ ...
Though now that I think about it, memory is surprisingly important in my case.
| | | |
Sebastian Witte
Alemania
Local time: 20:20
Miembro 2004
inglés al alemán
+ ...
| Concordance Search, dedicated Multiterm termbase, TM results | Apr 15 |
See above.
| | | |
Oh, I voted for memory, but I mean translation memory in CAT tools. 😅 It's more useful than a glossary or termbase, because it'll show the context, and matching different forms of words will work better too.
[Edited at 2026-04-15 15:55 GMT]
| | |
|
|
|
| Definitely CAT features including the termbase | Apr 15 |
My own memory often prompts me that there is something I should be looking for, and even tells me what it is, but I rely on CAT features, partly because they save typing! Once checked, the spelling is always correct, and I can insert whole strings with just a few keystrokes.
I have spent time entering terminology I have received from clients into the database or Autotext - it is usually well worth the effort.
| | | |
Except for CAT tools (I'm one of the last dinosaurs)...
| | | |
| My termbases, my glossaries and research | Apr 15 |
In addition to what my colleagues mentioned, having a style guide and clear client guidance/instructions on preferred terminology is very helpful for maintaining consistency across projects.
| | | |
| Outdated glossaries | Apr 17 |
One downside of glossaries or termbases is that they might not be up-to-date, especially when they're maintained by the end client. Then you'll get repeated instructions to ignore the glossary for certain key terms.
| | |
|
|
|
| Do you have a better solution? | Apr 19 |
Michelle den Boer wrote:
One downside of glossaries or termbases is that they might not be up-to-date, especially when they're maintained by the end client. Then you'll get repeated instructions to ignore the glossary for certain key terms.
Glossaries and termbases are not carved in stone.
I have actively contributed to client termbases, or informed the client when I found terms that needed updating.
I make an effort to keep my own glossaries updated. In quiet periopds I check them, and as a matter of principle I add a note to some entries, giving the date when they were last checked. Then, when the term comes up, I can check again if it was a while ago, and update the note and the entry if necessary.
Other tems don't change so often!
I think this is the kind of thing humans wil have to do for some years yet - I would not rely on AI to do it!
| | | |
jyuan_us
Estados Unidos
Local time: 14:20
Miembro 2005
inglés al chino
+ ...
| Across projects for whom? | Apr 19 |
I believe the question can be rewritten as "How do you usually handle terminology consistency across projects for the same end client?" This is because each client may have its unique glossary, and different clients could have different preferences over the translation of particular terms. For example, "creditable coverage" is translated very differently in the glossary of each of my three health insurance clients. In this case, maintaining terminology consistency across projects assigned by dif... See more I believe the question can be rewritten as "How do you usually handle terminology consistency across projects for the same end client?" This is because each client may have its unique glossary, and different clients could have different preferences over the translation of particular terms. For example, "creditable coverage" is translated very differently in the glossary of each of my three health insurance clients. In this case, maintaining terminology consistency across projects assigned by different clients can work against you.
[Edited at 2026-04-19 16:24 GMT] ▲ Collapse
| | | |
Login to reply/comment 
