Content deleted Content added
Citation bot (talk | contribs) Alter: journal. | Use this bot. Report bugs. | Suggested by Headbomb | Linked from Wikipedia:WikiProject_Academic_Journals/Journals_cited_by_Wikipedia/Sandbox | #UCB_webform_linked 139/157 |
→Main benefits: Included some industry-specific technical knowledge on how bespoke translation memories should be deployed to suit the needs of a given project. Tags: Reverted Visual edit |
||
Line 27:
* Reducing costs of long-term translation projects; for example the text of manuals, warning messages or series of documents needs to be translated only once and can be used several times.
* For large documentation projects, savings (in time or money) thanks to the use of a TM package may already be apparent even for the first translation of a new project, but normally such savings are only apparent when translating subsequent versions of a project that was translated before using translation memory.
It is important to keep in mind that while Translation Memory Management is a powerful tool for the above use-cases, it is best practice to tailor a given translation memory on the basis of each individual project/language pair. The structure and division of this customization can be decided upon based on:
* Linguistic consistency within and across TMs.
* Approval status of the <mark>translation</mark>s saved in them.
* Efficiency and risk evaluation regarding maintenance and the correct identification of linguistic assets.<ref>{{Cite web|last=Sheth|first=Rucha L.|date=2021-05-19|title=Translation memory management: best tips and practices|url=https://www.nimdzi.com/translation-memory-management/|access-date=2021-06-28|website=Nimdzi}}</ref>
=== Main obstacles ===
| |||