chhitz / postscriptbarcode Goto Github PK

Barcode Writer in Pure PostScript
http://www.terryburton.co.uk/barcodewriter/

Copyright (c) 2004-2013 Terry Burton

$Id$

Description:

Barcode Writer in Pure PostScript facilitates the printing of all
major barcode symbologies entirely within PostScript.

Since this resource is written in PostScript and interpretted
within the virtual machine of a printer it is compatible with
virtually any operating system and hardware platform.

It makes including any barcode within a PostScript document as
simple as inserting the following directive:

100 150 moveto (978-1-86074-2711) (includetext height=0.9) /isbn /uk.co.terryburton.bwipp findresource exec


Files:

barcode.ps

This file is the main PostScript resource that should be included
within the prologue of any PostScript document in which you would
like to produce barcodes. Alternatively this resource can be
loaded into the virtual machine of a PostScript printer until 
hardware reset, removing the need to include the resource in each
document. To do this uncomment the relevant line near top of the 
file and send it to the printer.

barcode_with_sample.ps

The file contains the resources together with example invocations of many of
them to produce a page containing an instance of several barcode symbologies.
It is suitable for viewing in a PostScript viewer such as gv or GSview, or
sending directly to the printer with a command like:

lpr barcode_with_sample.ps (Unix)
copy /B barcode_with_sample.ps LPT1: (Windows)


Support:

The project homepage which contains the latest downloads and
documentation is at http://www.terryburton.co.uk/barcodewriter/

The project mailing list archive is at
http://groups.google.co.uk/group/postscriptbarcode

There is an online demonstration of the project available via
the web-based front-end at 
http://www.terryburton.co.uk/barcodewriter/generator/


License:

Anybody is free to use and develop this code as they see fit, 
under the terms of the permissive MIT/X-Consortium License. 
As such the author takes no liability for its use or misuse.

If you make any improvements please send them to the mailing
list so that the mainline code may be improved.