User manual

User Manual Page 67
EDIsecure
®
XID 8300 Printer Driver
The extent of the user interface depends on each Plug-in, i.e. there are no generic options from the driver.
A sophisticated Plug-in should provide an easy-to-use user interface for both options and a way to do
encoding tests with real data in the test dialog, preferably with the same format templates that have been
set-up for the real encoding, as it is mandatory for the production that the hardware is working correctly with
the encoder software and the data is encoded properly on the chip.
Since both options are optional, a minimalist Plug-in does not need to provide these functions. The absence
of these options may also be desired by the security requirements of the application.
6.3 Application Setup
The chip encoding features of the driver are application independent, i.e. the application does not need to be
set-up for the specific encoder hardware of the encoding Plug-ins.
The entire encoder-specific configuration is done in the Plug-in Manager, stored and handled outside the
printing application, as well as the encoding process itself.
However, there are application requirements that need to be fulfilled in order to process the encoding data in
the driver.
All of the encoding data is transported in a so called "encoding string" to the driver and later to the Plug-in.
The card layout must contain this string somewhere on the front page. This is especially important to
remember when using two-sided layouts.
If the driver recognizes the encoding string on the layout, it will not print it on the card but use it for encoding.
Therefore, the encoding string must be sent "as text" by the application.
The "switch" for the driver to find the encoding string is in the Card Type section of the document's printer
properties. If "Smartchip" is selected here, the encoding string will be captured and processed.