[ < ]
[
#SEC2
>
]
[ << ]
[ Up ]
[
#SEC6
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
1. Introduction
This document describes GNU a2psversions may be found on the
http://www.inf.enst.fr/~demaille/a2ps
a2ps
We tried to make this document informative and pleasant. It tries to be more than a plain reference guide
not
because a2psdifficult to use. See section
#SEC148
Glossary
, for technical words or even general information.
Please
or if you just like a2ps@c, write to
mailto:Miguel.Santana@st.com
Miguel Santana
and
mailto:akim@freefriends.org
Akim Demaille
.
#SEC2
1.1 Description
What a2ps is
#SEC3
1.2 Reporting Bugs
What to do when you face problems
#SEC4
1.3 a2ps
Getting news about a2ps
#SEC5
1.4 Helping the Development
How to contribute
[
#SEC1
<
]
[
#SEC3
>
]
[
#SEC1
<<
]
[
#SEC1
Up
]
[
#SEC6
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
1.1 Description
a2ps
a2ps
The format used is nice and compact: normally two pages on each physical page
headers with useful information (page number, printing date, file name or supplied header), line numbering, pretty-printing, symbol substitution etc. This is very useful for making archive listings of programs or just to check your code in the bus. Actually a2psprinted with a2ps
While at the origin its names was derived from ``ASCII to PostScript''
a2pssupports
delegations
, i.e., you can safely use a2psPostScript, LaTeX, JPEG etc., even compressed.
A short list of features of a2ps
A short list of features of a2ps
-
Customizable through various configuration files (see section <a href=
Configuration Files
)">Customizable through various configuration files (see section
#SEC34
Configuration Files
)
-
Powerful escapes to define the headers
table of contents etc. the way you want (see section
#SEC30
Escapes
);
-
Variables to push even further the customizability in a comfortable manner (see section <a href=
Your Variables
);">Variables to push even further the customizability in a comfortable manner (see section
#SEC43
Your Variables
);
-
Open approach of encodings (see section <a href=
Encodings
);">Open approach of encodings (see section
#SEC59
Encodings
);
-
Excellent support of the Latin 2
4, 5 and 6 encodings, thanks to
Ogonkify
(see
ogonkify.html#Top
(ogonkify)top
section `Overview' in
Ogonkify manual
), written by Juliusz Chroboczek.
-
Fully customizable output style: fonts
line numbering style etc. (see section
#SEC109
Designing PostScript Prologues
).
-
Possibility to delegate the processing of some files to other filters (see section <a href=
Your Delegations
).">Possibility to delegate the processing of some files to other filters (see section
#SEC46
Your Delegations
).
-
Many contributions
pretty-print diffs, print reference cards of programs, sanitize broken PostScript files, print Duplex on Simplex printers etc. (see section
#SEC113
Contributions
).
-
And finally
the ability to pretty-print sources written in quite a few various languages (see section
#SEC65
Pretty Printing
).
[
#SEC2
<
]
[
#SEC4
>
]
[
#SEC1
<<
]
[
#SEC1
Up
]
[
#SEC6
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
1.2 Reporting Bugs
We try hard to make a2psBut sometimes there can still be bad surprises
even after having compiled and checked a2ps
You may encounter some of these problems yourself. In any case
please never abandon without giving us a chance. We need information from everybody so that mistakes get fixed as fast as possible.
So
compilation error, runtime error, documentation error or unclear), first check in the FAQ (see section
#SEC127
Frequently asked questions
), then on the page
http://www.inf.enst.fr/~demaille/a2ps/bugs.html
but it appears that the version of a2psconsider upgrading.
<a href=
the version of a2ps@c, every detail you have on your compiler, and as much traces as possible (the error messages you get on the screen, or the output of
make
when it fails etc.).
">
If the problem persists
the version of a2ps@c, every detail you have on your compiler, and as much traces as possible (the error messages you get on the screen, or the output of
make
when it fails etc.).
<a href=
Be sure to get a quick answer.
">
Be sure to get a quick answer.
Be sure to get a quick answer.
[
#SEC3
<
]
[
#SEC5
>
]
[
#SEC1
<<
]
[
#SEC1
Up
]
[
#SEC6
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
1.3 a2ps
<a href=
mailto:a2ps@gnu.org
a2ps@gnu.org
. There are also announcements about the version in alpha testing">new sheets, etc.
">
There is a mailing list in which are discussed various topics around a2ps@c: <a href=
a2ps@gnu.org
. There are also announcements about the version in alpha testing">new sheets, etc.
<a href=
with
`subscribe'
in the body.
">
To subscribe to the list
with
`subscribe'
in the body.
<a href=
note that the mailing list is by no means a bug reporting address: use
mailto:bug-a2ps@gnu.org
bug-a2ps@gnu.org
instead.
">
Please
note that the mailing list is by no means a bug reporting address: use
mailto:bug-a2ps@gnu.org
bug-a2ps@gnu.org
instead.
[
#SEC4
<
]
[
#SEC6
>
]
[
#SEC1
<<
]
[
#SEC1
Up
]
[
#SEC6
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
1.4 Helping the Development
<a href=
If you like a2psyou can do.
">
If you like a2psyou can do.
If you like a2psyou can do.
Testing
<a href=
in general the last weeks before a release are mostly dedicated to (Unix) portability issues.
">
You just can't imagine how hard it is to make sure that the program that works perfectly here will work on your machine. Actually
in general the last weeks before a release are mostly dedicated to (Unix) portability issues.
<a href=
need
beta-testers! To be one is fairly simple: subscribe to the mailing-list where the betas are announced and distributed.">So we
need
beta-testers! To be one is fairly simple: subscribe to the mailing-list where the betas are announced and distributed.
">
So we <strong>need</strong> beta-testers! To be one is fairly simple: subscribe to the mailing-list where the betas are announced and distributed.
So we
need
beta-testers! To be one is fairly simple: subscribe to the mailing-list where the betas are announced and distributed.
Translation
<a href=
without having to look at the code of a2ps@c: you don't need to be a programmer at all. All the details are available on
http://www.inf.enst.fr/~demaille/a2ps/po/
the a2ps translation page
.
">
The interface of a2psthe messages can be translated
without having to look at the code of a2ps@c: you don't need to be a programmer at all. All the details are available on
http://www.inf.enst.fr/~demaille/a2ps/po/
the a2ps translation page
.
Style Sheets
<a href=
improve the style sheet! (see section
#SEC65
Pretty Printing
for details.)
">
Since a2psshould be checked and improved. There are too many so that the authors work on them. Therefore if you feel your favorite language is not honored as it should be
improve the style sheet! (see section
#SEC65
Pretty Printing
for details.)
Encodings
<a href=
to know more).
">
a2pstoday by a2ps@c, you can easily provide the support yourself. Honestly
to know more).
Fonts
<a href=
http://www.dcs.ed.ac.uk/home/jec/ogonkify/missing.html
the list of missing characters
and
http://www.dcs.ed.ac.uk/home/jec/ogonkify/
the Ogonkify home page
for details.">There are still some characters missing in Ogonkify. See
http://www.dcs.ed.ac.uk/home/jec/ogonkify/missing.html
the list of missing characters
and
http://www.dcs.ed.ac.uk/home/jec/ogonkify/
the Ogonkify home page
for details.
">
There are still some characters missing in Ogonkify. See <a href=
the list of missing characters
and
http://www.dcs.ed.ac.uk/home/jec/ogonkify/
the Ogonkify home page
for details.">There are still some characters missing in Ogonkify. See
http://www.dcs.ed.ac.uk/home/jec/ogonkify/missing.html
the list of missing characters
and
http://www.dcs.ed.ac.uk/home/jec/ogonkify/
the Ogonkify home page
for details.
Documentation
<a href=
send us your contributions.
">
If you feel something is missing or is unclear
send us your contributions.
Porting
<a href=
or building special packages (e.g., RPM) requires having an access to these architectures. If you feel like maintaining such a port, tell us.
">
Porting a program to special architectures (MS-DOS
or building special packages (e.g., RPM) requires having an access to these architectures. If you feel like maintaining such a port, tell us.
Features
<a href=
go ahead! But contact us, because we have quite a big stack of things we want to do or have started to do, and synchronizing might be useful.
">
Well
go ahead! But contact us, because we have quite a big stack of things we want to do or have started to do, and synchronizing might be useful.
[
#SEC5
<
]
[
#SEC7
>
]
[
#SEC1
<<
]
[
#SEC1
Up
]
[
#SEC19
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
2. User's Guide
<a href=
see
#SEC148
Glossary
, for questions you have, see
#SEC127
Frequently asked questions
.
">
This chapter is devoted to people who don't know a2psgive a soft and smooth introduction to the most useful features. For a reference manual
see
#SEC148
Glossary
, for questions you have, see
#SEC127
Frequently asked questions
.
#SEC7
2.1 Purpose
What a2ps is made for
#SEC8
2.2 How to print
The basis
#SEC14
2.3 Important parameters
What needs to be set
#SEC15
2.4 Localizing
How to have a2ps speaking your language
#SEC16
2.5 Interfacing with Other Programs
Using a2ps from common programs
[
#SEC6
<
]
[
#SEC8
>
]
[
#SEC6
<<
]
[
#SEC6
Up
]
[
#SEC19
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
2.1 Purpose
<a href=
a2psand makes a PostScript file out of it. Typically output is sent to a printer.
">
a2psand makes a PostScript file out of it. Typically output is sent to a printer.
a2psand makes a PostScript file out of it. Typically output is sent to a printer.
[
#SEC7
<
]
[
#SEC9
>
]
[
#SEC6
<<
]
[
#SEC6
Up
]
[
#SEC19
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
2.2 How to print
<a href=
`doc.txt'
">just give it to a2ps@c: the default setting should be the one you'd like:
">
To print a file <tt>`doc.txt'</tt>
just give it to a2ps@c: the default setting should be the one you'd like:
<a href=
gargantua ~ $ a2ps doc.txt [doc.txt (plain): 9 pages on 5 sheets] [Total: 9 pages on 5 sheets] sent to the default printer
">
gargantua ~ $ a2ps doc.txt [doc.txt (plain): 9 pages on 5 sheets] [Total: 9 pages on 5 sheets] sent to the default printer
gargantua ~ $ a2ps doc.txt [doc.txt (plain): 9 pages on 5 sheets] [Total: 9 pages on 5 sheets] sent to the default printer
<a href=
by default a2ps
">
a2pstwo columns of text on a single face of the sheet. Indeed
by default a2ps
#SEC9
2.2.1 Basics for Printing
Printing text files
#SEC10
2.2.2 Special Printers
Some useful fake printers
#SEC11
2.2.3 Using Delegations
Printing special files (PS, DVI etc.)
#SEC12
2.2.4 Printing Duplex
Doing Fancy Things
#SEC13
2.2.5 Checking the Defaults
Is it set the way you want?
[
#SEC8
<
]
[
#SEC10
>
]
[
#SEC6
<<
]
[
#SEC8
Up
]
[
#SEC19
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
2.2.1 Basics for Printing
<a href=
`bar.c'
">on 4 virtual pages, and save it into the file
`foobar.ps'
. Just hit:
">
Say you want to print the C file <tt>`bar.c'</tt>
on 4 virtual pages, and save it into the file
`foobar.ps'
. Just hit:
<a href=
gargantua $ a2ps foo.h bar.c -4 -o foobar.ps [foo.h (C): 1 page on 1 sheet] [bar.c (C): 3 pages on 1 sheet] [Total: 4 pages on 2 sheets] saved into the file `foobar.ps'
">
gargantua $ a2ps foo.h bar.c -4 -o foobar.ps [foo.h (C): 1 page on 1 sheet] [bar.c (C): 3 pages on 1 sheet] [Total: 4 pages on 2 sheets] saved into the file `foobar.ps'
gargantua $ a2ps foo.h bar.c -4 -o foobar.ps [foo.h (C): 1 page on 1 sheet] [bar.c (C): 3 pages on 1 sheet] [Total: 4 pages on 2 sheets] saved into the file `foobar.ps'
<a href=
`-4'
tells a2pstwo columns. The option
`-o foobar.ps'
(which is the short version of
`--output=foobar.ps'
) specifies the output file. Long options must always be separated by spaces">though short options with no arguments may be grouped.
">
The option <samp>`-4'</samp> tells a2pstwo columns. The option <samp>`-o foobar.ps'</samp> (which is the short version of <samp>`--output=foobar.ps'</samp>) specifies the output file. Long options must always be separated by spaces
though short options with no arguments may be grouped.
<a href=
it does not matter.
">
Note too that the options may be specified before or after the files
it does not matter.
<a href=
`foobar.ps'
to a printer">that the strings and comments have a different face. Indeed, a2ps(programming) language in which your file is written, it will try to make it look nice and clear on the paper.
">
If you send <tt>`foobar.ps'</tt> to a printer
that the strings and comments have a different face. Indeed, a2ps(programming) language in which your file is written, it will try to make it look nice and clear on the paper.
<a href=
`foo.h'
is only one virtual page long">the comments are essential in those files. And even worse: the system's default printer is out of ink. Thanks god, precious options may help you:
">
But too bad: <tt>`foo.h'</tt> is only one virtual page long
the comments are essential in those files. And even worse: the system's default printer is out of ink. Thanks god, precious options may help you:
<a href=
gargantua $ a2ps -4 -Av foo.h bar.c --prologue=gray -P lw [foo.h (C): 1 page on 1 sheet] [bar.c (C): 3 pages on 1 sheet] [Total: 4 pages on 1 sheet] sent to the printer `lw'
">
gargantua $ a2ps -4 -Av foo.h bar.c --prologue=gray -P lw [foo.h (C): 1 page on 1 sheet] [bar.c (C): 3 pages on 1 sheet] [Total: 4 pages on 1 sheet] sent to the printer `lw'
gargantua $ a2ps -4 -Av foo.h bar.c --prologue=gray -P lw [foo.h (C): 1 page on 1 sheet] [bar.c (C): 3 pages on 1 sheet] [Total: 4 pages on 1 sheet] sent to the printer `lw'
<a href=
`-A'
is a short cut for the option
`--file-align'
which specifies how different files should be separated. This option allows several symbolic arguments:
`virtual'
">
`page'
,
`sheet'
(See section
#SEC23
Sheet Options
, for more details). The value
`virtual'
means not to start each file on a different virtual pages.
">
Here the option <samp>`-A'</samp> is a short cut for the option <samp>`--file-align'</samp> which specifies how different files should be separated. This option allows several symbolic arguments: <samp>`virtual'</samp>
`page'
,
`sheet'
(See section
#SEC23
Sheet Options
, for more details). The value
`virtual'
means not to start each file on a different virtual pages.
<a href=
`--file-align=virtual'
">so here, you can just use
`-Av'
.
">
So to fill the page is asked by <samp>`--file-align=virtual'</samp>
so here, you can just use
`-Av'
.
<a href=
`-P lw'
means to print on the printer named
`lw'
">the long option
`--prologue'
requires the use one of the alternative printing styles. There are other prologues (See section
#SEC26
Input Options
, option
`--prologue'
), and you can even design yours (see section
#SEC109
Designing PostScript Prologues
).
">
The option <samp>`-P lw'</samp> means to print on the printer named <samp>`lw'</samp>
the long option
`--prologue'
requires the use one of the alternative printing styles. There are other prologues (See section
#SEC26
Input Options
, option
`--prologue'
), and you can even design yours (see section
#SEC109
Designing PostScript Prologues
).
[
#SEC9
<
]
[
#SEC11
>
]
[
#SEC6
<<
]
[
#SEC8
Up
]
[
#SEC19
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
2.2.2 Special Printers
<a href=
There are three special printers pre-defined.
">
There are three special printers pre-defined.
There are three special printers pre-defined.
<a href=
sends the output to the trash. Its main use is to see how many pages would have been used.
">
The first one
sends the output to the trash. Its main use is to see how many pages would have been used.
<a href=
gargantua ~ $ a2ps -P void parsessh.c [parsessh.c (C): 33 pages on 17 sheets] [Total: 33 pages on 17 sheets] sent to the printer `void'
">
gargantua ~ $ a2ps -P void parsessh.c [parsessh.c (C): 33 pages on 17 sheets] [Total: 33 pages on 17 sheets] sent to the printer `void'
gargantua ~ $ a2ps -P void parsessh.c [parsessh.c (C): 33 pages on 17 sheets] [Total: 33 pages on 17 sheets] sent to the printer `void'
<a href=
so that you can check the output without printing. Of course if you don't have
Ghostview
, it won't work... And it is up to you to configure another displaying application (see section
#SEC39
Your Printers
).
">
The second
so that you can check the output without printing. Of course if you don't have
Ghostview
, it won't work... And it is up to you to configure another displaying application (see section
#SEC39
Your Printers
).
<a href=
saves into
`foo.ps'
when you print
`foo.c'
).
">
The last
saves into
`foo.ps'
when you print
`foo.c'
).
[
#SEC10
<
]
[
#SEC12
>
]
[
#SEC6
<<
]
[
#SEC8
Up
]
[
#SEC19
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
2.2.3 Using Delegations
<a href=
forget that there are delegations
. Indeed, the interface with the delegations has been designed so that you don't need to be aware that they exist to use them. Do as usual.
">
a2psIn that case it delegates the task to other programs. What you should retain from this
forget that there are delegations
. Indeed, the interface with the delegations has been designed so that you don't need to be aware that they exist to use them. Do as usual.
<a href=
just hit:
">
As an example
just hit:
<a href=
delegated to PsNup): 7 pages on 4 sheets] [Total: 8 pages on 4 sheets] sent to the default printer
">
gargantua ~ $ a2ps article.ps -d [article.ps (ps
delegated to PsNup): 7 pages on 4 sheets] [Total: 8 pages on 4 sheets] sent to the default printer
<a href=
a powerful filter part of the famous
psutils
by Angus Duggan.
">
While honoring your defaults settings
a powerful filter part of the famous
psutils
by Angus Duggan.
<a href=
provided you have all the programs a2ps
">
Suppose now that you want to display a Texinfo file. Then
provided you have all the programs a2ps
<a href=
delegated to texi2dvi): 75 pages on 38 sheets] [Total: 76 pages on 38 sheets] sent to the printer `display'
">
gargantua ~ $ a2ps a2ps.texi -P display [a2ps.texi (texinfo
delegated to texi2dvi): 75 pages on 38 sheets] [Total: 76 pages on 38 sheets] sent to the printer `display'
<a href=
plus the cover. Just hit:
">
Once the read documentation
plus the cover. Just hit:
<a href=
delegated to texi2dvi): 13 pages on 7 sheets] [Total: 14 pages on 7 sheets] sent to the default printer
">
gargantua ~ $ a2ps a2ps.texi --pages=1
delegated to texi2dvi): 13 pages on 7 sheets] [Total: 14 pages on 7 sheets] sent to the default printer
<a href=
A final word: compressed files can be treated in the very same way:
">
A final word: compressed files can be treated in the very same way:
A final word: compressed files can be treated in the very same way:
<a href=
delegated to Gzip-a2ps): 13 pages on 7 sheets] [Total: 14 pages on 7 sheets] sent to the default printer
">
gargantua ~ $ a2ps a2ps.texi.gz -a1
delegated to Gzip-a2ps): 13 pages on 7 sheets] [Total: 14 pages on 7 sheets] sent to the default printer
<a href=
You should be aware that:
">
You should be aware that:
You should be aware that:
-
<a href=
`-Z'
enables the delegations if they are not (see
`--list=defaults'
for your settings);">the option
`-Z'
enables the delegations if they are not (see
`--list=defaults'
for your settings);
">
the option <samp>`-Z'</samp> enables the delegations if they are not (see <samp>`--list=defaults'</samp> for your settings);
the option
`-Z'
enables the delegations if they are not (see
`--list=defaults'
for your settings);
-
<a href=
to know the delegations your a2ps
">
the set of delegations is customizable
to know the delegations your a2ps
[
#SEC11
<
]
[
#SEC13
>
]
[
#SEC6
<<
]
[
#SEC8
Up
]
[
#SEC19
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
2.2.4 Printing Duplex
<a href=
a2ps(See section
#SEC148
Glossary
, for definitions). The option to specify Duplex printing is
`--sides=
mode
'
(see section
#SEC29
PostScript Options
).
">
If you still want to save more paper
a2ps(See section
#SEC148
Glossary
, for definitions). The option to specify Duplex printing is
`--sides=
mode
'
(see section
#SEC29
PostScript Options
).
<a href=
`margot'
:">Here is how to print the documentation in Duplex and send it to the Duplex printer
`margot'
:
">
Here is how to print the documentation in Duplex and send it to the Duplex printer <samp>`margot'</samp>:
Here is how to print the documentation in Duplex and send it to the Duplex printer
`margot'
:
<a href=
delegated to texi2dvi): 109 pages on 28 sheets] [Total: 110 pages on 28 sheets] sent to the printer `margot'
">
quasimodo ~ a2ps/doc $ a2ps -s2 -Pmargot a2ps.texi [a2ps.texi (texinfo
delegated to texi2dvi): 109 pages on 28 sheets] [Total: 110 pages on 28 sheets] sent to the printer `margot'
<a href=
This is also valid for several files.
">
This is also valid for several files.
This is also valid for several files.
<a href=
because the pages needs to be completely reorganized another way. This is precisely the job of
psbook
, yet another PsUtil from Angus Duggan. But there is a user option which encapsulates the magic sequence of options:
`book'
. Therefore, just run
">
Actually
because the pages needs to be completely reorganized another way. This is precisely the job of
psbook
, yet another PsUtil from Angus Duggan. But there is a user option which encapsulates the magic sequence of options:
`book'
. Therefore, just run
<a href=
delegated to texi2dvi): 109 pages on 109 sheets] [Total: 109 pages on 109 sheets] sent to the printer `margot'
">
quasimodo a2ps/doc $ a2ps -=book -Pmargot a2ps.texi [a2ps.texi (texinfo
delegated to texi2dvi): 109 pages on 109 sheets] [Total: 109 pages on 109 sheets] sent to the printer `margot'
<a href=
voila` !
">a booklet printed on margot!
">
and <i>voila` !</i>
a booklet printed on margot!
<a href=
after all, the result will be exactly the same once you collated all the booklets together.
">
We strongly discourage you to try with several files at once
after all, the result will be exactly the same once you collated all the booklets together.
<a href=
Another limitation is that this does not work if it is not sent to a printer. This kind of weird limitations will be solved in the future.
">
Another limitation is that this does not work if it is not sent to a printer. This kind of weird limitations will be solved in the future.
Another limitation is that this does not work if it is not sent to a printer. This kind of weird limitations will be solved in the future.
[
#SEC12
<
]
[
#SEC14
>
]
[
#SEC6
<<
]
[
#SEC8
Up
]
[
#SEC19
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
2.2.5 Checking the Defaults
<a href=
If a2psthe default settings given by your system administrator. Checking those default values is easy:
">
If a2psthe default settings given by your system administrator. Checking those default values is easy:
If a2psthe default settings given by your system administrator. Checking those default values is easy:
<a href=
rows first borders = yes file alignment = page interior margin = 0
More stuff deleted here
Internals: ---------- verbosity level = 2 file command = /usr/bin/file -L temporary directory = /tmp library path = /home/akim/.a2ps /usr/share/a2ps/sheets /usr/share/a2ps/ps /usr/share/a2ps/encoding /usr/share/a2ps/afm /usr/share/ogonkify/afm /usr/share/a2ps/ppd /usr/share/a2ps/fonts /usr/share/ogonkify/fonts /usr/share/a2ps
">
~ % a2ps --list=defaults Configuration status of a2ps 4.12a ================================== Sheets: ------- medium = A4
rows first borders = yes file alignment = page interior margin = 0
More stuff deleted here
Internals: ---------- verbosity level = 2 file command = /usr/bin/file -L temporary directory = /tmp library path = /home/akim/.a2ps /usr/share/a2ps/sheets /usr/share/a2ps/ps /usr/share/a2ps/encoding /usr/share/a2ps/afm /usr/share/ogonkify/afm /usr/share/a2ps/ppd /usr/share/a2ps/fonts /usr/share/ogonkify/fonts /usr/share/a2ps
<a href=
you may
pipe
it into
more
. Just trust this:
">
Remember that the on-line help is always available. Moreover
you may
pipe
it into
more
. Just trust this:
<a href=
a2ps --help | more
">
a2ps --help | more
a2ps --help | more
[
#SEC13
<
]
[
#SEC15
>
]
[
#SEC6
<<
]
[
#SEC6
Up
]
[
#SEC19
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
2.3 Important parameters
<a href=
Many things are parameterizable in a2ps@c, but two things are just essential to make sure everything goes right:
">
Many things are parameterizable in a2ps@c, but two things are just essential to make sure everything goes right:
Many things are parameterizable in a2ps@c, but two things are just essential to make sure everything goes right:
The paper
<a href=
#SEC23
Sheet Options
">option
`--medium'
).
">
Make sure that the paper a2ps(See section <a href=
Sheet Options
">option
`--medium'
).
The encoding
<a href=
encoding
a2psstandard alphabet in your country (See section
#SEC26
Input Options
">option
`--encoding'
).
">
Make sure that the <em>encoding</em> a2psstandard alphabet in your country (See section <a href=
Input Options
">option
`--encoding'
).
<a href=
`a2ps --list=defaults'
.">Both values may be checked with
`a2ps --list=defaults'
.
">
Both values may be checked with <samp>`a2ps --list=defaults'</samp>.
Both values may be checked with
`a2ps --list=defaults'
.
[
#SEC14
<
]
[
#SEC16
>
]
[
#SEC6
<<
]
[
#SEC6
Up
]
[
#SEC19
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
2.4 Localizing
<a href=
a2psmother tongue. It uses three special features for non-English languages:
">
a2psmother tongue. It uses three special features for non-English languages:
a2psmother tongue. It uses three special features for non-English languages:
the tongue
<a href=
the language used by the interface
">
i.e.
the language used by the interface
the date
<a href=
the format and the words used in the language to specify a date.
">
i.e.
the format and the words used in the language to specify a date.
<a href=
for instance
`man locale'
,
`man environ'
etc.).
">
To enable these features
for instance
`man locale'
,
`man environ'
etc.).
<a href=
what may cause problems with
awk
and such.
">
The problem with this approach is that a lot more than just messages and time information is affected: especially the way numbers are written changes
what may cause problems with
awk
and such.
<a href=
then define:
">
So if you just want messages and time format to be localized
then define:
<a href=
set LC_MESSAGES=fr ; export LC_MESSAGES set LC_TIME=fr ; export LC_TIME
">
set LC_MESSAGES=fr ; export LC_MESSAGES set LC_TIME=fr ; export LC_TIME
set LC_MESSAGES=fr ; export LC_MESSAGES set LC_TIME=fr ; export LC_TIME
[
#SEC15
<
]
[
#SEC17
>
]
[
#SEC6
<<
]
[
#SEC6
Up
]
[
#SEC19
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
2.5 Interfacing with Other Programs
<a href=
Here are some tips on how to use a2ps
">
Here are some tips on how to use a2ps
Here are some tips on how to use a2ps
#SEC17
2.5.1 Interfacing With a Mailer
Printing Mails or News
#SEC18
2.5.2 Netscape
Interfacing with Netscape
[
#SEC16
<
]
[
#SEC18
>
]
[
#SEC6
<<
]
[
#SEC16
Up
]
[
#SEC19
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
2.5.1 Interfacing With a Mailer
<a href=
say a2psa2psbetter results, make sure to tell a2psoption
`mail'
(or
`longmail'
for longer inputs) encapsulates most typical tuning users want to print mails (for instance, don't print all the headers).
">
When you print from a mailer (or a news reader)
say a2psa2psbetter results, make sure to tell a2psoption
`mail'
(or
`longmail'
for longer inputs) encapsulates most typical tuning users want to print mails (for instance, don't print all the headers).
<a href=
if your mailer is:
">
Most specifically
if your mailer is:
elm
<a href=
hit
p
to edit the printer command, and enter
`a2ps -=mail %s -d'
. The option
`-d'
means to print on the default printer.
">
Once you are in elm
hit
p
to edit the printer command, and enter
`a2ps -=mail %s -d'
. The option
`-d'
means to print on the default printer.
pine
<a href=
mailto:jan@chrillesen.dk
Jan Chrillesen
suggests us how to use a2pswith the Pine mail-reader. Add the following to
`.pinerc'
(of course you can put it in
`pine.conf'
as well):">
mailto:jan@chrillesen.dk
Jan Chrillesen
suggests us how to use a2pswith the Pine mail-reader. Add the following to
`.pinerc'
(of course you can put it in
`pine.conf'
as well):
">
<a href=
Jan Chrillesen
suggests us how to use a2pswith the Pine mail-reader. Add the following to
`.pinerc'
(of course you can put it in
`pine.conf'
as well):">
mailto:jan@chrillesen.dk
Jan Chrillesen
suggests us how to use a2pswith the Pine mail-reader. Add the following to
`.pinerc'
(of course you can put it in
`pine.conf'
as well):
<a href=
# Your printer selection printer=a2ps -=mail -d # Special print command personal-print-command=a2ps -=mail -d
">
# Your printer selection printer=a2ps -=mail -d # Special print command personal-print-command=a2ps -=mail -d
# Your printer selection printer=a2ps -=mail -d # Special print command personal-print-command=a2ps -=mail -d
[
#SEC17
<
]
[
#SEC19
>
]
[
#SEC6
<<
]
[
#SEC16
Up
]
[
#SEC19
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
2.5.2 Netscape
<a href=
This is actually valid for any program that generates PostScript that you want to post-process with a2ps@c. Use the following command:
">
This is actually valid for any program that generates PostScript that you want to post-process with a2ps@c. Use the following command:
This is actually valid for any program that generates PostScript that you want to post-process with a2ps@c. Use the following command:
<a href=
a2ps
">
a2ps
a2ps
<a href=
isn't it?
">
Not too hard
isn't it?
<a href=
your
file(1)
detects correctly PostScript files, and your a2psdelegate. In case one one these conditions is not met, use:
">
Nevertheless
your
file(1)
detects correctly PostScript files, and your a2psdelegate. In case one one these conditions is not met, use:
<a href=
a2ps -ZEps
">
a2ps -ZEps
a2ps -ZEps
<a href=
and the type of paper it uses.
">
Do not forget to tell Netscape whether your printer supports colors
and the type of paper it uses.
[
#SEC18
<
]
[
#SEC20
>
]
[
#SEC6
<<
]
[
#SEC1
Up
]
[
#SEC34
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
3. Invoking a2ps
<a href=
Calling a2ps
">
Calling a2ps
Calling a2ps
<a href=
Options...
Files...
">a2ps
Options...
Files...
">
a2ps <var>Options...</var> <var>Files...</var>
a2ps
Options...
Files...
<a href=
Files...
are given">it designates the standard input too.
">
If no <var>Files...</var> are given
it designates the standard input too.
#SEC20
3.1 Command line options
#SEC30
3.2 Escapes
Strings ready to use in the headers
[
#SEC19
<
]
[
#SEC21
>
]
[
#SEC19
<<
]
[
#SEC19
Up
]
[
#SEC34
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
3.1 Command line options
<a href=
hence:
">
To read the options and arguments that you give
hence:
-
<a href=
the options (short with arguments or long) must be separated by spaces.
">
the options (short with arguments or long) must be separated by spaces.
the options (short with arguments or long) must be separated by spaces.
-
<a href=
`a2ps -4m main.c'
and
`a2ps main.c -4m'
are identical.">the order between options and files does not matter:
`a2ps -4m main.c'
and
`a2ps main.c -4m'
are identical.
">
the order between options and files does not matter: <samp>`a2ps -4m main.c'</samp> and <samp>`a2ps main.c -4m'</samp> are identical.
the order between options and files does not matter:
`a2ps -4m main.c'
and
`a2ps main.c -4m'
are identical.
-
<a href=
does matter
">especially between options that influence the same parameters. For instance
`a2ps -1 -l132'
is not the same as
`a2ps -l132 -1'
(the latter being equivalent to
`a2ps -1'
).
">
the order between options <strong>does matter</strong>
especially between options that influence the same parameters. For instance
`a2ps -1 -l132'
is not the same as
`a2ps -l132 -1'
(the latter being equivalent to
`a2ps -1'
).
-
<a href=
`a2ps -4mg main.c -P printer'
">short options may be grouped together:
`a2ps -4mg main.c -P printer'
">
short options may be grouped together: <samp>`a2ps -4mg main.c -P printer'</samp>
short options may be grouped together:
`a2ps -4mg main.c -P printer'
-
<a href=
e.g.,
`--pro'
will be understood as
`--prologue'
,
">
when there are no ambiguities
e.g.,
`--pro'
will be understood as
`--prologue'
,
-
<a href=
`--'
ends the options. Anything behind
`--'
is considered to be a file:
`a2ps -- -2'
prints the file
`-2'
#FOOT1
(1)
.">
`--'
ends the options. Anything behind
`--'
is considered to be a file:
`a2ps -- -2'
prints the file
`-2'
#FOOT1
(1)
.
">
#FOOT1
(1)
.">
`--'
ends the options. Anything behind
`--'
is considered to be a file:
`a2ps -- -2'
prints the file
`-2'
#FOOT1
(1)
.
<a href=
boolean
is considered as true (i.e. setting the option on)">or
`1'
; as false if it equals
`no'
or
`0'
; and raise an error otherwise. The corresponding short option takes no arguments, but corresponds to a positive answer.
">
Here after a <var>boolean</var> is considered as true (i.e. setting the option on)
or
`1'
; as false if it equals
`no'
or
`0'
; and raise an error otherwise. The corresponding short option takes no arguments, but corresponds to a positive answer.
<a href=
it means that it is optional. Optional arguments to short option must never be separated from the option.
">
When an argument is presented between square brackets
it means that it is optional. Optional arguments to short option must never be separated from the option.
#SEC21
3.1.1 Tasks Options
Exclusive options
#SEC22
3.1.2 Global Options
Settings involving the whole process
#SEC23
3.1.3 Sheet Options
Specify the layout on the sheet
#SEC24
3.1.4 Page Options
Specify the virtual pages
#SEC25
3.1.5 Headings Options
Specify the headers you want
#SEC26
3.1.6 Input Options
How to process the input files
#SEC27
3.1.7 Pretty Printing Options
Source files support
#SEC28
3.1.8 Output Options
What should be done of the output
#SEC29
3.1.9 PostScript Options
PostScript specific options
[
#SEC20
<
]
[
#SEC22
>
]
[
#SEC19
<<
]
[
#SEC20
Up
]
[
#SEC34
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
3.1.1 Tasks Options
<a href=
Task options specify the task a2psit executes the task and exits successfully.
">
Task options specify the task a2psit executes the task and exits successfully.
Task options specify the task a2psit executes the task and exits successfully.
Option:
-
-
version
<a href=
print version and exit successfully.
">
print version and exit successfully.
print version and exit successfully.
Option:
-
-
help
<a href=
and exit successfully.
">
Print a short help
and exit successfully.
Option:
-
-
copyright
<a href=
and exit successfully.
">
Display Copyright and copying conditions
and exit successfully.
Option:
-
-
guess
<a href=
file
does: display the (key of the) type of the
Files
.">Act like
file
does: display the (key of the) type of the
Files
.
">
Act like <code>file</code> does: display the (key of the) type of the <var>Files</var>.
Act like
file
does: display the (key of the) type of the
Files
.
<a href=
you expect it to answer
`c'
, and upon a PostScript file,
`ps'
.
">
For instance
you expect it to answer
`c'
, and upon a PostScript file,
`ps'
.
<a href=
#SEC58
Style Sheet Files
).">This can be very useful on broken systems to understand why a file is printed with a bad style sheet (see section
#SEC58
Style Sheet Files
).
">
This can be very useful on broken systems to understand why a file is printed with a bad style sheet (see section <a href=
Style Sheet Files
).">This can be very useful on broken systems to understand why a file is printed with a bad style sheet (see section
#SEC58
Style Sheet Files
).
Option:
-
-
which
<a href=
Look in the library for the files which names are given as arguments. For instance:
">
Look in the library for the files which names are given as arguments. For instance:
Look in the library for the files which names are given as arguments. For instance:
<a href=
~ % a2ps --which bw.pro gray.pro /usr/local/share/a2ps/ps/bw.pro /usr/local/share/a2ps/ps/gray.pro
">
~ % a2ps --which bw.pro gray.pro /usr/local/share/a2ps/ps/bw.pro /usr/local/share/a2ps/ps/gray.pro
~ % a2ps --which bw.pro gray.pro /usr/local/share/a2ps/ps/bw.pro /usr/local/share/a2ps/ps/gray.pro
<a href=
only the first one is reported: this allows to check which occurrence of a file is used by a2ps@c.
">
If there are several library files matching the name
only the first one is reported: this allows to check which occurrence of a file is used by a2ps@c.
Option:
-
-
glob
<a href=
Look in the library for the files which names match the patterns given as arguments. For instance:
">
Look in the library for the files which names match the patterns given as arguments. For instance:
Look in the library for the files which names match the patterns given as arguments. For instance:
<a href=
~ % a2ps --glob 'g*.pro' /usr/local/share/a2ps/ps/gray.pro /usr/local/share/a2ps/ps/gray2.pro
">
~ % a2ps --glob 'g*.pro' /usr/local/share/a2ps/ps/gray.pro /usr/local/share/a2ps/ps/gray2.pro
~ % a2ps --glob 'g*.pro' /usr/local/share/a2ps/ps/gray.pro /usr/local/share/a2ps/ps/gray2.pro
Option:
-
-
list=
topic
<a href=
topic
">and exit successfully.
topic
can be any non-ambiguous abbreviation of:
">
Display a report on a2ps@c' status with respect to <var>topic</var>
and exit successfully.
topic
can be any non-ambiguous abbreviation of:
`defaults'
`options'
<a href=
Give an extensive report on a2ps
">
Give an extensive report on a2ps
Give an extensive report on a2ps
`features'
<a href=
languages, prologues, printers, variables, delegations and user options are reported. In a word, anything that you may define.
">
Known media
languages, prologues, printers, variables, delegations and user options are reported. In a word, anything that you may define.
`delegations'
<a href=
#SEC46
Your Delegations
.">Detailed list of the delegations. See section
#SEC46
Your Delegations
.
">
Detailed list of the delegations. See section <a href=
Your Delegations
.">Detailed list of the delegations. See section
#SEC46
Your Delegations
.
`encodings'
<a href=
#SEC64
Some Encodings
.">Detailed list of known encodings. See section
#SEC64
Some Encodings
.
">
Detailed list of known encodings. See section <a href=
Some Encodings
.">Detailed list of known encodings. See section
#SEC64
Some Encodings
.
`media'
<a href=
#SEC38
Your Media
.">Detailed list of known media. See section
#SEC38
Your Media
.
">
Detailed list of known media. See section <a href=
Your Media
.">Detailed list of known media. See section
#SEC38
Your Media
.
`prologues'
<a href=
#SEC109
Designing PostScript Prologues
.">Detailed list of PostScript prologues. See section
#SEC109
Designing PostScript Prologues
.
">
Detailed list of PostScript prologues. See section <a href=
Designing PostScript Prologues
.">Detailed list of PostScript prologues. See section
#SEC109
Designing PostScript Prologues
.
`printers'
<a href=
#SEC39
Your Printers
.">Detailed list of printers and named outputs. See section
#SEC39
Your Printers
.
">
Detailed list of printers and named outputs. See section <a href=
Your Printers
.">Detailed list of printers and named outputs. See section
#SEC39
Your Printers
.
`style-sheets'
<a href=
#SEC67
Known Style Sheets
.">Detailed list of the known style sheets. See section
#SEC67
Known Style Sheets
.
">
Detailed list of the known style sheets. See section <a href=
Known Style Sheets
.">Detailed list of the known style sheets. See section
#SEC67
Known Style Sheets
.
`user-options'
<a href=
#SEC40
Your Shortcuts
.">Detailed list of the user options. See section
#SEC40
Your Shortcuts
.
">
Detailed list of the user options. See section <a href=
Your Shortcuts
.">Detailed list of the user options. See section
#SEC40
Your Shortcuts
.
`variables'
<a href=
#SEC43
Your Variables
.">Detailed list of the variables. See section
#SEC43
Your Variables
.
">
Detailed list of the variables. See section <a href=
Your Variables
.">Detailed list of the variables. See section
#SEC43
Your Variables
.
<a href=
presented for sake of completeness.
">
There are also options meant for the maintainers only
presented for sake of completeness.
`texinfo-style-sheets'
`ssh-texi'
<a href=
sheet
verbosity is set">requirements and ancestors.
">
Detailed list of known style sheets in Texinfo format. If the <code>sheet</code> verbosity is set
requirements and ancestors.
`html-style-sheets'
`ssh-html'
<a href=
HTML
format.">Detailed list of the style sheets in
HTML
format.
">
Detailed list of the style sheets in <code>HTML</code> format.
Detailed list of the style sheets in
HTML
format.
`texinfo-encodings'
`edf-texi'
<a href=
in Texinfo format.
">
Detailed list of encodings
in Texinfo format.
`texinfo-prologues'
`pro-texi'
<a href=
in Texinfo format.
">
Detailed list of prologues
in Texinfo format.
[
#SEC21
<
]
[
#SEC23
>
]
[
#SEC19
<<
]
[
#SEC20
Up
]
[
#SEC34
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
3.1.2 Global Options
<a href=
These options are related to the interface between you and a2ps@c.
">
These options are related to the interface between you and a2ps@c.
These options are related to the interface between you and a2ps@c.
Option:
-q
Option:
-
-
quiet
Option:
-
-
silent
<a href=
be really quiet
">
be really quiet
be really quiet
Option:
-v[
level
]
Option:
-
-
verbose[=
level
]
<a href=
tell what we are doing. At
">
tell what we are doing. At
tell what we are doing. At
-
<a href=
level
= 0">report nothing
">
<var>level</var> = 0
report nothing
-
<a href=
level
= 1">a2ps
">
<var>level</var> = 1
a2ps
-
<a href=
level
= 2 (default)">it reports it for each file
">
<var>level</var> = 2 (default)
it reports it for each file
-
<a href=
it gives internal details.
">
above
it gives internal details.
<a href=
level
is a list of tokens (non ambiguous abbreviations are valid) separated by either
`,'
or
`+'
. The tokens may be:">There is also an interface made for the maintainer with finer grained selection of the verbosity level.
level
is a list of tokens (non ambiguous abbreviations are valid) separated by either
`,'
or
`+'
. The tokens may be:
">
There is also an interface made for the maintainer with finer grained selection of the verbosity level. <var>level</var> is a list of tokens (non ambiguous abbreviations are valid) separated by either <samp>`,'</samp> or <samp>`+'</samp>. The tokens may be:
There is also an interface made for the maintainer with finer grained selection of the verbosity level.
level
is a list of tokens (non ambiguous abbreviations are valid) separated by either
`,'
or
`+'
. The tokens may be:
`configuration'
`options'
<a href=
reading the configurations files and the options
">
reading the configurations files and the options
reading the configurations files and the options
`encodings'
<a href=
the encodings
">
the encodings
the encodings
`expert'
<a href=
more detailed information is provided: PPD listings is exhaustive
">
more detailed information is provided: PPD listings is exhaustive
more detailed information is provided: PPD listings is exhaustive
`files'
<a href=
inputs and outputs
">
inputs and outputs
inputs and outputs
`fonts'
<a href=
the fonts
">
the fonts
the fonts
`escapes'
`variables'
`meta-sequences'
<a href=
the expansion of escapes and variables
">
the expansion of escapes and variables
the expansion of escapes and variables
`parsers'
<a href=
PPD files etc.)
">
any parsing process (style sheets
PPD files etc.)
`pathwalk'
`pw'
<a href=
the search for files
">
the search for files
the search for files
`ppd'
<a href=
PPD processing
">
PPD processing
PPD processing
`sheets'
<a href=
the style sheets
">
the style sheets
the style sheets
`stats'
<a href=
statistics on some internal data structures
">
statistics on some internal data structures
statistics on some internal data structures
`tools'
<a href=
`?V'
on (see section
#SEC33
Available Escapes
)">launched programs or shell commands ; triggers the escape
`?V'
on (see section
#SEC33
Available Escapes
)
">
launched programs or shell commands ; triggers the escape <samp>`?V'</samp> on (see section <a href=
Available Escapes
)">launched programs or shell commands ; triggers the escape
`?V'
on (see section
#SEC33
Available Escapes
)
`all'
<a href=
all the messages.
">
all the messages.
all the messages.
<a href=
A2PS_VERBOSITY
. If it is set">and
`-q'
etc. have then no influence). The valid values for
A2PS_VERBOSITY
are exactly the valid arguments of the option
`--verbose'
. This helps tracking down configuration problems that occur
before
a2pseven a chance to read the command line.
">
When a2ps<code>A2PS_VERBOSITY</code>. If it is set
and
`-q'
etc. have then no influence). The valid values for
A2PS_VERBOSITY
are exactly the valid arguments of the option
`--verbose'
. This helps tracking down configuration problems that occur
before
a2pseven a chance to read the command line.
Option:
-=
shortcut
Option:
-
-
user-option=
shortcut
<a href=
shortcut
defined by the user. See section
#SEC40
Your Shortcuts
. Shortcuts may be freely mixed with regular options and arguments.">use the
shortcut
defined by the user. See section
#SEC40
Your Shortcuts
. Shortcuts may be freely mixed with regular options and arguments.
">
use the <var>shortcut</var> defined by the user. See section <a href=
Your Shortcuts
. Shortcuts may be freely mixed with regular options and arguments.">use the
shortcut
defined by the user. See section
#SEC40
Your Shortcuts
. Shortcuts may be freely mixed with regular options and arguments.
<a href=
There are a few predefined user-options:
">
There are a few predefined user-options:
There are a few predefined user-options:
`lp'
<a href=
turn off most `pretty' features.
">
emulates a line printer
turn off most `pretty' features.
`mail'
`longmail'
<a href=
`longmail'
prints more text on a single sheet.">preferred options to print a mail or a news.
`longmail'
prints more text on a single sheet.
">
preferred options to print a mail or a news. <samp>`longmail'</samp> prints more text on a single sheet.
preferred options to print a mail or a news.
`longmail'
prints more text on a single sheet.
`manual'
<a href=
make the job be printed on the manually fed tray.
">
make the job be printed on the manually fed tray.
make the job be printed on the manually fed tray.
Option:
-
-
debug
<a href=
enable debugging features. They are:
">
enable debugging features. They are:
enable debugging features. They are:
-
<a href=
print the overall BoundingBox in PostScript;
">
print the overall BoundingBox in PostScript;
print the overall BoundingBox in PostScript;
-
<a href=
down load a PostScript debugger which helps understanding why a printer may reject a file.
">
down load a PostScript debugger which helps understanding why a printer may reject a file.
down load a PostScript debugger which helps understanding why a printer may reject a file.
Option:
-D
key
[=
value
]
Option:
-
-
define=
key
[=
value
]
<a href=
value
">set it to
value
. See section
#SEC43
Your Variables
, for more details. Note that
`-Dfoo='
gives
foo
an empty value, though
`-Dfoo'
unsets foo.
">
Without <var>value</var>
set it to
value
. See section
#SEC43
Your Variables
, for more details. Note that
`-Dfoo='
gives
foo
an empty value, though
`-Dfoo'
unsets foo.
[
#SEC22
<
]
[
#SEC24
>
]
[
#SEC19
<<
]
[
#SEC20
Up
]
[
#SEC34
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
3.1.3 Sheet Options
<a href=
how the sheet should be used.
">
This options specify the general layout
how the sheet should be used.
Option:
-M
medium
Option:
-
-
medium=
medium
<a href=
medium
. See the output of
`a2ps --list=media'
for the list of supported media. Typical values are
`A3'
">
`A5'
,
`B4'
,
`B5'
,
`Letter'
,
`Legal'
.
">
use output medium <var>medium</var>. See the output of <samp>`a2ps --list=media'</samp> for the list of supported media. Typical values are <samp>`A3'</samp>
`A5'
,
`B4'
,
`B5'
,
`Letter'
,
`Legal'
.
<a href=
`A4dj'
">since that printer needs bigger margins.
">
<samp>`A4dj'</samp>
since that printer needs bigger margins.
<a href=
medium
`libpaper'
means that you want a2psask the library
libpaper
for the medium to use. This choice is valid only if
libpaper
was available when a2psSee the man page of
paperconf
for more information.">The special
medium
`libpaper'
means that you want a2psask the library
libpaper
for the medium to use. This choice is valid only if
libpaper
was available when a2psSee the man page of
paperconf
for more information.
">
The special <var>medium</var> <samp>`libpaper'</samp> means that you want a2psask the library <code>libpaper</code> for the medium to use. This choice is valid only if <code>libpaper</code> was available when a2psSee the man page of <code>paperconf</code> for more information.
The special
medium
`libpaper'
means that you want a2psask the library
libpaper
for the medium to use. This choice is valid only if
libpaper
was available when a2psSee the man page of
paperconf
for more information.
Option:
-r
Option:
-
-
landscape
<a href=
print in landscape mode
">
print in landscape mode
print in landscape mode
Option:
-R
Option:
-
-
portrait
<a href=
print in portrait mode
">
print in portrait mode
print in portrait mode
Option:
-
-
columns=
num
<a href=
specify the number of columns of virtual pages per physical page.
">
specify the number of columns of virtual pages per physical page.
specify the number of columns of virtual pages per physical page.
Option:
-
-
rows=
num
<a href=
specify the number of rows of virtual pages per physical page.
">
specify the number of rows of virtual pages per physical page.
specify the number of rows of virtual pages per physical page.
Option:
-
-
major=
direction
<a href=
direction
=
`rows'
) or in columns (
direction
=
`columns'
).">specify whether the virtual pages should be first filled in rows (
direction
=
`rows'
) or in columns (
direction
=
`columns'
).
">
specify whether the virtual pages should be first filled in rows (<var>direction</var> = <samp>`rows'</samp>) or in columns (<var>direction</var> = <samp>`columns'</samp>).
specify whether the virtual pages should be first filled in rows (
direction
=
`rows'
) or in columns (
direction
=
`columns'
).
Option:
-1
<a href=
major rows (i.e. alias for
`--columns=1 --rows=1 --portrait --chars-per-line=80 --major=rows'
).
">
1 x 1 portrait
major rows (i.e. alias for
`--columns=1 --rows=1 --portrait --chars-per-line=80 --major=rows'
).
Option:
-2
<a href=
major rows.
">
2 x 1 landscape
major rows.
Option:
-3
<a href=
major rows.
">
3 x 1 landscape
major rows.
Option:
-4
<a href=
major rows.
">
2 x 2 portrait
major rows.
Option:
-5
<a href=
major rows.
">
5 x 1 landscape
major rows.
Option:
-6
<a href=
major rows.
">
3 x 2 landscape
major rows.
Option:
-7
<a href=
major rows.
">
7 x 1 landscape
major rows.
Option:
-8
<a href=
major rows.
">
4 x 2 landscape
major rows.
Option:
-9
<a href=
major rows.
">
3 x 3 portrait
major rows.
Option:
-j
Option:
-
-
borders=
boolean
<a href=
print borders around virtual pages.
">
print borders around virtual pages.
print borders around virtual pages.
Option:
-A
mode
Option:
-
-
file-align=
mode
<a href=
mode
. This option allows the printing of more than one file on the same page.
mode
can be any one of:">Align separate files according to
mode
. This option allows the printing of more than one file on the same page.
mode
can be any one of:
">
Align separate files according to <var>mode</var>. This option allows the printing of more than one file on the same page. <var>mode</var> can be any one of:
Align separate files according to
mode
. This option allows the printing of more than one file on the same page.
mode
can be any one of:
`virtual'
<a href=
leave no empty virtuals).
">
Each file starts on the next available virtual page (i.e.
leave no empty virtuals).
`rank'
<a href=
`--major'
setting.">Each file starts at the beginning of the next row or column depending on the
`--major'
setting.
">
Each file starts at the beginning of the next row or column depending on the <samp>`--major'</samp> setting.
Each file starts at the beginning of the next row or column depending on the
`--major'
setting.
`page'
<a href=
Each file starts on a new page.
">
Each file starts on a new page.
Each file starts on a new page.
`sheet'
<a href=
in Duplex mode, files always start on a front side.
">
Each file starts on a new sheet. In Simplex mode
in Duplex mode, files always start on a front side.
an integer
num
<a href=
num
plus 1. For instance">the files must start on odd pages.
">
Each file starts on a page which is a multiple of <var>num</var> plus 1. For instance
the files must start on odd pages.
Option:
-
-
margin[=
num
]
<a href=
num
PostScript points">and right for the back side). This is intended to ease the binding.
">
Specify the size of the margin (<var>num</var> PostScript points
and right for the back side). This is intended to ease the binding.
[
#SEC23
<
]
[
#SEC25
>
]
[
#SEC19
<<
]
[
#SEC20
Up
]
[
#SEC34
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
3.1.4 Page Options
<a href=
This options are related to the content of the virtual pages.
">
This options are related to the content of the virtual pages.
This options are related to the content of the virtual pages.
<a href=
`-f'
">
`-l'
,
`-m'
, and
`-1'
..
`-9'
all have an influence on the font size. Only the last one will win (i.e.,
`a2ps -L66 -l80'
is the same as
`a2ps -l80'
).
">
Please note that the options <samp>`-f'</samp>
`-l'
,
`-m'
, and
`-1'
..
`-9'
all have an influence on the font size. Only the last one will win (i.e.,
`a2ps -L66 -l80'
is the same as
`a2ps -l80'
).
Option:
-
-
line-numbers[=
number
]
<a href=
number
lines to
number
lines. Default is
`1'
.">print the line numbers from
number
lines to
number
lines. Default is
`1'
.
">
print the line numbers from <var>number</var> lines to <var>number</var> lines. Default is <samp>`1'</samp>.
print the line numbers from
number
lines to
number
lines. Default is
`1'
.
Option:
-C
<a href=
`--line-numbers=5'
.">Alias for
`--line-numbers=5'
.
">
Alias for <samp>`--line-numbers=5'</samp>.
Alias for
`--line-numbers=5'
.
Option:
-f
size
[
unit
]
Option:
-
-
font-size=
size
[
unit
]
<a href=
size
for body text.
size
is a float number">
`points'
for PostScript points, and
`in'
for inches. Default unit in
`points'
.
">
scale font to <var>size</var> for body text. <var>size</var> is a float number
`points'
for PostScript points, and
`in'
for inches. Default unit in
`points'
.
<a href=
change the current prologue (see section
#SEC109
Designing PostScript Prologues
.
">
To change the fonts used
change the current prologue (see section
#SEC109
Designing PostScript Prologues
.
Option:
-l
num
Option:
-
-
chars-per-line=
num
<a href=
num
columns appear per virtual pages.
num
is the real number of columns devoted to the body of the text">no matter whether lines are numbered or not.
">
Set the font size so that <var>num</var> columns appear per virtual pages. <var>num</var> is the real number of columns devoted to the body of the text
no matter whether lines are numbered or not.
Option:
-L
num
Option:
-
-
lines-per-page=
num
<a href=
num
lines appear per virtual pages. This is useful for printing preformatted documents which have a fixed number of lines per page. The minimum number of lines per page is set at 40 and maximum is at 160. If a number less than 40 is supplied">scaling will be turned off.
">
Set the font size so that <var>num</var> lines appear per virtual pages. This is useful for printing preformatted documents which have a fixed number of lines per page. The minimum number of lines per page is set at 40 and maximum is at 160. If a number less than 40 is supplied
scaling will be turned off.
Option:
-m
Option:
-
-
catman
<a href=
output
ie: 66 lines per page and possible bolding and underlining sequences. The understanding of bolding and underlining is there by default even if
`--catman'
is not specified. You may want to use the
`ul'
prologue (See section
#SEC26
Input Options
">option
`--prologue'
) if you prefer underlining over italics.
">
Understand UNIX manual <strong>output</strong> ie: 66 lines per page and possible bolding and underlining sequences. The understanding of bolding and underlining is there by default even if <samp>`--catman'</samp> is not specified. You may want to use the <samp>`ul'</samp> prologue (See section <a href=
Input Options
">option
`--prologue'
) if you prefer underlining over italics.
<a href=
input
">a roff file, then depending whether you left a2psreadable version of the text described, or a pretty-printed version of the describing file (see section
#SEC46
Your Delegations
).
">
If your file is actually a UNIX manual <em>input</em>
a roff file, then depending whether you left a2psreadable version of the text described, or a pretty-printed version of the describing file (see section
#SEC46
Your Delegations
).
Option:
-T
num
Option:
-
-
tabsize=
num
<a href=
num
. This option is ignored if
--interpret=no
is given.">set tabulator size to
num
. This option is ignored if
--interpret=no
is given.
">
set tabulator size to <var>num</var>. This option is ignored if <code>--interpret=no</code> is given.
set tabulator size to
num
. This option is ignored if
--interpret=no
is given.
Option:
-
-
non-printable-format=
format
<a href=
format
can be">specify how non-printable chars are printed.
format
can be
">
specify how non-printable chars are printed. <var>format</var> can be
specify how non-printable chars are printed.
format
can be
`caret'
<a href=
`^A'
">
`M-^B'
etc.
">
Use classical Unix representation: <samp>`^A'</samp>
`M-^B'
etc.
`space'
<a href=
A space is written instead of the non-printable character.
">
A space is written instead of the non-printable character.
A space is written instead of the non-printable character.
`question-mark'
<a href=
`?'
is written instead of the non-printable character.">A
`?'
is written instead of the non-printable character.
">
A <samp>`?'</samp> is written instead of the non-printable character.
A
`?'
is written instead of the non-printable character.
`octal'
<a href=
`\001'
">
`177'
etc.
">
For instance <samp>`\001'</samp>
`177'
etc.
`hexa'
<a href=
`\x01'
">
`\xfe'
etc.
">
For instance <samp>`\x01'</samp>
`\xfe'
etc.
`emacs'
<a href=
`C-h'
">
`M-C-c'
etc.
">
For instance <samp>`C-h'</samp>
`M-C-c'
etc.
[
#SEC24
<
]
[
#SEC26
>
]
[
#SEC19
<<
]
[
#SEC20
Up
]
[
#SEC34
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
3.1.5 Headings Options
<a href=
These are the options through which you may define the information you want to see all around the pages.
">
These are the options through which you may define the information you want to see all around the pages.
These are the options through which you may define the information you want to see all around the pages.
<a href=
text
as an argument">for details.
">
All these options support <var>text</var> as an argument
for details.
Option:
-B
Option:
-
-
no-header
<a href=
no page headers at all.
">
no page headers at all.
no page headers at all.
Option:
-b[
text
]
Option:
-
-
header[=
text
]
<a href=
set the page header
">
set the page header
set the page header
Option:
-
-
center-title[=
text
]
Option:
-
-
left-title[=
text
]
Option:
-
-
right-title[=
text
]
<a href=
left and right titles to
text
.
">
Set virtual page center
left and right titles to
text
.
Option:
-u[
text
]
Option:
-
-
underlay[=
text
]
<a href=
text
as
under lay
(or
water mark
)">in a light gray, and under every page.
">
use <var>text</var> as <em>under lay</em> (or <em>water mark</em>)
in a light gray, and under every page.
Option:
-
-
left-footer[=
text
]
Option:
-
-
footer[=
text
]
Option:
-
-
right-footer[=
text
]
<a href=
text
.">Set sheet footers to
text
.
">
Set sheet footers to <var>text</var>.
Set sheet footers to
text
.
[
#SEC25
<
]
[
#SEC27
>
]
[
#SEC19
<<
]
[
#SEC20
Up
]
[
#SEC34
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
3.1.6 Input Options
Option:
-a[
Page range
]
Option:
-
-
pages[=
Page range
]
<a href=
otherwise select the pages to print.
Page range
is a list of interval, such as
`-a1'
: print only the first page,
`-a-3,4,6,10-'
: print the first 3 pages, page 4 and 6, and all the page after 10 (included). Giving
`toc'
prints the table of content whatever its page number is.
">
With no argument
otherwise select the pages to print.
Page range
is a list of interval, such as
`-a1'
: print only the first page,
`-a-3,4,6,10-'
: print the first 3 pages, page 4 and 6, and all the page after 10 (included). Giving
`toc'
prints the table of content whatever its page number is.
<a href=
input
pages">that is, in
`-2'
, printing with
`-a1'
will print the first virtual page, i.e., you will get half the page filled.
">
The pages referred to are the <em>input</em> pages
that is, in
`-2'
, printing with
`-a1'
will print the first virtual page, i.e., you will get half the page filled.
<a href=
#SEC46
Your Delegations
).">Note that page selection does work with the delegations (see section
#SEC46
Your Delegations
).
">
Note that page selection does work with the delegations (see section <a href=
Your Delegations
).">Note that page selection does work with the delegations (see section
#SEC46
Your Delegations
).
Option:
-c
Option:
-
-
truncate-lines=
boolean
<a href=
Cut lines too large to be printed inside the borders. The maximum line size depends on format and font size used and whether line numbering is enabled.
">
Cut lines too large to be printed inside the borders. The maximum line size depends on format and font size used and whether line numbering is enabled.
Cut lines too large to be printed inside the borders. The maximum line size depends on format and font size used and whether line numbering is enabled.
Option:
-i
Option:
-
-
interpret=
boolean
<a href=
`^L'
jumps to a new (virtual) pages">
`tab'
advances to the next tabulation.
">
interpret tab and ff chars. This means that <samp>`^L'</samp> jumps to a new (virtual) pages
`tab'
advances to the next tabulation.
Option:
-
-
end-of-line=
type
<a href=
type
can be:">Specify what sequence of characters denotes the end of line.
type
can be:
">
Specify what sequence of characters denotes the end of line. <var>type</var> can be:
Specify what sequence of characters denotes the end of line.
type
can be:
n
unix
<a href=
`\n'
.">
`\n'
.
">
<samp>`\n'</samp>.
`\n'
.
r
mac
<a href=
`\r'
.">
`\r'
.
">
<samp>`\r'</samp>.
`\r'
.
nr
<a href=
`\n\r'
. As far as we know">this type of end-of-line is not used.
">
<samp>`\n\r'</samp>. As far as we know
this type of end-of-line is not used.
pc
rn
<a href=
`\r\n'
. This is the type of end-of-line on MS-DOS.">
`\r\n'
. This is the type of end-of-line on MS-DOS.
">
<samp>`\r\n'</samp>. This is the type of end-of-line on MS-DOS.
`\r\n'
. This is the type of end-of-line on MS-DOS.
any
auto
<a href=
`^M'
).">Any of the previous cases. This last case prevents the bad surprises with files from PC (trailing
`^M'
).
">
Any of the previous cases. This last case prevents the bad surprises with files from PC (trailing <samp>`^M'</samp>).
Any of the previous cases. This last case prevents the bad surprises with files from PC (trailing
`^M'
).
Option:
-X
key
Option:
-
-
encoding=
key
<a href=
key
. See section
#SEC64
Some Encodings
">
`latin1'
...
`latin6'
,
`iso
n
'
etc.
">
Use the input encoding identified by <var>key</var>. See section <a href=
Some Encodings
">
`latin1'
...
`latin6'
,
`iso
n
'
etc.
Option:
-
-
stdin=
filename
<a href=
filename
to the files read through the standard input.">Give the name
filename
to the files read through the standard input.
">
Give the name <var>filename</var> to the files read through the standard input.
Give the name
filename
to the files read through the standard input.
Option:
-t
name
Option:
-
-
title=
name
<a href=
name
to the document. Escapes can be used (see section
#SEC30
Escapes
).">Give the name
name
to the document. Escapes can be used (see section
#SEC30
Escapes
).
">
Give the name <var>name</var> to the document. Escapes can be used (see section <a href=
Escapes
).">Give the name
name
to the document. Escapes can be used (see section
#SEC30
Escapes
).
<a href=
Ghostview
and others can display a file with its real title">instead of just the PostScript file name).
">
This is used for instance in the name given to the document from within the PostScript code (so that <code>Ghostview</code> and others can display a file with its real title
instead of just the PostScript file name).
<a href=
not
the name of the output. It is just a logical title.">It is
not
the name of the output. It is just a logical title.
">
It is <strong>not</strong> the name of the output. It is just a logical title.
It is
not
the name of the output. It is just a logical title.
Option:
-
-
prologue=
prologue
<a href=
prologue
as the PostScript prologue for a2ps@c.
prologue
must be in a file named
`
prologue
.pro'
">which must be in a directory of your library path (see section
#SEC51
Library Files
). Available prologues are:
">
Use <var>prologue</var> as the PostScript prologue for a2ps@c. <var>prologue</var> must be in a file named <tt>`<var>prologue</var>.pro'</tt>
which must be in a directory of your library path (see section
#SEC51
Library Files
). Available prologues are:
`bold'
<a href=
-b
of a2ps 4.3. It is a copy of the black and white prologue">but in which all the fonts are in Bold.
">
This style is meant to replace the old option <code>-b</code> of a2ps 4.3. It is a copy of the black and white prologue
but in which all the fonts are in Bold.
`bw'
<a href=
with standard fonts.
">
Style is plain: pure black and white
with standard fonts.
`color'
<a href=
Colors are used to highlight the keywords.
">
Colors are used to highlight the keywords.
Colors are used to highlight the keywords.
`diff'
<a href=
udiff
">to underline the differences. New things are in bold on a diff background, while removed sequences are in italic.
">
This style is meant to be used with the <code>udiff</code>
to underline the differences. New things are in bold on a diff background, while removed sequences are in italic.
`fixed'
<a href=
This style uses exclusively fixed size fonts. You should use this style if you want the tabulations to be properly printed.
">
This style uses exclusively fixed size fonts. You should use this style if you want the tabulations to be properly printed.
This style uses exclusively fixed size fonts. You should use this style if you want the tabulations to be properly printed.
<a href=
therefore you should not use the heavy highlighting style.
">
There are no means to use a fixed size Symbol font
therefore you should not use the heavy highlighting style.
`gray'
<a href=
Gray background is used for comments and labels.
">
Gray background is used for comments and labels.
Gray background is used for comments and labels.
`gray2'
<a href=
Black background is used for comments and labels.
">
Black background is used for comments and labels.
Black background is used for comments and labels.
`matrix'
<a href=
`bw'
">but alternating gray and white lines. There are two macros defining the behavior:
`pro.matrix.cycle'
defines the length of the cycle (number of white and gray lines). It defaults to 6.
`pro.matrix.gray'
defines the number of gray lines. Default is 3.
">
The layout is the same as <samp>`bw'</samp>
but alternating gray and white lines. There are two macros defining the behavior:
`pro.matrix.cycle'
defines the length of the cycle (number of white and gray lines). It defaults to 6.
`pro.matrix.gray'
defines the number of gray lines. Default is 3.
`ul'
<a href=
but never italics. This is particularly meant for printing formatted man pages.
">
This style uses bold faces and underlines
but never italics. This is particularly meant for printing formatted man pages.
Option:
-
-
print-anyway=
boolean
<a href=
it's a binary file. a2ps
file(1)
what it thinks of the type of the file. If
file(1)
answers
`data'
, the file will also be considered as binary, hence not printed.
">
force binary printing. By default
it's a binary file. a2ps
file(1)
what it thinks of the type of the file. If
file(1)
answers
`data'
, the file will also be considered as binary, hence not printed.
Option:
-Z
Option:
-
-
delegate=
boolean
<a href=
then a2ps
">
Enable delegation of some files to delegated applications. If delegating is on
then a2ps
<a href=
but want to print what describes that file. Then set the delegations on.
">
Typically most people don't want to pretty-print a PostScript source file
but want to print what describes that file. Then set the delegations on.
<a href=
#SEC46
Your Delegations
for information on delegating">and option
`--list=delegations'
for the applications your a2ps
">
See <a href=
Your Delegations
for information on delegating">and option
`--list=delegations'
for the applications your a2ps
Option:
-
-
toc[=
format
]
<a href=
you wrote
`--toc'
), use the default table of contents shape (
#{toc}
). If the given format is empty (i.e., you wrote
`--toc='
), don't issue the table of contents.
">
Generate a Table of Contents
you wrote
`--toc'
), use the default table of contents shape (
#{toc}
). If the given format is empty (i.e., you wrote
`--toc='
), don't issue the table of contents.
<a href=
#SEC43
Your Variables
)">in a configuration file:
">
Note that it is most useful to define a variable (see section <a href=
Your Variables
)">in a configuration file:
<a href=
Variable: toc.mine \ \\Keyword{Table of Content}\n\ #-1!f\ |$2# \\keyword{$-.20n} sheets $3s< to $3s> ($2s#) \ pages $3p<-$3p> $4l# lines\n||\ \\Keyword{End of toc}\n
">
Variable: toc.mine \ \\Keyword{Table of Content}\n\ #-1!f\ |$2# \\keyword{$-.20n} sheets $3s&lt; to $3s&gt; ($2s#) \ pages $3p&lt;-$3p&gt; $4l# lines\n||\ \\Keyword{End of toc}\n
Variable: toc.mine \ \\Keyword{Table of Content}\n\ #-1!f\ |$2# \\keyword{$-.20n} sheets $3s< to $3s> ($2s#) \ pages $3p<-$3p> $4l# lines\n||\ \\Keyword{End of toc}\n
<a href=
`--toc'
:
`a2ps *.c --toc=#{toc.mine}'
.">and to give that variable as argument to
`--toc'
:
`a2ps *.c --toc=#{toc.mine}'
.
">
and to give that variable as argument to <samp>`--toc'</samp>: <samp>`a2ps *.c --toc=#{toc.mine}'</samp>.
and to give that variable as argument to
`--toc'
:
`a2ps *.c --toc=#{toc.mine}'
.
<a href=
`--pages'
:">Note too that you can generate only the table of content using
`--pages'
:
">
Note too that you can generate only the table of content using <samp>`--pages'</samp>:
Note too that you can generate only the table of content using
`--pages'
:
<a href=
a2ps *.c --toc -atoc
">
a2ps *.c --toc -atoc
a2ps *.c --toc -atoc
[
#SEC26
<
]
[
#SEC28
>
]
[
#SEC19
<<
]
[
#SEC20
Up
]
[
#SEC34
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
3.1.7 Pretty Printing Options
<a href=
These options are related to the pretty printing features of a2ps@c.
">
These options are related to the pretty printing features of a2ps@c.
These options are related to the pretty printing features of a2ps@c.
Option:
-
-
highlight-level=
level
<a href=
level
of highlighting.
level
can be">Specify the
level
of highlighting.
level
can be
">
Specify the <var>level</var> of highlighting. <var>level</var> can be
Specify the
level
of highlighting.
level
can be
`none'
<a href=
no highlighting
">
no highlighting
no highlighting
`normal'
<a href=
regular highlighting
">
regular highlighting
regular highlighting
`heavy'
<a href=
even more highlighting.
">
even more highlighting.
even more highlighting.
<a href=
`--list=style-sheets'
) for a description of
`heavy'
highlighting.">See the documentation of the style sheets (
`--list=style-sheets'
) for a description of
`heavy'
highlighting.
">
See the documentation of the style sheets (<samp>`--list=style-sheets'</samp>) for a description of <samp>`heavy'</samp> highlighting.
See the documentation of the style sheets (
`--list=style-sheets'
) for a description of
`heavy'
highlighting.
Option:
-g
<a href=
`--highlight-level=heavy'
.">Alias for
`--highlight-level=heavy'
.
">
Alias for <samp>`--highlight-level=heavy'</samp>.
Alias for
`--highlight-level=heavy'
.
Option:
-E
[
language
]
Option:
-
-
pretty-print[=
language
]
<a href=
set style to
language
. Note that setting
language
to
`plain'
turns off pretty-printing. See section
#SEC67
Known Style Sheets
, and the output of
`--list=style-sheets'
for the available style sheets.
">
With no arguments
set style to
language
. Note that setting
language
to
`plain'
turns off pretty-printing. See section
#SEC67
Known Style Sheets
, and the output of
`--list=style-sheets'
for the available style sheets.
<a href=
language
is
`
key
.ssh'
">but use the file
`
key.ssh
'
. This is to ease debugging non installed style sheets.
">
If <var>language</var> is <samp>`<var>key</var>.ssh'</samp>
but use the file
`
key.ssh
'
. This is to ease debugging non installed style sheets.
Option:
-
-
strip-level=
num
<a href=
num
:">Depending on the value of
num
:
">
Depending on the value of <var>num</var>:
Depending on the value of
num
:
`0'
<a href=
everything is printed;
">
everything is printed;
everything is printed;
`1'
<a href=
regular comments are not printed
">
regular comments are not printed
regular comments are not printed
`2'
<a href=
strong comments are not printed
">
strong comments are not printed
strong comments are not printed
`3'
<a href=
no comment is printed.
">
no comment is printed.
no comment is printed.
<a href=
java
in which case strong comments are the so called documentation comments">or in
SDL
for which some graphical editors pollutes the specification with internal data as comments.
">
This option is valuable for instance in <code>java</code> in which case strong comments are the so called documentation comments
or in
SDL
for which some graphical editors pollutes the specification with internal data as comments.
<a href=
Note that the current implementation is not satisfactory: some undesired blank lines remain. This is planed to be fixed.
">
Note that the current implementation is not satisfactory: some undesired blank lines remain. This is planed to be fixed.
Note that the current implementation is not satisfactory: some undesired blank lines remain. This is planed to be fixed.
[
#SEC27
<
]
[
#SEC29
>
]
[
#SEC19
<<
]
[
#SEC20
Up
]
[
#SEC34
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
3.1.8 Output Options
<a href=
if ever there are several options
`-o'
,
`-P'
or
`-d'
, the last one is honored.
">
These are the options to specify what you want to do out of what a2psproduces. Only a single destination is possible at a time
if ever there are several options
`-o'
,
`-P'
or
`-d'
, the last one is honored.
Option:
-o
file
Option:
-
-
output=
file
<a href=
file
. If
file
is
`-'
">leave output to the standard output.
">
leave output to file <var>file</var>. If <var>file</var> is <samp>`-'</samp>
leave output to the standard output.
Option:
-
-
version-control=
type
<a href=
is regular (that is, no backup is done on special files such as
`/dev/null'
), and is writable (in this case, disabling version control makes a2psas if version control was disabled: permission denied).
">
to avoid loosing a file
is regular (that is, no backup is done on special files such as
`/dev/null'
), and is writable (in this case, disabling version control makes a2psas if version control was disabled: permission denied).
<a href=
VERSION_CONTROL
environment variable">the default backup type is `existing'. The value of the
VERSION_CONTROL
environment variable and the argument to this option are like the GNU
Emacs
`version-control'
variable; they also recognize synonyms that are more descriptive. The valid values are (unique abbreviations are accepted):
">
The type of backups made can be set with the <code>VERSION_CONTROL</code> environment variable
the default backup type is `existing'. The value of the
VERSION_CONTROL
environment variable and the argument to this option are like the GNU
Emacs
`version-control'
variable; they also recognize synonyms that are more descriptive. The valid values are (unique abbreviations are accepted):
`none'
`off'
<a href=
Never make backups (override existing files).
">
Never make backups (override existing files).
Never make backups (override existing files).
`t'
`numbered'
<a href=
Always make numbered backups.
">
Always make numbered backups.
Always make numbered backups.
`nil'
`existing'
<a href=
simple backups of the others.
">
Make numbered backups of files that already have them
simple backups of the others.
`never'
`simple'
<a href=
Always make simple backups.
">
Always make simple backups.
Always make simple backups.
Option:
-
-
suffix=
suffix
<a href=
SIMPLE_BACKUP_SUFFIX
environment variable">the default is
`~'
, as it is in
Emacs
.
">
The suffix used for making simple backup files can be set with the <code>SIMPLE_BACKUP_SUFFIX</code> environment variable
the default is
`~'
, as it is in
Emacs
.
Option:
-P
name
Option:
-
-
printer=
name
<a href=
name
. See item
`Printer:'
and
`Unknown printer:'
in
#SEC39
Your Printers
and results of option
`--list=defaults'
to see the bindings between printer names and commands.">send output to printer
name
. See item
`Printer:'
and
`Unknown printer:'
in
#SEC39
Your Printers
and results of option
`--list=defaults'
to see the bindings between printer names and commands.
">
send output to printer <var>name</var>. See item <samp>`Printer:'</samp> and <samp>`Unknown printer:'</samp> in <a href=
Your Printers
and results of option
`--list=defaults'
to see the bindings between printer names and commands.">send output to printer
name
. See item
`Printer:'
and
`Unknown printer:'
in
#SEC39
Your Printers
and results of option
`--list=defaults'
to see the bindings between printer names and commands.
<a href=
lpr
or
lp
via the variable
`lp.options'
">for more information see
#SEC141
How Can I Pass Options to
`lpr'
.
">
It is possible to pass additional options to <code>lpr</code> or <code>lp</code> via the variable <samp>`lp.options'</samp>
for more information see
#SEC141
How Can I Pass Options to
`lpr'
.
Option:
-d
<a href=
`DefaultPrinter:'
in
#SEC39
Your Printers
.">send output to the default printer. See item
`DefaultPrinter:'
in
#SEC39
Your Printers
.
">
send output to the default printer. See item <samp>`DefaultPrinter:'</samp> in <a href=
Your Printers
.">send output to the default printer. See item
`DefaultPrinter:'
in
#SEC39
Your Printers
.
[
#SEC28
<
]
[
#SEC30
>
]
[
#SEC19
<<
]
[
#SEC20
Up
]
[
#SEC34
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
3.1.9 PostScript Options
<a href=
The following options are related only to variations you want to produce onto a PostScript output.
">
The following options are related only to variations you want to produce onto a PostScript output.
The following options are related only to variations you want to produce onto a PostScript output.
Option:
-
-
ppd[=
key
]
<a href=
otherwise set the PPD to
key
. FIXME: what to read.
">
With no argument
otherwise set the PPD to
key
. FIXME: what to read.
Option:
-n
num
Option:
-
-
copies=
num
<a href=
num
copies of each page">print
num
copies of each page
">
print <var>num</var> copies of each page
print
num
copies of each page
Option:
-s
duplex-mode
Option:
-
-
sides=
duplex-mode
<a href=
more generally, the Duplex mode (see section
#SEC148
Glossary
). The valid values for
duplex-mode
are:
">
Specify the number of sheet sides
more generally, the Duplex mode (see section
#SEC148
Glossary
). The valid values for
duplex-mode
are:
`1'
`simplex'
<a href=
One page per sheet.
">
One page per sheet.
One page per sheet.
`2'
`duplex'
<a href=
DuplexNoTumble mode.
">
Two pages per sheet
DuplexNoTumble mode.
`tumble'
<a href=
DuplexTumble mode.
">
Two pages per sheet
DuplexTumble mode.
<a href=
but it also enables duplex features from a2pspages to back pages etc.).
">
Not only does this option require Duplex from the printer
but it also enables duplex features from a2pspages to back pages etc.).
Option:
-S
key
[:
value
]
Option:
-
-
setpagedevice=
key
[:
value
]
<a href=
value
is given">
key
is removed from the definitions. Note that several
`--setpagedevice'
can be accumulated.
">
Pass a page device definition to the generated PostScript output. If no <var>value</var> is given
key
is removed from the definitions. Note that several
`--setpagedevice'
can be accumulated.
<a href=
command
">
For example
command
<a href=
ubu $ a2ps -SDuplex:true -STumble:true NEWS [NEWS (plain): 15 pages on 8 sheets] [Total: 15 pages on 8 sheets] sent to the default printer
">
ubu $ a2ps -SDuplex:true -STumble:true NEWS [NEWS (plain): 15 pages on 8 sheets] [Total: 15 pages on 8 sheets] sent to the default printer
ubu $ a2ps -SDuplex:true -STumble:true NEWS [NEWS (plain): 15 pages on 8 sheets] [Total: 15 pages on 8 sheets] sent to the default printer
<a href=
`report.pre'
in duplex (two sides) tumble (suitable for landscape documents). This is also valid for delegated files:">prints file
`report.pre'
in duplex (two sides) tumble (suitable for landscape documents). This is also valid for delegated files:
">
prints file <tt>`report.pre'</tt> in duplex (two sides) tumble (suitable for landscape documents). This is also valid for delegated files:
prints file
`report.pre'
in duplex (two sides) tumble (suitable for landscape documents). This is also valid for delegated files:
<a href=
a2ps -SDuplex:true -STumble:true a2ps.texi
">
a2ps -SDuplex:true -STumble:true a2ps.texi
a2ps -SDuplex:true -STumble:true a2ps.texi
<a href=
#SEC105
Page Device Options
">for details.
">
Page device operators are implementation dependent but they are standardized. See section <a href=
Page Device Options
">for details.
Option:
-
-
statusdict=
key
[:
value
]
Option:
-
-
statusdict=
key
[::
value
]
<a href=
statusdict
operators and variables are implementation dependent; see the documentation of your printer for details. See section
#SEC106
Statusdict Options
">for details. Several
`--statusdict'
can be accumulated.
">
Pass a statusdict definition to the generated PostScript output. <code>statusdict</code> operators and variables are implementation dependent; see the documentation of your printer for details. See section <a href=
Statusdict Options
">for details. Several
`--statusdict'
can be accumulated.
<a href=
value
is given">
key
is removed from the definitions.
">
If no <var>value</var> is given
key
is removed from the definitions.
<a href=
for instance:
">
With a single colon
for instance:
<a href=
a2ps --statusdict=setpapertray:1 quicksort.c
">
a2ps --statusdict=setpapertray:1 quicksort.c
a2ps --statusdict=setpapertray:1 quicksort.c
<a href=
`quicksort.c'
by using paper from the paper tray 1 (assuming that printer supports paper tray selection).">prints file
`quicksort.c'
by using paper from the paper tray 1 (assuming that printer supports paper tray selection).
">
prints file <tt>`quicksort.c'</tt> by using paper from the paper tray 1 (assuming that printer supports paper tray selection).
prints file
`quicksort.c'
by using paper from the paper tray 1 (assuming that printer supports paper tray selection).
<a href=
define variable
key
to equal
value
. For instance:
">
With two colons
define variable
key
to equal
value
. For instance:
<a href=
a2ps --statusdict=papertray::1 quicksort.c
">
a2ps --statusdict=papertray::1 quicksort.c
a2ps --statusdict=papertray::1 quicksort.c
<a href=
produces
">
produces
produces
<a href=
/papertray 1 def
">
/papertray 1 def
/papertray 1 def
<a href=
in the PostScript.
">
in the PostScript.
in the PostScript.
Option:
-k
Option:
-
-
page-prefeed
<a href=
enable page prefeeding. It consists in positioning the sheet in the printing area while the PostScript is interpreted (instead of waiting the end of the interpretation of the page before pushing the sheet). It can lead to an significant speed up of the printing.
">
enable page prefeeding. It consists in positioning the sheet in the printing area while the PostScript is interpreted (instead of waiting the end of the interpretation of the page before pushing the sheet). It can lead to an significant speed up of the printing.
enable page prefeeding. It consists in positioning the sheet in the printing area while the PostScript is interpreted (instead of waiting the end of the interpretation of the page before pushing the sheet). It can lead to an significant speed up of the printing.
<a href=
a2psprinters won't fail.
">
a2psprinters won't fail.
a2psprinters won't fail.
Option:
-K
Option:
-
-
no-page-prefeed
<a href=
disable page prefeeding.
">
disable page prefeeding.
disable page prefeeding.
[
#SEC29
<
]
[
#SEC31
>
]
[
#SEC19
<<
]
[
#SEC19
Up
]
[
#SEC34
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
3.2 Escapes
<a href=
The escapes are some sequences of characters that will be replaced by their values. They are very much like variables.
">
The escapes are some sequences of characters that will be replaced by their values. They are very much like variables.
The escapes are some sequences of characters that will be replaced by their values. They are very much like variables.
#SEC31
3.2.1 Use of Escapes
Where they are used
#SEC32
3.2.2 General Structure of the Escapes
Their syntax
#SEC33
3.2.3 Available Escapes
Detailed list
[
#SEC30
<
]
[
#SEC32
>
]
[
#SEC19
<<
]
[
#SEC30
Up
]
[
#SEC34
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
3.2.1 Use of Escapes
<a href=
They are used in several places in a2ps@c:
">
They are used in several places in a2ps@c:
They are used in several places in a2ps@c:
Page markers
<a href=
titles and the water mark (see section
#SEC25
Headings Options
), in general to print the name of file, page number etc. On a new sheet a2psthen the frame of the first page, (ditto with the others), and finally the sheet header and footers. This order must be taken into account for some escapes (e.g.,
`$l.'
,
`$l^'
).
">
Headers
titles and the water mark (see section
#SEC25
Headings Options
), in general to print the name of file, page number etc. On a new sheet a2psthen the frame of the first page, (ditto with the others), and finally the sheet header and footers. This order must be taken into account for some escapes (e.g.,
`$l.'
,
`$l^'
).
Named output
<a href=
or how to access a printer (see section
#SEC39
Your Printers
).
">
To specify the generic name of the file to produce
or how to access a printer (see section
#SEC39
Your Printers
).
Delegation
<a href=
#SEC46
Your Delegations
).">To specify the command associated to a delegation (see section
#SEC46
Your Delegations
).
">
To specify the command associated to a delegation (see section <a href=
Your Delegations
).">To specify the command associated to a delegation (see section
#SEC46
Your Delegations
).
Table of Content
<a href=
To specify an index/table of content printed at the end of the job.
">
To specify an index/table of content printed at the end of the job.
To specify an index/table of content printed at the end of the job.
Variables in PostScript prologue
<a href=
#SEC109
Designing PostScript Prologues
).">To allow the user to change some parameters to your prologues (see section
#SEC109
Designing PostScript Prologues
).
">
To allow the user to change some parameters to your prologues (see section <a href=
Designing PostScript Prologues
).">To allow the user to change some parameters to your prologues (see section
#SEC109
Designing PostScript Prologues
).
[
#SEC31
<
]
[
#SEC33
>
]
[
#SEC19
<<
]
[
#SEC30
Up
]
[
#SEC34
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
3.2.2 General Structure of the Escapes
<a href=
All format directives can also be given in format
">
All format directives can also be given in format
All format directives can also be given in format
<a href=
escape
width
directive
">
escape
width
directive
">
<var>escape</var> <var>width</var> <var>directive</var>
escape
width
directive
<a href=
where
">
where
where
escape
<a href=
In general
">
In general
In general
`%'
<a href=
the user's name etc.),
">
escapes are related to general information (e.g.
the user's name etc.),
`#'
<a href=
the number of virtual pages etc.), or to special constructions (e.g., enumerations of the files, or tests etc.),
">
escapes are related to the output (e.g.
the number of virtual pages etc.), or to special constructions (e.g., enumerations of the files, or tests etc.),
`$'
<a href=
its current page number etc.),
">
escapes are related to the current input file (e.g.
its current page number etc.),
`\'
<a href=
sequences (e.g.,
`\n'
,
`\f'
etc.).
">
introduces classical escaping
sequences (e.g.,
`\n'
,
`\f'
etc.).
width
<a href=
width
">Specifies the width of the column to which the escape is printed. There are three forms for
width
">
Specifies the width of the column to which the escape is printed. There are three forms for <var>width</var>
Specifies the width of the column to which the escape is printed. There are three forms for
width
`+
padding
integer
'
<a href=
padding
so that the whole result is as long as
integer
. For instance
`$+.10n'
with a file name
`$n'
=
`foo.c'
gives
`.....foo.c'
.">the result of the expansion is prefixed by the character
padding
so that the whole result is as long as
integer
. For instance
`$+.10n'
with a file name
`$n'
=
`foo.c'
gives
`.....foo.c'
.
">
the result of the expansion is prefixed by the character <var>padding</var> so that the whole result is as long as <var>integer</var>. For instance <samp>`$+.10n'</samp> with a file name <samp>`$n'</samp>=<tt>`foo.c'</tt> gives <samp>`.....foo.c'</samp>.
the result of the expansion is prefixed by the character
padding
so that the whole result is as long as
integer
. For instance
`$+.10n'
with a file name
`$n'
=
`foo.c'
gives
`.....foo.c'
.
<a href=
padding
is given">
` '
(white space) is used.
">
If no <var>padding</var> is given
` '
(white space) is used.
`-
padding
integer
'
<a href=
except that completion is done on the left:
`$+.10n'
gives
`foo.c.....'
.
">
Idem as above
except that completion is done on the left:
`$+.10n'
gives
`foo.c.....'
.
`
integer
'
<a href=
`+
integer
'
. For example">escape
`$5P'
will expand to something like
`   12'
.
">
which is a short cut for <samp>`+<var>integer</var>'</samp>. For example
escape
`$5P'
will expand to something like
`   12'
.
directive
<a href=
#SEC33
Available Escapes
.">See section
#SEC33
Available Escapes
.
">
See section <a href=
Available Escapes
.">See section
#SEC33
Available Escapes
.
[
#SEC32
<
]
[
#SEC34
>
]
[
#SEC19
<<
]
[
#SEC30
Up
]
[
#SEC34
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
3.2.3 Available Escapes
<a href=
Supported escapes are:
">
Supported escapes are:
Supported escapes are:
`\\'
<a href=
`\'
">character
`\'
">
character <samp>`\'</samp>
character
`\'
`\%'
<a href=
`%'
">character
`%'
">
character <samp>`%'</samp>
character
`%'
`\$'
<a href=
`$'
">character
`$'
">
character <samp>`$'</samp>
character
`$'
`\#'
<a href=
`#'
">character
`#'
">
character <samp>`#'</samp>
character
`#'
`#?
cond
|
if_true
|
if_false
|'
<a href=
`|'
) may be any character.
if_true
and
if_false
may be defined exactly the same way as regular headers">included escapes and the
`#?'
construct.
">
this may be used for conditional assignment. The separator (presented here as <samp>`|'</samp>) may be any character. <var>if_true</var> and <var>if_false</var> may be defined exactly the same way as regular headers
included escapes and the
`#?'
construct.
<a href=
The available tests are:
">
The available tests are:
The available tests are:
`#?1'
`#?2'
`#?3'
<a href=
2 or 3 is not empty. See item
`$t1'
for explanation.
">
true if tag 1
2 or 3 is not empty. See item
`$t1'
for explanation.
`#?d'
<a href=
`-s2'
).">true if Duplex printing is requested (
`-s2'
).
">
true if Duplex printing is requested (<samp>`-s2'</samp>).
true if Duplex printing is requested (
`-s2'
).
`#?j'
<a href=
`-j'
).">true if bordering is asked (
`-j'
).
">
true if bordering is asked (<samp>`-j'</samp>).
true if bordering is asked (
`-j'
).
`#?l'
<a href=
true if printing in landscape mode.
">
true if printing in landscape mode.
true if printing in landscape mode.
`#?o'
<a href=
`#v'
is 1).
">
true if only one virtual page per page (i.e.
`#v'
is 1).
`#?p'
<a href=
`#p'
is not empty).
">
a page range has been specified (i.e.
`#p'
is not empty).
`#?q'
<a href=
true if a2ps
">
true if a2ps
true if a2ps
`#?r'
<a href=
`--major=rows'
).">true if major is rows (
`--major=rows'
).
">
true if major is rows (<samp>`--major=rows'</samp>).
true if major is rows (
`--major=rows'
).
`#?v'
<a href=
true if printing on the back side of the sheet (verso).
">
true if printing on the back side of the sheet (verso).
true if printing on the back side of the sheet (verso).
`#?V'
<a href=
`tools'
flag (See section
#SEC22
Global Options
. option
`--verbosity'
).">true if verbosity level includes the
`tools'
flag (See section
#SEC22
Global Options
. option
`--verbosity'
).
">
true if verbosity level includes the <samp>`tools'</samp> flag (See section <a href=
Global Options
. option
`--verbosity'
).">true if verbosity level includes the
`tools'
flag (See section
#SEC22
Global Options
. option
`--verbosity'
).
`#!
key
|
in
|
between
|'
<a href=
`|'
) may be any character.
in
and
between
are escapes.">Used for enumerations. The separator (presented here as
`|'
) may be any character.
in
and
between
are escapes.
">
Used for enumerations. The separator (presented here as <samp>`|'</samp>) may be any character. <var>in</var> and <var>between</var> are escapes.
Used for enumerations. The separator (presented here as
`|'
) may be any character.
in
and
between
are escapes.
<a href=
The enumerations may be:
">
The enumerations may be:
The enumerations may be:
`#!$'
<a href=
in
in never used">but is replaced by the arguments.
">
enumeration of the command line options. In this case <var>in</var> in never used
but is replaced by the arguments.
`#!f'
<a href=
enumeration of the input files in the other they were given.
">
enumeration of the input files in the other they were given.
enumeration of the input files in the other they were given.
`#!F'
<a href=
enumeration of the input files in the alphabetical order of their names.
">
enumeration of the input files in the alphabetical order of their names.
enumeration of the input files in the alphabetical order of their names.
`#!s'
<a href=
enumeration of the files appearing in the current sheet.
">
enumeration of the files appearing in the current sheet.
enumeration of the files appearing in the current sheet.
<a href=
gives
`The files printed were: NEWS, main.c.'
.
">
For instance
gives
`The files printed were: NEWS, main.c.'
.
<a href=
e.g.,
`#10!f|$n|, |'
lists only the ten first file names. If
width
is negative, then it does not enumerate the -
width
last objects (e.g.,
`#-1!f|$n|, |'
lists all the files but the last).
">
As an exception
e.g.,
`#10!f|$n|, |'
lists only the ten first file names. If
width
is negative, then it does not enumerate the -
width
last objects (e.g.,
`#-1!f|$n|, |'
lists all the files but the last).
`${
var
}'
<a href=
var
if defined">nothing otherwise.
">
value of the environment variable <var>var</var> if defined
nothing otherwise.
`${
var
:-
word
}'
<a href=
var
is defined">otherwise
word
.
">
if the environment variable <var>var</var> is defined
otherwise
word
.
`${
var
:+
word
}'
<a href=
var
is defined">otherwise nothing.
">
if the environment variable <var>var</var> is defined
otherwise nothing.
`$[
num
]'
<a href=
num
th argument given on the command line. Note that $[0] is the name under which a2ps">value of the
num
th argument given on the command line. Note that $[0] is the name under which a2ps
">
value of the <var>num</var>th argument given on the command line. Note that $[0] is the name under which a2ps
value of the
num
th argument given on the command line. Note that $[0] is the name under which a2ps
`#{
key
}'
<a href=
key
if defined">nothing otherwise (see section
#SEC43
Your Variables
)
">
expansion of the value of the variable <var>key</var> if defined
nothing otherwise (see section
#SEC43
Your Variables
)
`#{
key
:-
word
}'
<a href=
var
is defined">otherwise
word
.
">
if the variable <var>var</var> is defined
otherwise
word
.
`#{
key
:+
word
}'
<a href=
var
is defined">otherwise nothing.
">
if the variable <var>var</var> is defined
otherwise nothing.
`#.'
<a href=
`ps'
).">the extension corresponding to the current output language (e.g.
`ps'
).
">
the extension corresponding to the current output language (e.g. <samp>`ps'</samp>).
the extension corresponding to the current output language (e.g.
`ps'
).
`%*'
<a href=
`hh:mm:ss'
">current time in 24-hour format with seconds
`hh:mm:ss'
">
current time in 24-hour format with seconds <samp>`hh:mm:ss'</samp>
current time in 24-hour format with seconds
`hh:mm:ss'
`$*'
<a href=
`hh:mm:ss'
">file modification time in 24-hour format with seconds
`hh:mm:ss'
">
file modification time in 24-hour format with seconds <samp>`hh:mm:ss'</samp>
file modification time in 24-hour format with seconds
`hh:mm:ss'
`$#'
<a href=
the sequence number of the current input file
">
the sequence number of the current input file
the sequence number of the current input file
`%#'
<a href=
the total number of files
">
the total number of files
the total number of files
`%a'
<a href=
`Printed by
User Name
'
.
User Name
is obtained from the variable
`user.name'
(see section
#SEC45
Predefined Variables
).">the localized equivalent for
`Printed by
User Name
'
.
User Name
is obtained from the variable
`user.name'
(see section
#SEC45
Predefined Variables
).
">
the localized equivalent for <samp>`Printed by <var>User Name</var>'</samp>. <var>User Name</var> is obtained from the variable <samp>`user.name'</samp> (see section <a href=
Predefined Variables
).">the localized equivalent for
`Printed by
User Name
'
.
User Name
is obtained from the variable
`user.name'
(see section
#SEC45
Predefined Variables
).
`%A'
<a href=
`Printed by
User Name
from
Host Name
'
. The variables
`user.name'
and
`user.host'
are used (see section
#SEC45
Predefined Variables
).">the localized equivalent for
`Printed by
User Name
from
Host Name
'
. The variables
`user.name'
and
`user.host'
are used (see section
#SEC45
Predefined Variables
).
">
the localized equivalent for <samp>`Printed by <var>User Name</var> from <var>Host Name</var>'</samp>. The variables <samp>`user.name'</samp> and <samp>`user.host'</samp> are used (see section <a href=
Predefined Variables
).">the localized equivalent for
`Printed by
User Name
from
Host Name
'
. The variables
`user.name'
and
`user.host'
are used (see section
#SEC45
Predefined Variables
).
`%c'
<a href=
trailing component of the current working directory
">
trailing component of the current working directory
trailing component of the current working directory
`%C'
<a href=
`hh:mm:ss'
format">current time in
`hh:mm:ss'
format
">
current time in <samp>`hh:mm:ss'</samp> format
current time in
`hh:mm:ss'
format
`$C'
<a href=
`hh:mm:ss'
format">file modification time in
`hh:mm:ss'
format
">
file modification time in <samp>`hh:mm:ss'</samp> format
file modification time in
`hh:mm:ss'
format
`%d'
<a href=
current working directory
">
current working directory
current working directory
`$d'
<a href=
`.'
if the directory part is empty).">directory part of the current file (
`.'
if the directory part is empty).
">
directory part of the current file (<samp>`.'</samp> if the directory part is empty).
directory part of the current file (
`.'
if the directory part is empty).
`%D'
<a href=
`yy-mm-dd'
format">current date in
`yy-mm-dd'
format
">
current date in <samp>`yy-mm-dd'</samp> format
current date in
`yy-mm-dd'
format
`$D'
<a href=
`yy-mm-dd'
format">file modification date in
`yy-mm-dd'
format
">
file modification date in <samp>`yy-mm-dd'</samp> format
file modification date in
`yy-mm-dd'
format
`%D{
string
}'
<a href=
string
with the
strftime(3)
function.">format current date according to
string
with the
strftime(3)
function.
">
format current date according to <var>string</var> with the <code>strftime(3)</code> function.
format current date according to
string
with the
strftime(3)
function.
`$D{
string
}'
<a href=
string
with the
strftime(3)
function.">format file's last modification date according to
string
with the
strftime(3)
function.
">
format file's last modification date according to <var>string</var> with the <code>strftime(3)</code> function.
format file's last modification date according to
string
with the
strftime(3)
function.
`%e'
<a href=
or
`14 Juil 89'
in French).
">
current date in localized short format (e.g.
or
`14 Juil 89'
in French).
`$e'
<a href=
file modification date in localized short format.
">
file modification date in localized short format.
file modification date in localized short format.
`%E'
<a href=
or
`Samedi 14 Juillet 89'
in French).
">
current date in localized long format (e.g.
or
`Samedi 14 Juillet 89'
in French).
`$E'
<a href=
file modification date in localized long format.
">
file modification date in localized long format.
file modification date in localized long format.
`$f'
<a href=
full file name (with directory and suffix).
">
full file name (with directory and suffix).
full file name (with directory and suffix).
`\f'
<a href=
`\f'
(
form feed
).">character
`\f'
(
form feed
).
">
character <samp>`\f'</samp> (<code>form feed</code>).
character
`\f'
(
form feed
).
`#f0'
`#f9'
<a href=
a2psremoves them at the end of the job. It is useful for the delegations (see section
#SEC46
Your Delegations
) and for the printer commands (see section
#SEC39
Your Printers
).
">
ten temporary file names. You can do anything you want with them
a2psremoves them at the end of the job. It is useful for the delegations (see section
#SEC46
Your Delegations
) and for the printer commands (see section
#SEC39
Your Printers
).
`%F'
<a href=
`dd.mm.yyyy'
format.">current date in
`dd.mm.yyyy'
format.
">
current date in <samp>`dd.mm.yyyy'</samp> format.
current date in
`dd.mm.yyyy'
format.
`$F'
<a href=
`dd.mm.yyyy'
format.">file modification date in
`dd.mm.yyyy'
format.
">
file modification date in <samp>`dd.mm.yyyy'</samp> format.
file modification date in
`dd.mm.yyyy'
format.
`#h'
<a href=
medium height in PostScript points
">
medium height in PostScript points
medium height in PostScript points
`$l^'
<a href=
top most line number of the current page
">
top most line number of the current page
top most line number of the current page
`$l.'
<a href=
use
`--right-title="$q:$l^-$l."'
.
">
current line number. To print the page number and the line interval in the right title
use
`--right-title="$q:$l^-$l."'
.
`$l#'
<a href=
number of lines in the current file.
">
number of lines in the current file.
number of lines in the current file.
`%m'
<a href=
`.'
character">the host name up to the first
`.'
character
">
the host name up to the first <samp>`.'</samp> character
the host name up to the first
`.'
character
`%M'
<a href=
the full host name
">
the full host name
the full host name
`\n'
<a href=
`\n'
(
new line
).">the character
`\n'
(
new line
).
">
the character <samp>`\n'</samp> (<code>new line</code>).
the character
`\n'
(
new line
).
`%n'
<a href=
`user.login'
(see section
#SEC45
Predefined Variables
).">shortcut for the value of the variable
`user.login'
(see section
#SEC45
Predefined Variables
).
">
shortcut for the value of the variable <samp>`user.login'</samp> (see section <a href=
Predefined Variables
).">shortcut for the value of the variable
`user.login'
(see section
#SEC45
Predefined Variables
).
`$n'
<a href=
input file name without the directory part.
">
input file name without the directory part.
input file name without the directory part.
`%N'
<a href=
`user.name'
(see section
#SEC45
Predefined Variables
).">shortcut for the value of the variable
`user.name'
(see section
#SEC45
Predefined Variables
).
">
shortcut for the value of the variable <samp>`user.name'</samp> (see section <a href=
Predefined Variables
).">shortcut for the value of the variable
`user.name'
(see section
#SEC45
Predefined Variables
).
`$N'
<a href=
on
`foo.c'
, it will produce
`foo'
).
">
input file name without the directory
on
`foo.c'
, it will produce
`foo'
).
`#o'
<a href=
argument of
`-P'
, or of
`-o'
).
">
name of the output
argument of
`-P'
, or of
`-o'
).
`#O'
<a href=
then the name of the file. If the output is a symbolic printer (see section
#SEC39
Your Printers
), the result of the evaluation. For instance, if the symbolic printer
`file'
is defined as
`> $n.%.'
, then
`#O'
returns
`foo.c.ps'
when printing
`foo.c'
to PostScript.
`#o'
would have returned
`file'
.
">
name of the output
then the name of the file. If the output is a symbolic printer (see section
#SEC39
Your Printers
), the result of the evaluation. For instance, if the symbolic printer
`file'
is defined as
`> $n.%.'
, then
`#O'
returns
`foo.c.ps'
when printing
`foo.c'
to PostScript.
`#o'
would have returned
`file'
.
`#p'
<a href=
`--pages=1-10,15'
">then
`#p'
evaluates to
`1-3,8'
.
">
the range of the page to print from this page. For instance if the user asked <samp>`--pages=1-10,15'</samp>
then
`#p'
evaluates to
`1-3,8'
.
`$p^'
<a href=
`$p.'
">is also the number of the last page of this file appearing on this sheet.
">
number of the first page of this file appearing on the current sheet. Note that <samp>`$p.'</samp>
is also the number of the last page of this file appearing on this sheet.
`$p-'
<a href=
`$p^-$p.'
">otherwise it is equal to
`$p.'
.
">
interval of the page number of the current file appearing on the current sheet. It is the same as <samp>`$p^-$p.'</samp>
otherwise it is equal to
`$p.'
.
`%p.'
<a href=
current page number
">
current page number
current page number
`$p.'
<a href=
page number for this file
">
page number for this file
page number for this file
`%p#'
<a href=
total number of pages printed
">
total number of pages printed
total number of pages printed
`$p#'
<a href=
number of pages of the current file
">
number of pages of the current file
number of pages of the current file
`$p<'
<a href=
number of the first page of the current file
">
number of the first page of the current file
number of the first page of the current file
`$p>'
<a href=
number of the last page of the current file
">
number of the last page of the current file
number of the last page of the current file
`%q'
<a href=
`Page %p.'
">localized equivalent for
`Page %p.'
">
localized equivalent for <samp>`Page %p.'</samp>
localized equivalent for
`Page %p.'
`$q'
<a href=
`Page $p.'
">localized equivalent for
`Page $p.'
">
localized equivalent for <samp>`Page $p.'</samp>
localized equivalent for
`Page $p.'
`%Q'
<a href=
`Page %p./%p#'
">localized equivalent for
`Page %p./%p#'
">
localized equivalent for <samp>`Page %p./%p#'</samp>
localized equivalent for
`Page %p./%p#'
`$Q'
<a href=
`Page $p./$p#'
">localized equivalent for
`Page $p./$p#'
">
localized equivalent for <samp>`Page $p./$p#'</samp>
localized equivalent for
`Page $p./$p#'
`$s<'
<a href=
number of the first sheet of the current file
">
number of the first sheet of the current file
number of the first sheet of the current file
`%s.'
<a href=
current sheet number
">
current sheet number
current sheet number
`$s.'
<a href=
sheet number for the current file
">
sheet number for the current file
sheet number for the current file
`$s>'
<a href=
number of the last sheet of the current file
">
number of the last sheet of the current file
number of the last sheet of the current file
`%s#'
<a href=
total number of sheets
">
total number of sheets
total number of sheets
`$s#'
<a href=
number of sheets of the current file
">
number of sheets of the current file
number of sheets of the current file
`%t'
<a href=
current time in 12-hour am/pm format
">
current time in 12-hour am/pm format
current time in 12-hour am/pm format
`$t'
<a href=
file modification time in 12-hour am/pm format
">
file modification time in 12-hour am/pm format
file modification time in 12-hour am/pm format
`$t1'
`$t2'
`$t3'
<a href=
according to the style. For instance, in
mail-folder
style, tag 1 is the title of the mail, and tag 2 its author.
">
Content of tag 1
according to the style. For instance, in
mail-folder
style, tag 1 is the title of the mail, and tag 2 its author.
`%T'
<a href=
`hh:mm'
">current time in 24-hour format
`hh:mm'
">
current time in 24-hour format <samp>`hh:mm'</samp>
current time in 24-hour format
`hh:mm'
`$T'
<a href=
`hh:mm'
">file modification time in 24-hour format
`hh:mm'
">
file modification time in 24-hour format <samp>`hh:mm'</samp>
file modification time in 24-hour format
`hh:mm'
`#v'
<a href=
number of virtual sheets
">
number of virtual sheets
number of virtual sheets
`%V'
<a href=
the version string of a2ps@c.
">
the version string of a2ps@c.
the version string of a2ps@c.
`#w'
<a href=
medium width in PostScript points
">
medium width in PostScript points
medium width in PostScript points
`%W'
<a href=
`mm/dd/yy'
format">current date in
`mm/dd/yy'
format
">
current date in <samp>`mm/dd/yy'</samp> format
current date in
`mm/dd/yy'
format
`$W'
<a href=
`mm/dd/yy'
format">file modification date in
`mm/dd/yy'
format
">
file modification date in <samp>`mm/dd/yy'</samp> format
file modification date in
`mm/dd/yy'
format
[
#SEC33
<
]
[
#SEC35
>
]
[
#SEC19
<<
]
[
#SEC1
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4. Configuration Files
<a href=
they are:
">
a2psorder
they are:
<a href=
`/usr/local/etc/a2ps.cfg'
) unless you have defined the environment variable
`A2PS_CONFIG'
">in which case a2ps
">
the system configuration file (usually <tt>`/usr/local/etc/a2ps.cfg'</tt>) unless you have defined the environment variable <samp>`A2PS_CONFIG'</samp>
in which case a2ps
<a href=
`$HOME/.a2ps/a2psrc'
)">the user's home configuration file (
`$HOME/.a2ps/a2psrc'
)
">
the user's home configuration file (<tt>`$HOME/.a2ps/a2psrc'</tt>)
the user's home configuration file (
`$HOME/.a2ps/a2psrc'
)
<a href=
`./.a2psrc'
)">the local file (
`./.a2psrc'
)
">
the local file (<tt>`./.a2psrc'</tt>)
the local file (
`./.a2psrc'
)
<a href=
lpr
command) and architecture independent information (such as the type of your printers)">
`a2ps-site.cfg'
(see section
#SEC35
Including Configuration Files
) is included from
`a2ps.cfg'
.
">
Because a2pslocal <code>lpr</code> command) and architecture independent information (such as the type of your printers)
`a2ps-site.cfg'
(see section
#SEC35
Including Configuration Files
) is included from
`a2ps.cfg'
.
<a href=
`a2ps.cfg'
is updated when you update a2ps@c, while
`a2ps-site.cfg'
is not">to preserve local definitions.
">
The file <tt>`a2ps.cfg'</tt> is updated when you update a2ps@c, while <tt>`a2ps-site.cfg'</tt> is not
to preserve local definitions.
<a href=
empty lines and lines starting with
`#'
are comments.
">
In the configuration files
empty lines and lines starting with
`#'
are comments.
<a href=
The other lines have all the following form:
">
The other lines have all the following form:
The other lines have all the following form:
<a href=
Topic:
Arguments
">
Topic:
Arguments
">
<var>Topic:</var> <var>Arguments</var>
Topic:
Arguments
<a href=
Topic:
is a keyword related to what you are customizing">provided that the last character of a line to continue is a
`\'
.
">
where <var>Topic:</var> is a keyword related to what you are customizing
provided that the last character of a line to continue is a
`\'
.
<a href=
each
Topic:
is detailed.
">
In the following sections
each
Topic:
is detailed.
#SEC35
4.1 Including Configuration Files
Isolating site specific values
#SEC36
4.2 Your Library Path
Setting the files search path
#SEC37
4.3 Your Default Options
Default state of a2ps
#SEC38
4.4 Your Media
Sheets dimensions
#SEC39
4.5 Your Printers
How to access the printers
#SEC40
4.6 Your Shortcuts
Your very own command line options
#SEC41
4.7 Your PostScript magic number
Handling very old printers
#SEC42
4.8 Your Page Labels
Page names as in
Ghostview
#SEC43
4.9 Your Variables
Short cut for long sequences
#SEC46
4.10 Your Delegations
Delegating some files to other filters
#SEC50
4.11 Your Internal Details
Details you might want to tune
[
#SEC34
<
]
[
#SEC36
>
]
[
#SEC34
<<
]
[
#SEC34
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.1 Including Configuration Files
Configuration Setting:
Include:
file
<a href=
file
. if
file
is a relative path (i.e.">then it is relatively to the current configuration file.
">
Include (read) the configuration <var>file</var>. if <var>file</var> is a relative path (i.e.
then it is relatively to the current configuration file.
<a href=
`etc/a2ps.cfg'
: you may tune your printers etc. in a separate file for easy upgrade of a2ps">This is especially useful for the site specific configuration file
`etc/a2ps.cfg'
: you may tune your printers etc. in a separate file for easy upgrade of a2ps
">
This is especially useful for the site specific configuration file <tt>`etc/a2ps.cfg'</tt>: you may tune your printers etc. in a separate file for easy upgrade of a2ps
This is especially useful for the site specific configuration file
`etc/a2ps.cfg'
: you may tune your printers etc. in a separate file for easy upgrade of a2ps
[
#SEC35
<
]
[
#SEC37
>
]
[
#SEC34
<<
]
[
#SEC34
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.2 Your Library Path
<a href=
you can use:
">
To define the default library path
you can use:
Configuration Setting:
LibraryPath:
path
<a href=
path
.">Set the library path the
path
.
">
Set the library path the <var>path</var>.
Set the library path the
path
.
Configuration Setting:
AppendLibraryPath:
path
<a href=
path
at the end of the current library path.">Add
path
at the end of the current library path.
">
Add <var>path</var> at the end of the current library path.
Add
path
at the end of the current library path.
Configuration Setting:
PrependLibraryPath:
path
<a href=
path
at the beginning of the current library path.">Add
path
at the beginning of the current library path.
">
Add <var>path</var> at the beginning of the current library path.
Add
path
at the beginning of the current library path.
<a href=
because the system's configuration has certainly been built to cope with your system's peculiarities. Use
`AppendLibraryPath:'
and
`PrependLibraryPath:'
.
">
Note that for users configuration files
because the system's configuration has certainly been built to cope with your system's peculiarities. Use
`AppendLibraryPath:'
and
`PrependLibraryPath:'
.
[
#SEC36
<
]
[
#SEC38
>
]
[
#SEC34
<<
]
[
#SEC34
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.3 Your Default Options
Configuration Setting:
Options:
options+
<a href=
#SEC19
Invoking a2ps
).">Give a2pssequence of regular command line options (see section
#SEC19
Invoking a2ps
).
">
Give a2pssequence of regular command line options (see section <a href=
Invoking a2ps
).">Give a2pssequence of regular command line options (see section
#SEC19
Invoking a2ps
).
<a href=
Letter
as medium">then use:
">
It is the correct way to define the default behavior you expect from a2ps@c. If for instance you want to use <code>Letter</code> as medium
then use:
<a href=
Options: --medium=Letter
">
Options: --medium=Letter
Options: --medium=Letter
<a href=
`--medium=Letter'
at run time.">It is exactly the same as always giving a2ps
`--medium=Letter'
at run time.
">
It is exactly the same as always giving a2ps<samp>`--medium=Letter'</samp> at run time.
It is exactly the same as always giving a2ps
`--medium=Letter'
at run time.
<a href=
The quoting mechanism is the same as that of a shell. For instance
">
The quoting mechanism is the same as that of a shell. For instance
The quoting mechanism is the same as that of a shell. For instance
<a href=
Options: --right-title="Page $p" --center-title="Hello World!" Options: --title="arg 'Jack said \\\"hi\\\"' has double quotes"
">
Options: --right-title=&quot;Page $p&quot; --center-title=&quot;Hello World!&quot; Options: --title=&quot;arg 'Jack said \\\&quot;hi\\\&quot;' has double quotes&quot;
Options: --right-title="Page $p" --center-title="Hello World!" Options: --title="arg 'Jack said \\\"hi\\\"' has double quotes"
[
#SEC37
<
]
[
#SEC39
>
]
[
#SEC34
<<
]
[
#SEC34
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.4 Your Media
Configuration Setting:
Medium:
name
dimensions
<a href=
name
to have the
dimensions
(in PostScript points">1/72 of inch).
">
Define the medium <var>name</var> to have the <var>dimensions</var> (in PostScript points
1/72 of inch).
<a href=
There are two formats supported:
">
There are two formats supported:
There are two formats supported:
long
<a href=
and the size of the printable area:
">
in which you must give both the size of the whole sheet
and the size of the printable area:
<a href=
name
w
h
llx
lly
urx
ury
Medium: A4dj 595 842 24 50 571 818"># A4 for Desk Jets #
name
w
h
llx
lly
urx
ury
Medium: A4dj 595 842 24 50 571 818
">
# A4 for Desk Jets # <var>name</var> <var>w</var> <var>h</var> <var>llx</var> <var>lly</var> <var>urx</var> <var>ury</var> Medium: A4dj 595 842 24 50 571 818
# A4 for Desk Jets #
name
w
h
llx
lly
urx
ury
Medium: A4dj 595 842 24 50 571 818
<a href=
w
x
h
are the dimension of the sheet">upper right x and y.
">
where <var>w</var>x<var>h</var> are the dimension of the sheet
upper right x and y.
short
<a href=
in which a surrounding margin of 24 points is used
">
in which a surrounding margin of 24 points is used
in which a surrounding margin of 24 points is used
<a href=
name
w
h
Medium: A4 595 842"># A4 #
name
w
h
Medium: A4 595 842
">
# A4 # <var>name</var> <var>w</var> <var>h</var> Medium: A4 595 842
# A4 #
name
w
h
Medium: A4 595 842
<a href=
is the same as
">
is the same as
is the same as
<a href=
name
w
h
Medium: A4 595 842 24 24 571 818"># A4 #
name
w
h
Medium: A4 595 842 24 24 571 818
">
# A4 # <var>name</var> <var>w</var> <var>h</var> Medium: A4 595 842 24 24 571 818
# A4 #
name
w
h
Medium: A4 595 842 24 24 571 818
[
#SEC38
<
]
[
#SEC40
>
]
[
#SEC34
<<
]
[
#SEC34
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.5 Your Printers
<a href=
the interface is still the same. Actually, the interface is so flexible, that you should understand `named destination' when we write `printer'.
">
A general scheme is used
the interface is still the same. Actually, the interface is so flexible, that you should understand `named destination' when we write `printer'.
Configuration Setting:
Printer:
name
PPD-key
destination
Configuration Setting:
Printer:
name
destination
Configuration Setting:
Printer:
name
PPD-key
<a href=
`-P
name
'
is given. If
PPD-key
is given">used that of the
`UnknownPrinter:'
.
">
Specify the destination of the output when the option <samp>`-P <var>name</var>'</samp> is given. If <var>PPD-key</var> is given
used that of the
`UnknownPrinter:'
.
<a href=
destination
must be of one of the following forms:">The
destination
must be of one of the following forms:
">
The <var>destination</var> must be of one of the following forms:
The
destination
must be of one of the following forms:
`|
command
'
<a href=
command
.">in which case the output is piped into
command
.
">
in which case the output is piped into <var>command</var>.
in which case the output is piped into
command
.
`>
file
'
<a href=
file
.">in which case the output is saved into
file
.
">
in which case the output is saved into <var>file</var>.
in which case the output is saved into
file
.
Configuration Setting:
UnknownPrinter:
[
PPD-key
]
destination
<a href=
`-P
name
'
is given">but there is no
`Printer:'
entry for
name
.
">
Specify the destination of the output when when the option <samp>`-P <var>name</var>'</samp> is given
but there is no
`Printer:'
entry for
name
.
Configuration Setting:
DefaultPrinter:
[
PPD-key
]
destination
<a href=
`-d'
(send to default output) is given.">Specify the destination of the output when when the option
`-d'
(send to default output) is given.
">
Specify the destination of the output when when the option <samp>`-d'</samp> (send to default output) is given.
Specify the destination of the output when when the option
`-d'
(send to default output) is given.
<a href=
destination
(see section
#SEC30
Escapes
). Recall that
`#o'
is evaluated to the destination name">the argument given to
`-P'
.
">
Escapes expansion is performed on <var>destination</var> (see section <a href=
Escapes
). Recall that
`#o'
is evaluated to the destination name">the argument given to
`-P'
.
<a href=
For instance
">
For instance
For instance
<a href=
# My Default Printer is called dominique DefaultPrinter: | lp -d dominique # `a2ps foo.c -P bar' will pipe into `lp -d bar' UnknownPrinter: | lp -d #o # `a2ps -P foo' saves into the file `foo' Printer: foo > foo.ps Printer: wc | wc Printer: lw | lp -d printer-with-a-rather-big-name # E.g. `a2ps foo.c bar.h -P file' will save into `foo.c.ps' Printer: file > $n.#. # E.g. `a2ps foo.c bar.h -P home' will save into `foo.ps' # in user's home Printer: home > ${HOME}/$N.#. # Here we address a printer which is not PostScript Printer: deskj | gs -q -sDEVICE=ljet3d -sOutputFile=- - \ | lpr -P laserwriter -h -l
">
# My Default Printer is called dominique DefaultPrinter: | lp -d dominique # `a2ps foo.c -P bar' will pipe into `lp -d bar' UnknownPrinter: | lp -d #o # `a2ps -P foo' saves into the file `foo' Printer: foo &gt; foo.ps Printer: wc | wc Printer: lw | lp -d printer-with-a-rather-big-name # E.g. `a2ps foo.c bar.h -P file' will save into `foo.c.ps' Printer: file &gt; $n.#. # E.g. `a2ps foo.c bar.h -P home' will save into `foo.ps' # in user's home Printer: home &gt; ${HOME}/$N.#. # Here we address a printer which is not PostScript Printer: deskj | gs -q -sDEVICE=ljet3d -sOutputFile=- - \ | lpr -P laserwriter -h -l
# My Default Printer is called dominique DefaultPrinter: | lp -d dominique # `a2ps foo.c -P bar' will pipe into `lp -d bar' UnknownPrinter: | lp -d #o # `a2ps -P foo' saves into the file `foo' Printer: foo > foo.ps Printer: wc | wc Printer: lw | lp -d printer-with-a-rather-big-name # E.g. `a2ps foo.c bar.h -P file' will save into `foo.c.ps' Printer: file > $n.#. # E.g. `a2ps foo.c bar.h -P home' will save into `foo.ps' # in user's home Printer: home > ${HOME}/$N.#. # Here we address a printer which is not PostScript Printer: deskj | gs -q -sDEVICE=ljet3d -sOutputFile=- - \ | lpr -P laserwriter -h -l
<a href=
and non-PostScript printer owners should take advantage in getting good configuration of these entries.
">
MS-DOS users
and non-PostScript printer owners should take advantage in getting good configuration of these entries.
[
#SEC39
<
]
[
#SEC41
>
]
[
#SEC34
<<
]
[
#SEC34
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.6 Your Shortcuts
<a href=
You can define some kind of `Macro Options' which stand for a set of options.
">
You can define some kind of `Macro Options' which stand for a set of options.
You can define some kind of `Macro Options' which stand for a set of options.
Configuration Setting:
UserOption:
shortcut
options...
<a href=
shortcut
to be the list of
options...
. When a2psis called with
`-=
shortcut
'
(or
`--user-option=
shortcut
'
)">consider the list of
options...
.
">
Define the <var>shortcut</var> to be the list of <var>options...</var>. When a2psis called with <samp>`-=<var>shortcut</var>'</samp> (or <samp>`--user-option=<var>shortcut</var>'</samp>)
consider the list of
options...
.
<a href=
Examples are
">
Examples are
Examples are
<a href=
and stripping `useless' headers. UserOption: mail -Email -g --strip=1
">
# This emulates a line printer: no features at all # call a2ps -=lp to use it UserOption: lp -1m --pretty-print=plain -B --borders=no # When printing mail
and stripping `useless' headers. UserOption: mail -Email -g --strip=1
[
#SEC40
<
]
[
#SEC42
>
]
[
#SEC34
<<
]
[
#SEC34
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.7 Your PostScript magic number
<a href=
a2psAdobe said
">
a2psAdobe said
a2psAdobe said
<a href=
Thou shalt start your PostScript DSC conformant files with
">
Thou shalt start your PostScript DSC conformant files with
Thou shalt start your PostScript DSC conformant files with
<a href=
%!PS-Adobe-3.0
">
%!PS-Adobe-3.0
%!PS-Adobe-3.0
<a href=
The bad news is that some printers will reject this header. Then you may change this header without any worry since the PostScript produced by a2psare no PostScript printers that don't understand these files.
.">
The bad news is that some printers will reject this header. Then you may change this header without any worry since the PostScript produced by a2psare no PostScript printers that don't understand these files.
The bad news is that some printers will reject this header. Then you may change this header without any worry since the PostScript produced by a2psare no PostScript printers that don't understand these files.
.
Configuration Setting:
OutputFirstLine:
magic-number
Specify the header of the produced PostScript file to be <var>magic-number</var>. Typical values include <samp>`%!PS-Adobe-2.0'</samp>
or just
`%!'
.
[
#SEC41
<
]
[
#SEC43
>
]
[
#SEC34
<<
]
[
#SEC34
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.8 Your Page Labels
In the PostScript file is dropped information on where sheets begin and end
2 etc. With this information can be also stored a label, i.e., a human readable text (typically the logical page numbers), which is for instance what
Ghostview
shows as the list of page numbers.
a2ps
a2ps
Configuration Setting:
PageLabelFormat:
format
Specify the <var>format</var> to use to label the PostScript pages. <var>format</var> can use Escapes (see section <a href=
Escapes
). Two variables are predefined for this:
`#{pl.short}'
and
`#{pl.long}'
.">Specify the
format
to use to label the PostScript pages.
format
can use Escapes (see section
#SEC30
Escapes
). Two variables are predefined for this:
`#{pl.short}'
and
`#{pl.long}'
.
[
#SEC42
<
]
[
#SEC44
>
]
[
#SEC34
<<
]
[
#SEC34
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.9 Your Variables
There are many places in a2psof extending things. It once became clear that <em>variables</em> where needed in a2ps@c.
There are many places in a2psof extending things. It once became clear that
variables
where needed in a2ps@c.
#SEC44
4.9.1 Defining Variables
Syntax and conventions
#SEC45
4.9.2 Predefined Variables
Builtin variables
[
#SEC43
<
]
[
#SEC45
>
]
[
#SEC34
<<
]
[
#SEC43
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.9.1 Defining Variables
Configuration Setting:
Variable:
key
value
Define the escape <samp>`#{<var>key</var>}'</samp> to be a short cut for <var>value</var>. <var>key</var> must not have any character from <samp>`:(){}'</samp>.
Define the escape
`#{
key
}'
to be a short cut for
value
.
key
must not have any character from
`:(){}'
.
As as example
which encloses all the option passing one would like. Delegations are then easier to write:
Variable: psnup psnup -#v -q #?j|-d|| #?r||-c| -w#w -h#h
Variable: psnup psnup -#v -q #?j|-d|| #?r||-c| -w#w -h#h
It is strongly suggested to follow a <samp>`.'</samp> (dot) separated hierarchy
starting with:
`del'
for variables that are related to delegations.
for variables that are related to delegations.
`pro'
for variables used in prologues (see section <a href=
Designing PostScript Prologues
). Please">
`pro.matrix.gray'
).
`ps'
for variables related to PostScript matters
the header etc.
`pl'
for page label formats. See section <a href=
Your Page Labels
">the option
`--page-label'
in
#SEC26
Input Options
.
`toc'
for toc formats. See the option <samp>`--toc'</samp> in <a href=
Input Options
.">for toc formats. See the option
`--toc'
in
#SEC26
Input Options
.
`user'
for user related information. See section <a href=
Predefined Variables
.">for user related information. See section
#SEC45
Predefined Variables
.
This naming convention has not fully stabilized. We apologize for the inconvenience this might cause to users.
This naming convention has not fully stabilized. We apologize for the inconvenience this might cause to users.
[
#SEC44
<
]
[
#SEC46
>
]
[
#SEC34
<<
]
[
#SEC43
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.9.2 Predefined Variables
There are a few predefined variables.  The fact that a2psat startup changes nothing to their status: they can be modified like
any other variable using
--define
(see section
#SEC22
Global Options
).
In what follows, there are numbers (i) like this, or (ii) this.  It
means that a2ps(non empty value), this is the value given to the variable.  Otherwise
it tries solution (ii), etc.  The rationale behind the order is usually
from user modifiable values (e.g. environment variables) through
system's hard coded values (e.g., calls to
getpwuid
) and finally
arbitrary values.
`user.comments'
Comments on the user.  Computed by (i) the system's database (the part
of
pw_gecos
after the first
`,'
), (ii) not defined.
`user.home'
The user's home directory.  Determined by (i) the environment variable
HOME
, (ii) the system's database (using
getpwuid
), (iii)
the empty string.
`user.host'
The user's host name.  Assigned from (i) the system (
gethostname
or
uname
), (ii) the empty string.
`user.login'
The user's login (e.g.
`bgates'
).  Computed by (i) the environment
variable
LOGNAME
, (ii) the environment variable
USERNAME
,
(iii) the system's database (using
getpwuid
), (iv) the translated
string
`user'
.
`user.name'
The user's name (e.g.
`William Gates'
).  Computed by (i) the
system's database (
pw_gecos
up to the first
`,'
), (ii)
capitalized value of the variable
`user.login'
unless it was the
translated string
`user'
, (iii) the translated string
`Unknown
User'
.
[
#SEC45
<
]
[
#SEC47
>
]
[
#SEC34
<<
]
[
#SEC34
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.10 Your Delegations
There are some files you don't really want a2pstypically page description files (e.g., PostScript files,
roff
files,
etc.).  You can let a2psapplications.  The behavior at run time depends upon the option
`--delegate'
(see section
#SEC26
Input Options
).
#SEC47
4.10.1 Defining a Delegation
Syntax of the definitions of the delegations
#SEC48
4.10.2 Guide Line for Delegations
What should be respected
#SEC49
4.10.3 Predefined Delegations
Making the best use of these delegations
[
#SEC46
<
]
[
#SEC48
>
]
[
#SEC34
<<
]
[
#SEC46
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.10.1 Defining a Delegation
Configuration Setting:
Delegation:
name
in
:
out
command
Define the delegation
name
.  It is to be applied upon files of
type
in
when output type is
out
#FOOT2
(2)
thanks to
command
.  Both
in
and
out
are a2psdefined in
`sheets.map'
(see section
#SEC100
The Entry in
`sheets.map'
).
command
should produce the file on its standard output.  Of course
escapes substitution is performed on
command
(see section
#SEC30
Escapes
).
In particular,
command
should use the input file
`$f'
.
# In general, people don't want to pretty-print PostScript files.
# Pass the PostScript files to psnup
Delegation: PsNup ps:ps \
psselect #?V||-q| -p#?p|#p|-| $f | \
psnup -#v -q #?j|-d|| #?r||-c| -w#w -h#h
Advantage should be taken from the variables, to encapsulate the
peculiarities of the various programs.
# Passes the options to psnup.
# The files (in and out) are to be given
Variable: psnup psnup -#v #?V||-q| #?j|-d|| #?r||-c| -w#w -h#h
# Passes to psselect for PS page selection
Variable: psselect psselect #?V||-q| -p#?p|#p|-|
# In general, people don't want to pretty-print PostScript files.
# Pass the PostScript files to psnup
Delegation: PsNup ps:ps     #{psselect} $f | #{psnup}
Temporary file names (
`#f0'
to
`#f9'
) are available for
complex commands.
# Pass DVI files to dvips.
# A problem with dvips is that even on failure it dumps its prologue,
# hence it looks like a success (output is produced).
# To avoid that, we use an auxiliary file and a conditional call to
# psnup instead of piping.
Delegation: dvips dvi:ps    #{dvips} $f -o #f0 && #{psnup} #f0
[
#SEC47
<
]
[
#SEC49
>
]
[
#SEC34
<<
]
[
#SEC46
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.10.2 Guide Line for Delegations
First of all, select carefully the applications you will use for the
delegations.  If a filter is known to cause problems, try to avoid it in
delegations
#FOOT3
(3)
.  As a thumb rule, you should check that the PostScript
generating applications produce files that start by:
%!PS-Adobe-3.0
a2psin order to output correctly the page device definitions.  It can happen
that your filters don't output this section.  In that case, you should
insert a call to
fixps
right after the PostScript generation:
########## ROFF files
# Pass the roff files to groff.  Ask grog how groff should be called.
# Use fixps to ensure there is a %%BeginSetup/%%EndSetup section.
Delegation: Groff roff:ps	\
eval `grog -Tps '$f'` | fixps #?V!!-q! | #{d.psselect} | #{d.psnup}
There are some services expected from the delegations.  The delegations
you may write should honor:
the input file
available via the escape
`$f'
.  You should be aware that there are
people who have great fun having spaces or dollars in their file names,
so you probably should always use
`'$f''
.  Some other variables are
affected.  Yes, I know, we need a special mechanism for
`''
itself.
Well, we'll see that later
`;-)'
.
the medium
the dimension of the medium selected by the user are available through
`#w'
and
`#h'
.
the page layout
the number of virtual pages is
`#v'
.
the page range
the page range (in a form
`1-2,4-6,10-'
for instance) is available
by
`#p'
.
the verbosity level
please, do not make your delegations verbose by default.  The silent
mode should always be requested, unless
`#?V'
is set (see the above
example with
groff
).
If ever you need several commands, do not use
`;'
to separate them,
since it may prevent detection of failure.  Use
`&&'
instead.
The slogan "
the sooner, the better
" should be applied here: in
the processing chain, it is better to ask a service to the first
application that supports it.  An example will make it clear: when
processing a
DVI
file,
dvips
knows better the page numbers
than
psselect
would.  So a
DVI
to PostScript delegation
should ask the page selection (
`#p'
) to
dvips
, instead of
using
psselect
later in the chain.  An other obvious reason here
is plain efficiency (globally, less data is processed).
[
#SEC48
<
]
[
#SEC50
>
]
[
#SEC34
<<
]
[
#SEC46
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.10.3 Predefined Delegations
The purpose of this section is not to document all the predefined
delegations, for this you should read the comments in the system
configuration file
`a2ps.cfg'
.  We just want to explain some choices,
and give hints on how to make the best use of these delegations.
Delegation:
dvips
(DVI to PostScript)
There is a problem when you use a naive implementation of this
delegation: landscape jobs are not recognized, and therefore n-upping
generally fails miserably.  Therefore, a2psis landscape by looking for the keyword
`landscape'
in it, using
strings(1)
:
Delegation: dvips dvi:ps\
if strings $f | sed 3q | fgrep landscape > /dev/null 2>&1; then \
#{d.dvips} -T#hpt,#wpt $f -o #f0 && #?o|cat|#{d.psnup} -r| #f0;\
else \
#{d.dvips} $f -o #f0 && #{d.psnup} #f0; \
fi
In order to have that rule work correctly, it is expected from the
TeX, or LaTeX file to include something like:
\renewcommand{\printlandscape}{\special{landscape}}
\printlandscape
in the preamble.
We don't use a pipe because dvips always outputs data (its prologue)
even if it fails, what prevents error detection.
Delegation:
LaTeX
(LaTeX to DVI)
We use a modern version of the shell script
texi2dvi
, from the
package
Texinfo
, which runs
makeindex
,
bibtex
and
latex
as many times as needed.  You should be aware that if the
file includes files from
other
directories, it may miss some
compilation steps.  Other cases (most typical) are well handled.
[
#SEC49
<
]
[
#SEC51
>
]
[
#SEC34
<<
]
[
#SEC34
Up
]
[
#SEC51
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
4.11 Your Internal Details
There are settings that only meant for a2psyourself.
Configuration Setting:
FileCommand:
command
The command to run to call
file(1)
on a file.  If possible, make
it follow the symbolic links.
[
#SEC50
<
]
[
#SEC52
>
]
[
#SEC34
<<
]
[
#SEC1
Up
]
[
#SEC59
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
5. Library Files
To be general and to allow as much customization as possible, a2psavoids to hard code its knowledge (encodings, PostScript routines,
etc.), and tries to split it in various files.  Hence it needs a path,
i.e., a list of directories, in which it may find the files it needs.
The exact value of this library path is available by
`a2ps
--list=defaults'
.  Typically its value is:
gargantua ~ $ a2ps --list=defaults
Configuration status of a2ps 4.13
More stuff deleted here
Internals:
verbosity level     = 2
file command        = /usr/ucb/file -L
temporary directory =
library path        =
/inf/soft/infthes/demaille/.a2ps
/usr/local/share/a2ps/sheets
/usr/local/share/a2ps/ps
/usr/local/share/a2ps/encoding
/usr/local/share/a2ps/afm
/usr/local/share/a2ps/printers
/usr/local/share/a2ps
You may change this default path through the configuration files
(see section
#SEC36
Your Library Path
).
If you plan to define yourself some files for a2ps@c, they should be in
one of those directories.
#SEC52
5.1 Documentation Format
Special tags to write a documentation
#SEC53
5.2 Map Files
Their general shape and rationale
#SEC54
5.3 Font Files
Using other fonts
#SEC58
5.4 Style Sheet Files
Defining pretty printing rules
[
#SEC51
<
]
[
#SEC53
>
]
[
#SEC51
<<
]
[
#SEC51
Up
]
[
#SEC59
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
5.1 Documentation Format
In various places a documentation can be given.  Since some
parts of this document and of web pages are extracted from documentations,
some tags are needed to provide a better layout.  The format is
a mixture made out of Texinfo like commands, but built so that
quick and easy processing can be made.
These tags are:
`code('
text
`)code'
Typeset
text
like a piece of code.  This should be used
for keys, variables, options etc.  For instance the documentation
of the
bold
prologue mentions the
bw
prologue:
Documentation
This style is meant to replace the old option
code(-b)code of a2ps 4.3.  It is a copy of the
black and white prologue, but in which all the
fonts are in Bold.
EndDocumentation
`href('
link
`)href('
text
`)href'
Specifies a hyper text
link
displayed as
text
.
`@example'
`@end example'
They must be alone on the line.  The text between these tags is
displayed in a code-like fonts.  This should be used for including a
piece of code.  For instance, in the documentation of the
gnuc
style sheet:
documentation is
"Declaration of functions are highlighted"
"emph(only)emph if you start the function name"
"in the first column, and it is followed by an"
"opening parenthesis.  In other words, if you"
"write"
"@example"
"int main (void)"
"@end example"
"it won't work.  Write:"
"@example"
"int"
"main (void)"
"@end example"
end documentation
`@itemize'
`@item'
text
`@end itemize'
Typeset a list of items. The opening and closing tags must be alone on
the line.
[
#SEC52
<
]
[
#SEC54
>
]
[
#SEC51
<<
]
[
#SEC51
Up
]
[
#SEC59
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
5.2 Map Files
Many things are defined through files.  There is a general scheme to
associate an object to the files to use: map files.  They are typically
used to:
-
resolve aliases.  For instance the ISO-8859-1 encoding is also called
ISO Latin 1, or Latin 1 for short.  The
`encoding.map'
file will
map these three names to the same Encoding Description File.
-
cope with broken files systems.  For instance,
the-one-you-know-I-don't-need-to-name cannot handle files named
`Courier-BoldOblique.afm'
: it is the same as
`Courier-Bold.afm'
.  The
`fonts.map'
file is here to associate
a font file name to a font name.
The syntax of these files is:
-
any empty line, or any line starting by a
`#'
is a comment.
-
a line with the format
***
path
requests that the file designated by
path
be included at this
point.
-
any other line has the format
key
value
meaning that when looking for
key
(e.g., name of a font, an
encoding etc.), a2psencoding description file name etc.).
The map files used in a2ps
`encoding.map'
Resolving encodings aliases.
`fonts.map'
Mapping font names to font file names.
`sheets.map'
Rules to decide what style sheet to use.
[
#SEC53
<
]
[
#SEC55
>
]
[
#SEC51
<<
]
[
#SEC51
Up
]
[
#SEC59
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
5.3 Font Files
Even when a PostScript printer knows the fonts you want to use, using
these fonts requires some description files.
#SEC55
5.3.1 Fonts Map File
Mapping a font name to a file name
#SEC56
5.3.2 Fonts Description Files
Needed files to use a Font
#SEC57
5.3.3 Adding More Font Support
Using even more Fonts
[
#SEC54
<
]
[
#SEC56
>
]
[
#SEC51
<<
]
[
#SEC54
Up
]
[
#SEC59
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
5.3.1 Fonts Map File
See section
#SEC53
Map Files
, for a description of the map files.  This file
associates the
font-key
to a
font
name. For instance:
Courier                 pcrr
Courier-Bold            pcrb
Courier-BoldOblique     pcrbo
Courier-Oblique         pcrro
associates to font named
Courier
, the key
pcrr
.  To be
recognized, the font name must be exact:
courier
and
COURIER
are not admitted.
[
#SEC55
<
]
[
#SEC57
>
]
[
#SEC51
<<
]
[
#SEC54
Up
]
[
#SEC59
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
5.3.2 Fonts Description Files
There are two kinds of data a2ps
-
the AFM file (
`
font-key
.afm'
), which describes the metrics
information corresponding to
font
;
-
in the case
font
is not known from the printer, the PFA or PFB
file which is down loaded to the printer.  These files are actually the
PostScript programs which execution produces the characters to be drawn
on the page, in this
font
.
[
#SEC56
<
]
[
#SEC58
>
]
[
#SEC51
<<
]
[
#SEC54
Up
]
[
#SEC59
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
5.3.3 Adding More Font Support
a2psname of the files in which are stored the fonts (see section
#SEC55
Fonts Map File
).  To this end, a very primitive but still useful shell script is
provided:
make_fonts_map.sh
.
First, you need to find the directories which store the fonts you want
to use, and extend the library path so that a2psdirectories.  For instance, add:
AppendLibraryPath: /usr/local/share/ghostscript/fonts
Then run
make_fonts_map.sh
.  It should be located in the
`afm/'
directory of the system's a2ps
`/usr/local/share/a2ps/afm/make_fonts_map.sh'
.
This script asks a2pscollecting
AFM
files, and digging information in them.
Once the script has finished, a file
`fonts.map.new'
was created.
Check its integrity, and if it's correct, either replace the old
`fonts.map'
with it, or rename
`fonts.map.new'
as
`fonts.map'
and place it higher in the the library path (for
instance in your
`~/.a2ps/'
directory).
[
#SEC57
<
]
[
#SEC59
>
]
[
#SEC51
<<
]
[
#SEC51
Up
]
[
#SEC59
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
5.4 Style Sheet Files
The style sheets are defined in various files.  See see section
#SEC65
Pretty Printing
for the structure of these files.  As for most other features,
there is main file, a road map, which defines in which condition a style
sheet should be used (see section
#SEC53
Map Files
).  This file is
`sheets.map'
.
Its format is simple:
style-key
:
patterns
or
include(
file
)
The
patterns
need not be on separate lines.  There are two kinds
of patterns:
/
pattern
/
flags
if the current file name matches
pattern
, then select style
style-key
(i.e. file
`
style-key
.ssh'
).
<
pattern
>
flags
if the result of a call to
file(1)
matches
pattern
, then
select style
style-key
.
Currently
flags
can only be
`i'
, standing for an insentive
match.  Please note that the matching is not truly case insensitive:
rather, a lower case version of the string is compared to the
pattern
as is, i.e., the
pattern
should itself be lower case.
The special
style-key
`binary'
tells a2psthe file should not be printed, and will be ignored, unless option
`--print-anyway'
is given.
If a style name can't be found, the plain style is used.
The map file is read bottom up, so that the ``last'' match is honored.
Two things are to retain from this:
if the file is presented through
stdin
, then a2ps
file(1)
.  However, unless you specify a fake file name with
`--stdin'
, pattern matching upon the name is turn off.  In general
you can expect correct delegations, but almost never pretty printing.
if
file
is wrong on some files, a2psIn this case, do try option
`--guess'
, compare it with the output
of
file
, and if the culprit is
file
, go and complain to
your system administrator :-), or fix it by defining your own filename
pattern matching rules.
Consider the case of Texinfo files as an example (the language in which
this documentation is written).  Files are usually named
`foo.texi'
,
`bar.txi'
, or even
`baz.texinfo'
.
file(1)
is able to recognize Texinfo files:
doc % file a2ps.texi
a2ps.texi: Texinfo source text
Therefore the sheets.map would look like:
# Texinfo files
texinfo:  /*.txi/  /*.texi/  /*.texinfo/
<Texinfo source*>
[
#SEC58
<
]
[
#SEC60
>
]
[
#SEC51
<<
]
[
#SEC1
Up
]
[
#SEC65
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
6. Encodings
a2psuse.  This chapter presents what an encoding is, how the encodings
support is handled within a2ps@c, and some encodings it supports.
#SEC60
6.1 What is an Encoding
The concept of encoding explained
#SEC61
6.2 Encoding Files
How a2ps handles the encodings
[
#SEC59
<
]
[
#SEC61
>
]
[
#SEC59
<<
]
[
#SEC59
Up
]
[
#SEC65
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
6.1 What is an Encoding
This section is actually taken from the web pages of
http://www.alis.com/
Alis Technologies inc.
Document encoding is the most important but also the most sensitive and
explosive topic in Internet internationalization. It is an essential
factor since most of the information distributed over the Internet is in
text format. But the history of the Internet is such that the
predominant - and in some cases the only possible - encoding is the very
limited ASCII, which can represent only a handful of languages, only
three of which are used to any great extent: English, Indonesian and
Swahili.
All the other languages, spoken by more than 90% of the world's
population, must fall back on other character sets. And there is a
plethora of them, created over the years to satisfy writing constraints
and constantly changing technological limitations.  The ISO
international character set registry contains only a small fraction;
IBM's character registry is over three centimeters thick; Microsoft and
Apple each have a bunch of their own, as do other software manufacturers
and editors.
The problem is not that there are too few but rather too many choices,
at least whenever Internet standards allow them. And the surplus is a
real problem; if every Arabic user made his own choice among the three
dozen or so codes available for this language, there is little
likelihood that his "neighbor" would do the same and that they would
thus be able to understand each other. This example is rather extreme,
but it does illustrate the importance of standards in the area of
internationalization. For a group of users sharing the same language to
be able to communicate,
the code used in the shared document must always be identified
(labeling)
they must agree on a small number of codes - only one, if possible
(standards);
their software must recognize and process all codes (versatility)
Certain character sets stand out either because of their status as an
official national or international standard, or simply because of their
widespread use.
First off, there is the ISO 8859 standards series that standardize a
dozen character sets that are useful for a large number of languages
using the Latin, Cyrillic, Arabic, Greek and Hebrew alphabets. These
standards have a limited range of application (8 bits per character, a
maximum of 190 characters, no combining) but where they suffice (as they
do for 10 of the 20 most widely used languages), they should be used on
the Internet in preference to other codes. For all other languages,
national standards should preferably be chosen or, if none are
available, a well-known and widely-used code should be the second
choice.
Even when we limit ourselves to the most widely used standards, the
overabundance remains considerable, and this significantly complicates
life for truly international software developers and users of several
languages, especially when such languages can only be represented by a
single code. It was to resolve this problem that both Unicode and the
ISO 10646 International standard were created. Two standards? Oh no!
Their designers soon realized the problem and were able to cooperate to
the extent of making the character set
repertoires
and coding
identical.
ISO 10646 (and Unicode) contain over 30,000 characters capable of
representing most of the living languages within a single code. All of
these characters, except for the
Han
(Chinese characters also
used in Japanese and Korean), have a name.  And there is still room to
encode the missing languages as soon as enough of the necessary research
is done.  Unicode can be used to represent several languages, using
different alphabets, within the same electronic document.
[
#SEC60
<
]
[
#SEC62
>
]
[
#SEC59
<<
]
[
#SEC59
Up
]
[
#SEC65
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
6.2 Encoding Files
#SEC62
6.2.1 Encoding Map File
Mapping an encoding name to a file name
#SEC63
6.2.2 Encoding Description Files
Specifying an encoding
#SEC64
6.2.3 Some Encodings
Classical or standard encodings
The support of the encodings in a2psto say, adding, removing or changing anything in its support for an encoding
does not require programming, nor even being a programmer.
See section
#SEC60
What is an Encoding
, if you want to know more about this.
[
#SEC61
<
]
[
#SEC63
>
]
[
#SEC59
<<
]
[
#SEC61
Up
]
[
#SEC65
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
6.2.1 Encoding Map File
See section
#SEC53
Map Files
, for a description of the map files.
The meaningful lines of the
`encoding.map'
file have the form:
alias
key
iso-8859-1 latin1
latin1     latin1
l1         latin1
where
alias
specifies any name under which the encoding may be used.  It influences
the option
`--encoding'
, but also the encodings dynamically
required, as for instance in the
mail
style sheet (support for
MIME).
When
encoding
is asked, the lower case version of
encoding
must be equal to
alias
.
key
specifies the prefix of the file describing the encoding
(
`
key
.edf'
,
#SEC63
Encoding Description Files
).
[
#SEC62
<
]
[
#SEC64
>
]
[
#SEC59
<<
]
[
#SEC61
Up
]
[
#SEC65
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
6.2.2 Encoding Description Files
The encoding description file describing the encoding
key
is named
`
key
.edf'
.  It is subject to the same rules as any other
a2ps
-
please make the name portable: alpha-numerical, at most 8 characters,
-
empty lines and lines starting by
`#'
are ignored.
The entries are
`Name:'
Specifies the full name of the encoding.  Please, try to use the
official name if there is one.
Name: ISO-8859-1
`Documentation/EndDocumentation'
Introduces the documentation on the encoding (see section
#SEC52
Documentation Format
).
Typical informations expected are
the other important names this encoding has, and the languages it covers.
Documentation
Also known as ISO Latin 1, or Latin 1.  It is a superset
of ASCII, and covers most West-European languages.
EndDocumentation
`Substitute:'
Introduces a font substitution.  The most common fonts (e.g.,
Courier
,
Times-Roman
...) do not support many encodings
(for instance it does not support Latin 2).  To avoid that Latin 2 users
have to replace everywhere calls to
Courier
, a2psspecify that whenever a font is called in an encoding, then another font
should be used.
For instance in
`iso2.edf'
one can read:
# Fonts from Ogonkify offer full support of ISO Latin 2
Substitute: Courier              Courier-Ogonki
Substitute: Courier-Bold         Courier-Bold-Ogonki
Substitute: Courier-BoldOblique  Courier-BoldOblique-Ogonki
Substitute: Courier-Oblique      Courier-Oblique-Ogonki
`Default:'
Introduces the name of the font that should be used when
a font (not substituted as per the previous item) is called
but provides to poor a support of the encoding.  The
Courier
equivalent is the best choice.
Default: Courier-Ogonki
`Vector:'
Introduces the PostScript encoding vector, that is a list of the 256
PostScript names of the characters.  Note that only the printable
characters are named in PostScript (e.g.,
`bell'
in ASCII
(
^G
) should not be named).  The special name
`.notdef'
is to
be used when the character is not printable.
Warning.
Make sure to use real, official, PostScript names.
Using names such as
`c123'
may be the sign you use unusual names.
On the other hand PostScript names such as
`afii8879'
are common.
[
#SEC63
<
]
[
#SEC65
>
]
[
#SEC59
<<
]
[
#SEC61
Up
]
[
#SEC65
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
6.2.3 Some Encodings
Most of the following information is a courtesy of
http://www.alis.com/
Alis Technologies inc.
and of
mailto:zcyborra@cs.tu-berlin.de
Roman Czyborra
's page about
http://czyborra.com/charsets/
The ISO 8859 Alphabet Soup
.
See section
#SEC60
What is an Encoding
, is an instructive presentation of the
encodings.
The known encodings are:
Encoding:
ASCII
(
`ascii.edf'
)
US-ASCII.
Encoding:
HPRoman
(
`hp.edf'
)
The 8 bits Roman encoding for HP.
Encoding:
IBM-CP437
(
`ibm-cp437.edf'
)
This encoding is meant to be used for PC files with drawing lines.
Encoding:
IBM-CP850
(
`ibm-cp850.edf'
)
Several characters may be missing, especially Greek letters and some
mathematical symbols.
Encoding:
ISO-8859-1
(
`iso1.edf'
)
The ISO-8859-1 character set, often simply referred to as Latin 1,
covers most West European languages, such as French, Spanish, Catalan,
Basque, Portuguese, Italian, Albanian, Rhaeto-Romanic, Dutch, German,
Danish, Swedish, Norwegian, Finnish, Faroese, Icelandic, Irish,
Scottish, and English, incidentally also Afrikaans and Swahili, thus
in effect also the entire American continent, Australia and the
southern two-thirds of Africa. The lack of the ligatures Dutch IJ,
French OE and ,,German`` quotation marks is considered tolerable.
The lack of the new C=-resembling Euro currency symbol U+20AC has
opened the discussion of a new Latin0.
Encoding:
ISO-8859-2
(
`iso2.edf'
)
The Latin 2 character set supports the Slavic languages of Central
Europe which use the Latin alphabet. The ISO-8859-2 set is used for
the following languages: Czech, Croat, German, Hungarian, Polish,
Romanian, Slovak and Slovenian.
Support is provided thanks to Ogonkify.
Encoding:
ISO-8859-3
(
`iso3.edf'
)
This character set is used for Esperanto, Galician, Maltese and Turkish.
Support is provided thanks to Ogonkify.
Encoding:
ISO-8859-4
(
`iso4.edf'
)
Some letters were added to the ISO-8859-4 to support languages such as
Estonian, Latvian and Lithuanian. It is an incomplete precursor of the
Latin 6 set.
Support is provided thanks to Ogonkify.
Encoding:
ISO-8859-5
(
`iso5.edf'
)
The ISO-8859-5 set is used for various forms of the Cyrillic
alphabet. It supports Bulgarian, Byelorussian, Macedonian, Serbian and
Ukrainian.
The Cyrillic alphabet was created by St. Cyril in the 9th century from
the upper case letters of the Greek alphabet. The more ancient
Glagolithic (from the ancient Slav glagol, which means "word"), was
created for certain dialects from the lower case Greek letters. These
characters are still used by Dalmatian Catholics in their liturgical
books. The kings of France were sworn in at Reims using a Gospel in
Glagolithic characters attributed to St. Jerome.
Note that Russians seem to prefer the KOI8-R character set to the ISO
set for computer purposes. KOI8-R is composed using the lower half
(the first 128 characters) of the corresponding American ASCII
character set.
Encoding:
ISO-8859-7
(
`iso7.edf'
)
ISO-8859-7 was formerly known as ELOT-928 or ECMA-118:1986.  It is
meant for modern Greek.
Encoding:
ISO-8859-9
(
`iso9.edf'
)
The ISO 8859-9 set, or Latin 5, replaces the rarely used Icelandic
letters from Latin 1 with Turkish letters.
Support is provided thanks to Ogonkify.
Encoding:
ISO-8859-10
(
`iso10.edf'
)
Latin 6 (or ISO-8859-10) adds the last letters from Greenlandic and
Lapp which were missing in Latin 4, and thereby covers all
Scandinavia.
Support is provided thanks to Ogonkify.
Encoding:
ISO-8859-13
(
`iso13.edf'
)
Latin7 (ISO-8859-13) is going to cover the Baltic Rim and re-establish
the Latvian (lv) support lost in Latin6 and may introduce the local
quotation marks.
Support is provided thanks to Ogonkify.
Encoding:
ISO-8859-15
(
`iso15.edf'
)
The new Latin9 nicknamed Latin0 aims to update Latin1 by replacing
some less needed symbols (some fractions and accents) with forgotten
French and Finnish letters and placing the U+20AC Euro sign in the
cell of the former international currency sign.
Very few fonts yet offer the possibility to print the Euro sign.
Encoding:
KOI8
(
`koi8.edf'
)
KOI-8 (+??) is a subset of ISO-IR-111 that can be used in Serbia, Belarus
etc.
Encoding:
MS-CP1250
(
`ms-cp1250.edf'
)
Microsoft's CP-1250 encoding (aka CeP).
Encoding:
Macintosh
(
`mac.edf'
)
For the Macintosh encoding.  The support is not sufficient, and a lot
of characters may be missing at the end of the job (especially Greek
letters).
[
#SEC64
<
]
[
#SEC66
>
]
[
#SEC59
<<
]
[
#SEC1
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7. Pretty Printing
The main feature of a2psTwo different levels of pretty printing can be reached:
-
basic (normal highlight level) in which what you print is what you
wrote.
-
string (heavy highlight level), in which in general, some keywords are
replaced by a Symbol character which best represents them.  For
instance, in most languages
`<='
and
`>='
will be replaced by
the corresponding single character from the font Symbol.
Note that the difference is up to the author of the style sheet.
#SEC66
7.1 Syntactic limits
What can't be done
#SEC67
7.2 Known Style Sheets
Some supported languages
#SEC68
7.3 Type Setting Style Sheets
a2ps as a tiny word processor
#SEC79
7.4 Faces
Encoding the look of pieces of text
#SEC80
7.5 Style Sheets Semantics
What is to be defined
#SEC88
7.6 Style Sheets Implementation
How they should be defined
#SEC97
7.7 A Tutorial on Style Sheets
Step by step example
[
#SEC65
<
]
[
#SEC67
>
]
[
#SEC65
<<
]
[
#SEC65
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.1 Syntactic limits
a2pshandles lexical structures, i.e., if in your favorite language
IF IF == THEN THEN THEN := ELSE ELSE ELSE := IF
is legal, then a2psjust looks for some keywords, or some
sequences
.
[
#SEC66
<
]
[
#SEC68
>
]
[
#SEC65
<<
]
[
#SEC65
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.2 Known Style Sheets
Style Sheet:
68000
(
`68000.ssh'
)
Althought designed at the origin for the 68k's assembler, this style
sheet seems to handle rather well other dialects.
Style Sheet:
a2ps configuration file
(
`a2psrc.ssh'
)
Meant to print files such as
`a2ps.cfg'
, or
`.a2ps/a2psrc'
, etc.
Style Sheet:
a2ps style sheet
(
`ssh.ssh'
)
Second level of highligthing (option
`-g'
)) substitutes the LaTeX symbols.
Style Sheet:
Ada
(
`ada.ssh'
)
This style sheets cover Ada 95.  If you feel the need for Ada 83,
you'll have to design another style sheet.
Style Sheet:
ASN.1
(
`asn1.ssh'
)
Written by Philippe Coucaud.
ASN.1 (Abstract Syntax Notation One) is used to define the protocol data
units (PDUs) of all application layer protocols to date.
Style Sheet:
Autoconf
(
`autoconf.ssh'
)
Suitable for both
configure.in
and library
m4
files.
Style Sheet:
AWK
(
`awk.ssh'
)
Written by Edward Arthur.
This style is devoted to the AWK pattern scanning and processing language.
It is supposed to support classic awk, nawk and gawk.
Style Sheet:
B
(
`b.ssh'
)
Written by Philippe Coucaud.
B is a formal specification method mostly used to describe critical
systems.  It is based on the mathematical sets theory.
Style Sheet:
BC
(
`bc.ssh'
)
bc is an arbitrary precision calculator language.
Style Sheet:
Bourne Shell
(
`sh.ssh'
)
Some classical program names, or builtin, are highlighted in the
second level of pretty-printing.
Style Sheet:
C
(
`c.ssh'
)
This style does not highlight the function definitions.
Another style which highlights them, GNUish C, is provided (gnuc.ssh).
It works only if you respect some syntactic conventions.
Style Sheet:
C Shell
(
`csh.ssh'
)
Written by Jim Diamond.
Some classical program names, and/or builtins, are highlighted in
the second level of pretty-printing.
Style Sheet:
C++
(
`cxx.ssh'
)
Should handle all known variations of C++.  Most declarations (classes
etc.) are not highlighted as they should be.  Please, step forward!
Style Sheet:
CAML
(
`caml.ssh'
)
This style is obsolete: use OCaml instead.
Style Sheet:
ChangeLog
(
`chlog.ssh'
)
This style covers the usual ChangeLog files.
Style Sheet:
Claire
(
`claire.ssh'
)
Claire is a high-level functional and object-oriented language with
advanced rule processing capabilities. It is intended to allow the
programmer to express complex algorithms with fewer lines and in an
elegant and readable manner.
To provide a high degree of expressivity, Claire uses:
-
A very rich type system including type intervals and second-order
types (with dual static/dynamic typing),
-
Parametric classes and methods,
-
An object-oriented logic with set extensions,
-
Dynamic versioning that supports easy exploration of search spaces.
To achieve its goal of readability, Claire uses
-
set-based programming with an intuitive syntax,
-
simple-minded object-oriented programming,
-
truly polymorphic and parametric functional programming,
-
a powerful-yet-readable extension of DATALOG to express logical conditions,
-
an entity-relation approach with explicit relations, inverses,
unknown values and relational
-
operations.
More information on claire can be found on
http://www.ens.fr/~laburthe/claire.html
claire home page
.
Style Sheet:
Common Lisp
(
`clisp.ssh'
)
Written by Juliusz Chroboczek.
It is not very clear what should be considered as a `keyword' in
Common Lisp.  I like binders, control structures and declarations to
be highlighted, but not assignments.
Names of defstructs are not highlighted because this would not work
with defstruct options.
Style Sheet:
Coq Vernacular
(
`coqv.ssh'
)
This style is devoted to the Coq v 5.10 vernacular language.
Style Sheet:
CORBA IDL
(
`cidl.ssh'
)
Written by Bob Phillips.
A first attempt at a style sheet for OMG CORBA IDL.
I believe I captured all the keywords for CORBA 2.2 IDL.
I also stole code from gnuc.ssh to print the method names
in bold face.  I'm not sure I quite like my own choices
for Keyword_strong and Keyword, so I'm looking for feedback.
Note that, as with gnuc.ssh, for a method name to be noted as such,
the left parenthesis associated with the argument list for the method
must appear on the same line as the method name.
Style Sheet:
CPP
(
`cpp.ssh'
)
C traditional preprocessor handling, mostly meant to be inherited.
Style Sheet:
dc_shell
(
`dc_shell.ssh'
)
Written by Philippe Le Van.
Synopsys Design Compiler is a synthesis tool used by
electronic companies for the design of their chips.
This sheet is very incomplete, we have a lot of keywords to
add, eventually options to highlight...
The Label_strong style is used for commands which change the design.
Style Sheet:
Eiffel
(
`eiffel.ssh'
)
Eiffel is an object oriented language that also includes a
comprehensive approach to software construction: a method.
The language itself is not just a programming language but also covers
analysis, design and implementation.
Heavy highlight uses symbols to represent common math operators.
Style Sheet:
Emacs Lisp
(
`elisp.ssh'
)
Written by Didier Verna.
This style sheet includes support for some extensions dumped with XEmacs.
Style Sheet:
Encapsulated PostScript
(
`eps.ssh'
)
Illegal PostScript operators are highlighted as Errors.
Style Sheet:
Extended Tcl
(
`tclx.ssh'
)
Written by Phil Hollenback.
Extensions to plain Tcl.
Style Sheet:
Fortran
(
`fortran.ssh'
)
Written by Denis Girou,  Alexander Mai.
There are several Fortran dialects, depending whether, on the one
hand, you use Fortran 77 or Fortran 90/95, and, on the other hand,
Fixed form comments, or Free form comments.
The style sheets
for77kwds
and
for90kwds
implements keywords only,
while the style sheets
for-fixed
and
for-free
implements comments
only.
This style sheet tries to support any of the various flavors
(Fortran 77/90/95, fixed or free form).  For more specific uses, you
should use either:
-
for77-fixed, for Fortran 77 fixed form,
-
for77-free, for Fortran 77 free form,
-
for90-fixed, for Fortran 90/95 fixed form,
-
for90-free, for Fortran 90/95 free form.
Style Sheet:
Fortran 77 Fixed
(
`for77-fixed.ssh'
)
Written by Denis Girou,  Alexander Mai.
Dedicated to Fortran 77 in fixed form, i.e., comments are
lines starting with c, C, or *, and only those lines are comments.
Style Sheet:
Fortran 77 Free
(
`for77-free.ssh'
)
Written by Denis Girou,  Alexander Mai.
Dedicated to Fortran 77 in free form, i.e., comments are introduced by !
anywhere on the line, and nothing else is a comment.
Style Sheet:
Fortran 77 Keywords
(
`for77kwds.ssh'
)
Written by Denis Girou,  Alexander Mai.
This sheet implements only Fortran 77 keywords, and avoids implementing
comments support. This is to allow for implementation of either fixed
or free source form.
See the documentation of the style sheet
fortran
for more details.
Style Sheet:
Fortran 90 Fixed
(
`for90-fixed.ssh'
)
Written by Denis Girou,  Alexander Mai.
Dedicated to Fortran 90/95 in fixed form, i.e., comments are
lines starting with c, C, or *, and only those lines are comments.
Style Sheet:
Fortran 90 Free
(
`for90-free.ssh'
)
Written by Denis Girou,  Alexander Mai.
Dedicated to Fortran 90/95 in free form, i.e., comments are introduced by !
anywhere on the line, and nothing else is a comment.
Style Sheet:
Fortran 90 Keywords
(
`for90kwds.ssh'
)
Written by Denis Girou,  Alexander Mai.
This sheet implements the superset which Fortran 90 and Fortran 95 provide
over Fortran 77.
See the documentation of the style sheet
fortran
for more details.
Style Sheet:
Fortran Fixed
(
`for-fixed.ssh'
)
Written by Denis Girou,  Alexander Mai.
Implements comments of Fortran in fixed form, i.e., comments are
lines starting with c, C, or *, and only those lines are comments.
No other highlighting is done.
See the documentation of the style sheet
fortran
for more details.
Style Sheet:
Fortran Free
(
`for-free.ssh'
)
Written by Denis Girou,  Alexander Mai.
Dedicated to Fortran in free form, i.e., comments are introduced by !
anywhere on the line, and nothing else is a comment.
Style Sheet:
GNUish C
(
`gnuc.ssh'
)
Declaration of functions are highlighted
only
if you start
the function name in the first column, and it is followed by an
opening parenthesis.  In other words, if you write
int main (void)
it won't work.  Write:
int
main (void)
Style Sheet:
GNUMakefile
(
`gmake.ssh'
)
Written by Alexander Mai.
Special tokens of GNUmakefiles and non terminal declarations are highlighted.
Style Sheet:
Haskell
(
`haskell.ssh'
)
Written by Ilya Beylin.
Haskell: non-strict functional programming language
http::/www.haskell.org/
Style Sheet:
HTML
(
`html.ssh'
)
Written by  Wesley J. Chun.
This style is meant to pretty print HTML source files, not to simulate
its interpretation (i.e.,
`<bold>foo</bold>'
does not print
`foo'
in bold).  If you really meant to print the result of the HTML file
interpreted
, then you should turn the delegations on, and make sure
`a2ps'
has HTML delegations.
Style Sheet:
IDL
(
`idl.ssh'
)
Written by Robert S. Mallozzi,  Manfred Schwarb.
Style sheet for IDL 5.2 (Interactive Data Language).
Obsolete routines are not supported.
http://www.rsinc.com.
Style Sheet:
InstallShield 5
(
`is5rul.ssh'
)
Written by Alex.
InstallShield5 _TM_ RUL script.
Style Sheet:
Java
(
`java.ssh'
)
Written by Steve Alexander.
Documentation comments are mapped to strong comments, and any other
comment is plain comment.
Style Sheet:
JavaScript
(
`js.ssh'
)
Written by Scott Pakin.
Keywords used are everything listed in the Client-Side JavaScript
Reference 1.3, plus "undefined" (why isn't that listed?) and
"prototype".  I omitted the semi-standard a2ps optional operators for
equality, because JavaScript's use of both strict- and non-strict equality
might ambiguate the output.  Finally, regular expressions are formatted
like strings.
Style Sheet:
LACE
(
`lace.ssh'
)
This is meant for the Eiffel equivalent of the Makefiles.
Style Sheet:
Lex
(
`lex.ssh'
)
In addition to the C constructs, it highlights the declaration of
states, and some special
`%'
commands.
Style Sheet:
Lout
(
`lout.ssh'
)
Written by Jean-Baptiste Nivoit.
This is the style for Lout files.
Style Sheet:
Mail Folder
(
`mail.ssh'
)
To use from elm and others, it is better to specify
`-g -Email'
,
since the file sent to printer is no longer truly a mail folder.
This style also suits to news.
`--strip'
options are also useful
(they strip "useless" headers).
Whenever the changes of encoding are clear, a2ps sets itself the
encoding for the parts concerned.
Tag 1 is the subject, and Tag 2 the author of the mail/news.
Note: This style sheet is _very_ difficult to write.  Please don't
report behavior you don't like.  Just send me improvements,
or write a Bison parser for mails.
Style Sheet:
Makefile
(
`make.ssh'
)
Special tokens, and non terminal declarations are highlighted.
Style Sheet:
Management Information Base
(
`mib.ssh'
)
Written by Kelly Wiles.
The MIB file is of ASN.1 syntax.
Style Sheet:
Maple
(
`maple.ssh'
)
Written by Richard J Mathar.
Some classical program names, and/or builtins, are highlighted in
the second level of pretty-printing.
Style Sheet:
MATLAB 4
(
`matlab4.ssh'
)
Written by Marco De la Cruz.
Note that comments in the code should have a space after the %.
Style Sheet:
Modula 2
(
`modula2.ssh'
)
Written by Peter Bartke.
Style Sheet:
Modula 3
(
`modula3.ssh'
)
Modula-3 is a member of the Pascal family of languages. Designed in
the late 1980s at Digital Equipment Corporation and Olivetti, Modula-3
corrects many of the deficiencies of Pascal and Modula-2 for practical
software engineering. In particular, Modula-3 keeps the simplicity of
type safety of the earlier languages, while providing new facilities
for exception handling, concurrency, object-oriented programming, and
automatic garbage collection. Modula-3 is both a practical
implementation language for large software projects and an excellent
teaching language.
This sheet was designed based on
http://www.research.digital.com/SRC/modula-3/html/home.html
Modula 3 home page
.
Style Sheet:
o2c
(
`o2c.ssh'
)
Style Sheet:
Oberon
(
`oberon.ssh'
)
Created by N. Wirth, Oberon is the successor of the Pascal and
Modula-2 family of programming languages. It was specifically designed
for systems programming, and was used to create the Oberon system in
cooperation with J. Gutknecht. A few years later, the Oberon language
was extended with additional object-oriented features to result in the
programming language Oberon-2.
Implementation of the sheet based on
http://www.math.tau.ac.il/~laden/Oberon.html
The Oberon Reference Site
.
Style Sheet:
Objective C
(
`objc.ssh'
)
Written by Paul Shum.
Style Sheet:
OCaml
(
`ocaml.ssh'
)
Written by Markus Mott.
This style should also suit other versions of ML (caml light, SML etc.).
Style Sheet:
OCaml Yacc
(
`mly.ssh'
)
Written by Jean-Baptiste Nivoit.
Should handle CAML Special Light parser files.
Style Sheet:
Octave
(
`octave.ssh'
)
Written by C.P. Earls.
Style Sheet:
Oracle parameter file
(
`initora.ssh'
)
Written by Pierre Mareschal.
For init.ora parameter files.
Style Sheet:
Oracle PL/SQL
(
`plsql.ssh'
)
Written by Pierre Mareschal.
This style is to be checked.
Style Sheet:
Oracle SQL
(
`sql.ssh'
)
Written by Pierre Mareschal.
a2ps-sql Pretty Printer Version 1.0.0 beta - 18-MAR-97
For comments, support for -- /*..*/ and //.
This style is to be checked.
Style Sheet:
Oracle SQL-PL/SQL-SQL*Plus
(
`oracle.ssh'
)
Written by Pierre Mareschal.
18-MAR-97
For comments, support for -- /*..*/ and //.
This style is to be checked.
Style Sheet:
Pascal
(
`pascal.ssh'
)
The standard Pascal is covered by this style.
But some extension have been added too, hence modern Pascal programs
should be correctly handled.
Heavy highlighting maps mathematical symbols to their typographic
equivalents.
Style Sheet:
Perl
(
`perl.ssh'
)
Written by Denis Girou.
As most interpreted languages, Perl is very free on its syntax, what
leads to significant problems for a pretty printer.  Please, be kind
with our try.  Any improvement is most welcome.
Style Sheet:
PostScript
(
`ps.ssh'
)
Only some keywords are highlighted, because otherwise listings are quickly
becoming a big bold spot.
Style Sheet:
PostScript Printer Description
(
`ppd.ssh'
)
Support for Adobe's PPD files.
Style Sheet:
Pov-Ray
(
`pov.ssh'
)
Written by Jean-Baptiste Nivoit.
Should handle Persistence Of Vision input files.
Style Sheet:
PreScript
(
`pre.ssh'
)
This style defines commands in the canonic syntax of a2ps.
It is meant to be used either as an input language, and to
highlight the table of contents etc.
It can be a good choice of destination language for people who
want to produce text to print (e.g. pretty-printing, automated
documentation etc.) but who definitely do not want to learn
PostScript, nor to require the use of LaTeX.
Style Sheet:
PreTeX
(
`pretex.ssh'
)
This style sheets provides LaTeX-like commands to format text.
It is an alternative to the PreScript style sheet, in which formating
commands are specified in a more a2ps related syntax.
It provides by the use of LaTeX like commands, a way to describe the
pages that this program should produce.
Style Sheet:
Prolog
(
`prolog.ssh'
)
Help is needed on this sheet.
Style Sheet:
Promela
(
`promela.ssh'
)
There is no way for this program to highlight send and receive primitives.
Style Sheet:
Python
(
`python.ssh'
)
Python is an easy to learn, powerful programming language. It has
efficient high-level data structures and a simple but effective
approach to object-oriented programming. Python's elegant syntax and
dynamic typing, together with its interpreted nature, make it an ideal
language for scripting and rapid application development in many areas
on most platforms.
The Python interpreter and the extensive standard library are freely
available in source or binary form for all major platforms from the
http://www.python.org
Python web site
, and can be freely distributed.
The same site also contains distributions of and pointers to many free
third party Python modules, programs and tools, and additional
documentation.
The Python interpreter is easily extended with new functions and data
types implemented in C or C++ (or other languages callable from
C). Python is also suitable as an extension language for customizable
applications.
Style Sheet:
Reference Card
(
`card.ssh'
)
This style sheet is meant to process help messages generated by
Unix applications.  It highlights the options (-short or --long),
and their arguments.
Normal use of this style sheet is through the shell script card
(part of the a2ps package), but a typical hand-driven use is:
program --help | a2ps -Ecard
Style Sheet:
REXX
(
`rexx.ssh'
)
Written by Alexander Mai.
This style sheet supports REXX.
You can get information about REXX from the
http://www.rexxla.org
REXX Language Association
.
Style Sheet:
Sather
(
`sather.ssh'
)
Sather is an object oriented language designed to be simple,
efficient, safe, flexible and non-proprietary. One way of placing it
in the `space of languages' is to say that it aims to be as efficient
as C, C++, or Fortran, as elegant as and safer than Eiffel, and
support higher-order functions and iteration abstraction as well as
Common Lisp, CLU or Scheme.
Implementation of the sheet based on the
http://www.icsi.berkeley.edu/~sather/index.html
Sather home page
.
Heavy highlighting uses symbols for common mathematical operators.
Style Sheet:
Scheme
(
`scheme.ssh'
)
This style sheet is looking for a maintainer and/or comments.
Style Sheet:
SDL-88
(
`sdl88.ssh'
)
Written by Jean-Philippe Cottin.
--strip-level=2 is very useful: it cancels the graphical information
left by graphic editors.  Only the pure specification is then printed.
Style Sheet:
Sed
(
`sed.ssh'
)
Comments and labels are highlighted.  Other ideas are welcome!
A lot of work is still needed.
Style Sheet:
Shell
(
`shell.ssh'
)
This style sheet is not meant to be used directly, but rather an as
ancestor for shell style sheets.
Style Sheet:
SQL 92
(
`sql92.ssh'
)
Written by Pierre Mareschal.
18-MAR-97
This style is to be checked.
Style Sheet:
Standard ML
(
`sml.ssh'
)
Written by Franklin Chen,  Daniel Wang.
This style sheet takes advantage of the Symbol font to replace many
ASCII operators with their natural graphical representation.  This
is enabled only at heavy highlighting.
Style Sheet:
Symbols
(
`symbols.ssh'
)
This style sheet should be a precursor for any style sheet which
uses LaTeX like symbols.
Style Sheet:
TC Shell
(
`tcsh.ssh'
)
Written by Jim Diamond.
C shell with file name completion and command line editing.
Style Sheet:
TeX
(
`tex.ssh'
)
Written by Denis Girou.
This is the style for (La)TeX files.
It's mainly useful for people who develop (La)TeX packages.
With
`-g'
, common mathematical symbols are represented graphically.
Style Sheet:
Texinfo
(
`texinfo.ssh'
)
Heavy highlighting prints the nodes on separate pages
which title is the name of the node.
Style Sheet:
TeXScript
(
`texscript.ssh'
)
TeXScript is the new name of what used to be called PreScript.
New PreScript has pure a2ps names, PreTeX has pure TeX names,
and TeXScript mixes both.
Style Sheet:
Tiger
(
`tiger.ssh'
)
Tiger is a toy language that serves as example of the book
http://www.cs.princeton.edu/~appel/modern/
Modern Compiler Implementation
by Andrew W. Appel.
Style Sheet:
tk
(
`tk.ssh'
)
Written by  Larry W. Virden.
Since everything, or almost, is a string, what is printed is not
always what you would like.
Style Sheet:
Tool Command Language
(
`tcl.ssh'
)
Written by  Larry W. Virden.
Since everything, or almost, is a string, what is printed is not
always what you would like.
Style Sheet:
Unified Diff
(
`udiff.ssh'
)
This style is meant to be used onto the output unidiffs, that is to say
output from
`diff -u'
.
Typical use of this style is:
diff -u old new | a2ps -Eudiff
The prologue
diff
helps to highlight the differences
(
`a2ps -Ewdiff --prologue=diff'
).
Style Sheet:
Unity
(
`unity.ssh'
)
Written by Jean-Philippe Cottin.
The graphic conversion of the symbols (option
`-g'
) is nice.
Style Sheet:
VERILOG
(
`verilog.ssh'
)
Written by Edward Arthur.
This style is devoted to the VERILOG hardware description language.
Style Sheet:
VHDL
(
`vhdl.ssh'
)
Written by Thomas Parmelan.
Non-textual operators are not highlighted.
Some logical operators are printed as graphical symbols
in the second level of pretty-printing.
Style Sheet:
Visual Basic for Applications
(
`vba.ssh'
)
Written by Dirk Eddelbuettel.
Style Sheet:
Visual Tcl
(
`vtcl.ssh'
)
Written by Phil Hollenback.
All the Vtcl keywords that aren't in Tcl or TclX.
Style Sheet:
VRML
(
`vrml.ssh'
)
Written by Nadine Richard.
According to
http://vag.vrml.org/VRML2.0/FINAL/spec/part1/grammar.html
Grammar Definition Version 2.0 ISO/IEC CD 14772
.
Style Sheet:
wdiff
(
`wdiff.ssh'
)
This style is meant to be used onto the output of Franc,ois Pinard's
program
wdiff
.
wdiff
is a utility that underlines the differences
of words between to files.  Where
diff
make only the difference between
lines that have changed,
wdiff
reports words that have changed inside the lines.
Typical use of this style is:
wdiff old new | a2ps -Ewdiff
wdiff
can be found in usual GNU repositories.  The prologue
diff
helps to highlight the differences (
`a2ps -Ewdiff --prologue=diff'
).
Style Sheet:
XS
(
`xs.ssh'
)
Written by Kestutis Kupciunas.
This style covers Perl XS language.
Style Sheet:
Yacc
(
`yacc.ssh'
)
Special tokens, and non terminal declarations are highlighted.
Style Sheet:
Z Shell
(
`zsh.ssh'
)
Zsh is a UNIX command interpreter (shell) usable as an interactive
login shell and as a shell script command processor.  Of the standard
shells, zsh most closely resembles ksh but includes many enhancements.
Zsh has comand line editing, builtin spelling correction, programmable
command completion, shell functions (with autoloading), a history
mechanism, and a host of other features.
This style sheet highlights some classical program names and builtins
in the second level of pretty-printing.
[
#SEC67
<
]
[
#SEC69
>
]
[
#SEC65
<<
]
[
#SEC65
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.3 Type Setting Style Sheets
This section presents a few style sheets that define page description
languages (compared to most other style sheet meant to pretty print
source files).
#SEC69
7.3.1 Symbol
Access to the glyphs of the Symbol font
#SEC70
7.3.2 PreScript
Typesetting in an a2ps like syntax
#SEC74
7.3.3 PreTeX
Typesetting in a LaTeX like syntax
#SEC78
7.3.4 TeXScript
Typesetting in a mixture of both
[
#SEC68
<
]
[
#SEC70
>
]
[
#SEC65
<<
]
[
#SEC68
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.3.1 Symbol
The style sheet
Symbol
introduces easy to type keywords to obtain
the special characters of the PostScript font
Symbol
.  The
keywords are named to provide a LaTeX taste.  These keywords are also
the names used when designing a style sheet, hence to get the full list,
see
#SEC89
A Bit of Syntax
.
If you want to know the correspondence, it is suggested to print the
style sheet file of
Symbol
:
a2ps -g symbol.ssh
[
#SEC69
<
]
[
#SEC71
>
]
[
#SEC65
<<
]
[
#SEC68
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.3.2 PreScript
PreScript
has been designed in conjunction with a2ps@c.  Since
bold sequences, special characters etc. were implemented in a2ps@c, we
thought it would be good to allow direct access to those features:
PreScript
became an input language for a2ps@c, where special
font treatments are specified in an
ssh
syntax (see section
#SEC88
Style Sheets Implementation
).
The main advantages for using
PreScript
are:
-
it is fairly simple,
-
a2psevery UNIX platform.
It can be a good candidate for generation of PostScript output
(syntactic pretty-printers, generation of various reports etc.).
#SEC71
7.3.2.1 Syntax
Lexical specifications
#SEC72
7.3.2.2 PreScript Commands
#SEC73
7.3.2.3 Examples
[
#SEC70
<
]
[
#SEC72
>
]
[
#SEC65
<<
]
[
#SEC70
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.3.2.1 Syntax
Every command name begins with a backslash (
`\'
). If the command
uses an argument, it is given between curly braces with no spaces
between the command name and the argument.
The main limit on
PreScript
is that no command can be used inside
another command. For instance the following line will be badly
interpreted by a2ps@c:
\Keyword{Problems using \keyword{recursive \copyright} calls}
The correct way to write this in
PreScript
is
\Keyword{Problems using} \keyword{recursive} \copyright \Keyword{calls}.
Everything from an unquoted % to the end of line is ignored
(comments).
[
#SEC71
<
]
[
#SEC73
>
]
[
#SEC65
<<
]
[
#SEC70
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.3.2.2 PreScript Commands
These commands required arguments.
`\keyword{
text
}'
`\Keyword{
text
}'
Highlight lightly/strongly the given
text
.  Should be used only
for a couple of adjacent words.
`\comment{
text
}'
`\Comment{
text
}'
The
text
is given a special face.  The
text
may be removed
if option
`--strip'
is used.
`\label{
text
}'
`\Label{
text
}'
text
should be considered as a definition, or an important point
in the structure of the whole text.
`\string{
text
}'
Write
text
with string's face (e.g., in font Times).
`\error{
text
}'
Write
text
with error's face (generally a very different face, so
that you see immediately).
`\symbol{
text
}'
text
is written in the PostScript symbol font.  This feature is
not compatible with LaTeX.  It is recommended, when possible, to use
the special keywords denoting symbols, which are compatible with
LaTeX (see section
#SEC69
Symbol
).
`\header{
text
}'
`\footer{
text
}'
Use
text
as header (footer) for the current page.  If several
headers or footers are defined on the same page, the last one is taken
into account.
`\encoding{
key
}'
Change dynamically the current encoding.  After this command, the text is
printed using the encoding corresponding to
key
.
[
#SEC72
<
]
[
#SEC74
>
]
[
#SEC65
<<
]
[
#SEC70
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.3.2.3 Examples
PreScript
and a2psformating. For instance, on the
`passwd'
file:
ypcat passwd |
awk -F: \
'{print "\Keyword{" $5 "} (" $1 ") \rightarrow\keyword{" $7 "}"}'\
| a2ps -Epre -P
[
#SEC73
<
]
[
#SEC75
>
]
[
#SEC65
<<
]
[
#SEC68
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.3.3 PreTeX
The aim of the PreTeX style sheet is to provide something similar to
PreScript
, but with a more LaTeX like syntax.
#SEC75
7.3.3.1 Special characters
#SEC76
7.3.3.2 PreTeX
#SEC77
7.3.3.3 Differences with LaTeX
[
#SEC74
<
]
[
#SEC76
>
]
[
#SEC65
<<
]
[
#SEC74
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.3.3.1 Special characters
`$'
is ignored in
PreTeX
for compatibility with LaTeX,
and
`%'
introduces a comment. Hence they are the only symbols which
have to be quoted by a
`\'
.  The following characters should also be
quoted to produce good LaTeX files, but are accepted by
PreScript
:
`_'
,
`&'
,
`#'
.
Note that
inside a command
, like
\textbf
, the quotation
mechanism does not work in
PreScript
(
\textrm{#$%}
writes
`#$%'
) though LaTeX still requires quotation. Hence whenever
special characters or symbols are introduced, they should be at the
outer most level.
[
#SEC75
<
]
[
#SEC77
>
]
[
#SEC65
<<
]
[
#SEC74
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.3.3.2 PreTeX
These commands required arguments.
`\section{
Title
}'
`\subsection{
Title
}'
`\subsubsection{
Title
}.'
Used to specify the title of a section, subsection or subsubsection.
`\textbf{
text
}'
`\textit{
text
}'
`\textbi{
text
}'
`\textrm{
text
}'
write
text
in bold, italic, bold-italic, Times.  Default font is
Courier.
`\textsy{
text
}'
text
is written in the PostScript symbol font.  This feature is
not compatible with LaTeX.  It is recommended, when possible, to use the
special keywords denoting symbols, which are compatible with LaTeX
(See the style sheet
Symbol
).
`\header{
text
}'
`\footer{
text
}'
Use
text
as header (footer) for the current page.  If several
headers or footers are defined on the same page, the last one is taken
into account.
`\verb+
text
+'
Quote
text
so that no special sequence will be interpreted.  In
`\verb+
quoted string
+'
`+'
can be any symbol in
`+'
,
`!'
,
`|'
,
`#'
,
`='
.
`\begin{document}'
`\end{document}'
`\begin{itemize}'
`\end{itemize}'
`\begin{enumerate}'
`\end{enumerate}'
`\begin{description}'
`\end{description}'
These commands are legal in LaTeX
Hence there are simply ignored and not printed (if immediately followed
by an end-of-line).
[
#SEC76
<
]
[
#SEC78
>
]
[
#SEC65
<<
]
[
#SEC74
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.3.3.3 Differences with LaTeX
The following symbols, inherited from the style sheet
Symbol
, are
not supported by LaTeX:
`\Alpha'
,
`\apple'
,
`\Beta'
,
`\carriagereturn'
,
`\Chi'
,
`\Epsilon'
,
`\Eta'
,
`\florin'
,
`\Iota'
,
`\Kappa'
,
`\Mu'
,
`\Nu'
,
`\Omicron'
,
`\omicron'
,
`\radicalex'
,
`\register'
,
`\Rho'
,
`\suchthat'
,
`\Tau'
,
`\therefore'
,
`\trademark'
,
`\varUpsilon'
,
`\Zeta'
.
LaTeX is more demanding about special symbols. Most of them must be
in so-called math mode, which means that the command must be inside
`$'
signs. For instance, though
If \forall x \in E, x \in F then E \subseteq F.
is perfectly legal in PreTeX, it should be written
If $\forall x \in E, x \in F$ then $E \subseteq F$.
for LaTeX. Since in PreTeX
quoted by a
`\'
), the second form is also admitted.
[
#SEC77
<
]
[
#SEC79
>
]
[
#SEC65
<<
]
[
#SEC68
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.3.4 TeXScript
TeXScript
is a replacement of the old version of
PreScript
: it combines both the a2ps@c-like and the
LaTeX-like syntaxes through inheritance of both
PreScript
and
PreTeX
.
In addition it provides commands meant to ease processing of file for
a2ps
Everything between
`%%TeXScript:skip'
and
`%%TeXScript:piks'
will be ignored in
TeXScript
command definitions for LaTeX exclusively.
The commands
`\textbi'
(for bold-italic) and
`\textsy'
(for
symbol) do not exist in LaTeX.  They should be defined in the
preamble:
%%TeXScript:skip
\newcommand{\textbi}[1]{\textbf{\textit{#1}}}
\newcommand{\textsy}[1]{#1}
%%TeXScript:piks
There is no way in TeXScript
no equivalent to the LaTeX environment
enumerate
.  But every
command beginning by
\text
is doubled by a command beginning by
`\magic'
.  a2psHence, if one specifies that arguments of those functions should be
ignored in the preamble of the LaTeX document, the numbering is
emulated.  For instance
\begin{enumerate}
\magicbf{1.}\item First line
\magicbf{2.}\item Second line
\end{enumerate}
will be treated the same way both in TeXScript
`\header'
and
`\footer'
, are not understood by LaTeX.
[
#SEC78
<
]
[
#SEC80
>
]
[
#SEC65
<<
]
[
#SEC65
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.4 Faces
A
face
is an attribute given to a piece of text, which specifies
how it should look like.  Since a2pssource files, the faces it uses are related to the syntactic entities
that can be encountered in a file.
The faces a2ps
`Plain'
This corresponds to the text body.
`Keyword'
`Keyword_strong'
These are related to the keywords that may appear in a text.
`Comment'
`Comment_strong'
These are related to comments in the text.  Remember that comments
should be considered as non essential ("
Aaaeaaarg
" says the
programmer); indeed, the user might suppress the comments thanks (?) to
the option
`--strip-level'
.  Hence,
never
use these faces
just because you think they look better on, say, strings.
`Label'
`Label_strong'
These are used when a point of extreme importance, or a sectioning
point, is met.  Typically, functions declarations etc.
`String'
Used mainly for string and character literals.
`Error'
Used to underline the presence of an error.  For instance in
Encapsulated PostScript, some PostScript operators are forbidden: they
are underlined as errors.
Actually, there is also the face
`Symbol'
, but this one is
particular: it is not legal changing its font.
[
#SEC79
<
]
[
#SEC81
>
]
[
#SEC65
<<
]
[
#SEC65
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.5 Style Sheets Semantics
a2psone per language.  In the following is described how the style sheets
are defined.  You may skip this section if you don't care how
a2ps
#SEC81
7.5.1 Name and key
Both names of a style sheet
#SEC82
7.5.2 Comments
Author name, version etc.
#SEC83
7.5.3 Alphabets
What words are legal
#SEC84
7.5.4 Case sensitivity
Is BEGIN different of begin
#SEC85
7.5.5 P-Rules
Pretty Printing Rules
#SEC86
7.5.6 Sequences
Strings, comments etc.
#SEC87
7.5.7 Optional entries
Second level of pretty printing
[
#SEC80
<
]
[
#SEC82
>
]
[
#SEC65
<<
]
[
#SEC80
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.5.1 Name and key
Every style sheet has both a key, and a name.  The name can be clean and
beautiful, with any character you might want.  The key is in fact the
prefix part of the file name, and is alpha-numerical, lower case, and
less than 8 characters long.
Anywhere a2psuses the key
(in the
`sheets.map'
file, with the option
`-E'
,
etc.).
As an example, C++ is implemented in a file called
`cxx.ssh'
, in
which the name is declared to be
`C++'
.
The rationale is that not every system accepts any character in the file
name (e.g., no
`+'
in MS-DOS).  Moreover, it allows to make
symbolic links on the ssh files (e.g.,
`ln -s cxx.ssh c++.ssh'
let's you use
`-E c++'
).
[
#SEC81
<
]
[
#SEC83
>
]
[
#SEC65
<<
]
[
#SEC80
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.5.2 Comments
ssh files can include the name of its author, a version number, a
documentation note and a requirement on the version of a2ps@c.  For
instance, if a style sheet requires a2psversion 4.9.5 will reject it.
[
#SEC82
<
]
[
#SEC84
>
]
[
#SEC65
<<
]
[
#SEC80
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.5.3 Alphabets
a2psespecially keywords.  Hence it needs two alphabets: the first one
specifying by which letters an identifier can begin, and the second one
for the rest of the word.  If you prefer, a keyword starts with a
character belonging to the first alphabet, and a character not
pertaining to the second is a separator.
[
#SEC83
<
]
[
#SEC85
>
]
[
#SEC65
<<
]
[
#SEC80
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.5.4 Case sensitivity
If the style is case insensitive, then matching is case insensitive
(keywords, operators and sequences).
[
#SEC84
<
]
[
#SEC86
>
]
[
#SEC65
<<
]
[
#SEC80
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.5.5 P-Rules
A
P-rule
(Pretty printing rule), or
rule
for short, is a
structure which consists of two items:
lhs
left-hand side
its source string, with which the source file is compared;
rhs
right hand side
a list of faced strings which will replace the text matched in the
pretty-printed output.  A faced string is composed of
-
a string, or a reference to a part of the source string
(see
regex.html#Back_002dreference-Operator
(regex)Back-reference Operator
section `Back-reference Operator' in
Regex manual
)
-
the face to use to print it
Just a short example:
`(foo, bar, Keyword_strong)'
as a rule
means that every input occurrence of
`foo'
will be replaced by
`bar'
, written with the
Keyword_strong
face.
If the destination string is empty, then a2psstring.  This is different from giving the source string as a
destination string if the case is different.  An example will make it
fairly clear.
Let
foobar
be a case insensitive style sheet including the
rules
`(foo, "", Keyword)'
and
`(bar, bar, Keyword)'
.  Then,
on the input
`FOO BAR'
, a2ps
Keyword
.
a2pscomes from that some keywords are sensitive to the delimiters around
them (such as
`unsigned'
and
`int'
in
C
, which are
definitely not the same thing as
`unsignedint'
), and others not (in
C
,
`!='
is "different from" both in
`a != b'
and
`a!=b'
).
The first ones are called
keywords
in a2psseconds are
operators
.  Operators are matched anywhere they
appear, while keywords need to have separators around them
(see section
#SEC83
Alphabets
).
Let us give a more complicated example: that of the
Yacc
rules.
A rule in
Yacc
is of the form:
a_rule : part1 part2 ;
Suppose you want to highlight these rules.  To recognize them, you will
write a regular expression specifying that:
it must start at the beginning of the line,
then there is string composed of symbols, which is what you want to
highlight,
and a colon, which can be preceded by blank characters.
The regexp you want is:
`/^[a-zA-Z0-9_]*[\t ]*:/'
.  But with the
rule
/^[a-zA-Z0-9_]*[\t ]*:/, "", Label_strong
the blanks and the colon are highlighted too.  Hence you need to
specify some parts in the regexp (see
regex.html#Back_002dreference-Operator
(regex)Back-reference Operator
section `Back-reference Operator' in
Regex manual
), and use a longer
list of destination strings.  The correct rule is
(/^([a-zA-Z0-9_]*)([\t ]*:)/, \1 Label_strong, \2 Plain)
Since it is a bit painful to read, regexps can be spread upon several
lines.  It is strongly suggested to break them by groups, and to
document the group:
(/^([a-zA-Z0-9_]*)/    # \1. Name of the rule
/([\t ]*:)/           # \2. Trailing space and colon
\1 Label_strong, \2 Plain)
[
#SEC85
<
]
[
#SEC87
>
]
[
#SEC65
<<
]
[
#SEC80
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.5.6 Sequences
A
sequence
is a string between two
markers
, along with a
list of exceptions.  A marker is a fixed string.  Typical examples are
comments, string (with usually
`"'
as opening and closing markers,
and
`\\'
and
`\"'
as exceptions) etc.  Three faces are used:
one for the initial marker, one for the core of the sequence, and a last
one for the final maker.
[
#SEC86
<
]
[
#SEC88
>
]
[
#SEC65
<<
]
[
#SEC80
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.5.7 Optional entries
There are two levels of pretty-printing encoded in the style sheets.  By
default, a2psoption
`-g'
is specified, in which case,
heavy
highlighting
is invoked, i.e., optional keywords, operators and sequences are
considered.
[
#SEC87
<
]
[
#SEC89
>
]
[
#SEC65
<<
]
[
#SEC65
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.6 Style Sheets Implementation
In the previous section (see section
#SEC80
Style Sheets Semantics
) were explained
the various items needed to understand the machinery involved in pretty
printing.  Here, their implementation, i.e., how to write a style sheet
file,  is explained.  The next section (see section
#SEC97
A Tutorial on Style Sheets
), exposes a step by step simple example.
#SEC89
7.6.1 A Bit of Syntax
Lexical rules of the ssh language
#SEC90
7.6.2 Style Sheet Header
Declaration of a style
#SEC91
7.6.3 Syntax of the Words
Classes of the Characters
#SEC92
7.6.4 Inheriting from Other Style Sheets
Extending existing style sheets
#SEC93
7.6.5 Syntax for the P-Rules
Atomic Pretty Printing rules
#SEC94
7.6.6 Declaring the keywords and the operators
Special Classes of Identifiers
#SEC95
7.6.7 Declaring the sequences
Bordered Lexical Entities
#SEC96
7.6.8 Checking a Style Sheet
Ask a2ps to Check the Sheet
[
#SEC88
<
]
[
#SEC90
>
]
[
#SEC65
<<
]
[
#SEC88
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.6.1 A Bit of Syntax
Here are the lexical rules underlying the style sheet language:
-
the separators are white space, form feed, new line, and tab.
-
`#'
introduces a comment, ended at the end of the line.
-
special characters are the separators, plus
`#'
,
`"'
,
`,'
,
`('
,
`)'
,
`+'
and
`/'
.  Any other
character is a regular character.
-
the list of the structuring keywords is
alphabet
,
alphabets
,
are
,
case
,
documentation
,
end
,
exceptions
,
first
,
in
,
insensitive
,
is
,
keywords
,
operators
,
optional
,
second
,
sensitive
,
sequences
,
style
-
the list of the keywords designating faces is
Comment
,
Comment_strong
,
Encoding
,
Error
,
Index1
,
Index2
,
Index3
,
Index4
,
Invisible
,
Keyword
,
Keyword_strong
,
Label
,
Label_strong
,
Plain
,
String
,
Symbol
,
Tag1
,
Tag2
,
Tag3
,
Tag4
-
the list of keywords designating special sequences is
C-char
,
C-string
-
the list of keywords representing special characters is
---
,
\Alpha
,
\Beta
,
\Chi
,
\Delta
,
\Downarrow
,
\Epsilon
,
\Eta
,
\Gamma
,
\Im
,
\Iota
,
\Kappa
,
\Lambda
,
\Leftarrow
,
\Leftrightarrow
,
\Mu
,
\Nu
,
\Omega
,
\Omicron
,
\Phi
,
\Pi
,
\Psi
,
\Re
,
\Rho
,
\Rightarrow
,
\Sigma
,
\Tau
,
\Theta
,
\Uparrow
,
\Upsilon
,
\Xi
,
\Zeta
,
\aleph
,
\alpha
,
\angle
,
\approx
,
\beta
,
\bullet
,
\cap
,
\carriagereturn
,
\cdot
,
\chi
,
\circ
,
\clubsuit
,
\cong
,
\copyright
,
\cup
,
\delta
,
\diamondsuit
,
\div
,
\downarrow
,
\emptyset
,
\epsilon
,
\equiv
,
\eta
,
\exists
,
\florin
,
\forall
,
\gamma
,
\geq
,
\heartsuit
,
\in
,
\infty
,
\int
,
\iota
,
\kappa
,
\lambda
,
\langle
,
\lceil
,
\ldots
,
\leftarrow
,
\leftrightarrow
,
\leq
,
\lfloor
,
\mu
,
\nabla
,
\neq
,
\not
,
\not\in
,
\not\subset
,
\nu
,
\omega
,
\omicron
,
\oplus
,
\otimes
,
\partial
,
\perp
,
\phi
,
\pi
,
\pm
,
\prime
,
\prod
,
\propto
,
\psi
,
\radicalex
,
\rangle
,
\rceil
,
\register
,
\rfloor
,
\rho
,
\rightarrow
,
\sigma
,
\sim
,
\spadesuit
,
\subset
,
\subseteq
,
\suchthat
,
\sum
,
\supset
,
\supseteq
,
\surd
,
\tau
,
\theta
,
\therefore
,
\times
,
\trademark
,
\uparrow
,
\upsilon
,
\varUpsilon
,
\varcopyright
,
\vardiamondsuit
,
\varphi
,
\varpi
,
\varregister
,
\varsigma
,
\vartheta
,
\vartrademark
,
\vee
,
\wedge
,
\wp
,
\xi
,
\zeta
It is a good idea to print the style sheet
`symbols.ssh'
to see
them:
a2ps symbols.ssh
-
a string starts and finishes with
`"'
, and may contain anything.
Regular
C
escaping mechanism is used.
-
a regular expression starts and finishes with
`/'
, and may contain
anything.  Regular
C
escaping mechanism is used.  Regexps can be
split in several parts,
a` la
C strings (i.e.,
`/part 1/ /part
2/'
).
-
any sequence of regular characters which is not a keyword, is a string
(consider this as a shortcut, avoiding extraneous
`"'
).
[
#SEC89
<
]
[
#SEC91
>
]
[
#SEC65
<<
]
[
#SEC88
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.6.2 Style Sheet Header
The definition of the name of the style sheet is:
style
name
is
# body of the style sheet
end
style
The following constructions are optional:
version
To define the version number of the style sheet
version is
version-number
written
To define the author(s).
written by
authors
Giving your email is useful for bug reports about style sheets.
written by "Some Body <Some.Body@some.whe.re>"
requires
To specify the version of a2pswhich requires a higher version number than its own.
requires a2ps
a2ps-version-number
documentation
To leave extra comments people should read.
documentation is
strings
end documentation
strings
may be a list of strings, without comas, in which case new
lines are automatically inserted between each item.  See section
#SEC52
Documentation Format
, for details on the format.
Please, write useful comments, not
`This style is devoted to C
files'
, since the name is here for that, nor
`Report errors to
mail@me.somewhere'
, since
written by
is there for that.
documentation is
"Not all the keywords are used, to avoid too much"
"bolding. Heavy highlighting (code(-g)code), covers"
"the whole language."
end documentation
[
#SEC90
<
]
[
#SEC92
>
]
[
#SEC65
<<
]
[
#SEC88
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.6.3 Syntax of the Words
There are two things a2psand whether the style is case insensitive.
alphabet
To define two different alphabets, use
first alphabet is
string
second alphabet is
string
If both are identical, you may use the shortcut
alphabets are
string
The default alphabets are
first alphabet is
"abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ_"
second alphabet is
"abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ_\
0123456789"
Note that it is on purpose that no characters interval are used.
case
case insensitive        #
e.g., C, C++ etc.
case sensitive          #
e.g., Perl, Sather, Java etc.
The default is
case insensitive
.
[
#SEC91
<
]
[
#SEC93
>
]
[
#SEC65
<<
]
[
#SEC88
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.6.4 Inheriting from Other Style Sheets
It is possible to extend an existing style. The syntax is:
ancestors are
ancestor_1
[,
ancestor_2
...]
end ancestors
where
ancestor1
etc. are style sheet keys.
For semantics, the rules are the following:
-
the ancestors are read in order;
-
the definition of the current style is read last;
-
it is always the last item read which wins (last defined alphabets, case
sensitivity, keywords, operators and sequences).
As an example, both
C++
and
Objective C
style sheets
extend the
C
style sheet:
style "Objective C" is
#
[...]
ancestors are
c
end ancestors
#
[...]
end style
To the biggest surprise of the author, mutually dependent style sheets
do work!
[
#SEC92
<
]
[
#SEC94
>
]
[
#SEC65
<<
]
[
#SEC88
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.6.5 Syntax for the P-Rules
See section
#SEC85
P-Rules
, for the definition of
P-rule
.
Because of various short cuts, there are many ways to declare a rule:
rules
::=
rule_1
`,'
rule_2
...
rule
::=
`('
lhs
rhs
`)'
|
lhs
srhs
;
lhs
::=
string
|
regex
;
rhs
::=
srhs
`,'
...
srhs
::=
latex-keyword
|
expansion
face
expansion
::=
string
|
`\'
num
| <nothing>;
face
::=
face-keyword
| <nothing>;
The rules are the following:
-
If the left-hand side (lhs) is a regular expression, then it is compiled
with the following syntax bits:
#define RE_SYNTAX_A2PS \
(/* Allow char classes. */					\
RE_CHAR_CLASSES						\
/* Be picky. */						\
| RE_CONTEXT_INVALID_OPS					\
/* Allow intervals with `{' and `}', forbid invalid ranges. */\
| RE_INTERVALS | RE_NO_BK_BRACES | RE_NO_EMPTY_RANGES		\
/* `(' and `)' are the grouping operators. */			\
| RE_NO_BK_PARENS						\
/* `|' is the alternation. */					\
| RE_NO_BK_VBAR)
Basically it means that all of the possible operators are used, and that
they are in non-backslashed form.  For instance
`('
and
`)'
stand for the group operator, while
`\\('
stands for the character
`('
.  See
regex.html#Regular-Expression-Syntax
(regex)Regular Expression Syntax
section `Regular Expression Syntax' in
Regex manual
, for a detailed description of the regular
expressions.
-
If no
expansion
is specified, then the matched string is used.
For instance
`(/fo*/, NULL, Keyword)'
applied on the source
`fooooo'
produces
`fooooo'
in
Keyword
.
-
If no
face
is given, then
-
if the context defines the default face, then this face is used;
-
if no default face is given,
PLAIN
is used.
[
#SEC93
<
]
[
#SEC95
>
]
[
#SEC65
<<
]
[
#SEC88
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.6.6 Declaring the keywords and the operators
Basically, keywords and operators are lists of rules.  The syntax is:
keywords are
rules
end keywords
or
keywords in
face-keyword
are
rules
end keywords
in which case the default face is set to
face-keyword
.
As an example:
keywords in Keyword_strong are
/foo*/,
"bar" "BAR" Keyword,
-> \rightarrow
end keywords
is valid.
The syntax for the operators is the same, and both constructs can be
qualified with an
optional
flag, in which case they are taken
into account in the heavy highlighting mode (see section
#SEC27
Pretty Printing Options
).
This is an extract of the
C
style sheet:
optional operators are
-> \rightarrow,
&& \wedge,
|| \vee,
!= \neq,
== \equiv,
# We need to protect these, so that <= is not replaced in <<=
<<=,
>>=,
<= \leq,
>= \geq,
! \not
end operators
Note how
`<<='
and
`>>='
are protected (there are defined to
be written as is when met in the source).  This is to prevent the two
last characters of
`<<='
from being converted into a `less or
equal' sign.
The order in which you define the elements of a category (but the
sequences) does not matter.  But since a2psmay save time if the alphabetical
C
-order is more or less
followed.
You should be aware that when declaring a keyword with a regular
expression as lhs, then a2psmatching only if there are no character of the first alphabet both just
before, and just after the string.
In term of implementation, it means that
keywords are
/foo|bar/
end keywords
is exactly the same as
operators are
/\\b(foo|bar)\\b/
end operators
This can cause problems if you use anchors (e.g.
$
, or
^
)
in keywords: the matcher will be broken.  In this particular case,
define your keywords as operators, taking care of the
`\\b'
by
yourself.
See
regex.html#Match_002dword_002dboundary-Operator
(regex)Match-word-boundary Operator
section `Match-word-boundary Operator' in
Regex manual
, for details on
`\b'
.
[
#SEC94
<
]
[
#SEC96
>
]
[
#SEC65
<<
]
[
#SEC88
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.6.7 Declaring the sequences
Sequences admit several declarations too:
sequences
::= sequences are
sequence_1
`,'
sequence_2
...
end sequences
sequence
::=
rule
in_face
close_opt
exceptions_opt
|
C-string
|
C-char
;
close_opt
::=
rule
| closers are
rules
end closers
| <nothing>
;
exceptions_opt
::= exceptions are
rules
end exceptions
| <nothing>
;
The rules are:
-
The default face is then
in_face
.
-
If no closing rule is given,
`"\n"'
(i.e., end-of-line) is used.
As a first example, here is the correct definition for a
C
string:
sequences are
"\"" Plain String "\"" Plain
exceptions are
"\\\\", "\\\""
end exceptions
end sequences
Since a great deal of languages uses this kind of constructs, you may
use
C-string
to mean exactly this, and
C-char
for
manifest characters defined the
C
way.
The following example comes from
`ssh.ssh'
, the style sheet for
style sheet files, in which there are two kinds of pseudo-strings: the
strings (
`"example"'
), and the regular expressions
(
`/example/'
).  We do not want the content of the pseudo-strings in
the face
String
.
sequences are
# The comments
"#" Comment,
# The name of the style sheet
"style " Keyword_strong (Label + Index1) " is" Keyword_strong,
# Strings are exactly the C-strings, though we don't want to
# have them in the "string" face
"\"" Plain "\""
exceptions are
"\\\\", "\\\""
end exceptions,
# Regexps
"/" Plain "/"
exceptions are
"\\\\", "\\\/"
end exceptions
end sequences
The order between sequences does matter.  For instance in Java,
`/**'
introduces strong comments, and
`/*'
comments.
`/**'
must
be declared before
`/*'
, or it will be
hidden.
There are actually some sequences that could have been implemented as
operators with a specific regular expression (that goes up to the
closer).  Nevertheless be aware of a big difference: regular expression
are applied to a single line of the source file, hence, they cannot
match on several lines.  For instance, the
C
comments,
/*
* a comment
*/
cannot be implemented with operators, though
C++
comments can:
//
// a comment
//
[
#SEC95
<
]
[
#SEC97
>
]
[
#SEC65
<<
]
[
#SEC88
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.6.8 Checking a Style Sheet
Once your style sheet is written, you may want to let a2pssimple tests on it (e.g., checking there are no rules involving upper
case characters in a case insensitive style sheet, etc.).  These tests
are performed when verbosity includes the style sheets.
you may also want to use the special convention that when a style sheet
is required with a suffix, then a2pspath, but precisely from when you are.
Suppose for instance you extended the
`c.ssh'
style sheet, which is
in the current directory, and is said case insensitive.  Run
ubu $ a2ps foo.c -Ec.ssh -P void -v sheets
# Long output deleted
Checking coherence of "C" (c.ssh)
a2ps: c.ssh:`FILE' uses upper case characters
a2ps: c.ssh:`NULL' uses upper case characters
"C" (c.ssh) is corrupted.
---------- End of Finalization of c.ssh
Here, it is clear that
C
is not case insensitive.
[
#SEC96
<
]
[
#SEC98
>
]
[
#SEC65
<<
]
[
#SEC65
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.7 A Tutorial on Style Sheets
In this section a simple example of style sheet is entirely covered:
that of
`ChangeLog'
files.
`ChangeLog'
files are some kind of memory of changes done to files,
so that various programmers can understand what happened to the sources.
This helps a lot, for instance, in guessing what recent changes may have
introduced new bugs.
#SEC98
7.7.1 Example and syntax
ChangeLog files
#SEC99
7.7.2 Implementation
Implementation of chlog.ssh
#SEC100
7.7.3 The Entry in
`sheets.map'
Getting automatic style selection
#SEC101
7.7.4 More Sophisticated Rules
Complex regular expressions
#SEC102
7.7.5 Guide Line for Distributed Style Sheets
Additional Constraints
[
#SEC97
<
]
[
#SEC99
>
]
[
#SEC65
<<
]
[
#SEC97
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.7.1 Example and syntax
First of all, here is a sample of a
`ChangeLog'
file, taken from
the
`misc/'
directory of the original a2ps
Sun Apr 27 14:29:22 1997  Akim Demaille  <demaille@inf.enst.fr>
* base.ps: Merged in color.ps, since now a lot is
common [added box and underline features].
Fri Apr 25 14:05:20 1997  Akim Demaille  <demaille@inf.enst.fr>
* color.ps: Added box and underline routines.
Mon Mar 17 20:39:11 1997  Akim Demaille  <demaille@gargantua.enst.fr>
* base.ps: Got rid of CourierBack and reencoded_backspace_font.
Now the C has to handle this by itself.
Sat Mar  1 19:12:22 1997  Akim Demaille  <demaille@gargantua.enst.fr>
* *.enc: they build their own dictionaries, to ease multi
lingual documents.
The syntax is really simple: A line specifying the author and the date
of the changes, then a list of changes, all of them starting with an
star followed by the name of the files concerned, then optionally
between parentheses the functions affected, and then some comments.
[
#SEC98
<
]
[
#SEC100
>
]
[
#SEC65
<<
]
[
#SEC97
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.7.2 Implementation
Quite naturally the style will be called
ChangeLog
, hence:
style ChangeLog is
written by "Akim Demaille <demaille@inf.enst.fr>"
version is 1.0
requires a2ps 4.9.5
documentation is
"This is a tutorial style sheet.\n"
end documentation
...
end style
A first interesting and easy entry is that of function names, between
`('
and
`)'
:
sequences are
"(" Plain Label ")" Plain
end sequences
A small problem that may occur is that there can be several functions
mentioned separated by commas, that we don't want to highlight this way.
Commas, here, are exceptions.  Since regular expressions are not yet
implemented in a2ps@c, there is a simple but stupid way to avoid that
white spaces are all considered as part of a function name, namely
defining two exceptions: one which captures a single comma, and a
second, capturing a comma and its trailing space.
For the file names, the problem is a bit more delicate, since they may
end with
`:'
, or when starts the list of functions.  Then, we
define two sequences, each one with one of the possible closers, the
exceptions being attached to the first one:
sequences are
"* " Plain Label_strong ":" Plain
exceptions are
", " Plain, "," Plain
end exceptions,
"* " Plain Label_strong " " Plain
end sequences
Finally, let us say that some words have a higher importance in the core
of text: those about removing or adding something.
keywords in Keyword_strong are
add, added, remove, removed
end keywords
Since they may appear in lower or upper, of mixed case, the style will
be defined as case insensitive.
Finally, we end up with this style sheet file, in which an optional
highlighting of the mail address of the author is done.  Saving the file
is last step.  But do not forget that a style sheet has both a name as
nice as you may want (such as
`Common Lisp'
), and a key on which
there are strict rules: the prefix must be alpha-numerical, lower case,
with no more than 8 characters.  Let's chose
`chlog.ssh'
.
# This is a tutorial on a2ps' style sheets
style ChangeLog is
written by "Akim Demaille <demaille@inf.enst.fr>"
version is 1.0
requires a2ps 4.9.5
documentation is
"Second level of high lighting covers emails."
end documentation
sequences are
"(" Plain Label ")" Plain
exceptions are
", " Plain, "," Plain
end exceptions,
"* " Plain Label_strong ":" Plain
exceptions are
", " Plain, "," Plain
end exceptions,
"* " Plain Label_strong " " Plain
end sequences
keywords in Keyword_strong are
add, added, remove, removed
end keywords
optional sequences are
< Plain Keyword > Plain
end sequences
end style
As a last step, you may which to let a2psits syntax, and common errors:
ubu $ a2ps -vsheet -E/tmp/chlog.ssh ChangeLog -P void
Long output deleted
Checking coherence of "ChangeLog" (/tmp/chlog.ssh)
"ChangeLog" (/tmp/chlog.ssh) is sane.
---------- End of Finalization of /tmp/chlog.ssh
It's all set, your style sheet is ready!
[
#SEC99
<
]
[
#SEC101
>
]
[
#SEC65
<<
]
[
#SEC97
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.7.3 The Entry in
`sheets.map'
The last touch is to include the pattern rules about
`ChangeLog'
files (which could appear as
`ChangeLog.old'
etc.) in
`sheets.map'
:
# ChangeLog files
chlog:  /ChangeLog*/
This won't work...  Well, not always.  Not for instance if you print
`misc/ChangeLog'
.  This is not a bug, but truly a feature, since
sometimes one gets more information about the type of a file from its
path, than from the file name.
Here, to match the preceding path that may appear, just use
`*'
:
# ChangeLog files
chlog:  /*ChangeLog*/
If you want to be more specific (
`FooChangeLog'
should not
match), use:
# ChangeLog files
chlog:  /ChangeLog*/ /*\/ChangeLog*/
[
#SEC100
<
]
[
#SEC102
>
]
[
#SEC65
<<
]
[
#SEC97
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.7.4 More Sophisticated Rules
The example we have presented until now uses only basic features, and
does not take advantage of the regexp.  In this section we should how
to write more evolved pretty printing rules.
The target will be the lines like:
Sun Apr 27 14:29:22 1997  Akim Demaille  <demaille@inf.enst.fr>
Fri Apr 25 14:05:20 1997  Akim Demaille  <demaille@inf.enst.fr>
There are three fields: the date, the name, the mail.  These lines all
start at the beginning of line.  The last field is the easier to
recognize: is starts with a
`<'
, and finishes with a
`>'
.  Its
rule is then
`/<[^>]+>/'
.  It is now easier to specify the second:
it is composed only of words, at least one, separated by blanks, and is
followed by the mail:
`/[[:alpha:]]+([ \t]+[[:alpha:]]+)*/'
.
To concatenate the two, we introduce optional blanks, and we put each one
into a pair of
`('
-
`)'
to make each one a recognizable
part:
([[:alpha:]]+([ \t]+[[:alpha:]]+)*)
(.+)
(<[^>]+>)
Now the first part is rather easy: it starts at the beginning of the
line, finishes with a digit.  Once again, it is separated from the
following field by blanks. Split by groups (see
regex.html#Grouping-Operators
(regex)Grouping Operators
section `Grouping Operators' in
Regex manual
), we have:
^
([^\t ].*[0-9])
([ \t]+)
([[:alpha:]]+([ \t]+[[:alpha:]]+)*)
(.+)
(<[^>]+>)
Now the destination is composed of back references to those groups,
together with a face:
# We want to highlight the date and the maintainer name
optional operators are
(/^([^\t ].*[0-9])/                        # \1. The date
/([ \t]+)/                                # \2. Spaces
/([[:alpha:]]+([ \t]+[[:alpha:]]+)*)/     # \3. Name
/(.+)/                                    # \5. space and <
/(<[^>]+)>/                               # \6. email
\1 Keyword, \2 Plain, \3 Keyword_strong,
\5 Plain, \6 Keyword, > Plain)
end operators
Notice the way regexps are split, to ease reading.
[
#SEC101
<
]
[
#SEC103
>
]
[
#SEC65
<<
]
[
#SEC97
Up
]
[
#SEC103
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
7.7.5 Guide Line for Distributed Style Sheets
This section is meant for people who wish to contribute style sheets.
There is a couple of additional constraints, explained here.
The Copyright
Please, do put a copyright in your file, the same as all other
distributed files have: it should include your name, but also the three
paragraphs stating the sheet is covered by the GPL.  I won't distribute
files without these paragraphs.
The Version
Do put a version number, so that people can track evolutions.
The Requirements
Make sure to include a requirement on the needed version of a2ps@c.  If
you don't know what to put, just put the version of the a2ps
The Documentation
The documentation string is mandatory.  Unless the language your style
sheet covers is widely known, please document a bit what the style sheet
is meant for.  If there were choices you made, if there are special
behaviors, document them.
The
`sheets.map'
Entries
Put in a comment on the
`sheets.map'
lines that correspond to your
style sheet.
A Test File
It is better to give a test file, as small as possible, that contains
the most specific and/or most difficult contructs that your style sheet
supports.  I need to be able to distribute this file, therefore, do not
put anything that is copyrighted.
Finally, make sure your style sheet behaves well! (see section
#SEC96
Checking a Style Sheet
)
[
#SEC102
<
]
[
#SEC104
>
]
[
#SEC65
<<
]
[
#SEC1
Up
]
[
#SEC113
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
8. PostScript
This chapter is devoted to the information which is only relevant to
PostScript.
#SEC104
8.1 Foreword: Good and Bad PostScript
How to lose, how to win
#SEC105
8.2 Page Device Options
Accessing some printers' features
#SEC106
8.3 Statusdict Options
Some other features
#SEC107
8.4 Colors in PostScript
Specifying a color or a gray
#SEC108
8.5 a2ps
Convention for PostScript library files
#SEC109
8.6 Designing PostScript Prologues
Make it look like what you want
[
#SEC103
<
]
[
#SEC105
>
]
[
#SEC103
<<
]
[
#SEC103
Up
]
[
#SEC113
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
8.1 Foreword: Good and Bad PostScript
To read this section, the reader must understand what DSC are
(see section
#SEC148
Glossary
).
Why are there good PostScript files, easy to post-process, and bad
files that none of my tools seem to understand?  They print fine
though!
Once you understood that PostScript is not a page description format
(like PDF is), you'll have understood most of the problem.  Let's
imagine for a second that you are a word processor.
The user asks you to print his/her 100 page document in PostScript.  Up
to page 50, there are few different fonts used.  Then, on pages 51 to
80, there are now many different heavy fonts.
When/where will you download the fonts?
The most typical choice, sometimes called
Optimize for Speed
, is,
once you arrived to page 51, to download those fonts
once
for
the rest of the document.  The global processing chain will have worked
quite quickly: little effort from the software, same from the printer;
better yet: you can start sending the file to the printer even before it
is finished!  The problem is that this is not DSC conformant, and it is
easy to understand why: if somebody wants to print only the page 60,
then s/he will lack the three fonts which were defined in page 51...
This document is not page independent.
Another choice is to download the three fonts in
each
page
ranging from 51 to 80, that is the PostScript file contains 30 times the
definition of each font.  It is easy for the application to do that, but
the file is getting real big, and the printer will have to interpret 30
times the same definitions of fonts.  But it is DSC conformant!  And you
can still send the file while you make it.
Now you understand why
Non DSC conformant files are not necessarily badly designed
files from broken applications.
They are files meant to be sent directly to the printer (they are still
perfect PostScript files after all!), they are not meant to be
post-processed.  And the example clearly shows why they are
right
.
There is a third possibility, sometimes called
Optimize for
Portability
: downloading the three fonts in the prologue of the
document, i.e., the section before the first page where are given all
the common definitions of the whole file.  This is a bit more
complicated to implement (the prologue, which is issued first though,
grows at the same time as you process the file), and cannot be sent
concurrently with the processing (you have to process the whole file to
design the prologue).  This file is small (the fonts are downloaded once
only), and DSC conformant.  Well, there are problems, of course...  You
need to wait before sending the output, it can be costly for the
computer (which cannot transfer as it produces), and for the printer
(you've burnt quite a lot of RAM right since the beginning just to hold
fonts that won't be used before page 51...  This can be a real problem
for small printers).
This is what a2ps
If should be clear that documents optimized for speed should never
escape the way between the computer and the printer: no post-processing
is possible.
What you should remember is that some applications offer the possibility
to tune the PostScript output, and they can be praised for that.
Unfortunately, when these very same applications don't automatically
switch to ``Optimize for Portability'' when you save the PostScript
file, and they can be criticized for that.
So please, think of the people after you: if you create a PostScript
file meant to be exchanged, read, printed, etc; by other people: give
sane DSC conformant, optimized for portability files.
[
#SEC104
<
]
[
#SEC106
>
]
[
#SEC103
<<
]
[
#SEC103
Up
]
[
#SEC113
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
8.2 Page Device Options
Page device is a PostScript level 2 feature that offers an uniform
interface to control the printer's output device.  a2pspage device options inside an if block so they have no effect in level 1
interpreters.  Although all level 2 interpreters support page device,
they do not have to support all page device options.  For example some
printers can print in duplex mode and some can not.  Refer to the
documentation of your printer for supported options.
Here are some usable page device options which can be selected with the
`-S'
option (
`--setpagedevice'
).  For a complete listing, see
PostScript Language Reference Manual
(section 4.11 Device Setup
in the second edition, or section 6, Device Control in the third
edition).
Collate
boolean
how output is organized when printing multiple copies
Duplex
boolean
duplex (two side) printing
ManualFeed
boolean
manual feed paper tray
OutputFaceUp
boolean
print output `face up' or `face down'
Tumble
boolean
how opposite sides are positioned in duplex printing
[
#SEC105
<
]
[
#SEC107
>
]
[
#SEC103
<<
]
[
#SEC103
Up
]
[
#SEC113
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
8.3 Statusdict Options
The
statusdict
is a special storage entity in PostScript (called
a
dictionary
), in which some variables and operators determine the
behavior of the printer.  This is an historic horror that existed before
page device definitions were defined.  They are even more printer
dependent, and are provided only for the people who don't have a level
printer.  In any case, refer to the documentation of your printer for
supported options.
Here are some statusdict definitions in which you might be interested:
manualfeed
boolean
Variable which determine that the manual fed paper tray will be used.
Use is
`--statusdict=manualfeed::true'
.
setmanualfeed
boolean
Idem as the previous point, but use is
`--statusdict=setmanualfeed:true'
.
setduplexmode
boolean
If
boolean
, then print Duplex.  Use if
`--statusdict=setduplexmode:true'
.
[
#SEC106
<
]
[
#SEC108
>
]
[
#SEC103
<<
]
[
#SEC103
Up
]
[
#SEC113
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
8.4 Colors in PostScript
Nevertheless, here are some tips on how to design your PostScript
styles.  It is strongly recommended to use
`gray.pro'
or
`color.pro'
as a template.
There are two PostScript instructions you might want to use in your new
PostScript prologue:
setgray
this instruction must be preceded by a number between 0 (black) and 1
(white).  It defines the gray level used.
setrgbcolor
this instruction must be preceded by three numbers between 0 (0 %) and 1
(100%).  Those three numbers are related to red, green and blue
proportions used to designate a color.
a2psboth use an argument as in
setrgbcolor
.  So if you wanted a gray
shade, just give three times the same ratio.
[
#SEC107
<
]
[
#SEC109
>
]
[
#SEC103
<<
]
[
#SEC103
Up
]
[
#SEC113
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
8.5 a2ps
a2psas font files, and others are meant for a2ps only.
All a2ps files have two parts, one being the comments, and the other
being the content, separated by the following line:
% code follows this line
[
#SEC108
<
]
[
#SEC110
>
]
[
#SEC103
<<
]
[
#SEC103
Up
]
[
#SEC113
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
8.6 Designing PostScript Prologues
It is pretty known that satisfying the various human tastes is an
NEXPTIME-hard problem, so a2psthrough the
prologue files
.  But since the authors feel a little
small against NEXPTIME, they agreed on the fact that
you
are
the one who will design the look you like.
Hence in this section, you will find what you need to know to be able to
customize a2ps
Basically, a2ps"meaning" in the text.  a2ps
#SEC110
8.6.1 Definition of the faces
What goes in a characters style
#SEC111
8.6.2 Prologue File Format
Including documentation
#SEC112
8.6.3 A step by step example
[
#SEC109
<
]
[
#SEC111
>
]
[
#SEC103
<<
]
[
#SEC109
Up
]
[
#SEC113
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
8.6.1 Definition of the faces
There are three things that define a face:
Its font
You should never call the font by yourself, because sometimes a2psdecide that another font would be better.  This is what happens for
instance if a font does not support the encoding you use.
Hence, never set the font by yourself, but ask a2psdone through a line:
%Face:
face
real-font-name
size
This line tells a2ps
real-font-name
.  It will replace this line by the correct
PostScript line to call the needed font, and will do everything needed
to set up the font.
The size of the text body is
bfs
.
Its background color
There are two cases:
You want a background color, then give the
RGB
(see section
#SEC107
Colors in PostScript
) ratio and
true
to
BG
:
0.8 0.8 0 true BG
You don't want a background color, then call
BG
with
false
:
false BG
Its foreground color
As
BG
, call
FG
with an
RGB
ratio:
0 0.5 0 FG
Its underlining
UL
requires a boolean argument, depending whether you want
or not the current face to be underlined.
true UL
Its boxing
Requiring a boolean,
BX
let's a face have a box drawn around.
[
#SEC110
<
]
[
#SEC112
>
]
[
#SEC103
<<
]
[
#SEC109
Up
]
[
#SEC113
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
8.6.2 Prologue File Format
Prologue files for a2ps(reported with
`--list-prologues'
) can be included in the comment
part:
Documentation
This prologue is the same as the prologue code(pb)code, but using
the bold version of the fonts.
EndDocumentation
% code follows this line
See section
#SEC52
Documentation Format
, for more on the format.
[
#SEC111
<
]
[
#SEC113
>
]
[
#SEC103
<<
]
[
#SEC109
Up
]
[
#SEC113
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
8.6.3 A step by step example
We strongly suggest our readers not to start from scratch, but to copy
one of the available styles (see the result of
`a2ps
--list=prologues'
), to drop it in one of a2ps
`$HOME/.a2ps'
, and to patch it until you like it.
Here, we will start from
`color.pro'
, trying to give it a funky
look.
Say you want the keywords to be in Helvetica, drawn in a flashy pink on
a light green.  And strong keywords, in Times Bold Italic in brown on a
soft Hawaiian sea green (you are definitely a fine art
amateur
).
Then you need to look for
`k'
and
`K'
:
/k {
false BG
0 0 0.9 FG
%Face: Keyword Courier bfs
Show
} bind def
/K {
false BG
0 0 0.8 FG
%Face: Keyword_strong Courier-Bold bfs
Show
} bind def
and turn it into:
/k {
0.2 1 0.2 true BG
1 0.2 1 FG
%Face: Keyword Helvetica bfs
Show
} bind def
/K {
0.4 0.2 0 true BG
0.5 1 1 FG
%Face: Keyword_strong Times-BoldItalic bfs
Show
} bind def
Waouh!  It looks great!
A bit trickier: let change the way the line numbers are printed.
First, let's look for the font definition:
%%BeginSetup
% The font for line numbering
/f# /Helvetica findfont bfs .6 mul scalefont def
%%EndSetup
Let it be in Times, twice bigger than the body font.
%%BeginSetup
% The font for line numbering
/f# /Times-Roman findfont bfs 2 mul scalefont def
%%EndSetup
How about its foreground color?
% Function print line number (<string> # -)
/# {
gsave
sx cw mul 2 div neg 0 rmoveto
f# setfont
0.8 0.1 0.1 FG
c-show
grestore
} bind def
Let it be blue.  Now you know the process: just put
`0 0 1'
as
FG
arguments.
[
#SEC112
<
]
[
#SEC114
>
]
[
#SEC103
<<
]
[
#SEC1
Up
]
[
#SEC127
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
9. Contributions
This chapter documents the various shell scripts or other tools that are
distributed with the a2psreader should also look at the documentation of
Ogonkify
(see
ogonkify.html#Top
(ogonkify)top
section `Overview' in
Ogonkify manual
), written by Juliusz
Chroboczek.
#SEC114
9.1
card
Printing Reference Cards
#SEC117
9.2
fixps
Fixing Some Ill Designed PostScript Files
#SEC119
9.3
fixnt
Fixing Microsoft NT PostScript Files
#SEC121
9.4
pdiff
Produce Pretty Comparison of Files
#SEC123
9.5
psmandup
Printing Duplex on Simplex Printers
#SEC125
9.6
psset
Inserting calls to setpagedevice
[
#SEC113
<
]
[
#SEC115
>
]
[
#SEC113
<<
]
[
#SEC113
Up
]
[
#SEC127
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
9.1
card
Many users of a2pssummary of the options.  In fact, something closely related to the
output of
`a2ps --help'
.
The first version of this reference card was a PreScript file
(see section
#SEC70
PreScript
) to be printed by a2ps@c.  Very soon a much better
scheme was found: using a style sheet to pretty print directly the
output of
`a2ps --help'
!  A first advantage is then that the
reference cards can be printed in the tongue you choose.
A second was that this treatment could be applied to any application
supporting a
`--help'
-like option.
#SEC115
9.1.1 Invoking
card
Command Line Interface
#SEC116
9.1.2 Caution when Using
card
card runs commands
[
#SEC114
<
]
[
#SEC116
>
]
[
#SEC113
<<
]
[
#SEC114
Up
]
[
#SEC127
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
9.1.1 Invoking
card
card [
options
]
applications
[--
a2ps@c-options
]
card
is a shell script which tries to guess how to get your
applications
' help message (typically by the options
`--help'
or
`-h'
), and pretty prints it thanks to a2psthe environment variable
`A2PS'
if it is set).
a2ps@c-options
are passed to a2ps@c.
Supported options are:
Option:
-h
Option:
-
-
help
print a short help message and exit successfully.
Option:
-V
Option:
-
-
version
report the version and exit successfully.
Option:
-q
Option:
-
-
quiet
Option:
-
-
silent
Run silently.
Option:
-D
Option:
-
-
debug
enter in debug mode.
Option:
-l
language
Option:
-
-
language=
language
specify the language in which the reference card should be printed.
language
should be the symbol used by
LC_ALL
etc.
(such as
`fr'
,
`it'
etc.).
If the
applications
don't support internationalization,
English will be used.
Option:
-
-
command=
command
Don't try to guess the
applications
' way to report their
help message, but rather use the call
command
.
A typical example is
card --command="cc -flags"
It is possible to give options to a2psspecifying them after
`--'
.  For instance
card gmake gtar --command="cc -flags" -- -Pdisplay
builds the reference card of
GNU make
,
GNU tar
(automatic
detection of
`--help'
support), and
cc
thanks to
`-flags'
.
[
#SEC115
<
]
[
#SEC117
>
]
[
#SEC113
<<
]
[
#SEC114
Up
]
[
#SEC127
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
9.1.2 Caution when Using
card
Remember that
card
runs the programs you give it, and the
commands you supplied.  Hence if there is a silly programs that has a
weird behavior given the option
`-h'
etc., beware of the result.
It is even clearer using
`--command'
: avoid running
`card
--command="rm -rf *"'
, because the result will be exactly what you think
it will be!
[
#SEC116
<
]
[
#SEC118
>
]
[
#SEC113
<<
]
[
#SEC113
Up
]
[
#SEC127
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
9.2
fixps
The shell script
fixps
tries its best to fix common problems in
PostScript files that may prevent post processing.  It makes heavy use
of the
psutils
.  It is a good idea to use
fixps
in the
PostScript delegations.
It first tries to make simple fixes, but some really broken files may
require a much deeper treatment.  If
fixps
feels the need for
such a major surgery act, it may give up local changes and ask
Ghostscript
for a global rewriting.
#SEC118
9.2.1 Invoking
fixps
Command Line Interface
[
#SEC117
<
]
[
#SEC119
>
]
[
#SEC113
<<
]
[
#SEC117
Up
]
[
#SEC127
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
9.2.1 Invoking
fixps
fixps [
options
] [
file
]
sanitize the PostScript
file
(or of the standard input if no
file
is given, or if
file
is
`-'
).
Supported options are:
Option:
-h
Option:
-
-
help
Print a short help message and a list of the fixes that are
performed.  Exit successfully.
Option:
-V
Option:
-
-
version
report the version and exit successfully.
Option:
-D
Option:
-
-
debug
enter in debug mode.
Option:
-q
Option:
-
-
quiet
Option:
-
-
silent
Run silently.
Option:
-o
file
Option:
-
-
output=
file
specify the
file
in which is saved the output.
Option:
-n
Option:
-
-
no-fix
Don't actually fix the
file
but still honor all of the other
options.  In particular,
`fixps -qn
file
'
is equivalent to
`cat
file
'
.
Option:
-c
Option:
-
-
check
Option:
-
-
dry-run
Don't actually fix the
file
: just report the diagnostics.
Contrary to the option
`fixps -qc'
does absolutely nothing (while
it does take some time to do it nicely).
Option:
-f
Option:
-
-
force
Ask
ghoscript
for a full rewrite of the
file
.  The output
file is really sane, but can be much longer than the original.  For this
reason and others, it is not always a good idea to make a full rewrite.
This option should be used only for files that give major problems.
[
#SEC118
<
]
[
#SEC120
>
]
[
#SEC113
<<
]
[
#SEC113
Up
]
[
#SEC127
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
9.3
fixnt
fixnt
(see its
http://www.itsm.uni-stuttgart.de/~bauer/fixnt.html
http://www.itsm.uni-stuttgart.de/~bauer/fixnt.html
, home page) is
maintained by
mailto:bauer@itsm.uni-stuttgart.de
Holger Bauer
and
mailto:rath@itsm.uni-stuttgart.de
Michael Rath
.  It is meant to fix
the problems of the PostScript files generated by the Microsoft
PostScript driver under Windows NT (3.5 and 4.0).
fixps
is aware of the cases where
fixnt
should be used,
hence you should not worry of when to use
fixnt
.
#SEC120
9.3.1 Invoking
fixnt
Command Line Interface
[
#SEC119
<
]
[
#SEC121
>
]
[
#SEC113
<<
]
[
#SEC119
Up
]
[
#SEC127
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
9.3.1 Invoking
fixnt
fixnt <
`file.ps'
sanitize the PostScript file
file.ps
and produce the result on
the standard output.
[
#SEC120
<
]
[
#SEC122
>
]
[
#SEC113
<<
]
[
#SEC113
Up
]
[
#SEC127
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
9.4
pdiff
The shell script
pdiff
aims to pretty print diffs between files.
It basically uses GNU
diff
(see
diff.html#diff
(diff)diff
section `Overview' in
Comparing and Merging Files
) or GNU
wdiff
(see
wdiff.html#wdiff
(wdiff)wdiff
section `The word difference finder' in
GNU wdiff
) to extract the diff, then calls
a2ps
#SEC122
9.4.1 Invoking
pdiff
Command Line Interface
[
#SEC121
<
]
[
#SEC123
>
]
[
#SEC113
<<
]
[
#SEC121
Up
]
[
#SEC127
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
9.4.1 Invoking
pdiff
pdiff [
options
]
file-1
file-2
[--
a2ps@c-options
]
make a pretty comparison between
file-1
and
file-2
.
a2ps@c-options
are passed to a2ps@c.
Supported options are:
Option:
-h
Option:
-
-
help
print a short help message and exit successfully.
Option:
-V
Option:
-
-
version
report the version and exit successfully.
Option:
-q
Option:
-
-
quiet
Option:
-
-
silent
Run silently.
Option:
-D
Option:
-
-
debug
enter in debug mode.
Option:
-w
Option:
-
-
words
Look for words differences (default).  White space differences are not
considered.
Option:
-l
Option:
-
-
lines
Look for lines differences.
It is possible to give options to a2psspecifying them after
`--'
.  For instance
pdiff COPYING COPYING.LIB -- -1 -P display
Compares the files
`COPYING'
and
`COPYING.LIB'
, and prints it
on the printer
display
(usually
Ghostview
or
gv
).
[
#SEC122
<
]
[
#SEC124
>
]
[
#SEC113
<<
]
[
#SEC113
Up
]
[
#SEC127
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
9.5
psmandup
I personally hate to print documents of hundreds of pages on a single
sided printer.  Too bad, here there are no Duplex printers.  The idea is
then simply first to print the odd pages, then the even in reversed
order.  To make sure one flips the page in the meanwhile, the second
half should be printed from the manual feed tray.
Make a shell script that automates this, and you get
psmandup
.
#SEC124
9.5.1 Invoking
psmandup
Command Line Interface
[
#SEC123
<
]
[
#SEC125
>
]
[
#SEC113
<<
]
[
#SEC123
Up
]
[
#SEC127
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
9.5.1 Invoking
psmandup
psmandup [
options
] [
file
]
produce a manual duplex version of the PostScript
file
(or of the
standard input if no
file
is given, or if
file
is
`-'
). Once the first half is printed, put the sheet stack in the
manual feed tray for the second half
#FOOT4
(4)
.
Be aware that there is a time out for manually fed jobs, usually short,
hence do not miss the moment when the printer asks for the stack.  If
ever you missed that moment, see option
`--back'
to recover the
second half.
Supported options are:
Option:
-h
Option:
-
-
help
print a short help message and exit successfully.
Option:
-V
Option:
-
-
version
report the version and exit successfully.
Option:
-q
Option:
-
-
quiet
Option:
-
-
silent
Run silently.
Option:
-D
Option:
-
-
debug
enter in debug mode.
Option:
-o
file
Option:
-
-
output=
file
specify the
file
in which is saved the output.
Option:
-n
Option:
-
-
no-fix
psmandup
will fail on ill designed PostScript (well, actually the
psutils will).  To avoid this, by default the PostScript file is
sanitized by
fixps
.
When given this option, don't run
fixps
.  This is meant to be
used when
fixps
has already been used higher in the processing
chain.
Option:
-f
Option:
-
-
front
Output only the front pages, with no special PostScript feature request.
Option:
-b
Option:
-
-
back
Output only the back pages, with a manual feed request.
This option is especially useful when the manual feed time out expired
before you could insert back the stack in the manual feed tray.
psmandup
assumes the printer is Level 2, and supports manual
feeding.  The
file
should be reasonably sane, otherwise
psmandup
fails miserably.
Typical use is
psmandup file.ps | lp
or can be put into a2ps@c' printer commands (see section
#SEC39
Your Printers
).
[
#SEC124
<
]
[
#SEC126
>
]
[
#SEC113
<<
]
[
#SEC113
Up
]
[
#SEC127
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
9.6
psset
The shell script
psset
inserts calls to
setpagedevice
in a
PostScript file.  This is useful for instance to add Tumble or Manual
feed request.  Actually,
psmandup
uses
psset
.
You should know nevertheless that a2ps
setpagedevice
by itself, i.e., you can run
`a2ps
-SManualFeed foo'
to print
`foo'
onto the manually fed tray, or run
`a2ps -s2 foo'
to print Duplex.  There are no need of
psset
from a2ps@c.
#SEC126
9.6.1 Invoking
psset
Command Line Interface
[
#SEC125
<
]
[
#SEC127
>
]
[
#SEC113
<<
]
[
#SEC125
Up
]
[
#SEC127
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
9.6.1 Invoking
psset
psset [
options
] [
file
]
produce a version of the PostScript
file
(or of the standard input
if no
file
is given, or if
file
is
`-'
) that makes
protected calls to the PostScript operator
setpagedevice
.
Typical use is making
file
print duplex, or on the manual tray
etc.
The call is protected so that the resulting file is safe, i.e., will
still be portable, even with requests such as
`-Sfoo:bar'
.
It is safe to run
psset
with no feature requests.  Depending upon
the option
`--no-fix'
, it is either equivalent to doing nothing, or
to running
fixps
(see section
#SEC117
fixps
).
Supported options are:
Option:
-h
Option:
-
-
help
Print a short help message and exit successfully.
Option:
-V
Option:
-
-
version
report the version and exit successfully.
Option:
-D
Option:
-
-
debug
enter in debug mode.
Option:
-q
Option:
-
-
quiet
Option:
-
-
silent
Run silently.
Option:
-o
file
Option:
-
-
output=
file
specify the
file
in which is saved the output.
Option:
-n
Option:
-
-
no-fix
psset
will fail on ill designed PostScript.  Actually it is the
psutils that fail.  To avoid this, by default the PostScript file is
sanitized by
fixps
.
When given this option, don't run
fixps
.  This is meant to be
used when
fixps
has already been used higher in the processing
chain.
Option:
-S
key
:
value
Option:
-
-
setpagedevice=
key
:
value
Insert a
setpagedevice
call setting
key
to
value
.
Multiple values accumulate.  Lists of requests separated with
`;'
are valid (e.g.,
`-SDuplex:true;Tumble:false'
).
Option:
-a
page
Option:
-
-
at=
page
Specify the page where the
setpagedevice
call should be done.
The
page
0, which is the default, corresponds to the
`Setup'
section of the document.  More precisely, the insertion is performed at
the end of the
`Setup'
section, so that if there are multiple calls
to
psset
on the same document (which is of course, a bad idea),
the last call is winning.
In a typical use you should not change the
page
.
Option:
-m
Option:
-
-
manualfeed
Alias for
`-SManualFeed:true'
, i.e., the request to print using the
manual feed tray.
Option:
-s
Option:
-
-
simplex
Alias for
`-SDuplex:false'
, i.e., force simplex printing.
Option:
-d
Option:
-
-
duplex
Alias for
`-SDuplex:true;Tumble:false'
, i.e., the request to print
in duplex mode, binding along the long edge of the paper.
Option:
-t
Option:
-
-
tumble
Alias for
`-SDuplex:true;Tumble:true'
, i.e., duplex printing
such that binding should happen on the short edge of the medium.
[
#SEC126
<
]
[
#SEC128
>
]
[
#SEC113
<<
]
[
#SEC1
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10. Frequently asked questions
Please, before sending us mail, make sure the problem you have is not
known, and explained.  Moreover, avoid using the mailing list for asking
question about the options, etc.  It has been built for announces and
suggestions, not to contact the authors.
#SEC128
10.1 Why Does...?
Questions on Error
#SEC136
10.2 How Can I ...?
a2ps' How-To
#SEC144
10.3 Please tell me...
Existential Questions on a2ps
[
#SEC127
<
]
[
#SEC129
>
]
[
#SEC127
<<
]
[
#SEC127
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.1 Why Does...?
Error related questions.
#SEC129
10.1.1 Why Does it Print Nothing?
The printer issues nothing
#SEC130
10.1.2 Why Does it Print in Simplex?
While I asked for Duplex
#SEC131
10.1.3 Why Does it Print in Duplex?
While I asked for Simplex
#SEC132
10.1.4 Why Does it Not Fit on the Paper?
Some parts are missing
#SEC133
10.1.5 Why Does it Print Junk?
Random characters
#SEC134
10.1.6 Why Does it Say my File is Binary?
And refuses to print it
#SEC135
10.1.7 Why Does it Refuse to Change the Font Size
[
#SEC128
<
]
[
#SEC130
>
]
[
#SEC127
<<
]
[
#SEC128
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.1.1 Why Does it Print Nothing?
a2ps
There are two ways that printing can fail: silently, or with a
diagnostic.
First,
check that the printer received what you sent
.  a2psmay correctly do its job, but have the printer queue fail to deliver the
job.  In case of doubt, please check that the printer's leds blink (or
whatever is its way to show that something is being processed).
If the printer does receive the job, but prints nothing at all, check
that you did not give exotic options to an old printer (typically, avoid
printing on two sides on a printer that does not support it).  Avoid
using
`-S'
,
`--setpagedevice'
(see section
#SEC105
Page Device Options
)
and
`--statusdict'
(see section
#SEC106
Statusdict Options
).
If the trouble persists, please try again but with the option
`--debug'
(a PostScript error handler is downloaded), and then send
us:
the input file that gives problems
the output file created by a2ps
the error message that was printed.
[
#SEC129
<
]
[
#SEC131
>
]
[
#SEC127
<<
]
[
#SEC128
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.1.2 Why Does it Print in Simplex?
Though I ask a2psprinted Simplex.
If your printer is too old, then a2pscode it needs when
`-s2'
is specified.  This is because your
printer uses an old and not standardized interface for special features.
So you need to
specify that you want Duplex mode:
`-s2'
,
remove by hand the standardized call to the Duplex feature:
`-SDuplex'
,
add the non standard call to Duplex.  Try
`--statusdict=setduplexmode:true'
.
Since this is painful to hit, a User Option (see section
#SEC40
Your Shortcuts
)
should help.
[
#SEC130
<
]
[
#SEC132
>
]
[
#SEC127
<<
]
[
#SEC128
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.1.3 Why Does it Print in Duplex?
Though I ask a2psprinted Duplex.
Actually when you require Simplex, a2psreasons.  Hence, if your printer is defaulted to Duplex, the job will be
Duplexed.  So you have to force a2ps
`-SDuplex:false'
.  The user options
`-=s1'
and
`-=simplex'
have names easier to remember.
In the next version of a2psfixed in a user friendly way.
[
#SEC131
<
]
[
#SEC133
>
]
[
#SEC127
<<
]
[
#SEC128
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.1.4 Why Does it Not Fit on the Paper?
When I print text files with a2ps@c, it prints beyond the frame of
the paper.
You are most probably printing with a bad medium, for instance using A4
paper within a2ps@c, while your printer uses Letter paper.  Some jet
printers have a small printable area, and a2psboth case, read
#SEC23
Sheet Options
, option
`--medium'
for more.
[
#SEC132
<
]
[
#SEC134
>
]
[
#SEC127
<<
]
[
#SEC128
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.1.5 Why Does it Print Junk?
What I get on the printer is long and incomprehensible.  It does not
seem to correspond to what I wanted to print.
You are probably printing a PostScript file or equivalent.  Try to print
with
`-Z'
: a2psprogram that can help you (see section
#SEC46
Your Delegations
).  In case of doubt,
don't hesitate to save into a file, and check the content with
Ghostview
, or equivalent:
$ a2ps my_weird_file -Z -o mwf.ps
$ gv mwf.ps
If your a2psfake-printer:
$ a2ps my_weird_file -Z -P display
If it is incorrect, ask for help around you.
[
#SEC133
<
]
[
#SEC135
>
]
[
#SEC127
<<
]
[
#SEC128
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.1.6 Why Does it Say my File is Binary?
a2ps
There are several reasons that can cause a2psbinary:
-
there are many non printable characters in the file.  Then you need to
use the option
`--print-anyway'
.
-
the file is sane, composed of printable characters.  Then it is very
likely that
file(1)
said the type of the file is
`data'
, in
which case a2ps
-
specify the type of the file, for instance
`-Eplain'
;
-
specify to print in any case,
`--print-anyway'
;
-
remove the annoying rule from the system's
`sheets.map'
:
binary: <data*>
-
insert in your own
`~/.a2ps/sheets.map'
a rule that overrides that
of the system's
`sheets.map'
:
# Load the system's sheets.map
include(/usr/local/share/a2ps/sheets/sheets.map)
# Override the rule for files with type `data' according to file(1)
plain: <data*>
But this is not very good, since then this rule is always the first
tested, which means that any file with type
`data'
according to
file(1)
will be printed in
`plain'
style, even if the file
is called
`foo.c'
.
-
if your files can be recognized, insert a new rule in a
`sheets.map'
, such as
# file(1) says it's data, but it's pure text
plain:   /*.txx/
[
#SEC134
<
]
[
#SEC136
>
]
[
#SEC127
<<
]
[
#SEC128
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.1.7 Why Does it Refuse to Change the Font Size
a2ps (or
`--lines-per-page'
, or
`--chars-per-line'
).
This is probably because you used
`-1'
..
`-9'
after the
`--font-size'
.  This is wrong, because the options
`-1'
..
`-9'
set the font size (so that there are 80 characters
per lines), and many other things (See section
#SEC24
Page Options
, option
`--font-size'
).
Hence
`a2ps --font-size=12km -4'
is exactly the same thing as
`a2ps -4'
, but is different from
`a2ps -4 --font-size=12km'
.
Note that the `pure' options (no side-effects) to specify the number of
virtual pages are
`--columns'
and
`--rows'
.
[
#SEC135
<
]
[
#SEC137
>
]
[
#SEC127
<<
]
[
#SEC127
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.2 How Can I ...?
A mini how-to on a2ps@c.
#SEC137
10.2.1 How Can I Leave Room for Binding?
Specifying Margins
#SEC138
10.2.2 How Can I Print
stdin
?
Using a2ps in a pipe chain
#SEC139
10.2.3 How Can I Change the Fonts?
Tired of Courier?
#SEC140
10.2.4 How Can I Simulate the Old Option
`-b'
?
Printing in Bold
#SEC141
10.2.5 How Can I Pass Options to
`lpr'
Disable the banner
#SEC142
10.2.6 How Can I Print on Non PostScript Printers?
Using GhostScript
#SEC143
10.2.7 How Can I Print Man Pages with Underlines
Now it Prints With Italics
[
#SEC136
<
]
[
#SEC138
>
]
[
#SEC127
<<
]
[
#SEC136
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.2.1 How Can I Leave Room for Binding?
The option
`--margin[=
size
]'
is meant for this.  See
#SEC23
Sheet Options
.
[
#SEC137
<
]
[
#SEC139
>
]
[
#SEC127
<<
]
[
#SEC136
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.2.2 How Can I Print
stdin
?
a2ps
`-'
as file name.  Automatic style selection is of course much
weaker: without the file name, a2psopinion (see section
#SEC58
Style Sheet Files
).  In general it means most
delegations are safe, but there will probably be no pretty-printing.
`You'
can supply a name to the standard input
(
`--stdin=
name
'
) with which it could guess the language.
[
#SEC138
<
]
[
#SEC140
>
]
[
#SEC127
<<
]
[
#SEC136
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.2.3 How Can I Change the Fonts?
See section
#SEC109
Designing PostScript Prologues
, for details.  Make sure that all
the information a2ps
[
#SEC139
<
]
[
#SEC141
>
]
[
#SEC127
<<
]
[
#SEC136
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.2.4 How Can I Simulate the Old Option
`-b'
?
By the past, a2psbold.  Since now the fonts are defined by prologues (see section
#SEC109
Designing PostScript Prologues
) this option no longer makes sense.  A replacement
prologue is provided:
`bold'
.  To use it, give the option
`--prologue=bold'
.
[
#SEC140
<
]
[
#SEC142
>
]
[
#SEC127
<<
]
[
#SEC136
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.2.5 How Can I Pass Options to
`lpr'
How can I tell
a2ps
to ask
lpr
no to print the banner?
How can I pass specific options to
lp
?
If your
`Printer:'
fields in the configuration files were properly
filled (see section
#SEC39
Your Printers
), you can use the variable
`lp.options'
to pass options to
lpr
(or
lp
, depending
on your environment):
a2ps -Dlp.options="-h -s" -P printer
You can also define
`lp.options'
once for all, See section
#SEC44
Defining Variables
.
Finally, you can use
`Printer:'
several times to reach a printer
with different
lpr
options.
[
#SEC141
<
]
[
#SEC143
>
]
[
#SEC127
<<
]
[
#SEC136
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.2.6 How Can I Print on Non PostScript Printers?
I use a2psnot PostScript.  How can I do?
Ghostscript
might be the tool you need (see section
#SEC148
Glossary
).  It
support conversion to many different non PostScript printers.
Here are some tips on how to use a non PostScript printer.  If somebody
feels like writing a more precise documentation, she really is welcome.
Please refer to the
Ghostscript
documentation for a precise
description of the tuning you need.
Basically, the first step you need is to achieve to call
Ghostscript
in a pipe chain.  In other words, try to find out the
right arguments
Ghostscript
needs in order to print with a
command like this:
$ cat file.ps | gs
more arguments
In general it is the same command as for calling
Ghostscript
with
a filename, except that the file name to use is
`-'
:
$ cat file.ps \
| gs -q -dNOPAUSE -sDEVICE=deskjet -sOutputFile=- - -c quit\
| lp -d
printer-name
Once it works, it is then easy to settle the right
Printer:
line
in your configuration file (see section
#SEC39
Your Printers
).  For instance:
Printer: djet \
| gs -q -dNOPAUSE -sDEVICE=deskjet -sOutputFile=- - -c quit\
| lp -d djet
mailto:scancm@biobase.dk
Christian Mondrup
uses a2pswith a non PostScript printer.  He uses:
DefaultPrinter: | //c/gstools/gs5.10/Gswin32c.exe         \
-Ic:\gstools\gs5.10;c:\gstools\gs5.10\fonts            \
-sDEVICE=ljet4 -sPAPERSIZE=a4 -dNOPAUSE -r300 -dSAFER  \
-sOutputFile="\\spool\HP LaserJet 5L (PCL)"            \
-q - -c quit
[
#SEC142
<
]
[
#SEC144
>
]
[
#SEC127
<<
]
[
#SEC136
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.2.7 How Can I Print Man Pages with Underlines
By the past, when I printed a man page with a2ps@c, it used
underlines, but now it uses italics.  I want underlines back!
Use
`a2ps --pro=ul'
.
[
#SEC143
<
]
[
#SEC145
>
]
[
#SEC127
<<
]
[
#SEC127
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.3 Please tell me...
Wondering something?
#SEC145
10.3.1 Is a2ps
Printing dates in short format
#SEC146
10.3.2 Why Have the Options Changed?
Respect The Users
#SEC147
10.3.3 Why not having used
yacc
and such
Why Using Style Sheets
[
#SEC144
<
]
[
#SEC146
>
]
[
#SEC127
<<
]
[
#SEC144
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.3.1 Is a2ps
The famous Y2K
#FOOT5
(5)
problem...
Yes, a2psmore recent than 4.10.3.  The expansions of the following escapes were
broken (giving
`100'
instead of
`00'
):
`%D'
,
`%W'
,
`$D'
,
`$W'
.
Nevertheless, please note that if you required a two digit year, expect
to have
`Jan 1st, 00'
someday.
You
are responsible of the
format you want for the date: See section
#SEC30
Escapes
.
[
#SEC145
<
]
[
#SEC147
>
]
[
#SEC127
<<
]
[
#SEC144
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.3.2 Why Have the Options Changed?
The options of this a2ps
True.  But the old scheme (up to version 4.6.1) prevented us from
offering more options.  We
had
to drop it, and to fully
redesign the options handling.
Since that profound change, we try to change as little as possible
between versions.  Nevertheless, as the time passes, we discover that
some never used options should be renamed, or used for something else.
In these cases, compatibility code is left for a long time.
Anywhere you put options but the command line (e.g., in a2psfiles or in shell scripts),
avoid using short options
, since short
options are much more likely to be changed (there are not so many, so it is
a precious resource).  Since there are as many long options as one wants,
we can leave compatibility code with the long options.
[
#SEC146
<
]
[
#SEC148
>
]
[
#SEC127
<<
]
[
#SEC144
Up
]
[
#SEC148
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
10.3.3 Why not having used
yacc
and such
There are several reasons why we decided not to use grammars to parse
the files.  Firstly it would have made the design of the style sheets
much more tricky, and today a2ps
Secondly, it limits the number of persons who could build a style sheet.
Thirdly, we did not feel the need for such a powerful tool: handling the
keywords and the sequences is just what the users expect.
Fourthly, any extension of a2ps
And last but not least, using a parser requires that the sources are
syntactic bug free, which is too strong a requirement.
Nevertheless,
PreScript
gives the possibility to have on the one
hand a syntactic parser which would produce
PreScript
code, and
on the other hand, a2ps@c, which would make it PostScript.  This schema
seems to us a good compromise.  If it is still not enough for you, you
can use the library.
[
#SEC147
<
]
[
#SEC149
>
]
[
#SEC127
<<
]
[
#SEC1
Up
]
[
#SEC149
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
A. Glossary
This section settles some terms used through out this document, and
provides the definitions of some terms you probably want to know about.
Adobe
Adobe is the firm who designed and owns the PostScript language.
The patent that printer manufacturers must pay to Adobe is the
main reason why PostScript printers are so expansive.
AFM file
AFM stands for Adobe Font Metrics.  These files contain everything one
needs to know about a font: the width of the characters, the available
characters etc.
Charset
Code Set
Cf. Encoding.
Delegate
Another filter (application) which a2psThis feature is especially meant for page description files (see section
#SEC46
Your Delegations
).
DSC
Document Structuring Conventions
Because PostScript is a language, any file describing a document can
have an arbitrary complexity.  To ease the post-processing of PostScript
files, the document should follow some conventions.  Basically there are
two kinds of conventions to follow:
Page Independence
Special comments state where the pages begin and end.  With these
comments (and the fact that the code describing a page starts and ends
somewhere, which is absolutely not necessary in PostScript), very simple
programs (such as
psnup
,
psselect
etc.) can post process
PostScript files.
Requirements
Special features may be needed to run correctly the file.  Some comments
specify what services are expected from the printer (e.g., fonts, duplex
printing, color etc.), and other what features are provided by the file
itself (e.g., fonts, procsets etc.), so that a print manager can decide
that a file cannot be printed on that printer, or that it is possible if
the file is slightly modified (e.g., adding a required font not known by
the printer) etc.
The DSC are edited by Adobe.  A document which respects them is said to
be
DSC conformant
.
a2ps
Duplex
DuplexTumble
DuplexNoTumble
To print
Duplex
is to print double-sided.  There are two ways to
print Duplex depending whether the second face is printed upside-down or
not:
DuplexTumble
DuplexTumble is suitable when (if it were to be bound) the document
would be bound along the short edge (for instance when you are printing
booklets).
DuplexNoTumble
DuplexNoTumble corresponds to binding along the long edge of the medium.
A typical case is when printing one-up.
Encoding
Association of human readable characters, and computers' internal
numbered representation.  In other words, they are the alphabets, which
are different according to your country/mother tongue.  E.g.: ASCII,
Latin 1, corresponding to Western Europe etc.
To know more about encodings, see
#SEC60
What is an Encoding
.
Ghostscript
gs
http://www.cs.wisc.edu/~ghost/index.html
Ghostscript
,
gs
for short, is a full PostScript interpreter running under many
various systems (Unices, MS-DOS, Mac etc.).  It comes with a large set
of output formats allowing many different applications:
Displaying
It can be used either to view PostScript files (in general thanks to a
graphic interface such as
Ghostview
or
gv
...).
Converting
To may useful languages/formats: PDF, rewriting in portable PostScript
or Encapsulated PS etc.
Translating
to a printer dedicated language, e.g., PCL.  In particular, thanks to
ghostscript
, you may print PostScript files on non PostScript
printers.
Face
A virtual style given to some text.  For instance,
Keyword
,
Comment
are faces.
Headings
Everything that goes around the page and is not part of the text body.
Typically the title, footer etc.
Key
Many objects used in a2ps@c, such as encodings, have both a key and a name.
The word
name
is used for a symbol, a label, which is only meant
to be nice to read by a human.  For instance
`ISO Latin 1'
is a name.
a2ps
A
key
is the identifier of a unique object.  This is information
that a2psa2ps@c, use the key, not its name.  For instance
`latin1'
is the
unique identifier of the
`ISO Latin 1'
encoding.
Logical page
Cf. Virtual page.
lhs
left hand side
See
P-rule
.
Medium
Official name (by Adobe) given to the output physical support.  In other
words, it means the description of a sheet, e.g., A4, Letter etc.
Name
See
Key
.
Page
A single side of a sheet.
Page Description Language
A language that describes some text (which may be enriched with
pointers, pictures etc.) and its layout.
HTML
, PostScript,
LaTeX,
roff
and others are such languages.  A file written in
those languages is not made to be read as is by a human, but to be
transformed (or compiled) into a readable form.
PCL
FIXME:
PFA file
PostScript Font in ASCII format.  This file can be directly down loaded
to provide support for another font.
PFB file
PostScript Font in Binary format.  In PFA files there are long sequences
of hexadecimal digits.  Here these digits are represented by their
value, hence compressing 2 characters in a PFA into 1 in the PFB.  This
is the only advantage since a PFB file cannot be directly sent to
printer: it must first be decompressed (hence turned into a PFA file)
before being used.
PostScript
PostScript
is a page description language designed for
Raster output devices
.  It is even more powerful than that:
unlike to
HTML
, or
roff
, but as TeX and LaTeX, it is
truly a programming language which main purpose is to draw (on sheets).
Most programs are a list of instructions that describes lines, shades of
gray, or text to draw on a page.  This is the language that most
printers understand.
Note that the fact that PostScript is a programming language is
responsible of both its success and its failure.  It is a big win for
the PostScript programmer who can easily implement a lot of nice visual
effects.  It is a big loss because the page descriptions can have an
arbitrary complexity, hence rendering can be really slow (remember the
first Laser you had, or even
Ghostscript
.
PDF
has been
invented by Adobe to remedy these problems).
PostScript is a trademark of Adobe Systems Incorporated.
PPD file
PostScript Printer Description file
These files report everything one needs to know about a printer: the known
fonts, the patches that should be down loaded, the available memory, the
trays, the way to ask it duplex printing, the supported media, etc.
PostScript has pretended to be a device independent page description
language, and the PPD files are here to prove that
device independence was a failure.
ProcSet
Set of (PostScript) procedures.
Prologue
PostScript being a language, a typical PostScript program (i.e. a
typical PostScript file) consists of two parts.  The first part is
composed of resources, such as fonts, procsets, etc. and the second part
of calls to these procedures.  The first part is called the
prologue
, and the second, the
script
.
P-rule
Pretty printing rule.  It is composed of a
left-hand side
,
(
lhs
for short), and a
right-hand side
, (
rhs
).  The
lhs describes when the rule is triggered (i.e., the pattern of text to
match), and the rhs specifies the pretty printed output.
See section
#SEC85
P-Rules
, for more semantical details, and see
#SEC93
Syntax for the P-Rules
, for implementation.
psutils
The
http://www.dcs.ed.ac.uk/home/ajcd/psutils/index.html
psutils
is a set of tools for PostScript post processing written
by
http://www.dcs.ed.ac.uk/home/ajcd/
Angus Duggan
.  They let
you resize the frame into which the page is drawn, reorder or select
pages, put several pages onto a single sheet, etc.  To allow the
psutils
to run correctly, the PostScript files must be DSC
conformant, and the bad news is that many PostScript drivers produce
files which are not.  For some common cases (e.g., Micro$oft tools),
Angus Duggan included in the package some tools (named
fix...ps
)
to fix typical problems.
fixps
is a collection of recipes on
when to run what
fix
tool.
Raster Image Processor
RIP
The hardware and/or software that translates data from a high-level
language (e.g., PostScript) into dots or pixels in a printer or
image setter.
Raster Output Device
Behind these words is hidden the general class of devices which have
Pixels that can be addressed individually: Laser, Ink or Dot printers,
but also regular screens etc.  It is typically opposed to the class of
devices which
plot
, i.e., have a pen that they move on the paper.
rhs
right hand side
See
P-rule
.
RIP
See
Raster Image Processor
.
Script
See
Prologue
.
Sheet
The physical support of the printing: it may support one or two pages,
depending on your printing options.
Style sheet
Set of rules used by a2psfile.  In a2ps@c, each programming language which is supported
is defined via one style-sheet.
Tumble
See
Duplex
.
Virtual page
Area on a physical page in which a2psThere may be several virtual pages on a physical page. (``virtual page''
is the name recommended by Adobe).
[
#SEC148
<
]
[
#SEC150
>
]
[
#SEC148
<<
]
[
#SEC1
Up
]
[
#SEC153
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
B. Genesis
Here are some words on a2ps
#SEC150
B.1 History
Where does it come from
#SEC151
B.2 Thanks
People who really helped
#SEC152
B.3 Translators
People who brought support of your tongue
[
#SEC149
<
]
[
#SEC151
>
]
[
#SEC149
<<
]
[
#SEC149
Up
]
[
#SEC153
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
B.1 History
The initial version was a shell program written by
mailto:evan@csli
Evan Kirshenbaum
.  It was very slow and contained many bugs.
A new version was written in
C
by
mailto:Miguel.Santana@st.com
Miguel Santana
to improve execution speed and portability.  Many new
features and improvements have been added since this first version.
Many contributions (changes, fixes, ideas) were done by a2psorder to improve it.
From the latest version from Miguel Santana (4.3), Emmanuel Briot
implemented bold faces for keywords in
Ada
,
C
and
C++
.
From that version,
mailto:akim@freefriends.org
Akim Demaille
generalized the pretty-printing capabilities, implemented more languages
support, and other features.
[
#SEC150
<
]
[
#SEC152
>
]
[
#SEC149
<<
]
[
#SEC149
Up
]
[
#SEC153
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
B.2 Thanks
Patrick Andries, from
http://www.alis.com/
Alis Technologies inc.
and Roman Czyborra (see his
http://czyborra.com/
home page
),
provided us with important information on encodings.  We strongly
recommend that you go and read these pages: there is a lot to learn.
Juliusz Chroboczek worked a lot on the integration of the products of
Ogonkify (such as Latin 2 etc. fonts) in a2ps@c.  Without his help, and
the time is devoted to both a2pswest-European people would still be unable to print easily texts written
in their mother tongue.
Denis Girou brought a constant and valuable support through out the
genesis of pretty-printing a2ps@c.  His comments on both the program
and the documentation are the origin of many pleasant features (such as
`--prologue'
).
Alexander Mai provided us with invaluable help in the development.  He
spotted several times subtle bugs in a2pskeeps a vigilant eye on portability issues, he checks and improves the
style sheets, and he maintains a port of a2ps
Graham Jenkins, with an extraordinary regularity, tortures a2psweird systems that nobody ever heard of
`:)'
.  Graham is usually
the ultimate test: if he says I can release a2ps@c, I rest reassured
that, yes, this time it
will
compile!  If a2pson your system, you should thank Graham too!
Of course this list is not up to date, and never will.  We would like to
thank everybody that helped us, talked to us, and even criticized us
with the intention to help us to improve a2ps@c.  Of course it doesn't
sound right, yes it sounds a little childish, but we can tell you: we
would
never
have the strength and the faith of building and
maintaining a2ps
While a2psis an adventure we live with other humans, and, boy, that's a darn good
pleasure!
[
#SEC151
<
]
[
#SEC153
>
]
[
#SEC149
<<
]
[
#SEC149
Up
]
[
#SEC153
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
B.3 Translators
Some people worked on the translation of a2ps@c:
-
Daniele Ghiotti (Italian)
-
Tomek Burdziak (Polish)
-
mailto:mvaro@dlsi.ua.es
Miguel A. Varo
(Maintains Spanish and Catalan)
-
mailto:mw@miwie.in-berlin.de
Michael Wiedmann
(Maintains German)
-
mailto:ck@held.mind.de
Christian Kirsch
(German)
-
mailto:bamse@gmx.de
Erwin Dieterich
(German)
-
mailto:jec@dcs.ed.ac.uk
Juliusz Chroboczek
(Polish) He is also the author of
Ogonkify
(see
ogonkify.html#Top
(ogonkify)top
section `Overview' in
Ogonkify manual
).
-
mailto:Marcel.van.der.Laan@home.ict.nl
Marcel van der Laan
(Dutch)
-
mailto:lorenzo@argon.roma2.infn.it
Lorenzo M. Catucci
(Maintains Italian)
-
mailto:junker@jazz.snu.ac.kr
Choi Jun Ho
(Korean)
-
mailto:uyar@cs.itu.edu.tr
Turgut Uyar
(Turkish)
-
mailto:pavlovsk@ff.cuni.cz
Jiri Pavlovsky
(Maintains Czech)
-
mailto:pnidv96@student.hv.se
Peter Nilsson
(Maintains Swedish)
-
mailto:pmmm@camoes.rnl.ist.utl.pt
Pedro Miguel Marques Morais
(Maintains Portugese)
-
mailto:voldemarus@geocities.com
Vladimir Vodolazkiy
(Russian) has a
http://come.to/vodolaz
home page
.
-
mailto:pjsm@students.fct.unl.pt
Paulo Matos
(Portugese)
-
mailto:jonr@sdata.no
Jon Ross
(Maintains Norwegian)
-
mailto:IgorF@ix.netcom.com
Igor Furlan
(Maintains Slovenian)
-
mailto:qrczak@knm.org.pl
Marcin 'Qrczak' Kowalczyk
(Polish)
-
mailto:smoke@casema.net
Tijs van Bakel
(Maintains Dutch)
-
mailto:dima@Chg.RU
Dmitry S. Sivachenko
(Maintains Russian)
[
#SEC152
<
]
[
#SEC154
>
]
[
#SEC149
<<
]
[
#SEC1
Up
]
[
#SEC154
>>
]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
C. Copying
The subroutines and source code in the a2ps"free"; this means that everyone is free to use them and free to
redistribute them on a free basis.  The a2ps@c-related programs are
not in the public domain; they are copyrighted and there are
restrictions on their distribution, but these restrictions are designed
to permit everything that a good cooperating citizen would want to do.
What is not allowed is to try to prevent others from further sharing any
version of these programs that they might get from you.
Specifically, we want to make sure that you have the right to give
away copies of the programs that relate to a2ps@c, that you receive
source code or else can get it if you want it, that you can change these
programs or use pieces of them in new free programs, and that you know
you can do these things.
To make sure that everyone has such rights, we have to forbid you to
deprive anyone else of these rights.  For example, if you distribute
copies of the a2ps@c-related code, you must give the recipients all
the rights that you have.  You must make sure that they, too, receive or
can get the source code.  And you must tell them their rights.
Also, for our own protection, we must make certain that everyone
finds out that there is no warranty for the programs that relate to
a2ps@c.  If these programs are modified by someone else and passed
on, we want their recipients to know that what they have is not what we
distributed, so that any problems introduced by others will not reflect
on our reputation.
The precise conditions of the licenses for the programs currently
being distributed that relate to a2psPublic Licenses that accompany them.
[
#SEC153
<
]
[ > ]
[
#SEC153
<<
]
[
#SEC1
Up
]
[ >> ]
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
Concept Index
Jump to:
#SEC154_0
%
#SEC154_1
.
#SEC154_2
:
#SEC154_3
A
#SEC154_4
B
#SEC154_5
C
#SEC154_6
D
#SEC154_7
E
#SEC154_8
F
#SEC154_9
G
#SEC154_10
H
#SEC154_11
I
#SEC154_12
K
#SEC154_13
L
#SEC154_14
M
#SEC154_15
N
#SEC154_16
O
#SEC154_17
P
#SEC154_18
R
#SEC154_19
S
#SEC154_20
T
#SEC154_21
U
#SEC154_22
V
#SEC154_23
W
Index Entry
Section
%
#SEC41
`%!'
#SEC41
4.7 Your PostScript magic number
.
#SEC34
`.a2ps'
#SEC34
4. Configuration Files
#IDX154
.afm
#SEC56
5.3.2 Fonts Description Files
#SEC63
.edf
#SEC63
6.2.2 Encoding Description Files
#SEC53
.map
#SEC53
5.2 Map Files
#IDX156
.pfa
#SEC56
5.3.2 Fonts Description Files
#IDX157
.pfb
#SEC56
5.3.2 Fonts Description Files
:
#SEC40
`:'
#SEC40
4.6 Your Shortcuts
A
#SEC34
`a2ps-site.cfg'
#SEC34
4. Configuration Files
#SEC34
`a2ps.cfg'
#SEC34
4. Configuration Files
#IDX123
`A2PS_CONFIG'
#SEC34
4. Configuration Files
#IDX15
A2PS_VERBOSITY
#SEC22
3.1.2 Global Options
#SEC34
`a2psrc'
#SEC34
4. Configuration Files
#IDX365
Adobe
#SEC148
A. Glossary
#IDX155
AFM
#SEC56
5.3.2 Fonts Description Files
#IDX366
AFM
#SEC148
A. Glossary
#SEC83
Alphabets
#SEC83
7.5.3 Alphabets
#IDX394
Angus Duggan
#SEC148
A. Glossary
#IDX128
`AppendLibraryPath:'
#SEC36
4.2 Your Library Path
B
#SEC141
banner
#SEC141
10.2.5 How Can I Pass Options to
`lpr'
#SEC3
Bug
#SEC3
1.2 Reporting Bugs
C
#IDX279
C-char
#SEC95
7.6.7 Declaring the sequences
#IDX278
C-string
#SEC95
7.6.7 Declaring the sequences
#IDX367
Charset
#SEC148
A. Glossary
#IDX368
Code Set
#SEC148
A. Glossary
#SEC20
Command line options
#SEC20
3.1 Command line options
#SEC34
Configuration Files
#SEC34
4. Configuration Files
#SEC153
Copying
#SEC153
C. Copying
D
#IDX140
`DefaultPrinter:'
#SEC39
4.5 Your Printers
#IDX369
Delegate
#SEC148
A. Glossary
#SEC47
`Delegation:'
#SEC47
4.10.1 Defining a Delegation
#SEC46
Delegations
#SEC46
4.10 Your Delegations
#SEC10
display
#SEC10
2.2.2 Special Printers
#IDX371
Document Structuring Conventions
#SEC148
A. Glossary
#SEC104
DSC
#SEC104
8.1 Foreword: Good and Bad PostScript
#IDX370
DSC
#SEC148
A. Glossary
#IDX110
Duplex
#SEC29
3.1.9 PostScript Options
#IDX372
Duplex
#SEC148
A. Glossary
#IDX374
DuplexNoTumble
#SEC148
A. Glossary
#IDX373
DuplexTumble
#SEC148
A. Glossary
E
#SEC63
EDF
#SEC63
6.2.2 Encoding Description Files
#IDX1
elm
#SEC17
2.5.1 Interfacing With a Mailer
#IDX82
Encoding
#SEC26
3.1.6 Input Options
#IDX375
Encoding
#SEC148
A. Glossary
#SEC43
Escape
#SEC43
4.9 Your Variables
#SEC30
Escapes
#SEC30
3.2 Escapes
F
#SEC79
Face
#SEC79
7.4 Faces
#IDX378
Face
#SEC148
A. Glossary
#SEC10
file
#SEC10
2.2.2 Special Printers
#SEC1
First Page
#SEC1
1. Introduction
G
#IDX376
Ghostscript
#SEC148
A. Glossary
#IDX377
gs
#SEC148
A. Glossary
H
#SEC25
Headers
#SEC25
3.1.5 Headings Options
#IDX379
Headings
#SEC148
A. Glossary
I
#SEC35
`Include:'
#SEC35
4.1 Including Configuration Files
K
#SEC81
key
#SEC81
7.5.1 Name and key
#IDX380
Key
#SEC148
A. Glossary
#SEC85
Keyword
#SEC85
7.5.5 P-Rules
L
#IDX275
lhs
#SEC85
7.5.5 P-Rules
#IDX23
libpaper
#SEC23
3.1.3 Sheet Options
#SEC51
Library files
#SEC51
5. Library Files
#IDX126
`LibraryPath:'
#SEC36
4.2 Your Library Path
#IDX381
Logical page
#SEC148
A. Glossary
M
#SEC57
make_fonts_map.sh
#SEC57
5.3.3 Adding More Font Support
#SEC53
Map files
#SEC53
5.2 Map Files
#SEC86
Markers
#SEC86
7.5.6 Sequences
#IDX382
Medium
#SEC148
A. Glossary
#SEC38
`Medium:'
#SEC38
4.4 Your Media
N
#IDX141
Non PostScript printers
#SEC39
4.5 Your Printers
O
#SEC85
Operator
#SEC85
7.5.5 P-Rules
#SEC104
Optimize for Portability
#SEC104
8.1 Foreword: Good and Bad PostScript
#SEC104
Optimize for Speed
#SEC104
8.1 Foreword: Good and Bad PostScript
#SEC87
Optional entries
#SEC87
7.5.7 Optional entries
#SEC20
Options
#SEC20
3.1 Command line options
#SEC37
`Options:'
#SEC37
4.3 Your Default Options
#SEC41
`OutputFirstLine:'
#SEC41
4.7 Your PostScript magic number
#IDX145
`OutputFirstLine:'
#SEC41
4.7 Your PostScript magic number
P
#SEC85
P-Rule
#SEC85
7.5.5 P-Rules
#IDX392
P-rule
#SEC148
A. Glossary
#IDX383
Page
#SEC148
A. Glossary
#IDX384
Page Description Language
#SEC148
A. Glossary
#IDX114
Page device
#SEC29
3.1.9 PostScript Options
#IDX120
Page prefeed
#SEC29
3.1.9 PostScript Options
#SEC26
Page Range
#SEC26
3.1.6 Input Options
#IDX147
`PageLabelFormat:'
#SEC42
4.8 Your Page Labels
#IDX24
paperconf
#SEC23
3.1.3 Sheet Options
#IDX385
PCL
#SEC148
A. Glossary
#IDX386
PFA file
#SEC148
A. Glossary
#IDX387
PFB file
#SEC148
A. Glossary
#IDX2
pine
#SEC17
2.5.1 Interfacing With a Mailer
#IDX388
PostScript
#SEC148
A. Glossary
#SEC104
PostScript Quality
#SEC104
8.1 Foreword: Good and Bad PostScript
#IDX389
PPD file
#SEC148
A. Glossary
#SEC45
Predefined Variables
#SEC45
4.9.2 Predefined Variables
#IDX130
`PrependLibraryPath:'
#SEC36
4.2 Your Library Path
#SEC70
PreScript
#SEC70
7.3.2 PreScript
#SEC65
Pretty printing
#SEC65
7. Pretty Printing
#IDX136
`Printer:'
#SEC39
4.5 Your Printers
#IDX390
ProcSet
#SEC148
A. Glossary
#IDX87
Prologue
#SEC26
3.1.6 Input Options
#IDX391
Prologue
#SEC148
A. Glossary
#IDX393
psutils
#SEC148
A. Glossary
R
#IDX395
Raster Output Device
#SEC148
A. Glossary
#IDX277
Regular expression
#SEC93
7.6.5 Syntax for the P-Rules
#IDX276
rhs
#SEC85
7.5.5 P-Rules
#SEC85
Rule
#SEC85
7.5.5 P-Rules
S
#IDX396
Script
#SEC148
A. Glossary
#SEC83
Separator
#SEC83
7.5.3 Alphabets
#SEC86
Sequences
#SEC86
7.5.6 Sequences
#IDX113
setpagedevice
#SEC29
3.1.9 PostScript Options
#IDX397
Sheet
#SEC148
A. Glossary
#SEC58
`sheets.map'
#SEC58
5.4 Style Sheet Files
#SEC81
`sheets.map'
#SEC81
7.5.1 Name and key
#IDX117
statusdict
#SEC29
3.1.9 PostScript Options
#SEC80
Style sheet
#SEC80
7.5 Style Sheets Semantics
#IDX398
Style sheet
#SEC148
A. Glossary
#SEC65
Symbol conversion
#SEC65
7. Pretty Printing
T
#IDX153
`TemporaryDirectory:'
#SEC50
4.11 Your Internal Details
#IDX399
Tumble
#SEC148
A. Glossary
U
#IDX68
Under lay
#SEC25
3.1.5 Headings Options
#IDX138
`UnknownPrinter:'
#SEC39
4.5 Your Printers
#IDX143
`UserOption:'
#SEC40
4.6 Your Shortcuts
V
#SEC43
Variable
#SEC43
4.9 Your Variables
#SEC44
`Variable:'
#SEC44
4.9.1 Defining Variables
#SEC45
Variables, predefined
#SEC45
4.9.2 Predefined Variables
#IDX400
Virtual page
#SEC148
A. Glossary
#SEC10
void
#SEC10
2.2.2 Special Printers
W
#IDX69
Water mark
#SEC25
3.1.5 Headings Options
Jump to:
#SEC154_0
%
#SEC154_1
.
#SEC154_2
:
#SEC154_3
A
#SEC154_4
B
#SEC154_5
C
#SEC154_6
D
#SEC154_7
E
#SEC154_8
F
#SEC154_9
G
#SEC154_10
H
#SEC154_11
I
#SEC154_12
K
#SEC154_13
L
#SEC154_14
M
#SEC154_15
N
#SEC154_16
O
#SEC154_17
P
#SEC154_18
R
#SEC154_19
S
#SEC154_20
T
#SEC154_21
U
#SEC154_22
V
#SEC154_23
W
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
Footnotes
#DOCF1
(1)
A
classical Unix trick to make the difference between the option
`-2'
, and the file
`-2'
is to type
`./-2'
.
#DOCF2
(2)
Current
a2ps
only handles PostScript output, i.e.
out
=
`ps'
#DOCF3
(3)
Because hiding its use into
a2ps
just makes
it even more difficult to the users to know why it failed.  Let them use
it by hand.
#DOCF4
(4)
Many people seem to ignore
that you can insert
several
sheets in the manual feed tray.
Try at least once, it will save you from hours spent feeding page per
page by hand!
#DOCF5
(5)
Year 2000.
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
Table of Contents
#SEC1
1. Introduction
#SEC2
1.1 Description
#SEC3
1.2 Reporting Bugs
#SEC4
1.3 a2ps
#SEC5
1.4 Helping the Development
#SEC6
2. User's Guide
#SEC7
2.1 Purpose
#SEC8
2.2 How to print
#SEC9
2.2.1 Basics for Printing
#SEC10
2.2.2 Special Printers
#SEC11
2.2.3 Using Delegations
#SEC12
2.2.4 Printing Duplex
#SEC13
2.2.5 Checking the Defaults
#SEC14
2.3 Important parameters
#SEC15
2.4 Localizing
#SEC16
2.5 Interfacing with Other Programs
#SEC17
2.5.1 Interfacing With a Mailer
#SEC18
2.5.2 Netscape
#SEC19
3. Invoking a2ps
#SEC20
3.1 Command line options
#SEC21
3.1.1 Tasks Options
#SEC22
3.1.2 Global Options
#SEC23
3.1.3 Sheet Options
#SEC24
3.1.4 Page Options
#SEC25
3.1.5 Headings Options
#SEC26
3.1.6 Input Options
#SEC27
3.1.7 Pretty Printing Options
#SEC28
3.1.8 Output Options
#SEC29
3.1.9 PostScript Options
#SEC30
3.2 Escapes
#SEC31
3.2.1 Use of Escapes
#SEC32
3.2.2 General Structure of the Escapes
#SEC33
3.2.3 Available Escapes
#SEC34
4. Configuration Files
#SEC35
4.1 Including Configuration Files
#SEC36
4.2 Your Library Path
#SEC37
4.3 Your Default Options
#SEC38
4.4 Your Media
#SEC39
4.5 Your Printers
#SEC40
4.6 Your Shortcuts
#SEC41
4.7 Your PostScript magic number
#SEC42
4.8 Your Page Labels
#SEC43
4.9 Your Variables
#SEC44
4.9.1 Defining Variables
#SEC45
4.9.2 Predefined Variables
#SEC46
4.10 Your Delegations
#SEC47
4.10.1 Defining a Delegation
#SEC48
4.10.2 Guide Line for Delegations
#SEC49
4.10.3 Predefined Delegations
#SEC50
4.11 Your Internal Details
#SEC51
5. Library Files
#SEC52
5.1 Documentation Format
#SEC53
5.2 Map Files
#SEC54
5.3 Font Files
#SEC55
5.3.1 Fonts Map File
#SEC56
5.3.2 Fonts Description Files
#SEC57
5.3.3 Adding More Font Support
#SEC58
5.4 Style Sheet Files
#SEC59
6. Encodings
#SEC60
6.1 What is an Encoding
#SEC61
6.2 Encoding Files
#SEC62
6.2.1 Encoding Map File
#SEC63
6.2.2 Encoding Description Files
#SEC64
6.2.3 Some Encodings
#SEC65
7. Pretty Printing
#SEC66
7.1 Syntactic limits
#SEC67
7.2 Known Style Sheets
#SEC68
7.3 Type Setting Style Sheets
#SEC69
7.3.1 Symbol
#SEC70
7.3.2 PreScript
#SEC71
7.3.2.1 Syntax
#SEC72
7.3.2.2 PreScript Commands
#SEC73
7.3.2.3 Examples
#SEC74
7.3.3 PreTeX
#SEC75
7.3.3.1 Special characters
#SEC76
7.3.3.2 PreTeX
#SEC77
7.3.3.3 Differences with LaTeX
#SEC78
7.3.4 TeXScript
#SEC79
7.4 Faces
#SEC80
7.5 Style Sheets Semantics
#SEC81
7.5.1 Name and key
#SEC82
7.5.2 Comments
#SEC83
7.5.3 Alphabets
#SEC84
7.5.4 Case sensitivity
#SEC85
7.5.5 P-Rules
#SEC86
7.5.6 Sequences
#SEC87
7.5.7 Optional entries
#SEC88
7.6 Style Sheets Implementation
#SEC89
7.6.1 A Bit of Syntax
#SEC90
7.6.2 Style Sheet Header
#SEC91
7.6.3 Syntax of the Words
#SEC92
7.6.4 Inheriting from Other Style Sheets
#SEC93
7.6.5 Syntax for the P-Rules
#SEC94
7.6.6 Declaring the keywords and the operators
#SEC95
7.6.7 Declaring the sequences
#SEC96
7.6.8 Checking a Style Sheet
#SEC97
7.7 A Tutorial on Style Sheets
#SEC98
7.7.1 Example and syntax
#SEC99
7.7.2 Implementation
#SEC100
7.7.3 The Entry in
`sheets.map'
#SEC101
7.7.4 More Sophisticated Rules
#SEC102
7.7.5 Guide Line for Distributed Style Sheets
#SEC103
8. PostScript
#SEC104
8.1 Foreword: Good and Bad PostScript
#SEC105
8.2 Page Device Options
#SEC106
8.3 Statusdict Options
#SEC107
8.4 Colors in PostScript
#SEC108
8.5 a2ps
#SEC109
8.6 Designing PostScript Prologues
#SEC110
8.6.1 Definition of the faces
#SEC111
8.6.2 Prologue File Format
#SEC112
8.6.3 A step by step example
#SEC113
9. Contributions
#SEC114
9.1
card
#SEC115
9.1.1 Invoking
card
#SEC116
9.1.2 Caution when Using
card
#SEC117
9.2
fixps
#SEC118
9.2.1 Invoking
fixps
#SEC119
9.3
fixnt
#SEC120
9.3.1 Invoking
fixnt
#SEC121
9.4
pdiff
#SEC122
9.4.1 Invoking
pdiff
#SEC123
9.5
psmandup
#SEC124
9.5.1 Invoking
psmandup
#SEC125
9.6
psset
#SEC126
9.6.1 Invoking
psset
#SEC127
10. Frequently asked questions
#SEC128
10.1 Why Does...?
#SEC129
10.1.1 Why Does it Print Nothing?
#SEC130
10.1.2 Why Does it Print in Simplex?
#SEC131
10.1.3 Why Does it Print in Duplex?
#SEC132
10.1.4 Why Does it Not Fit on the Paper?
#SEC133
10.1.5 Why Does it Print Junk?
#SEC134
10.1.6 Why Does it Say my File is Binary?
#SEC135
10.1.7 Why Does it Refuse to Change the Font Size
#SEC136
10.2 How Can I ...?
#SEC137
10.2.1 How Can I Leave Room for Binding?
#SEC138
10.2.2 How Can I Print
stdin
?
#SEC139
10.2.3 How Can I Change the Fonts?
#SEC140
10.2.4 How Can I Simulate the Old Option
`-b'
?
#SEC141
10.2.5 How Can I Pass Options to
`lpr'
#SEC142
10.2.6 How Can I Print on Non PostScript Printers?
#SEC143
10.2.7 How Can I Print Man Pages with Underlines
#SEC144
10.3 Please tell me...
#SEC145
10.3.1 Is a2ps
#SEC146
10.3.2 Why Have the Options Changed?
#SEC147
10.3.3 Why not having used
yacc
and such
#SEC148
A. Glossary
#SEC149
B. Genesis
#SEC150
B.1 History
#SEC151
B.2 Thanks
#SEC152
B.3 Translators
#SEC153
C. Copying
#SEC154
Concept Index
[
#SEC1
Top
]
[
#SEC_Contents
Contents
]
[
#SEC154
Index
]
[
#SEC_About
?
]
About This Document
This document was generated by
root
on
September, 13 2005
using
http://texi2html.cvshome.org/
texi2html 1.76
.
The buttons in the navigation panels have the following meaning:
Button
Name
Go to
From 1.2.3 go to
[ < ]
Back
previous section in reading order
1.2.2
[ > ]
Forward
next section in reading order
1.2.4
[ << ]
FastBack
beginning of this chapter or previous chapter
1
[ Up ]
Up
up section
1.2
[ >> ]
FastForward
next chapter
2
[Top]
Top
cover (top) of document
[Contents]
Contents
table of contents
[Index]
Index
index
[ ? ]
About
about (help)
where the
Example
assumes that the current position is at
Subsubsection One-Two-Three
of a document of the following structure:
1. Section One
1.1 Subsection One-One
...
1.2 Subsection One-Two
1.2.1 Subsubsection One-Two-One
1.2.2 Subsubsection One-Two-Two
1.2.3 Subsubsection One-Two-Three
<== Current Position
1.2.4 Subsubsection One-Two-Four
1.3 Subsection One-Three
...
1.4 Subsection One-Four
This document was generated by
root
on
September, 13 2005
using
http://texi2html.cvshome.org/
texi2html 1.76
.
