Today we are going to try to explain as simple as possible what TWAIN is all about.
Some time ago one could operate a scanner by using manufacturer’s software only.
That happened because, following a general pattern in software history, each producer attempted to provide its own proprietary product standard at first.
But soon enough the need of an unified standard emerged, so some important scanner manufacturers and software publishers gathered up to form a group meant to design and maintain a unique standard to allow any imaging software to operate their scanners.
The resulting protocol was called TWAIN and the group that maintains and develops it is named “TWAIN Working Group“.
As explained in the previous blog article, TWAIN is a set of specifications, not a software (just as a side note, the TWAIN Working Group releases toolkits but only for the purpose of providing vendors with assistance in achieving TWAIN compliance, nothing more).
By following these specifications when developing the drivers, scanner manufacturers give users the chance to use their particular scanner with any image or document processing software.
So basically, TWAIN contains the blueprint of a bridge, having one end “fixed” on a unique, specific image-acquisition device and the other end “opened” to any imaging/processing software.
After the scan is done, the acquired image is transfered to the application you are using, so you can process it.
If you are using PaperScan you can apply various filters, various image corrections and/or enhancements, various color and tonal balance tuning, image and document editing, add annotations, perform OCR and so on, then, finally, save it in a format of your choice.
The TWAIN protocol is being constantly improved so there are many revisions/versions of TWAIN.
Current release is 2.2, as of 16 February 2012.
This brief depiction intended only to highlight the bottom line about TWAIN.
Similarly, our next article will be about WIA.
See you next week!