![]() ![]() Here's the "fast path" for staying out of trouble: To avoid the trouble of multiple, role-based entries being written to a TM, settings must be created in which the option to Store modifying user's role in the TM entries in not selected, and these custom settings must be applied to the primary translation memory in the project (by default or explicit selection). The last tab of the default TM settings dialog looks like this: This would be the case there you want to apply a special set of penalties to the content of that TM, for example. Project home > Translation memories > (TM) > Settings where alternative TM settings can be specified for a particular translation memory selected in project. ![]() Project Settings ( Project home > Settings > TM settings) in a specific project, where the default settings for the current project can be set.> Default resources > TM settings), where the default for new projects can also be set The Resource Console,where settings can be created, edited, imported, exported, etc.TM settings are "light resources" which can be managed in four places: To avoid the problems that can result from this redundancy and preservation of errors in the translation memory, as of build 6.8.6 it is necessary for users to explicitly opt out of the current Kilgray TM settings defaults and create their own custom settings. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |