![]() ![]() The comments feature has at last been brought back after disappearing a year ago. If you’re translating a segment you can easily switch the focus to the filter display by clicking Ctrl+F6. It’s nice to have these details on permanent display down here: Keep an eye on the current filter down in the status bar at the bottom of the screen and double click the icon to call up the filter display in the ribbon. The workaround until this is corrected is to type any letter, then your real search in uppercase and then delete the prefixed letter. If you’re using the “case sensitive” options, right now Studio can’t cope with a search that starts with an uppercase letter. This is excellent for checking that auto-propagation has been performed correctly (yes, AP does get hiccups sometimes). It has been expanded in Studio 2014 and the old “duplicate” filter has been replaced with a “repetitions” filter. The display filter is located under the Review Tab in the ribbon. Just a minor detail, but it speeds up your work! When you’re translating, after confirming a segment, Studio now skips locked segments and goes to the next unlocked segment.Select the segments and toggle between the two using Ctrl+L. In the Editor View, you can now set the status of a group of adjacent segments as locked or unlocked even if they have a mixture of locked/unlocked segments inside them.By locking these segments during “pre-translate” I can just concentrate on the remaining 5,000 words that I’ve got left to do. I’ve just set up a project that has 75,000 words in 100% matches from a previous job I did. It’s not just agencies that benefit from this. If you work with those terrible agencies that don’t pay you to translate 100% matches, you can now lock them in the pre-translation task to make sure you don’t go near them.There are three improvements in this area. ![]() And while I’m on the subject of analysing files, you can now report locked segments separately in the analysis. Studio saves it in the background so that batch tasks are immediately available. You can now do a quick analysis on a new file by simply opening it in Studio ( Welcome View>Translate Single Document). To do this, select “Export to Workbench-optimized TMX format for use in Trados 2007” in the TMX export wizard. If you work with Trados 2007 buffs who want your TM returned with field values and all, you can now export your studio TM to TMX and carry over your text fields and attributes. OMEGAT MERGE SEGMENTS UPGRADESo the transition when you upgrade will be smoother than between 20 (where projects are only compatible if you select the right option in advance). Studio 20 use the same project and package formats. There’s also a link to the OpenExchange App Store right there.Īnd, if you use the new Menu Maker app, you can even customise the list of apps in the Welcome view. Now, I just go to the Studio Welcome View, and the left-hand menu lists all the apps that can be launched with a single click. I used to keep a bunch of these apps on my desktop and had to search for the right one each time. You can now launch OpenExchange apps directly from Studio. Again, there’s lots to talk about, so I’ll concentrate on the following topics: In this follow-up to last week’s post on SDL Trados Studio 2014: new features for beginners, I’m going to look at details that may be useful for people who already know their way around Studio. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |