Difference between revisions of "Naming your TMs and Glossaries"
(added ref and TOC) |
|||
| Line 11: | Line 11: | ||
Here are some examples of standardized naming conventions for TMs: | Here are some examples of standardized naming conventions for TMs: | ||
| − | # '''EndClient_TM_slLV_tlLV'''<ref>''slLV'' stands for source language locale variant and ''tlLV'' stands for target language locale variant. Sometimes, a locale variant is unspecified or unnecessary. For example, there are multiple variants of English (UK, US | + | # '''EndClient_TM_slLV_tlLV'''<ref>'''slLV''' stands for ''source language locale variant'' and '''tlLV''' stands for ''target language locale variant''. Sometimes, a locale variant is unspecified or unnecessary. For example, there are multiple variants of English (UK, US, Canadian, etc.) giving you language codes like ''enGB'', ''enUS'' or ''enCA'' whereas Corsican does not have a locale variant, resulting in the two-digit code ''co''.</ref> (e.g. a US English to Canadian French TM for a company called Acme could be named: Acme_TM_enUS_frCA) |
# '''Agency-EndClient_FIELD_slLV_tlLV''' (e.g. a US English to Canadian French TM for a company called Acme, via a translation agency called TransAgency could be named: TransAgency-Acme_TM_enUS_frCA) | # '''Agency-EndClient_FIELD_slLV_tlLV''' (e.g. a US English to Canadian French TM for a company called Acme, via a translation agency called TransAgency could be named: TransAgency-Acme_TM_enUS_frCA) | ||
# '''FTM_FIELD_slLV_tlLV''' (e.g. a TM for all software-related translations from US English to Canadian French could be named: FTM_SOFTWARE_enUS_frCA) | # '''FTM_FIELD_slLV_tlLV''' (e.g. a TM for all software-related translations from US English to Canadian French could be named: FTM_SOFTWARE_enUS_frCA) | ||
Revision as of 10:21, 10 December 2018
What’s in a name?
Database names should include information that helps you easily identify them in the future, without having to open them to know what is inside. They should also be standardized and scalable in the event you want to share them in the future.
Translation Memory (TM)
Best practice is to create a separate TM for each client. However, if you have many small jobs for different clients in the same field, you might consider creating a field-based TM.
Potential information to include in the name: end-client name, agency name, field, date, TM creator, source language, target language, tool name, etc.
Here are some examples of standardized naming conventions for TMs:
- EndClient_TM_slLV_tlLV[1] (e.g. a US English to Canadian French TM for a company called Acme could be named: Acme_TM_enUS_frCA)
- Agency-EndClient_FIELD_slLV_tlLV (e.g. a US English to Canadian French TM for a company called Acme, via a translation agency called TransAgency could be named: TransAgency-Acme_TM_enUS_frCA)
- FTM_FIELD_slLV_tlLV (e.g. a TM for all software-related translations from US English to Canadian French could be named: FTM_SOFTWARE_enUS_frCA)
Glossaries
The same principles described above can be applied to glossary names.
Here are some examples of standardized naming conventions for glossaries:
- EndClient_G_slLV_tlLV (e.g. a US English to Canadian French glossary for a company called Acme could be named: Acme_G_enUS_frCA)
- Agency-EndClient_G_slLV_tlLV (e.g. a US English to Canadian French glossary for a company called Acme, via a translation agency called TransAgency could be named: TransAgency-Acme_G_enUS_frCA)
- FG_FIELD_slLV_tlLV (e.g. a glossary for all software-related translations from US English to Canadian French could be named: FG_SOFTWARE_enUS_frCA)
Tips
- You can use both a client and field databases simultaneously. This allows you to leverage work done for other clients in the same field.
- The underscores are optional; the benefit of using underscores is that it stands out from other file and folder names on your computer so you can quickly identify it as a database.
- You should store all of your TMs in a dedicated TM folder on your computer. You should store all of your glossaries in a dedicated Glossary folder on your computer. Make sure that these folders are regularly backed up.
References
- ↑ slLV stands for source language locale variant and tlLV stands for target language locale variant. Sometimes, a locale variant is unspecified or unnecessary. For example, there are multiple variants of English (UK, US, Canadian, etc.) giving you language codes like enGB, enUS or enCA whereas Corsican does not have a locale variant, resulting in the two-digit code co.
