Working with glossaries: Difference between revisions

From Pangeanic
Jump to navigation Jump to search
No edit summary
Line 24: Line 24:
* Snippets are case sensitive, consider using different lines for different cased snippets
* Snippets are case sensitive, consider using different lines for different cased snippets
* When finished save the file with a name you can remember later and ''.txt'' file name, for instance ''my-first-glossary.txt''
* When finished save the file with a name you can remember later and ''.txt'' file name, for instance ''my-first-glossary.txt''
==Managing Glossaries in ECO==
Once you have a glossary in a txt file you should upload it to ECO using your ''admin'' account. Regular users can use but cannot manage glossaries.


==Using a Glossary when processing a File with ECO==
==Using a Glossary when processing a File with ECO==


==Using a Glossary Pangeanic Translatiuon API==
==Using a Glossary Pangeanic Translatiuon API==

Revision as of 08:22, 3 December 2021

Glossaries

A glossary is a file in plain text (UTF-8 encoded) containing bilingual alignments to force some tranalations. When a glossary is specified and the text to translate contains one or more snippets of one or more words that are included in the first part of the glossary file the translation will be forced to the second part. Let's conside this example for a Spanish to English glossary:

Pedro Pedro

Juan Juan

Please notice that first snippet and 2nd snippet in each line are separated by a TAB character

What we are indicating with that glossary file is that any ocurrences of the words Pedro and Juan should be kept invariant during the translation instead of trying to translate by Peter and John.

Glossaries are typically used to force the translation in some way of proper names, people names, brands, etc. They are not a replacement of Translation Memories and applicability is limited in flexive languages.

Creating a Glossary

Linguist create glossary files. using a plain text editor, for instance Sublime Text or Notepad+.

Some important points to take into account:

  • Use UTF-8 encoding ALWAYS, moreover when dealing with non-standard charsets
  • Use a TAB character to separate the two snippets in each line
  • Snippets are case sensitive, consider using different lines for different cased snippets
  • When finished save the file with a name you can remember later and .txt file name, for instance my-first-glossary.txt

Managing Glossaries in ECO

Once you have a glossary in a txt file you should upload it to ECO using your admin account. Regular users can use but cannot manage glossaries.


Using a Glossary when processing a File with ECO

Using a Glossary Pangeanic Translatiuon API