]> git.ipfire.org Git - thirdparty/cups.git/blame - pdftops/README
Load cups into easysw/current.
[thirdparty/cups.git] / pdftops / README
CommitLineData
ef416fc2 1Xpdf
2====
3
4version 2.02
52003-mar-24
6
7The Xpdf software and documentation are
8copyright 1996-2003 Glyph & Cog, LLC.
9
10Email: derekn@foolabs.com
11WWW: http://www.foolabs.com/xpdf/
12
13The PDF data structures, operators, and specification are
14copyright 1985-2001 Adobe Systems Inc.
15
16
17What is Xpdf?
18-------------
19
20Xpdf is an open source viewer for Portable Document Format (PDF)
21files. (These are also sometimes also called 'Acrobat' files, from
22the name of Adobe's PDF software.) The Xpdf project also includes a
23PDF text extractor, PDF-to-PostScript converter, and various other
24utilities.
25
26Xpdf runs under the X Window System on UNIX, VMS, and OS/2. The non-X
27components (pdftops, pdftotext, etc.) also run on Win32 systems and
28should run on pretty much any system with a decent C++ compiler.
29
30Xpdf is designed to be small and efficient. It can use Type 1,
31TrueType, or standard X fonts.
32
33
34Distribution
35------------
36
37Xpdf is licensed under the GNU General Public License (GPL), version
382. In my opinion, the GPL is a convoluted, confusing, ambiguous mess.
39But it's also pervasive, and I'm sick of arguing. And even if it is
40confusing, the basic idea is good.
41
42In order to cut down on the confusion a little bit, here are some
43informal clarifications:
44
45- I don't mind if you redistribute Xpdf in source and/or binary form,
46 as long as you include all of the documentation: README, man pages
47 (or help files), and COPYING. (Note that the README file contains a
48 pointer to a web page with the source code.)
49
50- Selling a CD-ROM that contains Xpdf is fine with me, as long as it
51 includes the documentation. I wouldn't mind receiving a sample
52 copy, but it's not necessary.
53
54- If you make useful changes to Xpdf, please make the source code
55 available -- post it on a web site, email it to me, whatever.
56
57If you're interested in commercial licensing, please see the Glyph &
58Cog web site:
59
60 http://www.glyphandcog.com/
61
62
63Compatibility
64-------------
65
66Xpdf is developed and tested on a Linux 2.2 x86 system.
67
68In addition, it has been compiled by others on Solaris, AIX, HP-UX,
69SCO UnixWare, Digital Unix, Irix, and numerous other Unix
70implementations, as well as VMS and OS/2. It should work on pretty
71much any system which runs X11 and has Unix-like libraries. You'll
72need ANSI C++ and C compilers to compile it.
73
74The non-X components of Xpdf (pdftops, pdftotext, pdfinfo, pdffonts,
75pdfimages) can also be compiled on Win32 systems. See the Xpdf web
76page for details.
77
78If you compile Xpdf for a system not listed on the web page, please
79let me know. If you're willing to make your binary available by ftp
80or on the web, I'll be happy to add a link from the Xpdf web page. I
81have decided not to host any binaries I didn't compile myself (for
82disk space and support reasons).
83
84If you can't get Xpdf to compile on your system, send me email and
85I'll try to help.
86
87Xpdf has been ported to the Acorn, Amiga, BeOS, and EPOC. See the
88Xpdf web page for links.
89
90
91Getting Xpdf
92------------
93
94The latest version is available from:
95
96 http://www.foolabs.com/xpdf/
97
98or:
99
100 ftp://ftp.foolabs.com/pub/xpdf/
101
102Source code and several precompiled executables are available.
103
104Announcements of new versions are posted to several newsgroups
105(comp.text.pdf, comp.os.linux.announce, and others) and emailed to a
106list of people. If you'd like to receive email notification of new
107versions, just let me know.
108
109
110Running Xpdf
111------------
112
113To run xpdf, simply type:
114
115 xpdf file.pdf
116
117To generate a PostScript file, hit the "print" button in xpdf, or run
118pdftops:
119
120 pdftops file.pdf
121
122To generate a plain text file, run pdftotext:
123
124 pdftotext file.pdf
125
126There are four additional utilities (which are fully described in
127their man pages):
128
129 pdfinfo -- dumps a PDF file's Info dictionary (plus some other
130 useful information)
131 pdffonts -- lists the fonts used in a PDF file along with various
132 information for each font
133 pdftopbm -- converts a PDF file to a series of PBM-format bitmaps
134 pdfimages -- extracts the images from a PDF file
135
136Command line options and many other details are described in the man
137pages (xpdf.1, etc.) and the VMS help files (xpdf.hlp, etc.).
138
139
140Upgrading from Xpdf 0.9x
141------------------------
142
143WARNING: Xpdf 1.x switched to a completely different config file setup
144than Xpdf 0.9x.
145
146Many of the configuration options that used to be X resources have
147been moved into the Xpdf config file. There are also lots of new and
148improved options. If you're upgrading from Xpdf 0.9x, please read
149through the sample config file (doc/sample-xpdfrc) and the xpdfrc(5)
150man page.
151
152The Asian language support has been pulled out into separate packages,
153loaded at run time. This is much cleaner than the 0.9x approach -- it
154makes the base distribution smaller, allows the language support
155packages to be upgraded separately, and lets users customize Xpdf for
156other text encodings without modifying the source. See the web site
157(http://www.foolabs.com/xpdf) for info on downloading the language
158support packages.
159
160All of the Xpdf tools, including the X viewer and the command line
161programs, read the same config file. They first attempt to read the
162user's personal config file:
163
164 $HOME/.xpdfrc
165
166If it is not found, the Xpdf tools read a system-wide config file,
167typically something like:
168
169 /usr/local/etc/xpdfrc
170
171(this location can be customized when building Xpdf).
172
173The Win32 command line tools look in the directory containing the
174executable, e.g.:
175
176 C:/Program Files/Xpdf/xpdfrc
177
178Xpdf comes with a "sample-xpdfrc" file in the doc directory. This is
179a good starting point for constructing your own config file.
180
181For full details, please see the xpdfrc(5) man page.
182
183
184Fonts
185-----
186
187By default, Xpdf will use X server fonts. It requires the following
188fonts:
189
190* Courier: medium-r, bold-r, medium-o, and bold-o
191* Helvetica: medium-r, bold-r, medium-o, and bold-o
192* Times: medium-r, bold-r, medium-i, and bold-i
193* Symbol: medium-r
194* Zapf Dingbats: medium-r
195
196Most X installations should already have all of these fonts (except
197maybe Zapf Dingbats).
198
199If Xpdf is built with support for t1lib (or FreeType 2), you can get
200much higher quality text by using Type 1 fonts instead of X server
201fonts. For example, you can use the Type 1 fonts that come with
202ghostscript. To do this, add the following lines to the xpdfrc file
203(e.g., /usr/local/etc/xpdfrc or $HOME/.xpdfrc):
204
205displayFontT1 Times-Roman /usr/local/share/ghostscript/fonts/n021003l.pfb
206displayFontT1 Times-Italic /usr/local/share/ghostscript/fonts/n021023l.pfb
207displayFontT1 Times-Bold /usr/local/share/ghostscript/fonts/n021004l.pfb
208displayFontT1 Times-BoldItalic /usr/local/share/ghostscript/fonts/n021024l.pfb
209displayFontT1 Helvetica /usr/local/share/ghostscript/fonts/n019003l.pfb
210displayFontT1 Helvetica-Oblique /usr/local/share/ghostscript/fonts/n019023l.pfb
211displayFontT1 Helvetica-Bold /usr/local/share/ghostscript/fonts/n019004l.pfb
212displayFontT1 Helvetica-BoldOblique /usr/local/share/ghostscript/fonts/n019024l.pfb
213displayFontT1 Courier /usr/local/share/ghostscript/fonts/n022003l.pfb
214displayFontT1 Courier-Oblique /usr/local/share/ghostscript/fonts/n022023l.pfb
215displayFontT1 Courier-Bold /usr/local/share/ghostscript/fonts/n022004l.pfb
216displayFontT1 Courier-BoldOblique /usr/local/share/ghostscript/fonts/n022024l.pfb
217displayFontT1 Symbol /usr/local/share/ghostscript/fonts/s050000l.pfb
218displayFontT1 ZapfDingbats /usr/local/share/ghostscript/fonts/d050000l.pfb
219
220You will need to replace '/usr/local/share/ghostscript/fonts' with the
221appropriate path on your system.
222
223
224Compiling Xpdf
225--------------
226
227See the separate file, INSTALL.
228
229
230Bugs
231----
232
233If you find a bug in Xpdf, i.e., if it prints an error message,
234crashes, or incorrectly displays a document, and you don't see that
235bug listed here, please send me email, with a pointer (URL, ftp site,
236etc.) to the PDF file.
237
238
239Acknowledgments
240---------------
241
242Thanks to:
243
244* Patrick Voigt for help with the remote server code.
245* Patrick Moreau, Martin P.J. Zinser, and David Mathog for the VMS
246 port.
247* David Boldt and Rick Rodgers for sample man pages.
248* Brendan Miller for the icon idea.
249* Olly Betts for help testing pdftotext.
250* Peter Ganten for the OS/2 port.
251* Michael Richmond for the Win32 port of pdftops and pdftotext and the
252 xpdf/cygwin/XFree86 build instructions.
253* Frank M. Siegert for improvements in the PostScript code.
254* Leo Smiers for the decryption patches.
255* Rainer Menzner for creating t1lib, and for helping me adapt it to
256 xpdf.
257* Pine Tree Systems A/S for funding the OPI and EPS support in
258 pdftops.
259* Easy Software Products for funding the "sh" operator support.
260* Tom Kacvinsky for help with FreeType and for being my interface to
261 the FreeType team.
262* Theppitak Karoonboonyanan for help with Thai support.
263* Leonard Rosenthol for help and contributions on a bunch of things.
264* Alexandros Diamantidis and Maria Adaloglou for help with Greek
265 support.
266* Lawrence Lai for help with the CJK Unicode maps.
267
268Various people have contributed modifications made for use by the
269pdftex project:
270
271* Han The Thanh
272