Miraplacid Text Driver SDK 5.3

Miraplacid Text Driver SDK 5.3 offers users all the functions of  virtual printer driver that you can find in Miraplacid Text Driver. You can customize it and embed into your software. With the driver generated with Miraplacid Text Driver SDK you can save the extracted information as plain, formatted text or as XML for future processing in all installed codepages and Unicode.

After installation on your PC, driver generated with the SDK appears as a new virtual printer in your system. All the documents you print to this "printer" will be accessible from you software via COM interface. You can browse through the document page to page, get and modify extracted text. Then you can save results to disk, upload to FTP or HTTP server, print them to a real printer or send by email.

Miraplacid Text Driver SDK supports plain and formatted text extraction in all major code pages as well as Unicode.

Turn "Auto Save" on if you want the driver to send extracted text to the chosen destinations without waiting for your input. If you want every document to be saved to an individual file, add {{DATE}}, {{TIME}}, {{SYSFOLDER}}, {{IDENTITY}}, {{PAGE}} or {{JOB}} to the file name or path. They will be replaced with current date, time, system folder, some unique number, page number and print job id respectively.

SDK is free, but you will need a license to use or redistribute the printer driver it generates.

Do you need SDK or regular Miraplacid Text Driver is what you need?

Miraplacid Text Driver saves all the settings to system registry as a set of profiles. It means, that you can set it once and use it over and over. If you never change settings, just turn auto-save mode on and Miraplacid Text Driver will not bug you with UI dialog. You can add something like {{DATE}}, {{JOB}} and {{PAGE}} to path or filename, and all the result images will be saved separately.

If it works for you, you probably do not need the SDK.

All the Miraplacid Text Driver controls you can see on Miraplacid Text Driver UI dialog, also available through COM interface. In fact, UI communicates with Core through COM. It means, that you can write a script or application to manage printing process.

If this is what you need, you still can do it without using SDK.

There are the folowing cases when you need the SDK:

• When you integrate Miraplacid Text Driver with your product and want everything to be installed by your installer. Meaning, you do not want Miraplacid Text Driver installation dialogs to pop up.
• When you need custom User Interface which will be compatible with your product by functionality.
• When you need to have much more control over printing process. In this case, you will need to write your own User Interface, which could not contain any actual graphics elements. This UI may just control printing process.
• When you need to have a automation component for document-to-text conversion purposes which will be named and look like integral part of your own product (re-branding). 

How to start working with SDK?

• With Miraplacid Text Driver SDK you will prepare printer driver installation package and install the driver on your PC.
• If you skip these steps and launch some sample application, you will probably get an error mesage, cause some SDK components require proper registration and installation.
• Launch setupmaker.exe. Default settings work fine. Press Ok button.
• Copy mtd.dll generated by setupmaker.exe to examplessetupui folder.
• Launch Setup.exe and press Install button.

Now you can start over and change settings or play with other SDK modules.
 
Major Features:

1. Setup making wizard  setupmaker.exe. Start it, set all the parameters, push "Ok" buttons and get your custom Text Driver installation component mtd.dll. This dll has everything to install Miraplacid Text Driver to new PC. Those parameters include printer driver name and all the other names. You can change it to your company name or your product name.
2. Miraplacid Text Driver documentation
3. SDK documentation
4. Custom installer, sample registration utility and custom User Interface.

Enhancements:

• Printing speed increased
• Monitors default printer change
• Redirects RAW print jobs
• New options
• COM model improved
• Some fixes made

Requirements:

• Pentium-II 266
• At least 64 MB RAM
• At least 100 MB HDD
• Windows 2000/XP/2003/XP 64-bit/2008/Vista.