On the first day of Christmas my Studio gave to me…
12 Verification SDK and API!
11 QA Checker Profiles
10 Segments to exclude
9 Punctuation checks
8 Regular Expressions
7 Terminology Verification
6 Trademark checks
5 Number checks
4 Segment Verifications
3 Length Verification checks
2 Word Lists
… and no Inconsistencies by default
The Quality Assurance features in Studio are quite extensive, and they are often loved and hated all at the same time. Loved because when used correctly they can provide excellent assurance that you’ll have happy clients… hated because the automated recognition of numbers, dates etc. in Studio follow the settings of your computer and sometimes these are not what you need.
The release of Studio 2014 will bring a number of new OpenExchange applications to the App Store. One of these is already becoming well known based on the name alone… the SDLXLIFF Toolkit! The name suggests this is a tool for working with an SDLXLIFF and being able to take it to pieces and interact with all of it’s components… and this is probably a good explanation of what it actually does.
By taggy files I mean “embedded xml or html content” that is written into an Excel file alongside translatable text. In the 
Unfortunately the practice of being asked to translate a Microsoft Word file that contains HTML code doesn’t look as though it will go away any time soon for some translators. But it’s not the end of the world and it’s often all in the preparation of the Word file before you translate it. 
When I first started adding articles about how to use regular expressions I thought I’d only write three… but I had an interesting question from one of our resellers, 
A few 