If you work together on a regular basis you could even set up project templates for the same thing. Then each person can read all three TMs, but only writes to their own. You can use three TMs for the Project instead of one. If you had three people working in a small team and accessing the same drive then the solution is simple. But of course you don’t have to share the same one with Studio, and this is a big advantage over the old Trados. These are all true when you are attempting to share the same file-based resource. Translation memory administrators should not do any maintenance work on the translation memory as this typically means heavy load.Project managers should not run the Prepare Task Sequence nor any other batch processing activity while other users are using the translation memory for interactive translation.Instead, the local fuzzy index for users is synched up with new translation units every twenty minutes – from that point the newly added translation units can also be shared as fuzzy matches.
Fuzzy matches cannot be shared instantly in this way as updating the local fuzzy index for each segment added to the translation memory would affect performance negatively, resulting in unacceptable response times for users.That means, if a user adds a new translation unit and another user comes across the same segment, the latter will be able to retrieve it immediately as a 100% match. Newly added translations can be shared instantly as 100% matches and seen by all users of the translation memory.Limitations like these that are detailed in KB Article #5098 in the SDL Knowledgebase: You may well have read that several times just to make sure this is what I actually said! If this is possible then why do we sell server solutions at all, as we have SDL GroupShare, SDL WorldServer and SDL TMS? The reason of course is that sharing a filebased resource like this has many limitations and it’s not a solution for serious Projects. So you have a Translation Memory (*.sdltm), and a termbase (*.sdltb) for example, both of which can be accessed by several translators at the same time. Sharing resources at a simple level is pretty straightforward with Studio because they are mostly file based. Many Translation Environments require the use of a server solution in order to share work and if you only do this occasionally, or if you work with a couple of colleagues, then whilst the server solutions can offer a lot of additional capabilities they are often over the top for simple sharing needs and may even require you signing up for things you may not be interested in. One of the reasons SDL Trados Studio, and Trados before that, has been such a popular choice for translators and small teams is the ability to work with shared resources.
0 kommentar(er)
