The title of this article is only half joking… half because the Terminjector provides a mechanism for filling a neat hole in the armour of Studio… and the other half because this application takes advantage of exactly what the SDL OpenExchange (now RWS AppStore) was designed to do.  It was designed to provide a mechanism for any developer to develop and plug into the Studio product to introduce capabilities that give them an advantage over anyone else, or share with others so they can get the benefit too.
In this case the developer, Tommi Nieminen, has created this plugin for himself and then published it free of charge for others to enjoy as well.  The basic idea behind the plugin is that it can modify the output of the Translation Memory before it is passed to the editor for you to use.  Why is this useful you may ask?  Well consider the following example of a document (created to demonstrate the point of course) you may wish to translate in Studio:

The first two segments were confirmed into the TM and rest of the document allowed to pick up the best match for each segment.  The point of interest here are these:

The codes CO10 0DT and AB10 1AA are variables in this document and as you can see (if it’s not too small) they have been reused throughout the document because the rest of the text is the same, apart from the dates.  The dates 20/03/1962 and 24/3/1962 have been autolocalised by Studio into the format demanded by the target language.  In this case I am going from en(GB) to en(US) just to keep this simple, so the dates were changed to 3/20/1962 and 3/24/1962 respectively.  The exception being segment #5 as here the date as a 3-digit year, 1/1/793, and this is not recognised at all, so the autolocalisation changed this to 3/20/1962 as the closest match… clearly something you don’t want as it’s easy to miss.
Dealing with the codes is something you could do in Studio by adding them as variables to the Language Resource template.  But what if there were hundreds, or thousands (in the case of post codes as this example).  The current version of the Studio desktop tool doesn’t allow for importing a list so you would have to add them one by one… not really practical for a large list.  Studio GroupShare will allow the import of variable lists but if you’re using the desktop tool this doesn’t help you.
Terminjector provides the ability to create regular expressions (here we go again… but you may be seeing how useful they can be now) that allow you to set up patterns to look for variables and dates and then replace the suggestion from the TM with the matching pattern replacement.  One word of caution though… I have mentioned before that Studio uses the .NET flavour of Regex… here Terminjector uses POSIX.  I don’t intend to go into this in a lot of detail as this is an exercise to show you the possibilities, but RegexBuddy can handle all the flavours of regex and can even convert the code between flavours… so another good reason to buy a copy.!
To make Terminjector work you simply download the plugin from the OpenExchange, unzip it and run the msi.  Then start Studio and add the Terminjector as a new Translation Provider.  It should be added to the specific language pair rather than All Languages, so in here:

You will then be presented with the Options window where for this exercise you must do two things, create a txt file (this is just a click of a button and decide where to put it), and select the Translation Memory you wish to associate the plugin with.  The full details of how to configure this and how to use it are here so I won’t go into the details now.  Rather I’ll show you the potential effect on this file.
First of all I added a regular expression like this:

([A-Z][A-Z][0-9]{1,2} [0-9][A-Z][A-Z]) 1

This is to grab the postcode from the source and then replace the Translation Memory match with it.
Then I opened the txt file that was created for me and added the expressions for the dates directly into it like this:

([A-Z][A-Z][0-9]{1,2} [0-9][A-Z][A-Z]) 1
([0-9][0-9]?)/(01)|1/([0-9]{1,4}) 1 January 3
([0-9][0-9]?)/(02)|2/([0-9]{1,4}) 1 February 3
([0-9][0-9]?)/(03)|3/([0-9]{1,4}) 1 March 3
([0-9][0-9]?)/(04)|4/([0-9]{1,4}) 1 April 3
([0-9][0-9]?)/(05)|5/([0-9]{1,4}) 1 May 3
([0-9][0-9]?)/(06)|6/([0-9]{1,4}) 1 June 3
([0-9][0-9]?)/(07)|7/([0-9]{1,4}) 1 July 3
([0-9][0-9]?)/(08)|8/([0-9]{1,4}) 1 August 3
([0-9][0-9]?)/(09)|9/([0-9]{1,4}) 1 September 3
([0-9][0-9]?)/10/([0-9]{1,4}) 1 October 2
([0-9][0-9]?)/11/([0-9]{1,4}) 1 November 2
([0-9][0-9]?)/12/([0-9]{1,4}) 1 December 2

