![]() ![]() The trick now is to NOT “Confirm Translation” as you work. But now I can run whatever QA checks I have in mind to verify that my TM is sound: It took 5 – 10 minutes to complete the project creation for me with some 600K words split into 84 files. This part could take a little while depending on the size of your TM, so you could also select to do this in bite sized chunks too and create several projects until you finish the job. ![]() Then I create a project in Studio with all of the XLIFF files and add the SDLTM I just converted and any other resources I want to help me with the QA checks I intend to run. This is pretty quick, less than 7 seconds for 42 thousand TUs, and at the end I get a report in the bottom half of the window ending like this: In a nutshell this is what you’d do.Ĭonvert your SDLTM to bite sized XLIFF files (say 500 TUs at a time for example). But the process of converting your TM to XLIFF files, adding to a project and QA’ing them is not insurmountable… you just need to be careful and Costas kindly provides good information in his help file explaining the process. This is an option you need to be careful with if you’re working through your own TMs because once you do this and create a new TM with a QA’d XLIFF then you will lose all the context information that is held in the TM but not in an XLIFF… so information related to Context Match, TU information and custom fields. I’m not going to run through everything this tool can do as there is an excellent help file that explains how to use the features and also what they may be useful for, but I will pick out a couple of things that are interesting for me.įirst of all the ability to convert your TM to XLIFF. To work with TMs greater than that you need the Pro version which is €35… but this is a bargain for the functionality we see. This application has a free version that allows you to work with TMs containing up to 50,000 Translation Units. You can immediately see this is a very compact application filled with some excellent features, and you’ll also see there is some licensing information too. The application itself looks like this (the control part of the screen anyway): The one I want to focus on with this article is SDL TmConvert as this is the most recent application Costas has submitted and it allows you to do all of the things I mentioned at the start and more. A good example of how this can be used is by another Hellenic, although this time a developer and not a dramatist Costas Nadalis has developed four applications for the OpenExchange and is one of the most prolific developers creating applications for others to benefit from:Īll of these are really useful applications and all of them are applications that centre around the wisdom of maximising the use of your TMs. It really is a well developed and supported tool in it’s own right. This platform and the capability that is available for anyone who has the knowledge to do their own programming is not provided by anyone else. So I’m talking about the SDL OpenExchange of course. If you wanted to do these sorts of things to help you properly maintain your TMs or use them for other things then you would have to use tools that operate outside of Studio… but not necessarily outside the Studio platform. enhance TM with the translatable content of tags.convert to other formats (xliff, xml, csv etc).stripping out fields, attributes and other translation unit information.export subsets of your Translation Memories based on complex queries.check your TMs for consistency and other QA requirements. ![]() Studio does have some simple features for helping you to maintain your Translation Memories, but there are things you might want to do that go beyond the capabilities of search and replace, creating and editing fields and attributes or exporting subsets or complete copies of your Translation Memories… let’s refer to these as TMs from here on in. TMX.Ī free version is limited to 50K segments. Paul Filkin wrote about the tool SDL TmConvert that helps to manage the Translation Memories of SDL Studio, eg. I tried Trados Studio Resource Converter, with updating Jave Runtime Environment, it works fine. I tried Wordfast Converter with SQLite DLL, however it didn’t work for my computer. Xbench can also convert SDLTM to TMX, however it is more complicated for this task. (Required DLL: – file to download: sqlite-dll-win32-x86-*.zip) I then found these tools for converting SDLTM to TMX, for free: ![]() Hence this is not accessible for people not holding a license of SDL Trados. Update: SDL TmConvert (or any tool in the SDL App Store) requires users to have bought the license of the corresponding program. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |