Free postscript printer software for linux

Prima::Printer is a system printing services.

SYNOPSIS

my $printer = $::application-> get_printer;
print "printing to ", $printer->printer, "...n";
$p-> options( Orientation => Landscape, PaperSize => A4);
if ( $p-> begin_doc) {
$p-> bar( 0, 0, 100, 100);
print "another page...n";
$p-> new_page;
$p-> ellipse( 100, 100, 200, 200);
(time % 1) ? # depending on the moon phase, print it or cancel out
$p-> end_doc :
$p-> abort_doc;
} else {
print "failedn";
}

Prima::Printer is a descendant of Prima::Drawable class. It provides access to the system printing services, where available. If the system provides no graphics printing, the default PostScript (tm) interface module Prima::PS::Printer is used instead.

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.

system-config-printer purpose is to configure a CUPS server (often the local machine) using the CUPS API. The tool is written in Python, using pygtk for the graphical parts and with some Python bindings (pycups) for the CUPS API.
It is largely the same as using the CUPS web interface for configuring printers, but has the advantage of being a native application rather than a web page. It appears in the Fedora menu under System -> Administration -> Printing.
As a result of using the CUPS API the tool is able to configure remote CUPS instances and is not limited to configuring CUPS on the local machine. The CUPS library providing the API uses HTTP and IPP to communicate with the CUPS server.
Enhancements:
- Several improvements for the new-printer wizard have been made, and assorted bugs have been fixed.

CAD::Drawing::IO::PostScript is a Perl module with PostScript output methods.

I would like this module to both load and save PostScript vector graphics, but I have not yet found a suitable PostScript parsing package.

This module should be considered pre-ALPHA and untested. Some features rely on the authors hacks to PostScript::Simple, which may or may not have been incorporated into the CPAN distribution of PostScript::Simple. For bleeding-edge code, see http://ericwilhelm.homeip.net.

Requisite Plug-in Functions

See CAD::Drawing::IO for a description of the plug-in architecture.

check_type

Returns true if $type is "circ" or $filename is a directory containing a ".circ" file.

$fact = check_type($filename, $type);

Methods

load

load();

save

$drw->save($filename, %opts);

PostScript::Simple::setpscolor

PostScript::Simple::setpscolor();

TurboPrint is a high-quality printer driver system for Linux built on existing standards (e.g. ghostscript). It is designed to produce maximum quality photo printouts as well as high-speed text documents.

TurboPrint provides printer drivers for almost every inkjet printer, e.g. Canon BJC / S, Epson Stylus Color & Photo, HP DeskJet. All printer features are supported. TurboPrint comes with its own color matching system "TrueMatch".

High quality color profiles ensure optimum color reproduction on all print media (glossy paper, inkjet paper, ...). A comfortable GUI configuration menu and a printer toolbox (head cleaning, alignment, ink quantity) are included.

TurboPrint can be easily integrated into the CUPS printing system. The FreeEdition of TurboPrint can be obtained free of charge. It contains almost the full functionality.

pstoedit program converts Postscript and PDF files to other vector graphic formats so that they can be edited graphically.
Supported Formats
Currently pstoedit can generate the following major formats:
- Tgif .obj format (for tgif version >= 3)
- .fig format for xfig
- pdf - Adobes Portable Document Format
- gnuplot format
- Flattened PostScript (with or without Bezier curves)
- DXF - CAD exchange format
- LWO - LightWave 3D
- RIB - RenderMan
- RPL - Real3D
- Java 1 or Java 2 applet
- Idraw format (in fact a special form of EPS that idraw can read)
- Tcl/Tk
- HPGL
- AI (Adobe Illustrator) (based on ps2ai.ps - not a real pstoedit driver - see notes below and manual)
- Windows Meta Files (WMF) (Windows 9x/NT only)
- Enhanced Windows Meta Files (EMF) (Windows 9x/NT only)
- OS/2 meta files (OS/2 only)
- PIC format for troff/groff
- MetaPost format for usage with TeX/LaTeX
- LaTeX2e picture
- Kontour
- GNU Metafile (plotutils / libplot)
- Skencil( http://www.skencil.org )
- Mathematica
- via ImageMagick to any format supported by ImageMagick
- SWF
Enhancements:
- Several usability improvements were introduced.
- Secure versions of several functions are used where possible.
- The code was cleaned up and a driver was included for the OpenOffice metafile format.