1PSTOEDIT(1) Conversion Tools PSTOEDIT(1)
2
6 pstoedit - a tool converting PostScript and PDF files into various vec‐
7 tor graphic formats
8
10 FROM THE COMMAND SHELL
11 pstoedit [-v -help]
12 pstoedit [-include name of a PostScript file to be included] [-df font
14 name] [-nomaptoisolatin1] [-dis] [-pngimage filename] [-q] [-nq] [-nc]
15 [-mergelines] [-filledrecttostroke] [-mergetext] [-dt] [-adt] [-ndt]
16 [-dgbm] [-correctdefinefont] [-pti] [-pta] [-xscale number] [-yscale
17 number] [-xshift number] [-yshift number] [-centered] [-minlinewidth
18 number] [-pagenumberformat page number format specification] [-split]
19 [-v] [-vl ] [-usebbfrominput] [-ssp] [-sfill] [-uchar character] [-nb]
20 [-rdb] [-page page number] [-flat flatness factor] [-sclip] [-ups]
21 [-rgb] [-useagl] [-noclip] [-t2fontsast1] [-keep] [-debugfonthandling]
22 [-gstest] [-fakedateandversion] [-nfr] [-glyphs] [-useoldnormalization]
23 [-rotate angle (0-360)] [-fontmap name of font map file for pstoedit]
24 [-pagesize page format] [-help] [-gs path to the Ghostscript exe‐
25 cutable/DLL] [-bo] [-psarg argument string] [-pslanguagelevel Post‐
26 Script Language Level 1, 2, or 3 to be used.] -f "format[:options]"
27 [-gsregbase Ghostscript base registry path] [ inputfile [outputfile] ]
28 FROM GSVIEW
30 Pstoedit can be called from within gsview via "Edit | Convert to vector
31 format"
32 FROM PROGRAMS THAT SUPPORT THE ALDUS GRAPHIC IMPORT FILTER INTERFACE
34 pstoedit can also be used as PostScript and PDF graphic import filter
35 for several programs including MS Office, PaintShop-Pro and PhotoLine.
36 See http://www.pstoedit.net/importps/ for more details.
37
39 RELEASE LEVEL
40 This manpage documents release 3.78 of pstoedit.
41 USE
43 pstoedit converts PostScript and PDF files to various vector graphic
44 formats. The resulting files can be edited or imported into various
45 drawing packages. Type
46 pstoedit -help
48 to get a list of supported output formats. Pstoedit comes with a large
50 set of format drivers integrated in the binary. Additional drivers can
51 be installed as plugins and are available via
52 http://www.pstoedit.net/plugins/. Just copy the plugins to the same
53 directory where the pstoedit binary is installed or - under Unix like
54 systems only - alternatively into the lib directory parallel to the bin
55 directory where pstoedit is installed.
56 However, unless you also get a license key for the plugins, the addi‐
58 tional drivers will slightly distort the resulting graphics. See the
59 documentation provided with the plugins for further details.
60 PRINCIPLE OF CONVERSION
62 pstoedit works by redefining some basic painting operators of Post‐
63 Script, e.g. stroke or show (bitmaps drawn by the image operator are
64 not supported by all output formats.) After redefining these operators,
65 the PostScript or PDF file that needs to be converted is processed by a
66 PostScript interpreter, e.g., Ghostscript (gs(1)). You normally need
67 to have a PostScript interpreter installed in order to use this pro‐
68 gram. However, you can perform some "back end only" processing of files
69 following the conventions of the pstoedit intermediate format by speci‐
70 fying the -bo option. See "Available formats and their specific op‐
71 tions" below.
72 The output that is written by the interpreter due to the redefinition
74 of the drawing operators is a sort of 'flat' PostScript file that con‐
75 tains only simple operations like moveto, lineto, show, etc. You can
76 look at this file using the -f debug option.
77 This output is read by end-processing functions of pstoedit and trig‐
79 gers the drawing functions in the selected output format driver some‐
80 time called also "backend".
81 NOTES
83 If you want to process PDF files directly, your PostScript interpreter
84 must provide this feature, as does Ghostscript. Aladdin Ghostscript is
85 recommended for processing PDF and PostScript files.
86
88 GENERAL OPTIONS
89 The following format specific options are available:
90 [-include name of a PostScript file to be included]
92 This option allows specifying an additional PostScript file
93 that will be executed just before the normal input is read. This
94 is helpful for including specific page settings or for disabling
95 potentially unsafe PostScript operators, e.g., file, renamefile,
96 or deletefile.
97 [-xscale number]
99 .PP
100 [-yscale number]
102 .PP
103 [-xshift number]
105 .PP
106 [-yshift number]
108 .PP
109 [-centered]
111 .PP
112 [-minlinewidth number]
114 .PP
115 [-pagenumberformat page number format specification]
117 .PP
118 [-split]
120 Create a new file for each page of the input. For this the out‐
121 put filename must contain a %d which is replaced with the cur‐
122 rent page number. This option is automatically switched on for
123 output formats that do not support multiple pages within one
124 file, e.g. fig or gnuplot.
125 [-usebbfrominput]
127 If specified, pstoedit uses the BoundingBox as is (hopefully)
128 found in the input file instead of one that is calculated by its
129 own.
130 [-page page number]
132 Select a single page from a multi-page PostScript or PDF file.
133 [-rgb]
135 Since version 3.30 pstoedit uses the CMYK colors internally.
136 The -rgb option turns on the old behavior to use RGB values.
137 [-useagl]
139 .PP
140 [-noclip]
142 .PP
143 [-rotate angle (0-360)]
145 Rotate image by angle.
146 [-pagesize page format]
148 set page size for output medium. This option sets the page
149 size for the output medium. Currently this is just used by the
150 libplot output format driver, but might be used by other output
151 format drivers in future. The page size is specified in terms of
152 the usual page size names, e.g. letter or a4.
153 [-help]
155 .PP
156 [-gs path to the Ghostscript executable/DLL]
158 .PP
159 [-bo]
161 You can run backend processing only (without the PostScript in‐
162 terpreter frontend) by first running pstoedit -f dump infile
163 dumpfile and then running pstoedit -f format -bo dumpfile out‐
164 file.
165 [-psarg argument string]
167 The string given with this option is passed directly to Ghost‐
168 script when Ghostscript is called to process the PostScript file
169 for pstoedit. For example: -psarg "-r300x300". This causes the
170 resolution to be changed to 300x300 dpi. (With older versions of
171 Ghostscript, changing the resolution this way has an effect only
172 if the -dis option is given.) If you want to pass multiple op‐
173 tions to Ghostscript you can use multiple -psarg options -psarg
174 opt1 -psarg opt2 -psarg opt2. See the Ghostscript manual for
175 other possible options.
176 [-pslanguagelevel PostScript Language Level 1, 2, or 3 to be used.]
178 .PP
179 -f "format[:options]"
181 target output format recognized by pstoedit. Since other for‐
182 mat drivers can be loaded dynamically, type pstoedit -help to
183 get a full list of formats. See "Available formats and their
184 specific options" below for an explanation of the [:options] to
185 -f format. If the format option is not given, pstoedit tries to
186 guess the target format from the suffix of the output filename.
187 However, in a lot of cases, this is not a unique mapping and
188 hence pstoedit demands the -f option.
189 [-gsregbase Ghostscript base registry path]
191 registry path to use as a base path when searching Ghostscript
192 interpreter. This option provides means to specify a registry
193 key under HKLM/Software where to search for GS interpreter key,
194 version and GS_DLL / GS_LIB values. Example: "-gsregbase My‐
195 Company" means that HKLM/Software/MyCompany/GPL Ghostscript
196 would be searched instead of HKLM/Software/GPL Ghostscript.
197 TEXT AND FONT HANDLING RELATED OPTIONS
199 The following format specific options are available:
200 [-df font name]
202 Sometimes fonts embedded in a PostScript program do not have a
203 fontname. For example, this happens in PostScript files gener‐
204 ated by dvips(1). In such a case pstoedit uses a replacement
205 font. The default for this is Courier. Another font can be spec‐
206 ified using the -df option. -df Helvetica causes all unnamed
207 fonts to be replaced by Helvetica.
208 [-nomaptoisolatin1]
210 Normally pstoedit maps all character codes to the ones defined
211 by the ISO Latin1 encoding. If you specify -nomaptoisolatin1
212 then the encoding from the input PostScript is passed unchanged
213 to the output. This may result in strange text output but on the
214 other hand may be the only way to get some fonts converted ap‐
215 propriately. Try what fits best to your concrete case.
216 [-pngimage filename]
218 .PP
219 [-dt]
221 draw text. Text is drawn as polygons. This might produce a
222 large output file. This option is automatically switched on if
223 the selected output format does not support text, e.g. gnu‐
224 plot(1).
225 [-adt]
227 automatic draw text. This option turns on the -dt option selec‐
228 tively for fonts that seem to be no normal text fonts, e.g. Sym‐
229 bol.
230 [-ndt]
232 never draw text. Fully disable the heuristics used by pstoedit
233 to decide when to "draw" text instead of showing it as text.
234 This may produce incorrect results, but in some cases it might
235 nevertheless be useful. "Use at own risk".
236 [-dgbm]
238 .PP
239 [-correctdefinefont]
241 Some PostScript files, e.g. such as generated by ChemDraw, use
242 the PostScript definefont operator in a way that is incompatible
243 with pstoedit's assumptions. The new font is defined by copying
244 an old font without changing the FontName of the new font. When
245 this option is applied, some "patches" are done after a define‐
246 font in order to make it again compatible with pstoedit's as‐
247 sumptions. This option is not enabled by default, since it may
248 break other PostScript files. It is tested only with ChemDraw
249 generated files.
250 [-pti]
252 precision text. Normally a text string is drawn as it occurs in
253 the input file. However, in some situations, this might produce
254 wrongly positioned characters. This is due to limitations in
255 most output formats of pstoedit. They cannot represent text with
256 arbitrary inter-letter spacing which is easily possible in PDF
257 and PostScript. With -pta, each character of a text string is
258 placed separately. With -pti, this is done only in cases when
259 there is a non zero inter-letter spacing. The downside of "pre‐
260 cision text" is a bigger file size and hard to edit text.
261 [-pta]
263 see -pti
264 [-uchar character]
266 Sometimes pstoedit cannot map a character from the encoding
267 used by the PostScript file to the font encoding of the target
268 format. In this case pstoedit replaces the input character by a
269 special character in order to show all the places that could not
270 be mapped correctly. The default for this is a "#". Using the
271 -uchar option it is possible to specify another character to be
272 used instead. If you want to use a space, use -uchar " ".
273 [-t2fontsast1]
275 Handle Type 2 fonts same as Type 1. Type 2 fonts sometimes oc‐
276 cur as embedded fonts within PDF files. In the default mode,
277 text using such fonts is drawn as polygons since pstoedit as‐
278 sumes that such a font is not available on the user's machine.
279 If this option is set, pstoedit assumes that the internal encod‐
280 ing follows the same as for a standard font and generates normal
281 text output. This assumption may not be true in all cases. But
282 it is nearly impossible for pstoedit to verify this assumption -
283 it would have to do a sort of OCR.
284 [-nfr]
286 In normal mode pstoedit replaces bitmap fonts with a font as
287 defined by the -df option. This is done, because most output
288 formats cannot handle such fonts. This behavior can be switched
289 off using the -nfr option but then it strongly depends on the
290 application reading the generated file whether the file is us‐
291 able and correctly interpreted or not. Any problems are then out
292 of control of pstoedit.
293 [-glyphs]
295 pass glyph names to the output format driver. So far no output
296 format driver really uses the glyph names, so this does not have
297 any effect at the moment. It is a preparation for future work.
298 [-useoldnormalization]
300 Just use this option in case the new heuristic introduced in
301 3.5 does not produce correct results - however, this normaliza‐
302 tion of font encoding will always be a best-effort approach
303 since there is no real general solution to it with reasonable
304 effort
305 [-fontmap name of font map file for pstoedit]
307 The font map is a simple text file containing lines in the fol‐
308 lowing format:
309 document_font_name target_font_name
311 Lines beginning with % are considerd comments.
312 For font names with spaces use the "font name with spaces" notation.
313 If a target_font_name starts with /, it is regarded as alias to a for‐
315 mer entry.
316 Each font name found in the document is checked against this mapping
318 and if there is a corresponding entry, the new name is used for the
319 output.
320 If the -fontmap option is not specified, pstoedit automatically looks
322 for the file drivername.fmp in the installation directory and uses that
323 file as a default fontmap file if available. The installation directory
324 is:
325 * MS Windows: The same directory where the pstoedit exe‐
327 cutable is located
328 * Unix:
330 The default installation directory. If it fails, then
331 <The directory where the pstoedit executable is located>
332 /../lib/
333 The mpost.fmp in the misc directory of the pstoedit distribution
335 is a sample map file with mappings from over 5000 PostScript
336 font names to their TeX equivalents. This is useful because
337 MetaPost is frequently used with TeX/LaTeX and those programs do
338 not use standard font names. This file and the MetaPost output
339 format driver are provided by Scott Pakin
340 (scott+ps2ed_AT_pakin.org). Another example is wemf.fmp to be
341 used under Windows. See the misc directory of the pstoedit
342 source distribution. After loading the implicit (based on
343 driver name) or explicit (based on the -fontmap option) font map
344 file, a system specific map file is searched and loaded from the
345 installation directory (unix.fmp or windows.fmp). This file can
346 be used to redirect certain fonts to system specific names using
347 the /AliasName notation described above.
348 DRAWING RELATED OPTIONS
350 The following format specific options are available:
351 [-nc]
353 no curves. Normally pstoedit tries to keep curves from the in‐
354 put and transfers them to the output if the output format sup‐
355 ports curves. If the output format does not support curves, then
356 pstoedit replaces curves by a series of lines (see also -flat
357 option). However, in some cases the user might wish to have this
358 behavior also for output formats that originally support curves.
359 This can be forced via the -nc option.
360 [-mergelines]
362 Some output formats permit the representation of filled poly‐
363 gons with edges that are in a different color than the fill
364 color. Since PostScript does not support this by the standard
365 drawing primitives directly, drawing programs typically generate
366 two objects (the outline and the filled polygon) into the Post‐
367 Script output. pstoedit is able to recombine these, if they fol‐
368 low each other directly and you specify -mergelines. However,
369 this merging is not supported by all output formats due to re‐
370 strictions in the target format.
371 [-filledrecttostroke]
373 Rectangles filled with a solid color can be converted to a
374 stroked line with a width that corresponds to the width of the
375 rectangle. This is of primary interest for output formats which
376 do not support filled polygons at all. But it is restricted to
377 rectangles only, i.e. it is not supported for general polygons
378 [-mergetext]
380 In order to produce nice looking text output, programs produc‐
381 ing PostScript files often split words into smaller pieces which
382 are then placed individually on adjacent positions. However,
383 such split text is hard to edit later on and hence it is some‐
384 time better to recombine these pieces again to form a word (or
385 even sequence of words). For this pstoedit implements some
386 heuristics about what text pieces are to be considered parts of
387 a split word. This is based on the geometrical proximity of the
388 different parts and seems to work quite well so far. But there
389 are certainly cases where this simple heuristic fails. So please
390 check the results carefully.
391 [-ssp]
393 simulate subpaths. Several output formats do not support Post‐
394 Script paths containing subpaths, i.e. paths with intermediate
395 movetos. In the normal case, each subpath is treated as an inde‐
396 pendent path for such output formats. This can lead to bad look‐
397 ing results. The most common case where this happens is if you
398 use the -dt option and show some text with letters like e, o, or
399 b, i.e. letters that have a "hole". When the -ssp option is set,
400 pstoedit tries to eliminate these problems. However, this option
401 is CPU time intensive!
402 [-sfill]
404 simulate filling by individual strokes.
405 [-flat flatness factor]
407 If the output format does not support curves in the way Post‐
408 Script does or if the -nc option is specified, all curves are
409 approximated by lines. Using the -flat option one can control
410 this approximation. This parameter is directly converted to a
411 PostScript setflat command. Higher numbers, e.g. 10 give
412 rougher, lower numbers, e.g. 0.1, give finer approximations.
413 [-sclip]
415 simulate clipping. Most output formats of pstoedit do not have
416 native support for clipping. For that pstoedit offers an option
417 to perform the clipping of the graphics directly without passing
418 the clippath to the output driver. However, this results in
419 curves being replaced by a lot of line segments and thus larger
420 output files. So use this option only if your output looks dif‐
421 ferent from the input due to clipping. In addition, this "simu‐
422 lated clipping" is not exactly the same as defined in Post‐
423 Script. There might be lines drawn at double size. Also clipping
424 of text is not supported unless you also use the -dt option.
425 DEBUG OPTIONS
427 The following format specific options are available:
428 [-dis]
430 Open a display during processing by Ghostscript. Some files
431 only work correctly this way.
432 [-q]
434 .PP
435 [-nq]
437 no exit from the PostScript interpreter. Normally Ghostscript
438 exits after processing the pstoedit input-file. For debugging it
439 can be useful to avoid this. If you do, you will have to type
440 quit at the GS> prompt to exit from Ghostscript.
441 [-v]
443 Switch on verbose mode. Some additional information is shown
444 during processing.
445 [-vl ]
447 Switch on verbose mode with a given level. Some additional in‐
448 formation is shown during processing.
449 [-nb]
451 Since version 3.10 pstoedit uses the -dDELAYBIND option when
452 calling Ghostscript. Previously the -dNOBIND option was used in‐
453 stead but that sometimes caused problems if a user's PostScript
454 file overloaded standard PostScript operator with totally new
455 semantic, e.g. lt for lineto instead of the standard meaning of
456 "less than". Using -nb the old style can be activated again in
457 case the -dDELAYBIND gives different results as before. In such
458 a case please also contact the author.
459 [-rdb]
461 Since version 3.10 pstoedit uses the -dDELAYBIND option when
462 calling Ghostscript. But in version 9.22 of GhostScript, that
463 option is not supported anymore because of security reasons. As
464 a fallback, that version provides the REALLYDELAYBIND option and
465 pstoedit can use this if you supply the -rdb option. Use this
466 with caution as it might open security risks, e.g. a PostScript
467 file injecting some malicious code into PostScript standard op‐
468 erators. However, not using this option can cause some of the
469 PostScript drawings operations to be not seen by pstoedit, hence
470 causing missing artefacts in the output. Later versions of
471 Ghostscript will probably support -dDELAYBIND again. But also in
472 that case the security risk remains. So be careful with what
473 files you process with pstoedit and Ghostscript.
474 [-ups]
476 .PP
477 [-keep]
479 .PP
480 [-debugfonthandling]
482 .PP
483 [-gstest]
485 .PP
486 [-fakedateandversion]
488 .PP
489 INPUT AND OUTFILE FILE ARGUMENTS
491 [ inputfile [outputfile] ]
492 If neither an input nor an output file is given as argument, pstoedit
494 works as filter reading from standard input and writing to standard
495 output. The special filename "-" can also be used. It represents stan‐
496 dard input if it is the first on the command line and standard output
497 if it is the second. So "pstoedit - output.xxx" reads from standard in‐
498 put and writes to output.xxx
499
501 pstoedit allows passing individual options to an output format driver.
502 This is done by appending all options to the format specified after the
503 -f option. The format specifier and its options must be separated by a
504 colon (:). If more than one option needs to be passed to the output
505 format driver, the whole argument to -f must be enclosed within dou‐
506 ble-quote characters, thus:
507 -f "format[:option option ...]"
509 To see which options are supported by a specific format, type: pstoedit
511 -f format:-help
512 The following description of the different formats supported by
514 pstoedit is extracted from the source code of the individual drivers.
515 Format group: psf ps debug dump gs ps2ai
517 This group consists of the following variants:
518 psf: Flattened PostScript (no curves).
520 ps: Simplified PostScript with curves.
522 debug: for test purposes.
524 dump: for test purposes (same as debug).
526 gs: any device that Ghostscript provides - use gs:format, e.g.
528 gs:pdfwrite.
529 ps2ai: Adobe Illustrator via ps2ai.ps of Ghostscript.
531 No format specific options
533 Format group: gmfa gmfb plot plot-cgm plot-ai plot-svg plot-ps plot-fig
535 plot-pcl plot-hpgl plot-tek
536 This group consists of the following variants:
537 gmfa: ASCII GNU metafile .
539 gmfb: binary GNU metafile .
541 plot: GNU libplot output types, e.g. plot:-plotformat X.
543 plot-cgm:
545 cgm via GNU libplot.
546 plot-ai:
548 ai via GNU libplot.
549 plot-svg:
551 svg via GNU libplot.
552 plot-ps:
554 ps via GNU libplot.
555 plot-fig:
557 fig via GNU libplot.
558 plot-pcl:
560 pcl via GNU libplot.
561 plot-hpgl:
563 hpgl via GNU libplot.
564 plot-tek:
566 tek via GNU libplot.
567 The following format specific options are available:
569 [-plotformat string]
571 plotutil format to generate
572 magick - MAGICK driver compatible with version 7.0.7 of ImageMagick.
574 This driver uses the C++ API of ImageMagick or GraphicsMagick to fi‐
575 nally produce different output formats. The output format is determined
576 automatically by Image-/GraphicsMagick based on the suffix of the out‐
577 put filename. So an output file test.png will force the creation of an
578 image in PNG format. This binary of pstoedit was compiled against ver‐
579 sion 7.0.7 of ImageMagick.
580 No format specific options
582 swf - SWF driver:
584 The following format specific options are available:
585 [-cubic]
587 cubic ???
588 [-trace]
590 trace ???
591 Format group: svg xaml
593 This group consists of the following variants:
594 svg: Scalable Vector Graphics.
596 xaml: eXtensible Application Markup Language.
598 The following format specific options are available:
600 [-localdtd]
602 use local DTD
603 [-standalone]
605 create stand-alone type svg
606 [-withdtd]
608 write DTD
609 [-withgrouping]
611 write also ordinary save/restores as SVG group
612 [-nogroupedpath]
614 do not write a group around paths
615 [-noviewbox]
617 do not write a view box
618 [-texmode]
620 TeX mode
621 [-imagetofile]
623 write raster images to separate files instead of embedding them
624 [-notextrendering]
626 do not write textrendering attribute
627 [-border number]
629 additional border to draw around bare bounding box (in percent
630 of width and height)
631 [-title string]
633 text to use as title for the generated document
634 Format group: cgmb1 cgmb cgmt
636 This group consists of the following variants:
637 cgmb1: CGM Binary format (V1).
639 cgmb: CGM Binary format (V3).
641 cgmt: CGM Textual format.
643 No format specific options
645 mif - (Frame)Maker Intermediate Format
647 The following format specific options are available:
648 [-nopage]
650 do not add a separate Page entry
651 rtf - Rich Text Format
653 No format specific options
654 Format group: wemf wemfc wemfnss
656 This group consists of the following variants:
657 wemf: Wogl's version of EMF.
659 wemfc: Wogl's version of EMF with experimental clip support.
661 wemfnss:
663 Wogl's version of EMF - no subpaths.
664 The following format specific options are available:
666 [-df]
668 write info about font processing
669 [-dumpfontmap]
671 write info about font mapping
672 [-size:psbbox]
674 use the bounding box as calculated by the PostScript frontend
675 as size
676 [-size:fullpage]
678 set the size to that of the full page
679 [-size:automatic]
681 let MS Windows calculate the bounding box (default)
682 [-keepimages]
684 debug option - keep the embedded bitmaps as external files
685 [-useoldpolydraw]
687 do not use MS Windows' PolyDraw but an emulation of it - some‐
688 times needed for certain programs reading the EMF files
689 [-donotusepolydraw]
691 use lineto and moveto instead of polydraw when drawing a path
692 [-OO]
694 generate OpenOffice compatible EMF file
695 Format group: hpgl pcl
697 This group consists of the following variants:
698 hpgl: HPGL code.
700 pcl: PCL code.
702 The following format specific options are available:
704 [-penplotter]
706 plotter is pen plotter (i.e. no support for specific line
707 widths)
708 [-pencolorsfromfile]
710 read pen colors from file drvhpgl.pencolors in pstoedit's data
711 directory
712 [-pencolors number]
714 maximum number of pen colors to be used by pstoedit (default 0)
715 -
716 [-filltype string]
718 select fill type e.g. FT 1
719 [-hpgl2]
721 Use HPGL/2 instead of HPGL/1
722 [-rot90]
724 rotate hpgl by 90 degrees
725 [-rot180]
727 rotate hpgl by 180 degrees
728 [-rot270]
730 rotate hpgl by 270 degrees
731 pcb-rnd - pcb-rnd format
733 See also: http://repo.hu/pcb-rnd and http://www.pen‐
734 guin.cz/~utx/pstoedit-pcb/
735 The following format specific options are available:
737 [-grid missing arg name]
739 attempt to snap relevant output to grid (mils) and put failed
740 objects to a different layer
741 [-snapdist missing arg name]
743 grid snap distance ratio (0 < snapdist <= 0.5, default 0.1)
744 [-tshiftx missing arg name]
746 additional x shift measured in target units (mils)
747 [-tshifty missing arg name]
749 additional y shift measured in target units (mils)
750 [-grid missing arg name]
752 attempt to snap relevant output to grid (mils) and put failed
753 objects to a different layer
754 [-mm]
756 switch to metric units (mm)
757 [-forcepoly]
759 force all objects to be interpreted as polygons
760 pic - PIC format for troff et.al.
762 The following format specific options are available:
763 [-troff]
765 troff mode (default is groff)
766 [-landscape]
768 landscape output
769 [-portrait]
771 portrait output
772 [-keepfont]
774 print unrecognized literally
775 [-text]
777 try not to make pictures from running text
778 [-debug]
780 enable debug output
781 asy - Asymptote Format
783 No format specific options
784 cairo - cairo driver
786 generates compilable c code for rendering with cairo
787 The following format specific options are available:
789 [-pango]
791 use pango for font rendering
792 [-funcname string]
794 sets the base name for the generated functions and variables.
795 e.g. myfig
796 [-header string]
798 sets the output file name for the generated C header file. e.g.
799 myfig.h
800 cfdg - Context Free Design Grammar
802 Context Free Design Grammar, usable by Context Free Art
803 (http://www.contextfreeart.org/)
804 No format specific options
806 Format group: dxf dxf_14 dxf_s
808 This group consists of the following variants:
809 dxf: CAD exchange format version 9 - only limited features. Consider
811 using dxf_14 instead..
812 dxf_14:
814 CAD exchange format version 14 supporting splines and linetypes.
815 dxf_s: CAD exchange format version 14 supporting splines and linetypes.
817 The following format specific options are available:
819 [-polyaslines]
821 use LINE instead of POLYLINE in DXF
822 [-mm]
824 use mm coordinates instead of points in DXF (mm=pt/72*25.4)
825 [-ctl]
827 map colors to layers
828 [-filltohatch]
830 generate hatch objects from fill operations (still experimen‐
831 tal)
832 [-splineaspolyline]
834 approximate splines with PolyLines (only for -f dxf_s)
835 [-splineasnurb]
837 experimental (only for -f dxf_s)
838 [-splineasbspline]
840 experimental (only for -f dxf_s)
841 [-splineassinglespline]
843 experimental (only for -f dxf_s)
844 [-splineasmultispline]
846 experimental (only for -f dxf_s)
847 [-splineasbezier]
849 use Bezier splines in DXF format (only for -f dxf_s)
850 [-splineprecision number]
852 number of samples to take from spline curve when doing approxi‐
853 mation with -splineaspolyline or -splineasmultispline - should
854 be >= 2 (default 5)
855 [-dumplayernames]
857 dump all layer names found to standard output
858 [-layers string]
860 layers to be shown (comma separated list of layer names, no
861 space)
862 [-layerfilter string]
864 layers to be hidden (comma separated list of layer names, no
865 space)
866 Format group: fig xfig tfig
868 This group consists of the following variants:
869 fig: .fig format for xfig.
871 xfig: .fig format for xfig.
873 tfig: .fig format for xfig - test only version.
875 The xfig format driver supports special fontnames, which may be pro‐
877 duced by using a fontmap file. The following types of names are sup‐
878 ported:
879 General notation:
880 "PostScript Font Name" ((LaTeX|PostScript|empty)(::special)::)XFigFontName
881 Examples:
883 Helvetica LaTeX::SansSerif
885 Courier LaTeX::special::Typewriter
886 GillSans "AvantGarde Demi"
887 Albertus PostScript::special::"New Century Schoolbook Italic"
888 Symbol ::special::Symbol (same as PostScript::special::Symbol)
889 See also the file examplefigmap.fmp in the misc directory of the
891 pstoedit source distribution for an example font map file for xfig.
892 Please note that the fontname has to be among those supported by xfig.
893 See - http://www.xfig.org/userman/fig-format.html for a list of legal
894 font names
895 The following format specific options are available:
897 [-startdepth number]
899 set the initial depth (default 999)
900 [-metric]
902 switch to centimeter display (default inches)
903 [-usecorrectfontsize]
905 do not scale fonts for xfig. Use this if you also use this op‐
906 tion with xfig
907 [-depth number]
909 set the page depth in inches (default 11)
910 gcode - emc2 gcode format
912 See also: http://linuxcnc.org/
913 No format specific options
915 gnuplot - gnuplot format
917 No format specific options
918 gschem - gschem format
920 See also: http://www.geda.seul.org/tools/gschem/
921 No format specific options
923 idraw - Interviews draw format (EPS)
925 No format specific options
926 java1 - java 1 applet source code
928 The following format specific options are available:
929 [java class name string]
931 name of java class to generate
932 java2 - java 2 source code
934 The following format specific options are available:
935 [java class name string]
937 name of java class to generate
938 kil - .kil format for Kontour
940 No format specific options
941 latex2e - LaTeX2e picture format
943 The following format specific options are available:
944 [-integers]
946 round all coordinates to the nearest integer
947 lwo - LightWave 3D object format
949 No format specific options
950 mma - Mathematica graphics
952 The following format specific options are available:
953 [-eofillfills]
955 Filling is used for eofill (default is not to fill)
956 mpost - MetaPost format
958 No format specific options
959 noixml - Nemetschek NOI XML format
961 Nemetschek Object Interface XML format
962 The following format specific options are available:
964 [-r string]
966 Allplan resource file
967 [-bsl number]
969 Bezier Split Level (default 3)
970 pcbi - engrave data - insulate/PCB format
972 See http://home.vr-web.de/~hans-juergen-jahn/software/devpcb.html for
973 more details.
974 No format specific options
976 pcb - pcb format
978 See also: http://pcb.sourceforge.net and http://www.pen‐
979 guin.cz/~utx/pstoedit-pcb/
980 The following format specific options are available:
982 [-grid missing arg name]
984 attempt to snap relevant output to grid (mils) and put failed
985 objects to a different layer
986 [-snapdist missing arg name]
988 grid snap distance ratio (0 < snapdist <= 0.5, default 0.1)
989 [-tshiftx missing arg name]
991 additional x shift measured in target units (mils)
992 [-tshifty missing arg name]
994 additional y shift measured in target units (mils)
995 [-grid missing arg name]
997 attempt to snap relevant output to grid (mils) and put failed
998 objects to a different layer
999 [-mm]
1001 switch to metric units (mm)
1002 [-stdnames]
1004 use standard layer names instead of descriptive names
1005 [-forcepoly]
1007 force all objects to be interpreted as polygons
1008 pcbfill - pcb format with fills
1010 See also: http://pcb.sourceforge.net
1011 No format specific options
1013 pdf - Adobe's Portable Document Format
1015 No format specific options
1016 pptx - PresentationML (PowerPoint) format
1018 This is the format used internally by Microsoft PowerPoint. LibreOffice
1019 can also read/write PowerPoint files albeit with some lack of function‐
1020 ality.
1021 The following format specific options are available:
1023 [-colors string]
1025 "original" to retain original colors (default), "theme" to con‐
1026 vert randomly to theme colors, or "theme-lum" also to vary lumi‐
1027 nance
1028 [-fonts string]
1030 use "windows" fonts (default), "native" fonts, or convert to
1031 the "theme" font
1032 [-embed string]
1034 embed fonts, specified as a comma-separated list of EOT-format
1035 font files
1036 rib - RenderMan Interface Bytestream
1038 No format specific options
1039 rpl - Real3D Programming Language format
1041 No format specific options
1042 sample - sample driver: if you do not want to see this, uncomment the cor‐
1044 responding line in makefile and make again
1045 This is a long description for the sample driver
1046 The following format specific options are available:
1048 [-sampleoption integer]
1050 just an example
1051 sk - Sketch format
1053 No format specific options
1054 svm - StarView/OpenOffice.org metafile
1056 StarView/OpenOffice.org metafile, readable from OpenOffice.org
1057 1.0/StarOffice 6.0 and above.
1058 The following format specific options are available:
1060 [-m]
1062 map to Arial
1063 [-nf]
1065 emulate narrow fonts
1066 text - text in different forms
1068 The following format specific options are available:
1069 [-height number]
1071 page height in terms of characters
1072 [-width number]
1074 page width in terms of characters
1075 [-dump]
1077 dump text pieces
1078 tgif - Tgif .obj format
1080 The following format specific options are available:
1081 [-ta]
1083 text as attribute
1084 tk - tk and/or tk applet source code
1086 The following format specific options are available:
1087 [-R]
1089 swap HW
1090 [-I]
1092 no impress
1093 [-n string]
1095 tagnames
1096 vtk - VTK driver: if you do not want to see this, uncomment the correspond‐
1098 ing line in makefile and make again
1099 this is a long description for the VTKe driver
1100 The following format specific options are available:
1102 [-VTKeoption integer]
1104 just an example
1105 Format group: wmf emf
1107 This group consists of the following variants:
1108 wmf: MS Windows Metafile.
1110 emf: Enhanced MS Windows Metafile.
1112 The following format specific options are available:
1114 [-m]
1116 map to Arial
1117 [-nf]
1119 emulate narrow fonts
1120 [-drawbb]
1122 draw bounding box
1123 [-p]
1125 prune line ends
1126 [-nfw]
1128 Newer versions of MS Windows (2000, XP, Vista, 7, ...) will not
1129 accept WMF/EMF files generated when this option is set and the
1130 input contains text. But if this option is not set, then the
1131 WMF/EMF driver will estimate interletter spacing of text using a
1132 very coarse heuristic. This may result in ugly looking output.
1133 On the other hand, OpenOffice can still read EMF/WMF files where
1134 pstoedit delegates the calculation of the inter letter spacing
1135 to the program reading the WMF/EMF file. So if the generated
1136 WMF/EMF file shall never be processed under MS Windows, use this
1137 option. If WMF/EMF files with high precision text need to be
1138 generated under *nix the only option is to use the -pta option
1139 of pstoedit. However that causes every text to be split into
1140 single characters which makes the text hard to edit afterwards.
1141 Hence the -nfw option provides a sort of compromise between
1142 portability and nice to edit but still nice looking text. Again
1143 - this option has no meaning when pstoedit is executed under MS
1144 Windows anyway. In that case the output is portable but never‐
1145 theless not split and still looks fine.
1146 [-winbb]
1148 let the MS Windows API calculate the Bounding Box (MS Windows
1149 only)
1150 [-OO]
1152 generate OpenOffice compatible EMF file
1153
1155 AUTOTRACE
1156 pstoedit cooperates with autotrace. Autotrace can now produce a dump
1157 file for further processing by pstoedit using the -bo (backend only)
1158 option. Autotrace is a program written by a group around Martin Weber
1159 and can be found at http://sourceforge.net/projects/autotrace/.
1160 PS2AI
1162 The ps2ai output format driver is not a native pstoedit output format
1163 driver. It does not use the pstoedit PostScript flattener, instead it
1164 uses the PostScript program ps2ai.ps which is installed in the Ghost‐
1165 script distribution directory. It is included to provide the same
1166 "look-and-feel" for the conversion to AI. The additional benefit is
1167 that this conversion is now available also via the "convert-to-vector"
1168 menu of Gsview. However, lot's of files do not convert nicely or at all
1169 using ps2ai.ps. So a native pstoedit driver would be much better. Any‐
1170 one out there to take this? The AI format is usable for example by
1171 Mayura Draw (http://www.mayura.com). Also a driver to the Mayura na‐
1172 tive format would be nice.
1173 An alternative to the ps2ai based driver is available via the -f
1175 plot:ai format if the libplot(ter) is installed.
1176 You should use a version of Ghostscript greater than or equal to 6.00
1178 for using the ps2ai output format driver.
1179 METAPOST
1181 Note that, as far as Scott knows, MetaPost does not support Post‐
1182 Script's eofill. The MetaPost output format driver just converts eofill
1183 to fill, and issues a warning if verbose is set. Fortunately, very few
1184 PostScript programs rely on the even-odd fill rule, even though many
1185 specify it.
1186 For more on MetaPost see:
1188 http://tug.org/metapost
1190 CONTEXT FREE - CFDG
1192 The driver for the CFDG format (drvcfdg) defines one shape per page of
1193 PostScript, but only the first shape is actually rendered (unless the
1194 user edits the generated CFDG code, of course). CFDG does not support
1195 multi-page output, so this probably is a reasonable thing to do.
1196 For more on Context Free see: http://www.contextfreeart.org/
1198 LaTeX2E
1200 * LaTeX2e's picture environment is not very powerful. As a result,
1201 many elementary PostScript constructs are ignored -- fills, line
1202 thicknesses (besides "thick" and "thin"), and dash patterns, to
1203 name a few. Furthermore, complex pictures may overrun TeX's mem‐
1204 ory capacity. (The eepic package overcomes many such restric‐
1205 tions.)
1206 * Some PostScript constructs are not supported directly by "pic‐
1208 ture", but can be handled by external packages. If a figure uses
1209 color, the top-level document will need to do a "\usepack‐
1210 age{color}" or "\usepackage{xcolor}". And if a figure contains
1211 rotated text, the top-level document will need to do a "\usepa‐
1212 ckage{rotating}".
1213 * All lengths, coordinates, and font sizes output by the output
1215 format driver are in terms of \unitlength, so scaling a figure
1216 is simply a matter of doing a "\setlength{\unitlength}{...}".
1217 * The output format driver currently supports one output format
1219 driver specific option, "integers", which rounds all lengths,
1220 coordinates, and font sizes to the nearest integer. This makes
1221 hand-editing the picture a little nicer.
1222 * Why is this output format driver useful? One answer is porta‐
1224 bility; any LaTeX2e system can handle the picture environment,
1225 even if it cannot handle PostScript graphics. (pdfLaTeX comes to
1226 mind here.) A second answer is that pictures can be edited eas‐
1227 ily to contain any arbitrary LaTeX2e code. For instance, the
1228 text in a figure can be modified to contain complex mathematics,
1229 non-Latin alphabets, bibliographic citations, or -- the real
1230 reason Scott wrote the LaTeX2e output format driver -- hyper‐
1231 links to the surrounding document (with help from the hyperref
1232 package).
1233 CREATING A NEW OUTPUT FORMAT DRIVER
1235 To implement a new output format driver you can start from drvsampl.cpp
1236 and drvsampl.h. See also comments in drvbase.h and drvfuncs.h for an
1237 explanation of methods that should be implemented for a new output for‐
1238 mat driver.
1239
1241 A default PostScript interpreter to be called by pstoedit is specified
1242 at compile time. You can overwrite the default by setting the GS envi‐
1243 ronment variable to the name of a suitable PostScript interpreter.
1244 You can check which name of a PostScript interpreter was compiled into
1246 pstoedit using: pstoedit -help -v.
1247 See the Ghostscript manual for descriptions of environment variables
1249 used by Ghostscript, most importantly GS_FONTPATH and GS_LIB; other en‐
1250 vironment variables also affect output to display, print, and addi‐
1251 tional filtering and processing. See the related documentation.
1252 pstoedit allocates temporary files using the function tempnam(3). Thus
1254 the location for temporary files might be controllable by other envi‐
1255 ronment variables used by this function. See the tempnam(3) manpage for
1256 descriptions of environment variables used. On UNIX like system this is
1257 probably the TMPDIR variable, on DOS/WINDOWS either TMP or TEMP.
1258
1260 If you have problems with pstoedit first try whether Ghostscript suc‐
1261 cessfully displays your file. If yes, then try pstoedit -f ps infile.ps
1262 testfile.ps and check whether testfile.ps still displays correctly us‐
1263 ing Ghostscript. If this file does not look correctly then there seems
1264 to be a problem with pstoedit's PostScript frontend. If this file looks
1265 good but the output for a specific format is wrong, the problem is
1266 probably in the output format driver for the specific format. In either
1267 case send bug fixes and reports to the author.
1268 A common problem with PostScript files is that the PostScript file re‐
1270 defines one of the standard PostScript operators inconsistently. There
1271 is no effect of this if you just print the file since the original
1272 PostScript "program" uses these new operators in the new meaning and
1273 does not use the original ones anymore. However, when run under the
1274 control of pstoedit, these operators are expected to work with the
1275 original semantics.
1276 So far I've seen redefinitions for:
1278 * lt - "less-then" to mean "draw a line to"
1280 * string - "create a string object" to mean "draw a string"
1282 * length - "get the length of e.g. a string" to a "float constant"
1284 I've included work-arounds for the ones mentioned above, but some oth‐
1286 ers could show up in addition to those.
1287
1289 * Non-standard fonts (e.g. TeX bitmap fonts) are mapped to a de‐
1290 fault font which can be changed using the -df option. pstoedit
1291 chooses the size of the replacement font such that the width of
1292 the string in the original font is the same as with the replace‐
1293 ment font. This is done for each text fragment displayed. Spe‐
1294 cial character encoding support is limited in this case. If a
1295 character cannot be mapped into the target format, pstoedit dis‐
1296 plays a '#' instead. See also the -uchar option.
1297 * pstoedit supports bitmap graphics only for some output format
1299 drivers.
1300 * Some output format drivers, e.g. the Gnuplot output format
1302 driver or the 3D output format driver (rpl, lwo, rib) do not
1303 support text.
1304 * For most output format drivers pstoedit does not support clip‐
1306 ping (mainly due to limitations in the target format). You can
1307 try to use the -sclip option to simulate clipping. However, this
1308 does not work in all cases as expected.
1309 * Special note about the Java output format drivers (java1 and
1311 java2). The java output format drivers generate a java source
1312 file that needs other files in order to be compiled and usable.
1313 These other files are Java classes (one applet and support
1314 classes) that allow stepping through the individual pages of a
1315 converted PostScript document. This applet can easily be acti‐
1316 vated from a html-document. See the con‐
1317 trib/java/java1/readme_java1.txt or con‐
1318 trib/java/java2/readme_java2.htm files for more details.
1319
1321 1. Why do letters like O or B get strange if converted to tgif/xfig
1322 using the -dt option?
1323 Most output format drivers do not support composite paths with interme‐
1325 diate gaps (moveto's) and second do not support very well the (eo)fill
1326 operators of PostScript (winding rule). For such objects pstoedit
1327 breaks them into smaller objects whenever such a gap is found. This re‐
1328 sults in the "hole" being filled with black color instead of being
1329 transparent. Since version 3.11 you can try the -ssp option in combina‐
1330 tion with the xfig output format driver.
1331 2. Why does pstoedit produce ugly results from PostScript files
1333 generated by dvips?
1334 This is because TeX documents usually use bitmap fonts. Such fonts can‐
1336 not be used as native font in other format. So pstoedit replaces the
1337 TeX font with another native font. Of course, the replacement font will
1338 in most cases produce another look, especially if mathematical symbols
1339 are used. Try to use PostScript fonts instead of the bitmap fonts when
1340 generating a PostScript file from TeX or LaTeX.
1341
1343 Wolfgang Glunz, wglunz35_AT_pstoedit.net,
1344 http://de.linkedin.com/in/wolfgangglunz
1345
1347 http://www.pstoedit.net/pstoedit/
1348 At this site you also find more information about pstoedit and related
1350 programs and hints how to subscribe to a mailing list in order to get
1351 informed about new releases and bug-fixes.
1352 If you like pstoedit - please express so also at Facebook
1354 http://www.facebook.com/pstoedit.
1355
1357 * Klaus Steinberger Klaus.Steinberger_AT_physik.uni-muenchen.de
1358 wrote the initial version of this manpage.
1359 * Lar Kaufman revised the increasingly complex command syntax dia‐
1361 grams and updated the structure and content of this manpage fol‐
1362 lowing release 2.5.
1363 * David B. Rosen rosen_AT_unr.edu provided ideas and some Post‐
1365 Script code from his ps2aplot program.
1366 * Ian MacPhedran Ian_MacPhedran_AT_engr.USask.CA provided the xfig
1368 output format driver.
1369 * Carsten Hammer chammer_AT_hermes.hrz.uni-bielefeld.de provided
1371 the gnuplot output format driver and the initial DXF output for‐
1372 mat driver.
1373 * Christoph Jaeschke provided the OS/2 metafile (MET) output for‐
1375 mat driver. Thomas Hoffmann thoffman_AT_zappa.sax.de did some
1376 further updates on the OS/2 part.
1377 * Jens Weber rz47b7_AT_PostAG.DE provided the MS Windows metafile
1379 (WMF) output format driver, and a graphical user interface
1380 (GUI).
1381 * G. Edward Johnson lorax_AT_nist.gov provided the CGM Draw li‐
1383 brary used in the CGM output format driver.
1384 * Gerhard Kircher kircher_AT_edvz.tuwien.ac.at provided some bug
1386 fixes.
1387 * Bill Cheng bill.cheng_AT_acm.org provided help with the tgif
1389 format and some changes to tgif to make the output format driver
1390 easier to implement. http://bourbon.usc.edu:8001/
1391 * Reini Urban rurban_AT_sbox.tu-graz.ac.at provided input for the
1393 extended DXF output format driver.(http://autocad.xarch.at/)
1394 * Glenn M. Lewis glenn_AT_gmlewis.com provided RenderMan (RIB),
1396 Real3D (RPL), and LightWave 3D (LWO) output format drivers.
1397 (http://www.gmlewis.com/)
1398 * Piet van Oostrum piet_AT_cs.ruu.nl made several bug fixes.
1400 * Lutz Vieweg lkv_AT_mania.robin.de provided several bug fixes and
1402 suggestions for improvements.
1403 * Derek B. Noonburg derekn_AT_vw.ece.cmu.edu and Rainer Dorsch
1405 rd_AT_berlepsch.wohnheim.uni-ulm.de isolated and resolved a
1406 Linux-specific core dump problem.
1407 * Rob Warner rcw2_AT_ukc.ac.uk made pstoedit compile under RiscOS.
1409 * Patrick Gosling jpmg_AT_eng.cam.ac.uk made some suggestions re‐
1411 garding the usage of pstoedit in Ghostscript's SAFER mode.
1412 * Scott Pakin scott+ps2ed_AT_pakin.org for the Idraw output format
1414 driver and the autoconf support.
1415 * Peter Katzmann p.katzmann_AT_thiesen.com for the HPGL output
1417 format driver.
1418 * Chris Cox ccox_AT_airmail.net contributed the Tcl/Tk output for‐
1420 mat driver.
1421 * Thorsten Behrens Thorsten_Behrens_AT_public.uni-hamburg.de and
1423 Bjoern Petersen for reworking the WMF output format driver.
1424 * Leszek Piotrowicz leszek_AT_sopot.rodan.pl implemented the image
1426 support for the xfig driver and a JAVA based GUI.
1427 * Egil Kvaleberg egil_AT_kvaleberg.no contributed the pic output
1429 format driver.
1430 * Kai-Uwe Sattler kus_AT_iti.cs.uni-magdeburg.de implemented the
1432 output format driver for Kontour.
1433 * Scott Pakin, scott+ps2ed_AT_pakin.org provided the MetaPost and
1435 LaTeX2e and MS PowerPoint output format driver.
1436 * The MS PowerPoint driver uses the libzip library -
1438 http://www.nih.at/libzip. Under MS Windows, this library is
1439 linked into the provided binary statically. Thanks to the whole
1440 libzip team.
1441 * Burkhard Plaum plaum_AT_IPF.Uni-Stuttgart.de added support for
1443 complex filled paths for the xfig output format driver.
1444 * Bernhard Herzog herzog_AT_online.de contributed the output for‐
1446 mat driver for sketch ( http://www.skencil.org/ )
1447 * Rolf Niepraschk (niepraschk_AT_ptb.de) converted the HTML man
1449 page to LaTeX format. This allows generating the UNIX style and
1450 the HTML manual from this base format.
1451 * Several others sent smaller bug fixed and bug reports. Sorry if
1453 I do not mention them all here.
1454 * Gisbert W. Selke (gisbert_AT_tapirsoft.de) for the Java 2 output
1456 format driver.
1457 * Robert S. Maier (rsm_AT_math.arizona.edu) for many improvements
1459 on the libplot output format driver and for libplot itself.
1460 * The authors of pstotext (mcjones_AT_pa.dec.com and bir‐
1462 rell_AT_pa.dec.com) for giving me the permission to use their
1463 simple PostScript code for performing rotation.
1464 * Daniel Gehriger gehriger_AT_linkcad.com for his help concerning
1466 the handling of Splines in the DXF format.
1467 * Allen Barnett libemf_AT_lignumcomputing.com for his work on the
1469 libEMF which allows creating WMF/EMF files under *nix systems.
1470 * Dave dave_AT_opaque.net for providing the libming which is a
1472 multiplatform library for generating SWF files.
1473 * Masatake Yamoto for the introduction of autoconf, automake and
1475 libtool into pstoedit
1476 * Bob Friesenhahn for his help and the building of the Magick++
1478 API to ImageMagick.
1479 * But most important: Peter Deutsch ghost_AT_aladdin.com and Rus‐
1481 sell Lang gsview_AT_ghostgum.com.au for their help and answers
1482 regarding Ghostscript and gsview.
1483
1485 Trademarks mentioned are the property of their respective owners.
1486 Some code incorporated in the pstoedit package is subject to copyright
1488 or other intellectual property rights or restrictions including attri‐
1489 bution rights. See the notes in individual files.
1490 pstoedit is controlled under the Free Software Foundation GNU Public
1492 License (GPL). However, this does not apply to importps and the addi‐
1493 tional plugins.
1494 Aladdin Ghostscript is a redistributable software package with copy‐
1496 right restrictions controlled by Aladdin Software.
1497 pstoedit has no other relation to Ghostscript besides calling it in a
1499 subprocess.
1500 The authors, contributors, and distributors of pstoedit are not respon‐
1502 sible for its use for any purpose, or for the results generated
1503 thereby.
1504 Restrictions such as the foregoing may apply in other countries accord‐
1506 ing to international conventions and agreements.
1507Conversion Tools 22 November 2021 PSTOEDIT(1)