
Some of the terms raised debates among the translators – thus, they suggested “a member, a participant and a shareholder” as an equivalent of an Italian term “socio”. So we asked the translators to add to it the terms which they consider important and recurrent. Obviously, we had no time or additional resources to prepare a term base, which was very important for the consistency of the translation. It was an IT>EN translation of a package of legal documents – about 100 pages in 2 days.

I think this was an interesting experience of developing a term base in the cloud – something that cannot be done outside the cloud environment. “Just wanted to share our recent experience of running a rush project on the MemSource platform. Minor MemSource releases (these are most frequent) get now deployed without any interruption to the MemSource Cloud serviceĪpriori Translations CEO, Yulia Tulinova, based Moscow has shared her feedback on managing a rush project in MemSource Cloud:.When editing multiple jobs at once, users can now decide which specific fields should be batch updated and which should be left intact (these can be removed).to copy all communication to an email archive) Email templates allow defining a cc email address (e.g.For locked jobs, confirming a segment or uploading to server is blocked.“previous workflow step not completed (85% confirmed)” If a preceding workflow step has not yet been completed, the user is alerted to this fact – the indicator of the number of segments confirmed turns red and a message is displayed, e.g.Alerting a user to the status of the preceding workflow step (only in the Team edition).Now it is possible to assign different translation memories to different workflow steps in a project Previously, all workflow steps in a project had to share identical translation memories.Different translation memories can be assigned to workflow steps in a project (only in the Team edition).Unapproved terms (“new” terms) are now displayed in gray in MemSource Cloud, so that they can be easily distinguished from approved terms that are displayed in black color font.If multiple term bases are selected for a project, only the one in the write mode is displayed to the linguist in the linguist portal.A project manager or administrator may, in addition, allow specific linguists to “edit and delete approved terms”, effectively promoting that linguist user to a terminologist.By default linguists may edit “new” (not approved) terms.


Also, it is much easier now to take on large translation projects and rely on MemSource support us all the way with keeping terminology and style consistent.”
#Apsic xbench free download license#
Its translator’s workbench, MemSource Editor, is available as a free download, so we do not have to worry about freelancers having to license MemSource before we start working with them. Hannah Davies, Project Manager at SBC added: “MemSource gives flexibility that we did not have before. We have been using MemSource Cloud for over 4 months now, completed hundreds of translation projects in it, and are extremely happy with this technology.” In the end they decided to go with MemSource Cloud and subscribed to its Team Start edition in March 2012.Ĭherie Plaice, SBC founder said: “We were looking for a team-oriented translation tool that would adjust to our needs and not the other way round. For six months, they tested, month after month, 6 different translation tools. The decision was made but a question remained – which product should be selected? SBC management did not want to take any chances.

Instead of mailing TMX files back and forth, users would just connect to the centrally stored translation memory and other translation data. A decision was made by the business owner to purchase new translation technology that would allow efficient sharing of translation memories and terminology across the entire team: project managers, inhouse and freelance translators. SBC Translations, a UK-based translation and localization company, decided in the summer of 2011 that the legacy desktop translation tools they were using did not match their fast-paced translation business anymore.
