In this example I’m just adding three files, and once they are in the list you can right click on a file (or folder), or select several files together using the ctrl key and choose the Analyze Only batch task, or select it from the Batch Task icon on the ribbon: If you decide you want to change the purpose of a file after adding it then you can change this by selecting the files and then clicking on this icon in the ribbon: If you change to the source language then you won’t get this option and they will be added as translatable files. If you drag and drop without changing to the source language first then you will be presented with an option: The one difference between these methods is that if you select Add Files in either of the latter methods they will always be treated as translatable files as long as they are recognised filetypes.
If you prefer you can also use the Add Files button from the File Actions group in the ribbon or Right-Click from the Files View window:
All you have to do is activate the Project by double clicking it whenever you want to analyse a file, or files, then drag and drop them onto the Files View. Once you’ve done this the process becomes quite simple. The basic concept behind getting a quick and simple analysis report before you take on a job is that you create a Project that you only use for analysis and then you leave this permanently in the Projects View: What they might not think of is how you can use the Projects concept to make this easy for you once you become just as experienced with the new tools. Now I have to create a Project in Studio and it takes so long to do the same thing.” I do think this is something you’re more likely to hear from experienced users of the older products because they initially find that getting a quick report out of Studio is a far more onerus process than it used to be.
Something I only occasionally hear these days is “When I used Workbench or SDLX it was simple to create a quick analysis of my files.
It’s such a good title (in my opinion -)) I decided to keep it and write the same article again, but refreshed and enhanced a little for SDL Trados Studio 2014. If this title sounds familiar to you it’s probably because I wrote an article three years ago on the SDL blog with the very same title.
0 kommentar(er)
