![]() ![]() Let’s start by looking at a very basic workflow for exporting and importing files with the desktop version of Studio. So, what to do when you want to send a file to someone else to translate and you want to review it in the editor? Or if you want to outsource both the translation and review, and you simply want to ‘verify’ and finalise the file to generate a target version? It’s not obvious. The cloud version of Studio looks like Team, and works pretty much in the same way, except as a single license user it automatically assigns the task to you – the only user. Team also has a nifty feature where you can email someone a link which allows them to open up the cloud editor and translate a file, all without the person needing Studio software or a license. The main differences between Team and Studio are that Team allows multiple users to share the same resources and assign tasks to other users on the team. ![]() The cloud version for a single license version of Trados Studio is very similar to Trados Team. You can easily add TMs and termbases, but how do you add a translated xliff to your project? The key is to understand that the cloud version is not simply translation software, but also a project management tool which enables collaborative working. ![]() There is no ‘add translation’ button, and it’s not clear how to add any translations that you haven’t done yourself. If you choose to ‘add files’ you end up with another source file. ![]() Trados’ tutorials, although they may mention LSPs, translation teams and even in-house translation departments, do not effectively show how to import files translated externally into the online or ‘cloud’ version. Granted, the cloud version doesn’t have all of the same features and capabilities as desktop Studio, but it could still be useful for you as an outsourcer or small team. As a LSP we were accustomed to working with the desktop version of Studio, and when cloud capabilities were introduced as part of the 2021 edition of Studio, we looked into ways to incorporate the cloud into our existing workflows. I'm happy we found a solution, but this means a lot of work for us to go through all the new translation jobs again and fill in the missing translations.Have you watched the webinar ‘Get to know the cloud capabilities of Trados Studio 2022’ and trawled through the available information, yet still can’t quite figure out the cloud version? After fill in the missing translations I imported it and the translations are coming through. Re-edited it and also saw most translated text were present. I also sent the homepage for translation again, took the translation job and downloaded the XLIFF file. So, while I'm not sure of the history that produced a problem with the existing XLIFF files, it should be possible to fix the issue as described above.Ĭould you please try that and confirm it works? The translation status was updated, and the translated heading appeared on the home page. So I updated the XLIFF file with the translated text, saved it, and re-imported it on the WPML > Translations page. I edited it, and saw that most of the translated texts were present, minus the few isolated headings where the translation was missing. So I sent the home page for translation again, took the translation job and downloaded the XLIFF file. I can't spot what the problem with the XLIFF file is, but there does appear to be an issue with it. (Only the assigned translator can import the XLIFF file.)Īlthough at face value it appears to import okay, it was still the case that if I checked the translation status on the Translation Management Dashboard, it didn't appear to have completed updating the translation.Īnd, sure enough, the missing heading translations on the home page were still missing. OK, so on my local copy of your site I logged in as the 100leiden user so that I could re-import the XLIFF file you provided. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |