Passa ai contenuti principali

Hacking your translations with glossaries

A glossary helps you to make sure that each time a defined term appears in your translation project, it is used consistently and correctly.

You have to spend time to save time.

Our whole career as modern-day translators spins around technological devices, and time is always short. Learning how to set up our CAT tools and every other translation software known to man, takes a lot of time.

Glossary editing, for example, is one of those time-consuming activities that we have to carry out in order to provide a good quality translation. It’s boring, but it proves to be an investment for later on because a glossary is THE reference for consistent terminology.

It requires a glossary to make sure that every translator uses the same term for the same concept overall the translation project and uses approved standardised terms for each target language.
    

Four reasons you should use a glossary:

1. Keep translations consistent.
 
2. Ensure that your brand is protected.
 
3. Speed up the translation process: when translators are confused, they have to ask questions. The process slows down. A clear glossary means that translators have fewer questions for you, which means that they work much faster.

4. Save on translation costs.

Moreover, a glossary becomes even more important if:
  •   you use more than one translation resource;
  • in case of short deadlines;
  • when many translators are working on the same project simultaneously.
  • the documents have to be provided in multiple languages. 
Glossaries, as you can see, help you working on standardising your content’s terminology, tone, style, and goes a long way toward saving you time. 


A good is a work in progress. If you have new terms that might benefit from a glossary entry, add them.
 
Good translation takes work. The more care you put in, the better translation you’ll get. A good glossary is a key step in creating a clear, consistent, readable translation:
Quality in, quality out.



Commenti

Post popolari in questo blog

Differenza tra football e soccer

Perché il calcio viene chiamato in modo diverso da inglesi (football) e americani (soccer)?

I due termini, football e soccer, si usano per indicare lo stesso sport sebbene football sia presente in un maggior numero di lingue con un più alto numero di occorrenze.

Footballrisale a un decreto del 1424 in cui re Giacomo I di Scozia bandiva il gioco con la frase: "That na man play at the Fute-ball".

Nel 1863 viene fondata a Londra la Football Association (FA), la prima federazione calcistica nazionale che unificò definitivamente il regolamento. Queste regole furono adottate da tutti eccetto che dalla Scuola di Rugby, che preferiva un gioco più fisico in cui si potesse toccare il pallone anche con le mani. Si venne a creare cosi il termine soccer, entrato a far parte dello slang universitario comeabbreviazione colloquiale di Assoc., da  Association football+ la formazione agentiva "-er" per distinguerlo dal Rugby Football.

Fonti:


Terminologia etcEnglishfor.it





Football or soccer, which came first?

With the World Cup underway in Brazil, a lot of people are questioning if we should refer to the "global round-ball game" as "soccer" or "football"? This is visible from the queries of the readers that access my blog. The most visited post ever is indeed “Differenza tra football e soccer” and since we are in the World Cup craze I think this topic is worth a post.

According to a paper published in May by the University of Michigan and written by the sport economist Stefan Szymanski, "soccer" is a not a semantically bizarre American invention but a British import.

Soccer comes from "association football" and the term was used in the UK to distinguish it from rugby football. In countries with other forms of football (USA, Australia) soccer became more generic, basically a synonym for 'football' in the international sense, to distinguish it from their domestic game.

If the word "soccer" originated in England, why did it f…

You are doing terminology management all wrong. Here is why

We all know the never-ending, love-hate relationship between translators and terminology… now, let’s explore some of the most common errors.
Generally speaking, when thinking of terminology, we imagine a glossary, made of two parallel columns full of terms, with the source language on one side and the target language on the other.

Easy.

And what better than an Excel file for this type of structure? Seems easy and intuitive enough. Plus, you can also add an extra column to the right, to add comments or other notes.

Well, there’s something wrong here: Excel was never designed to store text, much less terminological data.

Yes, you guessed it… Excel was created to crunch numbers, not words!

Using Excel files is not an effective or efficient way to manage complex databases. If you use it to create glossaries as mentioned above, you will not be able to specify additional attributes for those terms. It is indeed possible to add extra columns but always limited to one field or category for ea…