1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
|
<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!-- $Id: ps2eps.sgml,v 1.9 2010-05-07 19:56:27 bless Exp $ -->
<!-- $Source: /home/bless/src/ps2eps/cvs-repository/ps2eps/doc/ps2eps.sgml,v $ -->
<!-- Fill in your name for FIRSTNAME and SURNAME. -->
<!ENTITY dhfirstname "<firstname>Roland</firstname>">
<!ENTITY dhsurname "<surname>Bless</surname>">
<!-- Please adjust the date whenever revising the manpage. -->
<!ENTITY dhdate "<date>May 7, 2010</date>">
<!-- SECTION should be 1-8, maybe w/ subsection other parameters are
allowed: see man(7), man(1). -->
<!ENTITY dhsection "<manvolnum>1</manvolnum>">
<!ENTITY dhemail "<email>roland at bless.de</email>">
<!ENTITY dhusername "Roland Bless">
<!ENTITY dhucpackage "<refentrytitle>ps2eps</refentrytitle>">
<!ENTITY dhpackage "ps2eps">
<!ENTITY ps2eps "<command>ps2eps</command>">
<!ENTITY ps2epsver "1.68">
<!ENTITY gs "ghostscript">
<!ENTITY debian "<productname>Debian</productname>">
<!ENTITY gnu "<acronym>GNU</acronym>">
<!ENTITY gpl "&gnu; <acronym>GPL</acronym>">
]>
<refentry>
<refentryinfo>
<address>
&dhemail;
</address>
<author>
&dhfirstname;
&dhsurname;
</author>
<copyright>
<year>2009</year>
<holder>&dhusername;</holder>
</copyright>
&dhdate;
</refentryinfo>
<refmeta>
&dhucpackage;
&dhsection;
</refmeta>
<refnamediv>
<refname>&dhpackage;</refname>
<refpurpose>
convert PostScript to EPS (Encapsulated PostScript) files
</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis>
&ps2eps;
<arg><option>-f</option></arg>
<arg><option>-q</option></arg>
<arg><option>-N</option></arg>
<arg><option>-O</option></arg>
<arg><option>-n</option></arg>
<arg><option>-P</option></arg>
<arg><option>-c</option></arg>
<arg><option>-C</option></arg>
<arg><option>-m</option></arg>
<arg><option>-B</option></arg>
<arg><option>-E</option></arg>
<arg><option>-s <replaceable>pagedim</replaceable></option></arg>
<arg><option>-t <replaceable>offset</replaceable></option></arg>
<arg><option>-r <replaceable>resolution</replaceable></option></arg>
<arg><option>-R <replaceable>+|-|^</replaceable></option></arg>
<arg><option>-l</option></arg>
<arg><option>-g</option></arg>
<arg><option>-H</option></arg>
<arg><option>-d</option></arg>
<arg><option>-h|--help</option></arg>
<arg><option>-a</option></arg>
<arg><option>-W</option></arg>
<arg><option>-L</option></arg>
<arg><option>-V|--version</option></arg>
<arg><option>--</option></arg>
<arg><replaceable>psfile1</replaceable></arg>
<arg><replaceable>psfile2</replaceable></arg>
<arg><replaceable>...</replaceable></arg>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1>
<title>DESCRIPTION</title>
<para>This manual page documents &ps2eps; version &ps2epsver;.</para>
<para>&ps2eps; is a tool (written in Perl) to produce
Encapsulated PostScript Files (EPS/EPSF) from usual one-paged Postscript
documents. It calculates correct Bounding Boxes for those EPS files and
filters some special postscript command sequences that can produce
erroneous results on printers. EPS files are often needed for including
(scalable) graphics of high quality into TeX/LaTeX (or even Word) documents.
</para>
<para>Without any argument, ps2eps reads from standard input
and writes to standard output.
If filenames are given as arguments they are processed
one by one and output files are written to filenames
with extension <filename>.eps</filename>. If input filenames have the
extension <filename>.ps</filename> or <filename>.prn</filename>, this extension is replaced with <filename>.eps</filename>.
In all other cases <filename>.eps</filename> is appended to the input filename.
Please note that PostScript files for input should contain
only one single page (you can possibly use the <command>psselect</command> from the
psutils package to extract a single page from a document that
contains multiple pages).</para>
<para>
If BoundingBox in output seems to be wrong, please try options <option>--size</option> or
<option>--ignoreBB</option>. See also section TROUBLESHOOTING. <!-- <xref -->
<!-- linkend="TROUBLESHOOTING" endterm="TROUBLESHOOTING.title"/> -->
</para>
</refsect1>
<refsect1>
<title>OPTIONS</title>
<para>
&ps2eps; follows the usual &gnu; command line syntax,
with long options starting with two dashes (`-'). A summary of
options is included below.
</para>
<variablelist>
<varlistentry>
<term><option>-h</option>, <option>--help</option>
</term>
<listitem>
<para>Show summary of options.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-V</option>, <option>--version</option>
</term>
<listitem>
<para>Show version of program.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-f</option>, <option>--force</option>
</term>
<listitem>
<para>Force overwriting existing files. &ps2eps;
will not overwrite files by default to avoid deleting original EPS
files accidently.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-q</option>, <option>--quiet</option>
</term>
<listitem>
<para>quiet operation (no output while processing files, except errors).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-N</option>, <option>--noinsert</option>
</term>
<listitem>
<para>do not insert any postscript code. Normally a few postscript
instructions are added around the original postscript code by
&ps2eps; which can be turned off by this option.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-O</option>, <option>--preserveorientation</option>
</term>
<listitem>
<para>do not filter %%Orientation: header comment.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-n</option>, <option>--nofix</option>
</term>
<listitem>
<para>do not try to fix postscript code by filtering some instructions.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-P</option>, <option>--removepreview</option>
</term>
<listitem>
<para>remove preview image (smaller file, but no preview anymore).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-F</option>, <option>--fixps</option>
</term>
<listitem>
<para>fix postscript code unconditionally. Otherwise, filtering is
usually triggered by detection of certain drivers only.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-c</option>, <option>--comments</option>
</term>
<listitem>
<para>preserve document structure comments.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-C</option>, <option>--clip</option>
</term>
<listitem>
<para>insert postscript code for clipping. Unless
<option>--nohires</option> is specified, the HiResBoundingBox
(enlarged by 0.1 points) is used for clipping. </para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-m</option>, <option>--mono</option>
</term>
<listitem>
<para>use black/white bitmap as base for calculation (default: off).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-s</option>, <option>--size</option>=<varname>pagedim</varname>
</term>
<listitem>
<para>where <varname>pagedim</varname> is a pre-defined standard page size
(e.g., a4,a0,b0,letter,...) or explicitly specified in a
format <varname>pagedim</varname>:=<replaceable>X</replaceable>x<replaceable>Y</replaceable>[cm|in],
where <replaceable>X</replaceable> and <replaceable>Y</replaceable> are numbers (floating points are accepted) followed by
units centimeter (cm) or inch (in), (default: cm).
Use <option>--size=list</option> to list pre-defined pagesizes.
See also environment variable <varname>PS2EPS_SIZE</varname>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-t</option>, <option>--translate=x,y</option>
</term>
<listitem>
<para>specify an x,y offset (may be negative) in postscript points
(1/72 dpi) for drawing. This option may be required
if your drawing has negative coordinates which usually lets &gs;
cut the negative part of your picture, because it starts to render
at positive coordinates. The resulting output will
also be shifted.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-r</option>, <option>--resolution=dpi</option>
</term>
<listitem>
<para>specify a resolution in dpi (dots per inch) for drawing under
ghostscript. Default
resolution is 144 dpi which is the double of the typical 72 dpi.
This option may help if there is a hardware dependent resolution
encoded in the postscript, e.g., 600dpi. Example:
<userinput>ps2eps -l -r 600 test.ps</userinput>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-R</option>, <option>--rotate=direction</option>
</term>
<listitem>
<para>
This option rotates the resulting EPS output.
The parameter <varname>direction</varname> determines the direction of
rotation: + means +90 degrees (clockwise),- means -90 degrees
(counter-clockwise), and ^ means 180 degrees (up-side down).
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-l</option>, <option>--loose</option>
</term>
<listitem>
<para>expand the original tight bounding box by one point in each
direction.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-B</option>, <option>--ignoreBB</option>
</term>
<listitem>
<para>do not use existing bounding box as page size for
rendering.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-E</option>, <option>--ignoreEOF</option>
</term>
<listitem>
<para>do not use %%EOF as hint for end of file. Otherwise, &ps2eps; assumes
that postscript code ends after the last %%EOF comment, because
some drivers add trailing binary <quote>garbage</quote> code which gets deleted
by &ps2eps; by default.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-g</option>, <option>--gsbbox</option>
</term>
<listitem>
<para>use internal bbox device of &gs; instead of the external C
program <command>bbox</command>. The internal bbox device of &gs;
generates different values (sometimes even incorrect),
so using the provided <command>bbox</command> should be more robust.
See also environment variable <varname>PS2EPS_GSBBOX</varname>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-H</option>, <option>--nohires</option>
</term>
<listitem>
<para>
do not generate a %%HiResBoundingBox comment for output.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-a</option>, <option>--accuracy</option>
</term>
<listitem>
<para>
increase the accuracy by turning subsample antialiasing on (may be slower)
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-L</option>, <option>--license</option>
</term>
<listitem>
<para>show licensing information.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-d</option>, <option>--debuggs</option>
</term>
<listitem>
<para>show &gs; call. This may be helpful for solving problems that
occur during a &gs; call.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-W</option>, <option>--warnings</option>
</term>
<listitem>
<para>show warnings about sanity of generated EPS file. Certain
postscript commands should not be contained in an EPS file.
With this option set &ps2eps; will issue a warning if it
detects at least one of them.
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 id="TROUBLESHOOTING">
<title id="TROUBLESHOOTING.title">TROUBLESHOOTING</title>
<para>Based on the given postscript source code (in most cases generated by
some postscript printer driver) there are many potential obstacles or
problems that may occur when trying to create proper EPS files. Please
read this section carefully to be aware of common pitfalls.</para>
<refsect2>
<title>Incomplete/Clipped Images</title>
<para>or how to determine the right size for &gs;.</para>
<para>If you have documents that are larger than your
&gs; default (usually A4 or US letter), you have to
specify the page dimensions explicitly using the
<option>-s</option> option. Otherwise your EPS
might be cut off during rasterizing by &gs; resulting
in a wrongly calculated bounding box. You can pass
all pre-defined page sizes to <option>-s</option> that &gs; understands. These are
currently: 11x17, ledger, legal, letter, lettersmall, archA, archB, archC, archD, archE
a0, a1, a2, a3, a4, a5, a6, a7, a8, a9, a10, isob0, isob1, isob2, isob3, isob4, isob5, isob6,
b0, b1, b2, b3, b4, b5, c0, c1, c2, c3, c4, c5, c6, jisb0, jisb1,
jisb2, jisb3, jisb4, jisb5, jisb6, flsa, flse, halfletter.
Unfortunately, all sizes are currently only available in portrait
orientation (not landscape).
</para>
<para>
By default, &ps2eps; uses an already given %%BoundingBox
from the source file, which often corresponds to the size of
the physical page format for which the document was
printed. However, you should be aware that this already
specified bounding box may be not correct, thus resulting in a
wrongly cropped (or even no usable) <filename>.eps</filename>-file.
&ps2eps; can only do as good as &gs; does in rendering the original
postscript file (though &ps2eps; even works with negative and
fractional values are contained in the original bounding box by using
automatic translation). Therefore, if the given bounding box is to
small or incorrect anyway, you can ignore the existing bounding box with the <option>-B</option>
option, which will cause &gs; to use its internal
default size (or use <option>-s</option>). However, if the
BoundingBox has negative coordinates, which is not allowed by
the specification, &ps2eps; will shift the output to positive values.
</para>
<para>Hint: to avoid rotating the picture
if you have the original drawing in landscape format, you may
use the <quote>Encapsulated Postscript</quote> option in the printer driver
which should generate an EPS file (but with a bounding box of
the sheet size!). But some Windows printer drivers are drawing
the image with an offset from the bottom of the portrait page,
so that a part of it is drawn outside the landscape oriented
page. In this case, you'll have to specify a square size of
the page using the maximum length, e.g., 29.7cm x 29.7cm for
an A4 page.</para>
</refsect2>
<refsect2>
<title>Clipping</title>
<para>or why gets some of my text deleted above the included <filename>.eps</filename> file?</para>
<para>
Some postscript drivers draw a white rectangle from the top left
corner of the page to the right lower corner of the object. This may
erase some or even all text above your imported/included EPS file,
which is very annoying. In order to prevent this, most programs have a
clipping option for imported <filename>.eps</filename> files (within LaTeX you can use
\includegraphics*{}) for this purpose. If this is unfortunately not
the case, you can use the <option>-C</option> option of &ps2eps; which will (hopefully)
do it for you. Unfortunately, PScript.dll 5.2 (Windows XP) introduced
new very badly behaving Postscript code (initclip) which will even
override the outer clipping! Thus, a new filter had to be installed
in &ps2eps; which will fix it.
</para>
<para>
However, because most programs clip directly on the bounding box,
you still may loose some pixels of your image, because the bounding
box is described in the coarse resolution of postscript points,
i.e. 72 dpi. In order to prevent this, you can use the <option>-l</option>
option or <option>-C</option> option (for the latter, clipping by the importing program
should be disabled then) to allow for a 1 point larger bounding box.
<option>-C</option> clips around a 1 point enlarged bounding box and <option>-l</option> enlarges the
bounding box values by 1 point (you can also combine both options).
</para>
</refsect2>
<refsect2>
<title>Included Filters</title>
<para>
Some postscript sequences, e.g., for using specific printer
features (featurebegin ...), are not working well within an <filename>.eps</filename>
file, so &ps2eps; tries to filter them out. But please note that
filters for postscript code may not work properly for your printer
driver (&ps2eps; was mainly tested with HP and Adobe printer
drivers, although it may work for all printers using the
PScript.dll). In this case you can try to turn of filtering by
using option <option>-n</option>, or try to find the bad sequence in the postscript
code and adapt the filter rule in the &ps2eps; script (variables
$linefilter, $rangefilter_begin, $rangefilter_end; linefilter is
an expression for filtering single lines, rangefilter_... are
expressions that filter all lines between a pattern matching
$rangefilter_begin and $rangefilter_end; drop me an e-mail with
your modifications). However, things may change as the printer
drivers (e.g., PScript.dll) or postscript language evolve.
</para>
<para>
Some applications or drivers generate postscript code with leading
or trailing binary code, which often confuses older postscript
interpreters. &ps2eps; tries to remove such code, but it may
sometimes make a wrong guess about start and end of the real
postscript code (drop me an e-mail with a zipped postscript
source, see section BUGS). <!--<xref linkend="BUGS" --> <!--endterm="BUGS.title"/>-->
</para>
<para>Comment lines or even blank lines are removed
(which is the default to make .eps files smaller), which may corrupt your
output. Please check the next section how to fix this.
&ps2eps; removes blank lines and also <CR> (carriage ceturn
<quote>\r</quote>) at the end of lines. However, nicely formatted postscript code
gives a hint by using <quote>%%BeginBinary</quote> <quote>%%EndBinary</quote> comments. When
&ps2eps; detects these comments it will refrain from any filtering
action within the marked binary sections.
</para>
<para>
&ps2eps; filters also %%Orientation: comments by
default (you can use option <option>-O</option> to turn off filtering),
because &gs; may <quote>automagically</quote> rotate images when generating PDF
images, which is not desired in most cases. Hint: you can turn off that
feature in &gs; unconditionally by specifying -dAutoRotatePages=/None.
</para>
</refsect2>
<refsect2>
<title>Corrupted Output</title>
<para>
Some postscript code may get corrupted when comment lines or even blank
lines are removed (which is the default to make .eps files smaller),
because those files may contain encoded images
which also have a % as first character in a line or use a special
comment as end of image delimiter. If this is the case, use the <option>-c</option>
option to prevent filtering comments.
</para>
</refsect2>
<refsect2>
<title>Color and memory</title>
<para>&ps2eps; supports colored postscript, consequently
letting &gs; consume more resources for drawing its bitmap
(roughly 6MBytes for an A4 page). <command>bbox</command> is reading
the bitmap line by line so it consumes only minimal memory. If you experience problems
with memory consumption of &gs;, you may use the <option>-m</option> option
for using a monochrome image. But this will probably result in wrongly
determined bounding boxes with colored
images, because &gs; has to do black/white dithering and may thus suppress
objects drawn in light colors.</para>
<para>Another option in case of memory problems and too long run times
is to use the much more memory efficient internal &gs bbox by using the
<option>-g</option> option.
</para>
</refsect2>
</refsect1>
<refsect1>
<title>ENVIRONMENT VARIABLES</title>
<para>Please note that a command line option always takes precedence over
the related environment variable.</para>
<para>The environment variable <varname>PS2EPS_SIZE</varname> can be used
to specify a default page size and take any argument that
<option>--size</option> accepts. Examples: <userinput>export PS2EPS_SIZE=a0</userinput> (bash-like syntax)
or <userinput>setenv PS2EPS_SIZE letter</userinput> (csh syntax). </para>
<para>If the environment variable <varname>PS2EPS_GSBBOX</varname> is set
the internal bbox device of &gs; will be used instead of the external
command <command>bbox</command>. Examples: <userinput>export PS2EPS_GSBBOX=true</userinput> (bash-like syntax)
or <userinput>setenv PS2EPS_GSBBOX 1</userinput> (csh syntax).</para>
</refsect1>
<refsect1>
<title>EXAMPLES</title>
<para>The usual call is simply:
<userinput>ps2eps -l <replaceable>file</replaceable></userinput></para>
<para>A relatively failsafe call would be (if your postscript is smaller
than iso b0 [100cm x 141.4cm] and you have a fast computer with enough memory):
<userinput>ps2eps -l -B -s b0 -c -n <replaceable>file</replaceable></userinput></para>
<para>If output is not correct try:
<userinput>ps2eps -l -B -s b0 -F <replaceable>file</replaceable></userinput> </para>
</refsect1>
<refsect1>
<title>AUTHOR</title>
<para>&ps2eps; was written by &dhusername;. </para>
<refsect2>
<title>WHY?</title>
<para>
Other programs like <command>ps2epsi</command> do not calculate the
bounding box always correctly (because the values are put on the
postscript stack which may get corrupted by bad postscript code) or
rounded it off so that clipping the EPS cut off some part of the
image. &ps2eps; uses a double precision resolution
of 144 dpi and appropriate rounding to get a proper bounding
box. The internal bbox device of &gs; generates different values
(sometimes even incorrect), so using the provided <command>bbox</command>
should be more robust.
However, because normal clipping has only a resolution of 1/72dpi
(postscript point), the clipping process may still erase parts of your
EPS image. In this case please use the <option>-l</option> option to add
an additional point of white space around the tight bounding box.
</para>
</refsect2>
<refsect2>
<title>ACKNOWLEDGMENTS</title>
<para>Some people contributed code or suggestions to improve &ps2eps;. Here
are at least some names (sorry if I forgot your name):
Christophe Druet, Hans Ecke, Berend Hasselman, Erik Joergensen, Koji Nakamaru, Hans Fredrik Nordhaug, Michael Sharpe.
Special thanks goes to Michael Sharpe from UCSD who suggested a lot of useful features for ps2eps and
who fixed bbox to become more precise and robust.
</para>
<para>An earlier version of this manual page was originally written by
Rafael Laboissiere <email>rafael at debian.org</email> for
the &debian; system. Thank you Rafael! </para>
<para>
Permission is granted to copy, distribute and/or modify this document under
the terms of the &gnu; Free Documentation
License, Version 1.1 or any later version published by the Free
Software Foundation; with no Invariant Sections, no Front-Cover
Texts and no Back-Cover Texts.</para>
</refsect2>
</refsect1>
<refsect1 id="BUGS">
<title id="BUGS.title">BUGS</title>
<para>
If you experience problems, please check carefully all hints in the section
TROUBLESHOOTING
<!-- <xref linkend="TROUBLESHOOTING" endterm="TROUBLESHOOTING.title"/> -->
first. Otherwise, check for an updated
version at <ulink URL="http://www.tm.uka.de/~bless/ps2eps"></ulink>
or send a gzipped file of
relevant postscript source code with your error description
and &ps2eps; version number to &dhemail; (please allow some time
to reply).
</para>
</refsect1>
<refsect1>
<title>SEE ALSO</title>
<para>bbox (1), gs (1), ps2epsi (1)</para>
</refsect1>
</refentry>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-default-dtd-file:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->
|
