version 2, including all changes.
.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
PS2EPSI |
|
|
2 |
!!!PS2EPSI |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
USAGE |
|
|
7 |
LIMITATIONS |
|
|
8 |
COMPATIBILITY |
|
|
9 |
FILES |
|
|
10 |
SEE ALSO |
|
|
11 |
VERSION |
|
|
12 |
AUTHOR |
|
|
13 |
---- |
|
|
14 |
!!NAME |
|
|
15 |
|
|
|
16 |
|
2 |
perry |
17 |
ps2epsi - generate conforming Encapsulated !PostScript |
1 |
perry |
18 |
!!SYNOPSIS |
|
|
19 |
|
|
|
20 |
|
|
|
21 |
__ps2epsi__ ''infile.ps'' [[ ''outfile.epsi'' ] |
|
|
22 |
__(Unix) |
|
|
23 |
ps2epsi__ ''infile.ps'' [[ ''outfile.epi'' ] |
|
|
24 |
__(DOS)__ |
|
|
25 |
!!DESCRIPTION |
|
|
26 |
|
|
|
27 |
|
|
|
28 |
__ps2epsi__ uses gs(1) to process a |
2 |
perry |
29 |
__!PostScript__(tm) file and generate as output a new file |
|
|
30 |
which conforms to Adobe's __Encapsulated !PostScript |
1 |
perry |
31 |
Interchange__ (EPSI) format. EPSI is a special form of |
2 |
perry |
32 |
encapsulated !PostScript (EPS) which adds to the beginning of |
|
|
33 |
the file in the form of !PostScript comments a bitmapped |
1 |
perry |
34 |
version of the final displayed page. Programs which |
|
|
35 |
understand EPSI (usually word processors or DTP programs) |
|
|
36 |
can use this bitmap to give a preview version on screen of |
2 |
perry |
37 |
the !PostScript. The displayed quality is often not very good |
1 |
perry |
38 |
(e.g., low resolution, no colours), but the final printed |
2 |
perry |
39 |
version uses the real !PostScript, and thus has the normal |
|
|
40 |
!PostScript quality. |
1 |
perry |
41 |
!!USAGE |
|
|
42 |
|
|
|
43 |
|
|
|
44 |
On Unix systems invoke __ps2epsi__ like |
|
|
45 |
this: |
|
|
46 |
|
|
|
47 |
|
|
|
48 |
__ps2epsi__ ''infile.ps'' [[ ''outfile.epsi'' |
|
|
49 |
] |
|
|
50 |
|
|
|
51 |
|
|
|
52 |
where |
|
|
53 |
|
|
|
54 |
|
|
|
55 |
__ps2epsi__ ''infile.ps outfile.epi'' |
|
|
56 |
|
|
|
57 |
|
|
|
58 |
where |
|
|
59 |
!!LIMITATIONS |
|
|
60 |
|
|
|
61 |
|
2 |
perry |
62 |
Not every !PostScript file can be encapsulated successfully, |
|
|
63 |
because there are restrictions on what !PostScript constructs |
1 |
perry |
64 |
a correct encapsulated file may contain. __ps2epsi__ does |
|
|
65 |
a little extra work to try to help encapsulation, and it |
|
|
66 |
automatically calculates the bounding box required for all |
2 |
perry |
67 |
encapsulated !PostScript files, so most of the time it does a |
1 |
perry |
68 |
pretty good job. There are certain to be cases, however, |
|
|
69 |
where the encapsulation does not work because of the content |
2 |
perry |
70 |
of the original !PostScript file. |
1 |
perry |
71 |
!!COMPATIBILITY |
|
|
72 |
|
|
|
73 |
|
|
|
74 |
The __Framemaker__ DTP system is one application which |
|
|
75 |
understands EPSI files, and __ps2epsi__ has been tested |
2 |
perry |
76 |
on a number of !PostScript diagrams from a variety of |
1 |
perry |
77 |
sources, using Framemaker 3.0 on a Sun workstation. |
|
|
78 |
Framemaker on other platforms should be able to use these |
|
|
79 |
files, although I have not been able to test |
|
|
80 |
this. |
|
|
81 |
!!FILES |
|
|
82 |
!!SEE ALSO |
|
|
83 |
|
|
|
84 |
|
|
|
85 |
gs (1) |
|
|
86 |
!!VERSION |
|
|
87 |
|
|
|
88 |
|
|
|
89 |
This document was last revised for Ghostscript version 6.53. |
|
|
90 |
However, the content may be obsolete, or inconsistent with |
|
|
91 |
ps2epsi.txt. |
|
|
92 |
!!AUTHOR |
|
|
93 |
|
|
|
94 |
|
|
|
95 |
George Cameron |
|
|
96 |
---- |