Free definition of postscript software for linux

Barcode Writer in Pure Postscript is an award-winning open source project, as used by NASA, that facilitates the printing of all major barcode symbologies entirely within level 2 PostScript.
Hence the process of generating a printed barcode representing a given input is performed entirely within the printer (or print system) so that it is no longer the responsibility of your application or a library.
There is no need for any barcode fonts and the flexibility gained by using direct PostScript allows you to avoid re-implementing barcode generator code, or migrating to new libraries, whenever your project language needs change.
Barcode Writer in Pure Postscript project makes including any barcode within a PostScript document as simple as inserting the following directive:
(1-86074-271) (includetext) isbn barcode
The project generates all of the major types of one-dimensional barcode supported by the vast majority of barcode scanners.
The current list of supported symbologies includes: EAN-13, EAN-8, UPC-A, UPC-E, EAN-5 & EAN-2 (EAN/UPC add-ons), ISBN (including ISBN-13), Code 128 (A, B & C, including EAN-128), Code 39 Extended, Code 93 Extended, Interleaved 2 of 5 (including ITF-14), Code 2 of 5, Codabar, MSI, Plessey, PostNet, Royal Mail (RM4SCC), FIM symbols.
This list is growing all the time. If it doesnt contain the format you are looking for then make a request via the mailing list and check back soon.
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, for example Windows 95/XP on i386, Mac OS X/Linux on Power PC, Solaris on SPARC, and OpenVMS on Alpha AXP.
Enhancements:
- Support for the MaxiCode 2D barcode was added.

PostScript::File is a Perl base class for creating Adobe PostScript files.

SYNOPSIS

use PostScript::File qw(check_tilde check_file
incpage_label incpage_roman);

Simplest

An hello world program:
use PostScript::File;

my $ps = new PostScript::File();

$ps->add_to_page( Letter,
height => 500,
width => 400,
bottom => 30,
top => 30,
left => 30,
right => 30,
clip_command => stroke,
clipping => 1,
eps => 1,
dir => ~/foo,
file => "bar",
landscape => 0,

headings => 1,
reencode => ISOLatin1Encoding,
font_suffix => -iso,

errors => 1,
errmsg => Failed:,
errfont => Helvetica,
errsize => 12,
errx => 72,
erry => 300,

debug => 2,
db_active => 1,
db_xgap => 120,
db_xtab => 8,
db_base => 300,
db_ytop => 500,
db_color => 1 0 0 setrgbcolor,
db_font => Times-Roman,
db_fontsize => 11,
db_bufsize => 256,
);

PostScript::MailLabels are modules for creating PostScript files of mailing address labels.
Flexible enough to tackle other printing tasks, basically anything requiring a set fields be printed on a regular grid. Also creates PostScript(tm) code for calibrating and testing mailing label printing.
The module has three distinct output modes. In my experience, printing mailing labels is a matter of tweaking parameters to get them all to fit properly on the page. This module is designed with this in mind.
The first output is the calibration sheet. This is a pair of annotated axes, either in inches or centimeters, centered on the page and covering the whole page in X and Y directions. The intent is for you to output this page first, and simply read off the relevant page dimensions directly.
The second output is the label test. This output is a series of boxes drawn on the page, meant to outline the edges of all the mailing labels. Take this sheet and line it up with a sheet of labels to see if they actually match perfectly. If not, tweak the parameters until they do. Note that sometimes you will get a message at the bottom of the sheet saying ``Bottom gap too large, last row cannot be printed.
This means that the printable area of your printer is too small to utilize the last row of labels. I have this problem. But I handle it for you. Note also the arrows on the test sheet. As you hold the test sheet over a sheet of labels, hold it up to the light and slide the test sheet so that the boxes match the edges of the labels. If you slide in the arrow direction, that is a positive adjustment.
The other direction is negative. If the edges of some boxes come out dashed, that means that the non-printing border cuts off the end of the label, so I will adjust the printing area appropriately. Dont try to line up the dashed lines with label edges - it wont work. Just line up the solid lines.
The third output is the labels themselves. By default, I have set up a US-centric address definition :
firstname, lastname, street address, city, state, zipcode
But with version 2.0, you can now create your own definition. You can define new fields, and you can define how those fields land on a label. You can also control the fonts on a per-field basis. Not the size, yet - later pilgrim.
Parameters you can set :
Paper size, orientation, borders on the printable area (many printers will not print right up to the edge of the paper), where the labels live on the page and how big they are, overall x-y shift of page, whether or not to print PostNET barcode, font, fontsize, units (english or metric), which Avery(tm) product code to use, and where the first label starts.
This last needs explanation. If you have a partially used sheet of labels, you might want to use it up. So you count the missing labels, starting at the upper left, and counting across, and then down. For example, if I have 3 columns of labels, label five is the second label in the second row.
If you have an Avery(tm) product that I havent defined, send me the specs and Ill add it.
Also, if there is another brand of labels that you use, send me the relevant data and Ill add that as well. I suspect that there must be some other vendor in Europe, but I dont know who that would be.
When setting up the addresses, I check to see if they will fit on the label. If not, I try to shorten them semi-intelligently until they fit. This part could use quite a bit more work, if done right it probably merits a module all its own.
Briefly, for the name line, I start trimming the ends off the first name, and leave the last name alone.
For the street, I look for things like Road or Avenue and nuke those first, then I trim the street name from the right.
Enhancements:
- Parentheses are now escaped in the generated PostScript code.