This may look odd to you, but this is the second part I wanted to show you.  Within Studio you can change a short date to another formatted short date, and a long date to another formatted long date.  But you cannot change a short date into a long date.  So I decided to have a go at changing the short date here into a long one, and also get around the problem of the 3-digits for the year at the same time.
So these expressions are intended to look for a date with a 3 and change it to March, for a date with a 7 and change it to July etc.  So I needed 12 expressions to do this and you can store as many different regex expressions in here as you like, all used by the Terminjector provider when a match is found in the source text.
The effect of this when I click on a segment in Studio is something like this: 
The second result in the TM results window here is coming from the terminjector translation provider as you can see, the first one is from the Studio TM.  What you can see is that the Terminjector has correctly replaced the post code and the date with the details I needed.  Brilliant..!
If I now go through my document using these improved results then I now see this instead:

One drawback is that the TM results are all 0%.  I guess this is because there is nothing to match with in the Terminjector as it’s just a wrapper around the Studio TM.  But if it’s not important for you to show the matches in a completed bilingual file then this is certainly a good way to handle the problems of long variable lists and difficult date transitions with regular expressions.
I’d thoroughly recommend you review the help documentation with this plugin because it can do more than I have outlined here… but on this quick test I did this afternoon of the updated version I’m impressed.

Updated 4 September 2012

After writing this article I had an interesting set of questions from Mats (as you can see below), and I realised that I had not made it clear enough in the example I was showing… I also realised I had omitted some important details in order to achieve what Mats referred to which was to allow this:

To clarify the difference.  In this screenshot I have translated the first two segments only and then Terminjector has inserted the correct variables and dates into the target (the red underlines are spelling mistakes as I am still using an English target language but with Welsh text )… this works during interactive translation or pre-translation so is a powerful tool over the use of variables or simple search and replace.
In the previous example I was actually converting a no match value into the target, hence the reason for this being the same as the source, but with correct use of the regular expressions to substitute the values I searched for.  I was not replacing the values found in a TM as a fuzzy match.
The missing parts were these.  First I needed to make sure that the Terminjector TM provider was activated for update and then I don’t even need the SDLTM I had also used before.  So this is what I did.  I deactivated the file based TM I was using and checked the update box for the Terminjector:

So the Terminjector is still using the filebased TM I deactivated but this is set through the Terminjector settings and not in here… first basic error on my part.
Next, in order to replace a value that is being presented as a replacement for the target coming from the TM you have to add a third component to the regex patterns… this is clearly documented in the help but I didn’t read it properly.  So this third regex, and this is quite hard to get your head around, “refers to the text in the source segment that the capturing group expressions of the first field matched.”  I put this in quotes because I needed help from Tommi to understand this and he explained it to me using these words… better than I could explain it!
So for the post codes for example I changed this:

([A-Z][A-Z][0-9]{1,2} [0-9][A-Z][A-Z]) 1

to this:

([A-Z][A-Z][0-9]{1,2} [0-9][A-Z][A-Z]) 1 [A-Z][A-Z][0-9]{1,2}
[0-9][A-Z][A-Z]

So basically as I wanted to use the entire pattern for the post code I just needed to add it again at the end for the replacement when there is a fuzzy match from the TM.
The dates on the other hand were a little more tricky and lengthy because of the operation I decided to attempt… and I will add that I needed help with both of these concepts from Tommi.  So I changed this:

([0-9][0-9]?)/(01)|1/([0-9]{1,4}) Ionawr 1, 3

Which is a little different from the original because now I’m doing this properly and am translating to a different language to make sure it’s clear… to this:

([0-9][0-9]?)/(01)|1/([0-9]{1,4}) Ionawr 1, 3 ((Ionawr)|(Chwefror)
|(Mawrth)|(Ebrill)|(Mai)|(Mehefin)|(Gorffennaf)|(Awst)|(Medi)|(Hydref)
|(Tachwedd)|(Rhagfyr)) [0-9][0-9]?, [0-9]{1,4}

So basically I had to identify the pattern from the source with the first field:

([0-9][0-9]?)/(01)|1/([0-9]{1,4})

provide an option for a specific month in the case of a no match:

Ionawr 1, 3

and finally provide the ability to recognise the appropriate month from the possible twelve based on what was found in the source and matched, and then use it in the replacement regex for the date:

((Ionawr)|(Chwefror)|(Mawrth)|(Ebrill)|(Mai)|(Mehefin)|(Gorffennaf)
|(Awst)|(Medi)|(Hydref)|(Tachwedd)|(Rhagfyr)) [0-9][0-9]?, [0-9]{1,4}

So quite lengthy and more intricate a process than I first described.  But this is incredibly powerful because I can now pre-translate the entire file and all the variable postcodes, and in addition transform the short English UK dates to long Welsh dates.  So probably not the best example to make this look easy..!
I think for most users the ability to handle huge variable lists like this is a real plus, and when you are only thinking about one thing not even difficult to set up.  So give it a try… the capabilities once you get your head around the basics are very impressive.  A really good application from Tommi Nieminen on the SDL OpenExchange (now RWS AppStore).