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 A COMMAND SHELL
11 pstoedit [-v -help]
12 pstoedit The following options are available: [-include filename] [-df
14 font name] [-nomaptoisolatin1] [-dis] [-pngimage filename] [-q] [-nq]
15 [-nc] [-mergelines] [-filledrecttostroke] [-mergetext] [-dt] [-adt]
16 [-ndt] [-dgbm] [-correctdefinefont] [-pti] [-pta] [-xscale number]
17 [-yscale number] [-xshift number] [-yshift number] [-centered] [-min‐
18 linewidth number] [-pagenumberformat page number format specification]
19 [-split] [-v] [-vl ] [-usebbfrominput] [-ssp] [-sfill] [-uchar charac‐
20 ter] [-nb] [-rdb] [-page page number] [-flat flatness factor] [-sclip]
21 [-ups] [-rgb] [-useagl] [-noclip] [-t2fontsast1] [-keep] [-debug‐
22 fonthandling] [-gstest] [-fakedateandversion] [-nfr] [-glyphs] [-use‐
23 oldnormalization] [-rotate angle (0-360)] [-fontmap name of font map
24 file for pstoedit] [-pagesize page format] [-help] [-bo] [-psarg argu‐
25 ment string] [-pslanguagelevel PostScript Language Level 1, 2, or 3 to
26 be used.] -f "format[:options]" [-gs either full path to the Ghost‐
27 script executable/DLL or - for Windows - just a version number (e.g.
28 10.01.0), in which case the version is used to look up the path from
29 the registry.] [-gsregbase Ghostscript base registry path] [ inputfile
30 [outputfile] ]
31 FROM PSTOEDITQTGUI
33 PstoeditQtGui provides an alternative to the command driven operation.
34 The GUI provides access to almost all options and features that are
35 supported by pstoedit. In addition it supports the conversion of mul‐
36 tiple files in one job and also provides some shortcuts to some of
37 Ghostscript's high level output devices.
38 The GUI is implemented using QT (https://www.qt.io).
40 The various options provided by pstoedit are displayed in different
42 tabs in the GUI according to their category. A link to a more detailed
43 description of each option into this manual is provided with each op‐
44 tion in the GUI.
45 Side note: None of the options are "hard coded" into the GUI. Instead
47 the meta information is retrieved from pstoedit itself. By this the
48 GUI is always up to date with respect to the options and formats pro‐
49 vided by pstoedit.
50
52 RELEASE LEVEL
53 This man-page documents release 4.00 of pstoedit.
54 USE
56 pstoedit converts PostScript and PDF files into various vector graphics
57 formats. The resulting files can be edited or imported into various
58 drawing packages. Type
59 pstoedit -help
61 for a list of supported output formats. Pstoedit comes with a large set
63 of format drivers built into in the binary. Additional drivers can be
64 installed as plugins and are available from
65 http://www.pstoedit.net/plugins/. Simply copy the plugins into the
66 same directory where the pstoedit binary is installed or - on Unix like
67 systems only - alternatively into the lib directory in parallel to the
68 bin directory where pstoedit is installed.
69 However, unless you also get a license key for the plugins, the addi‐
71 tional drivers will slightly distort the resulting graphics. See the
72 documentation that comes with the plugins for more details.
73 PRINCIPLE OF CONVERSION
75 pstoedit works by redefining some of PostScript's basic drawing opera‐
76 tors, such as stroke or show (bitmaps drawn by the image operator are
77 not supported by all output formats.) After redefining these operators,
78 the PostScript or PDF file that needs to be converted is processed by a
79 PostScript interpreter, e.g., Ghostscript (gs(1)). You normally need
80 to have a PostScript interpreter installed in order to use this pro‐
81 gram. However, you can perform some "back end only" processing of files
82 following the conventions of the pstoedit intermediate format by speci‐
83 fying the -bo option. See "Available formats and their specific op‐
84 tions" below.
85 The output that is written by the interpreter due to the redefinition
87 of the drawing operators is a kind of 'flat' PostScript file containing
88 only simple operations such as moveto, lineto, show, etc. You can view
89 this file using the -f debug option.
90 This output is read by the end-processing functions of pstoedit and
92 triggers the drawing functions in the selected output format driver
93 sometimes called also "back-end".
94 NOTES ON GHOSTSCRIPT
96 Although pstoedit was designed to allow the use of any kind of Post‐
97 Script interpreter, it has only been tested in combination with Ghost‐
98 script (https://ghostscript.com).
99 Up to version 9.55 of Ghostscript, it's PDF interpreter was implemented
101 in PostScript itself. That allowed pstoedit to handle PDF files in the
102 same way as PostScript files since the same mechanisms for intercepting
103 the drawing operations could be used.
104 However, from version 9.56 on, the PDF interpreter of Ghostscript was
106 implemented in C and hence the interceptions used by pstoedit are no
107 longer effective when processing PDF files.
108 You need to convert the PDF to PostScript at first before you can con‐
110 vert it into another format. You can use Ghostscript for that or also
111 use the gs:ps2write (-f gs:ps2write) driver from pstoedit.
112
114 GENERAL OPTIONS
115 The following options are available:
116 [-include filename]
118 This option allows specifying an additional PostScript file that
120 will be executed just before the normal input is read. This is
121 helpful for including specific page settings or for disabling
122 potentially unsafe PostScript operators, e.g., file, renamefile,
123 or deletefile.
124 [-xscale number]
126 scale by a factor in x-direction
128 [-yscale number]
130 scale by a factor in y-direction
132 [-xshift number]
134 shift image in x-direction
136 [-yshift number]
138 shift image in y-direction
140 [-centered]
142 center image before scaling or shifting
144 [-minlinewidth number]
146 minimal line width. All lines thinner than this will be drawn in
148 this line width - especially zero-width lines
149 [-pagenumberformat page number format specification]
151 format specification for page numbers in filename if -split is
153 used. The specification is used to create the page number using
154 sprintf. The specification shall not include the leading % nor
155 the trailing d. Default is empty string which results in format‐
156 ting the page number using %d. This results in page numbers like
157 1, 2, ..., 10. Sometimes you may want to have fixed length with
158 leading 0, so you might want to specify 02 which means 2 digits
159 with leading 0.
160 [-split]
162 Create a new file for each page of the input. For this the out‐
164 put filename must contain a %d which is replaced with the cur‐
165 rent page number. This option is automatically switched on for
166 output formats that do not support multiple pages within one
167 file, e.g. fig or gnuplot.
168 [-usebbfrominput]
170 If specified, pstoedit uses the BoundingBox as is (hopefully)
172 found in the input file instead of one that is calculated by its
173 own.
174 [-page page number]
176 Select a single page from a multi-page PostScript or PDF file.
178 [-rgb]
180 Since version 3.30 pstoedit uses the CMYK colors internally. The
182 -rgb option turns on the old behavior to use RGB values.
183 [-useagl]
185 use Adobe Glyph List instead of the ISO Latin-1 table (this is
187 experimental)
188 [-noclip]
190 do not use clipping (relevant only if output format supports
192 clipping at all)
193 [-rotate angle (0-360)]
195 Rotate image by angle.
197 [-pagesize page format]
199 set page size for output medium. This option sets the page size
201 for the output medium. Currently this is just used by the lib‐
202 plot output format driver, but might be used by other output
203 format drivers in future. The page size is specified in terms of
204 the usual page size names, e.g. letter or a4.
205 [-help]
207 show the help information
209 [-bo]
211 You can run backend processing only (without the PostScript in‐
213 terpreter frontend) by first running pstoedit -f dump infile
214 dumpfile and then running pstoedit -f format -bo dumpfile out‐
215 file.
216 [-psarg argument string]
218 The string given with this option is passed directly to Ghost‐
220 script when Ghostscript is called to process the PostScript file
221 for pstoedit. For example: -psarg "-r300x300". This causes the
222 resolution to be changed to 300x300 dpi. (With older versions of
223 Ghostscript, changing the resolution this way has an effect only
224 if the -dis option is given.) If you want to pass multiple op‐
225 tions to Ghostscript you can use multiple -psarg options -psarg
226 opt1 -psarg opt2 -psarg opt2. See the Ghostscript manual for
227 other possible options.
228 [-pslanguagelevel PostScript Language Level 1, 2, or 3 to be used.]
230 PostScript Language Level 1, 2, or 3 to be used. You can switch
232 Ghostscript into PostScript Level 1 only mode by -pslan‐
233 guagelevel 1. This can be useful for example if the PostScript
234 file to be converted uses some Level 2 specific custom color
235 models that are not supported by pstoedit. However, this re‐
236 quires that the PostScript program checks for the PostScript
237 level supported by the interpreter and "acts" accordingly. The
238 default language level is 3.
239 -f "format[:options]"
241 target output format recognized by pstoedit. Since other format
243 drivers can be loaded dynamically, type pstoedit -help to get a
244 full list of formats. See "Available formats and their specific
245 options" below for an explanation of the [:options] to -f for‐
246 mat. If the format option is not given, pstoedit tries to guess
247 the target format from the suffix of the output filename. How‐
248 ever, in a lot of cases, this is not a unique mapping and hence
249 pstoedit demands the -f option.
250 [-gs either full path to the Ghostscript executable/DLL or - for Win‐
252 dows - just a version number (e.g. 10.01.0), in which case the version
253 is used to look up the path from the registry.]
254 tells pstoedit which Ghostscript executable/DLL to use - over‐
256 writes the internal search heuristic
257 [-gsregbase Ghostscript base registry path]
259 registry path to use as a base path when searching Ghostscript
261 interpreter. This option provides means to specify a registry
262 key under HKLM/Software where to search for GS interpreter key,
263 version and GS_DLL / GS_LIB values. Example: "-gsregbase My‐
264 Company" means that HKLM/Software/MyCompany/GPL Ghostscript
265 would be searched instead of HKLM/Software/GPL Ghostscript.
266 TEXT AND FONT HANDLING RELATED OPTIONS
268 The following options are available:
269 [-df font name]
271 Sometimes fonts embedded in a PostScript program do not have a
273 fontname. For example, this happens in PostScript files gener‐
274 ated by dvips(1). In such a case pstoedit uses a replacement
275 font. The default for this is Courier. Another font can be spec‐
276 ified using the -df option. -df Helvetica causes all unnamed
277 fonts to be replaced by Helvetica.
278 [-nomaptoisolatin1]
280 Normally pstoedit maps all character codes to the ones defined
282 by the ISO Latin1 encoding. If you specify -nomaptoisolatin1
283 then the encoding from the input PostScript is passed unchanged
284 to the output. This may result in strange text output but on the
285 other hand may be the only way to get some fonts converted ap‐
286 propriately. Try what fits best to your concrete case.
287 [-pngimage filename]
289 for debugging purpose mainly. Write result of processing also to
291 a PNG file
292 [-dt]
294 draw text. Text is drawn as polygons. This might produce a large
296 output file. This option is automatically switched on if the se‐
297 lected output format does not support text, e.g. gnuplot(1).
298 [-adt]
300 automatic draw text. This option turns on the -dt option selec‐
302 tively for fonts that seem to be no normal text fonts, e.g. Sym‐
303 bol.
304 [-ndt]
306 never draw text. Fully disable the heuristics used by pstoedit
308 to decide when to "draw" text instead of showing it as text.
309 This may produce incorrect results, but in some cases it might
310 nevertheless be useful. "Use at own risk".
311 [-dgbm]
313 experimental - draw also bitmaps generated by fonts/glyphs
315 [-correctdefinefont]
317 Some PostScript files, e.g. such as generated by ChemDraw, use
319 the PostScript definefont operator in a way that is incompatible
320 with pstoedit's assumptions. The new font is defined by copying
321 an old font without changing the FontName of the new font. When
322 this option is applied, some "patches" are done after a define‐
323 font in order to make it again compatible with pstoedit's as‐
324 sumptions. This option is not enabled by default, since it may
325 break other PostScript files. It is tested only with ChemDraw
326 generated files.
327 [-pti]
329 precision text. Normally a text string is drawn as it occurs in
331 the input file. However, in some situations, this might produce
332 wrongly positioned characters. This is due to limitations in
333 most output formats of pstoedit. They cannot represent text with
334 arbitrary inter-letter spacing which is easily possible in PDF
335 and PostScript. With -pta, each character of a text string is
336 placed separately. With -pti, this is done only in cases when
337 there is a non zero inter-letter spacing. The downside of "pre‐
338 cision text" is a bigger file size and hard to edit text.
339 [-pta]
341 see -pti
343 [-uchar character]
345 Sometimes pstoedit cannot map a character from the encoding used
347 by the PostScript file to the font encoding of the target for‐
348 mat. In this case pstoedit replaces the input character by a
349 special character in order to show all the places that could not
350 be mapped correctly. The default for this is a "#". Using the
351 -uchar option it is possible to specify another character to be
352 used instead. If you want to use a space, use -uchar " ".
353 [-t2fontsast1]
355 Handle Type 2 fonts same as Type 1. Type 2 fonts sometimes occur
357 as embedded fonts within PDF files. In the default mode, text
358 using such fonts is drawn as polygons since pstoedit assumes
359 that such a font is not available on the user's machine. If this
360 option is set, pstoedit assumes that the internal encoding fol‐
361 lows the same as for a standard font and generates normal text
362 output. This assumption may not be true in all cases. But it is
363 nearly impossible for pstoedit to verify this assumption - it
364 would have to do a sort of OCR.
365 [-nfr]
367 In normal mode pstoedit replaces bitmap fonts with a font as de‐
369 fined by the -df option. This is done, because most output for‐
370 mats cannot handle such fonts. This behavior can be switched off
371 using the -nfr option but then it strongly depends on the appli‐
372 cation reading the generated file whether the file is usable and
373 correctly interpreted or not. Any problems are then out of con‐
374 trol of pstoedit.
375 [-glyphs]
377 pass glyph names to the output format driver. So far no output
379 format driver really uses the glyph names, so this does not have
380 any effect at the moment. It is a preparation for future work.
381 [-useoldnormalization]
383 Just use this option in case the new heuristic introduced in 3.5
385 does not produce correct results - however, this normalization
386 of font encoding will always be a best-effort approach since
387 there is no real general solution to it with reasonable effort
388 [-fontmap name of font map file for pstoedit]
390 The font map is a simple text file containing lines in the fol‐
392 lowing format:
393 document_font_name target_font_name
395 Lines beginning with % are considered comments.
396 For font names with spaces use the "font name with spaces" notation.
397 If a target_font_name starts with /, it is regarded as alias to a for‐
399 mer entry.
400 Each font name found in the document is checked against this mapping
402 and if there is a corresponding entry, the new name is used for the
403 output.
404 If the -fontmap option is not specified, pstoedit automatically looks
406 for the file drivername.fmp in the installation directory and uses that
407 file as a default fontmap file if available. The installation directory
408 is:
409 * MS Windows: The same directory where the pstoedit exe‐
411 cutable is located
412 * Unix:
414 The default installation directory. If it fails, then
415 <The directory where the pstoedit executable is located>
416 /../lib/
417 The mpost.fmp in the misc directory of the pstoedit distribution
419 is a sample map file with mappings from over 5000 PostScript
420 font names to their TeX equivalents. This is useful because
421 MetaPost is frequently used with TeX/LaTeX and those programs do
422 not use standard font names. This file and the MetaPost output
423 format driver are provided by Scott Pakin
424 (scott+ps2ed_AT_pakin.org). Another example is wemf.fmp to be
425 used under Windows. See the misc directory of the pstoedit
426 source distribution. After loading the implicit (based on
427 driver name) or explicit (based on the -fontmap option) font map
428 file, a system specific map file is searched and loaded from the
429 installation directory (unix.fmp or windows.fmp). This file can
430 be used to redirect certain fonts to system specific names using
431 the /AliasName notation described above.
432 DRAWING RELATED OPTIONS
434 The following options are available:
435 [-nc]
437 no curves. Normally pstoedit tries to keep curves from the in‐
439 put and transfers them to the output if the output format sup‐
440 ports curves. If the output format does not support curves, then
441 pstoedit replaces curves by a series of lines (see also -flat
442 option). However, in some cases the user might wish to have this
443 behavior also for output formats that originally support curves.
444 This can be forced via the -nc option.
445 [-mergelines]
447 Some output formats permit the representation of filled polygons
449 with edges that are in a different color than the fill color.
450 Since PostScript does not support this by the standard drawing
451 primitives directly, drawing programs typically generate two ob‐
452 jects (the outline and the filled polygon) into the PostScript
453 output. pstoedit is able to recombine these, if they follow each
454 other directly and you specify -mergelines. However, this merg‐
455 ing is not supported by all output formats due to restrictions
456 in the target format.
457 [-filledrecttostroke]
459 Rectangles filled with a solid color can be converted to a
461 stroked line with a width that corresponds to the width of the
462 rectangle. This is of primary interest for output formats which
463 do not support filled polygons at all. But it is restricted to
464 rectangles only, i.e. it is not supported for general polygons
465 [-mergetext]
467 In order to produce nice looking text output, programs producing
469 PostScript files often split words into smaller pieces which are
470 then placed individually on adjacent positions. However, such
471 split text is hard to edit later on and hence it is sometime
472 better to recombine these pieces again to form a word (or even
473 sequence of words). For this pstoedit implements some heuristics
474 about what text pieces are to be considered parts of a split
475 word. This is based on the geometrical proximity of the differ‐
476 ent parts and seems to work quite well so far. But there are
477 certainly cases where this simple heuristic fails. So please
478 check the results carefully.
479 [-ssp]
481 simulate subpaths. Several output formats do not support Post‐
483 Script paths containing subpaths, i.e. paths with intermediate
484 movetos. In the normal case, each subpath is treated as an inde‐
485 pendent path for such output formats. This can lead to bad look‐
486 ing results. The most common case where this happens is if you
487 use the -dt option and show some text with letters like e, o, or
488 b, i.e. letters that have a "hole". When the -ssp option is set,
489 pstoedit tries to eliminate these problems. However, this option
490 is CPU time intensive!
491 [-sfill]
493 simulate filling by individual strokes.
495 [-flat flatness factor]
497 If the output format does not support curves in the way Post‐
499 Script does or if the -nc option is specified, all curves are
500 approximated by lines. Using the -flat option one can control
501 this approximation. This parameter is directly converted to a
502 PostScript setflat command. Higher numbers, e.g. 10 give
503 rougher, lower numbers, e.g. 0.1, give finer approximations.
504 [-sclip]
506 simulate clipping. Most output formats of pstoedit do not have
508 native support for clipping. For that pstoedit offers an option
509 to perform the clipping of the graphics directly without passing
510 the clippath to the output driver. However, this results in
511 curves being replaced by a lot of line segments and thus larger
512 output files. So use this option only if your output looks dif‐
513 ferent from the input due to clipping. In addition, this "simu‐
514 lated clipping" is not exactly the same as defined in Post‐
515 Script. There might be lines drawn at double size. Also clipping
516 of text is not supported unless you also use the -dt option.
517 DIAGNOSTIC AND DEBUG OPTIONS
519 The following options are available:
520 [-dis]
522 Open a display during processing by Ghostscript. Some files only
524 work correctly this way.
525 [-q]
527 quiet mode - do not write startup message
529 [-nq]
531 no exit from the PostScript interpreter. Normally Ghostscript
533 exits after processing the pstoedit input-file. For debugging it
534 can be useful to avoid this. If you do, you will have to type
535 quit at the GS> prompt to exit from Ghostscript.
536 [-v]
538 Switch on verbose mode. Some additional information is shown
540 during processing.
541 [-vl ]
543 Switch on verbose mode with a given level. Some additional in‐
545 formation is shown during processing.
546 [-nb]
548 Since version 3.10 pstoedit uses the -dDELAYBIND option when
550 calling Ghostscript. Previously the -dNOBIND option was used in‐
551 stead but that sometimes caused problems if a user's PostScript
552 file overloaded standard PostScript operator with totally new
553 semantic, e.g. lt for lineto instead of the standard meaning of
554 "less than". Using -nb the old style can be activated again in
555 case the -dDELAYBIND gives different results as before. In such
556 a case please also contact the author.
557 [-rdb]
559 Since version 3.10 pstoedit uses the -dDELAYBIND option when
561 calling Ghostscript. But in version 9.22 of Ghostscript, that
562 option is not supported anymore because of security reasons. As
563 a fallback, that version provides the REALLYDELAYBIND option and
564 pstoedit can use this if you supply the -rdb option. Use this
565 with caution as it might open security risks, e.g. a PostScript
566 file injecting some malicious code into PostScript standard op‐
567 erators. However, not using this option can cause some of the
568 PostScript drawings operations to be not seen by pstoedit, hence
569 causing missing artefacts in the output. Later versions of
570 Ghostscript will probably support -dDELAYBIND again. But also in
571 that case the security risk remains. So be careful with what
572 files you process with pstoedit and Ghostscript.
573 [-ups]
575 write text as plain string instead of hex string in intermediate
577 format - normally useful for trouble shooting and debugging
578 only.
579 [-keep]
581 keep the intermediate files produced by pstoedit - for debug
583 purposes only
584 [-debugfonthandling]
586 writes verbose messages related to internal font processing -
588 for debug purposes only
589 [-gstest]
591 perform a basic test of the interworking with Ghostscript
593 [-fakedateandversion]
595 Just for regression testing - uses a constant date and version
597 string.
598 INPUT AND OUTFILE FILE ARGUMENTS
600 [ inputfile [outputfile] ]
601 If neither an input nor an output file is given as argument, pstoedit
603 works as filter reading from standard input and writing to standard
604 output. The special filename "-" can also be used. It represents stan‐
605 dard input if it is the first on the command line and standard output
606 if it is the second. So "pstoedit - output.xxx" reads from standard in‐
607 put and writes to output.xxx
608
610 pstoedit allows passing individual options to an output format driver.
611 This is done by appending all options to the format specified after the
612 -f option. The format specifier and its options must be separated by a
613 colon (:). If more than one option needs to be passed to the output
614 format driver, the whole argument to -f must be enclosed within dou‐
615 ble-quote characters, thus:
616 -f "format[:option option ...]"
618 To see which options are supported by a specific format, type: pstoedit
620 -f format:-help
621 The following description of the different formats supported by
623 pstoedit is extracted from the source code of the individual drivers.
624 FORMAT GROUP: PSF PS DEBUG DUMP PS2AI GS
626 This group consists of the following variants:
627 psf: Flattened PostScript (no curves).
629 ps: Simplified PostScript with curves.
631 debug: for test purposes.
633 dump: for test purposes (same as debug).
635 ps2ai: Adobe Illustrator via ps2ai.ps of Ghostscript.
637 gs: any device that Ghostscript provides - use gs:format, e.g.
639 gs:pdfwrite.
640 No format specific options
642 FORMAT GROUP: GMFA GMFB PLOT PLOT-PNM PLOT-CGM PLOT-AI PLOT-SVG PLOT-PS
644 PLOT-FIG PLOT-PCL PLOT-HPGL PLOT-TEK
645 This group consists of the following variants:
646 gmfa: ASCII GNU metafile.
648 gmfb: binary GNU metafile.
650 plot: GNU libplot output types, e.g. plot:-plotformat X.
652 plot-pnm:
654 pnm via GNU libplot.
655 plot-cgm:
657 cgm via GNU libplot.
658 plot-ai:
660 ai via GNU libplot.
661 plot-svg:
663 svg via GNU libplot.
664 plot-ps:
666 ps via GNU libplot.
667 plot-fig:
669 fig via GNU libplot.
670 plot-pcl:
672 pcl via GNU libplot.
673 plot-hpgl:
675 hpgl via GNU libplot.
676 plot-tek:
678 tek via GNU libplot.
679 The following driver specific options are available in this group:
681 [-plotformat string]
683 plotutil format to generate
685 PPTX - PRESENTATIONML (POWERPOINT) FORMAT
687 This is the format used internally by Microsoft PowerPoint. LibreOffice
688 can also read/write PowerPoint files albeit with some lack of function‐
689 ality.
690 The following driver specific options are available:
692 [-colors string]
694 "original" to retain original colors (default), "theme" to con‐
696 vert randomly to theme colors, or "theme-lum" also to vary lumi‐
697 nance
698 [-fonts string]
700 use "windows" fonts (default), "native" fonts, or convert to the
702 "theme" font
703 [-embed string]
705 embed fonts, specified as a comma-separated list of EOT-format
707 font files
708 GCODE - EMC2 GCODE FORMAT
710 See also: http://linuxcnc.org/
711 No format specific options
713 CAIRO - CAIRO DRIVER
715 generates compilable c code for rendering with cairo
716 The following driver specific options are available:
718 [-pango]
720 use pango for font rendering
722 [-funcname string]
724 sets the base name for the generated functions and variables.
726 e.g. myfig
727 [-header string]
729 sets the output file name for the generated C header file. e.g.
731 myfig.h
732 LWO - LIGHTWAVE 3D OBJECT FORMAT
734 No format specific options
735 RIB - RENDERMAN INTERFACE BYTESTREAM
737 No format specific options
738 RPL - REAL3D PROGRAMMING LANGUAGE FORMAT
740 No format specific options
741 FORMAT GROUP: DXF DXF_14 DXF_S
743 This group consists of the following variants:
744 dxf: CAD exchange format version 9 - only limited features. Consider
746 using dxf_14 instead..
747 dxf_14:
749 CAD exchange format version 14 supporting splines and linetypes.
750 dxf_s: CAD exchange format version 14 supporting splines and linetypes.
752 The following driver specific options are available in this group:
754 [-polyaslines]
756 use LINE instead of POLYLINE in DXF
758 [-mm]
760 use mm coordinates instead of points in DXF (mm=pt/72*25.4)
762 [-ctl]
764 map colors to layers
766 [-filltohatch]
768 generate hatch objects from fill operations (still experimental)
770 [-splineaspolyline]
772 approximate splines with PolyLines (only for -f dxf_s)
774 [-splineasnurb]
776 experimental (only for -f dxf_s)
778 [-splineasbspline]
780 experimental (only for -f dxf_s)
782 [-splineassinglespline]
784 experimental (only for -f dxf_s)
786 [-splineasmultispline]
788 experimental (only for -f dxf_s)
790 [-splineasbezier]
792 use Bezier splines in DXF format (only for -f dxf_s)
794 [-splineprecision number]
796 number of samples to take from spline curve when doing approxi‐
798 mation with -splineaspolyline or -splineasmultispline - should
799 be =2 (default 5)
800 [-dumplayernames]
802 dump all layer names found to standard output
804 [-layers string]
806 layers to be shown (comma separated list of layer names, no
808 space)
809 [-layerfilter string]
811 layers to be hidden (comma separated list of layer names, no
813 space)
814 JAVA1 - JAVA 1.PPLET SOURCE CODE
816 The following driver specific options are available:
817 [java_class_name string]
819 name of java class to generate
821 JAVA2 - JAVA 2 SOURCE CODE
823 The following driver specific options are available:
824 [java_class_name string]
826 name of java class to generate
828 PDF - ADOBE'S PORTABLE DOCUMENT FORMAT
830 No format specific options
831 KIL - .KIL FORMAT FOR KONTOUR
833 No format specific options
834 TEXT - TEXT IN DIFFERENT FORMS
836 The following driver specific options are available:
837 [-height number]
839 page height in terms of characters
841 [-width number]
843 page width in terms of characters
845 [-dump]
847 dump text pieces
849 SK - SKETCH FORMAT
851 No format specific options
852 MPOST - METAPOST FORMAT
854 No format specific options
855 ASY - ASYMPTOTE FORMAT
857 No format specific options
858 MMA - MATHEMATICA GRAPHICS
860 The following driver specific options are available:
861 [-eofillfills]
863 Filling is used for eofill (default is not to fill)
865 LATEX2E - LaTeX2E PICTURE FORMAT
867 The following driver specific options are available:
868 [-integers]
870 round all coordinates to the nearest integer
872 NOIXML - NEMETSCHEK NOI XML FORMAT
874 Nemetschek Object Interface XML format
875 The following driver specific options are available:
877 [-r string]
879 Allplan resource file
881 [-bsl number]
883 Bezier Split Level (default 3)
885 PIC - PIC FORMAT FOR TROFF ET.AL.
887 The following driver specific options are available:
888 [-troff]
890 troff mode (default is groff)
892 [-landscape]
894 landscape output
896 [-portrait]
898 portrait output
900 [-keepfont]
902 print unrecognized literally
904 [-text]
906 try not to make pictures from running text
908 [-debug]
910 enable debug output
912 FORMAT GROUP: HPGL PCL
914 This group consists of the following variants:
915 hpgl: HPGL code.
917 pcl: PCL code.
919 The following driver specific options are available in this group:
921 [-penplotter]
923 plotter is pen plotter (i.e. no support for specific line
925 widths)
926 [-pencolorsfromfile]
928 read pen colors from file drvhpgl.pencolors in pstoedit's data
930 directory
931 [-pencolors number]
933 maximum number of pen colors to be used by pstoedit (default 0)
935 -
936 [-filltype string]
938 select fill type e.g. FT 1
940 [-hpgl2]
942 Use HPGL/2 instead of HPGL/1
944 [-rot90]
946 rotate hpgl by 90 degrees
948 [-rot180]
950 rotate hpgl by 180 degrees
952 [-rot270]
954 rotate hpgl by 270 degrees
956 PCBI - ENGRAVE DATA - INSULATE/PCB FORMAT
958 No format specific options
959 PCB - PCB FORMAT
961 See also: http://pcb.sourceforge.net and http://www.pen‐
962 guin.cz/~utx/pstoedit-pcb/
963 The following driver specific options are available:
965 [-grid double number]
967 attempt to snap relevant output to grid (mils) and put failed
969 objects to a different layer
970 [-snapdist double number]
972 grid snap distance ratio (0 < snapdist <= 0.5, default 0.1)
974 [-tshiftx double number]
976 additional x shift measured in target units (mils)
978 [-tshifty double number]
980 additional y shift measured in target units (mils)
982 [-mm]
984 switch to metric units (mm)
986 [-stdnames]
988 use standard layer names instead of descriptive names
990 [-forcepoly]
992 force all objects to be interpreted as polygons
994 PCBFILL - PCB FORMAT WITH FILLS
996 See also: http://pcb.sourceforge.net
997 No format specific options
999 PCB-RND - PCB-RND FORMAT
1001 See also: http://repo.hu/projects/pcb-rnd and http://www.pen‐
1002 guin.cz/~utx/pstoedit-pcb/
1003 The following driver specific options are available:
1005 [-grid double number]
1007 attempt to snap relevant output to grid (mils) and put failed
1009 objects to a different layer
1010 [-snapdist double number]
1012 grid snap distance ratio (0 < snapdist <= 0.5, default 0.1)
1014 [-tshiftx double number]
1016 additional x shift measured in target units (mils)
1018 [-tshifty double number]
1020 additional y shift measured in target units (mils)
1022 [-mm]
1024 switch to metric units (mm)
1026 [-forcepoly]
1028 force all objects to be interpreted as polygons
1030 GSCHEM - GSCHEM FORMAT
1032 See also: http://wiki.geda-project.org/geda:gaf
1033 No format specific options
1035 CFDG - CONTEXT FREE DESIGN GRAMMAR
1037 Context Free Design Grammar, usable by Context Free Art
1038 (http://www.contextfreeart.org/)
1039 No format specific options
1041 TK - TK AND/OR TK.PPLET SOURCE CODE
1043 The following driver specific options are available:
1044 [-R]
1046 swap HW
1048 [-I]
1050 no impress
1052 [-n string]
1054 tagnames
1056 VTK - VTK DRIVER: IF YOU DO NOT WANT TO SEE THIS, UNCOMMENT THE CORRESPOND‐
1058 ING LINE IN MAKEFILE AND MAKE AGAIN
1059 this is a long description for the VTKe driver
1060 The following driver specific options are available:
1062 [-VTKeoption integer]
1064 just an example
1066 SVM - STARVIEW/OPENOFFICE.ORG METAFILE
1068 StarView/OpenOffice.org metafile, readable from OpenOffice.org
1069 1.0/StarOffice 6.0 and above.
1070 The following driver specific options are available:
1072 [-m]
1074 map to Arial
1076 [-nf]
1078 emulate narrow fonts
1080 GNUPLOT - GNUPLOT FORMAT
1082 No format specific options
1083 TGIF - TGIF .OBJ FORMAT
1085 The following driver specific options are available:
1086 [-ta]
1088 text as attribute
1090 FORMAT GROUP: FIG XFIG TFIG
1092 This group consists of the following variants:
1093 fig: .fig format for xfig.
1095 xfig: .fig format for xfig.
1097 tfig: .fig format for xfig - test only version.
1099 The xfig format driver supports special fontnames, which may be pro‐
1101 duced by using a fontmap file. The following types of names are sup‐
1102 ported:
1103 General notation:
1104 "PostScript Font Name" ((LaTeX|PostScript|empty)(::special)::)XFigFontName
1105 Examples:
1107 Helvetica LaTeX::SansSerif
1109 Courier LaTeX::special::Typewriter
1110 GillSans "AvantGarde Demi"
1111 Albertus PostScript::special::"New Century Schoolbook Italic"
1112 Symbol ::special::Symbol (same as PostScript::special::Symbol)
1113 See also the file examplefigmap.fmp in the misc directory of the
1115 pstoedit source distribution for an example font map file for xfig.
1116 Please note that the fontname has to be among those supported by xfig.
1117 See - https://mcj.sourceforge.net/fig-format.html for a list of legal
1118 font names
1119 The following driver specific options are available in this group:
1121 [-startdepth number]
1123 set the initial depth (default 999)
1125 [-metric]
1127 switch to centimeter display (default inches)
1129 [-usecorrectfontsize]
1131 do not scale fonts for xfig. Use this if you also use this op‐
1133 tion with xfig
1134 [-depth number]
1136 set the page depth in inches (default 11)
1138 IDRAW - INTERVIEWS DRAW FORMAT (EPS)
1140 No format specific options
1141 SAMPLE - SAMPLE DRIVER: IF YOU DO NOT WANT TO SEE THIS, UNCOMMENT THE COR‐
1143 RESPONDING LINE IN MAKEFILE AND MAKE AGAIN
1144 This is a long description for the sample driver
1145 The following driver specific options are available:
1147 [-sampleoption integer]
1149 just an example
1151 EMF - ENHANCED MS WINDOWS METAFILE
1153 The following driver specific options are available:
1154 [-m]
1156 map to Arial
1158 [-nf]
1160 emulate narrow fonts
1162 [-drawbb]
1164 draw bounding box
1166 [-p]
1168 prune line ends
1170 [-nfw]
1172 Newer versions of MS Windows (2000, XP, Vista, 7, ...) will not
1174 accept WMF/EMF files generated when this option is set and the
1175 input contains text. But if this option is not set, then the
1176 WMF/EMF driver will estimate interletter spacing of text using a
1177 very coarse heuristic. This may result in ugly looking output.
1178 On the other hand, OpenOffice can still read EMF/WMF files where
1179 pstoedit delegates the calculation of the inter letter spacing
1180 to the program reading the WMF/EMF file. So if the generated
1181 WMF/EMF file shall never be processed under MS Windows, use this
1182 option. If WMF/EMF files with high precision text need to be
1183 generated under *nix the only option is to use the -pta option
1184 of pstoedit. However that causes every text to be split into
1185 single characters which makes the text hard to edit afterwards.
1186 Hence the -nfw option provides a sort of compromise between
1187 portability and nice to edit but still nice looking text. Again
1188 - this option has no meaning when pstoedit is executed under MS
1189 Windows anyway. In that case the output is portable but never‐
1190 theless not split and still looks fine.
1191 [-winbb]
1193 let the MS Windows API calculate the Bounding Box (MS Windows
1195 only)
1196 [-OO]
1198 generate OpenOffice compatible EMF file
1200
1202 AUTOTRACE
1203 pstoedit cooperates with autotrace. Autotrace can now produce a dump
1204 file for further processing by pstoedit using the -bo (back-end only)
1205 option. Autotrace is a program written by a group around Martin Weber
1206 and can be found at https://sourceforge.net/projects/autotrace/.
1207 PS2AI
1209 The ps2ai output format driver is not a native pstoedit output format
1210 driver. It does not use the pstoedit PostScript flattener, instead it
1211 uses the PostScript program ps2ai.ps which is installed in the Ghost‐
1212 script distribution directory. It is included to provide the same
1213 "look-and-feel" for the conversion to AI. However, lot's of files do
1214 not convert nicely or at all using ps2ai.ps. So a native pstoedit
1215 driver would be much better. Anyone out there to take this? The AI for‐
1216 mat is usable for example by Mayura Draw (http://www.mayura.com). Also
1217 a driver to the Mayura native format would be nice.
1218 An alternative to the ps2ai based driver is available via the -f
1220 plot:ai format if the libplot(ter) is installed.
1221 You should use a version of Ghostscript greater than or equal to 6.00
1223 for using the ps2ai output format driver.
1224 METAPOST
1226 Note that, as far as Scott knows, MetaPost does not support Post‐
1227 Script's eofill. The MetaPost output format driver just converts eofill
1228 to fill, and issues a warning if verbose is set. Fortunately, very few
1229 PostScript programs rely on the even-odd fill rule, even though many
1230 specify it.
1231 For more on MetaPost see:
1233 http://tug.org/metapost
1235 CONTEXT FREE - CFDG
1237 The driver for the CFDG format (drvcfdg) defines one shape per page of
1238 PostScript, but only the first shape is actually rendered (unless the
1239 user edits the generated CFDG code, of course). CFDG does not support
1240 multi-page output, so this probably is a reasonable thing to do.
1241 For more on Context Free see: http://www.contextfreeart.org/
1243 LaTeX2E
1245 * LaTeX2e's picture environment is not very powerful. As a result,
1246 many elementary PostScript constructs are ignored -- fills, line
1247 thicknesses (besides "thick" and "thin"), and dash patterns, to
1248 name a few. Furthermore, complex pictures may overrun TeX's mem‐
1249 ory capacity. (The eepic package overcomes many such restric‐
1250 tions.)
1251 * Some PostScript constructs are not supported directly by "pic‐
1253 ture", but can be handled by external packages. If a figure uses
1254 color, the top-level document will need to do a "\usepack‐
1255 age{color}" or "\usepackage{xcolor}". And if a figure contains
1256 rotated text, the top-level document will need to do a "\usepa‐
1257 ckage{rotating}".
1258 * All lengths, coordinates, and font sizes output by the output
1260 format driver are in terms of \unitlength, so scaling a figure
1261 is simply a matter of doing a "\setlength{\unitlength}{...}".
1262 * The output format driver currently supports one output format
1264 driver specific option, "integers", which rounds all lengths,
1265 coordinates, and font sizes to the nearest integer. This makes
1266 hand-editing the picture a little nicer.
1267 * Why is this output format driver useful? One answer is porta‐
1269 bility; any LaTeX2e system can handle the picture environment,
1270 even if it cannot handle PostScript graphics. (pdfLaTeX comes to
1271 mind here.) A second answer is that pictures can be edited eas‐
1272 ily to contain any arbitrary LaTeX2e code. For instance, the
1273 text in a figure can be modified to contain complex mathematics,
1274 non-Latin alphabets, bibliographic citations, or -- the real
1275 reason Scott wrote the LaTeX2e output format driver -- hyper‐
1276 links to the surrounding document (with help from the hyperref
1277 package).
1278 CREATING A NEW OUTPUT FORMAT DRIVER
1280 To implement a new output format driver you can start from drvsampl.cpp
1281 and drvsampl.h. See also comments in drvbase.h and drvfuncs.h for an
1282 explanation of methods that should be implemented for a new output for‐
1283 mat driver.
1284
1286 A default PostScript interpreter to be called by pstoedit is specified
1287 at compile time. You can overwrite the default by setting the GS envi‐
1288 ronment variable to the name of a suitable PostScript interpreter.
1289 You can check which name of a PostScript interpreter was compiled into
1291 pstoedit using: pstoedit -help -v.
1292 See the Ghostscript manual for descriptions of environment variables
1294 used by Ghostscript, most importantly GS_FONTPATH and GS_LIB; other en‐
1295 vironment variables also affect output to display, print, and addi‐
1296 tional filtering and processing. See the related documentation.
1297 pstoedit allocates temporary files using the function tempnam(3). Thus
1299 the location for temporary files might be controllable by other envi‐
1300 ronment variables used by this function. See the tempnam(3) man-page
1301 for descriptions of environment variables used. On UNIX like system
1302 this is probably the TMPDIR variable, on DOS/WINDOWS either TMP or
1303 TEMP.
1304
1306 If you have problems with pstoedit first try whether Ghostscript suc‐
1307 cessfully displays your file. If yes, then try pstoedit -f ps infile.ps
1308 testfile.ps and check whether testfile.ps still displays correctly us‐
1309 ing Ghostscript. If this file does not look correctly then there seems
1310 to be a problem with pstoedit's PostScript front-end. If this file
1311 looks good but the output for a specific format is wrong, the problem
1312 is probably in the output format driver for the specific format. In ei‐
1313 ther case send bug fixes and reports to the author.
1314 A common problem with PostScript files is that the PostScript file re‐
1316 defines one of the standard PostScript operators inconsistently. There
1317 is no effect of this if you just print the file since the original
1318 PostScript "program" uses these new operators in the new meaning and
1319 does not use the original ones anymore. However, when run under the
1320 control of pstoedit, these operators are expected to work with the
1321 original semantics.
1322 So far I've seen redefinitions for:
1324 * lt - "less-then" to mean "draw a line to"
1326 * string - "create a string object" to mean "draw a string"
1328 * length - "get the length of e.g. a string" to a "float constant"
1330 I've included work-arounds for the ones mentioned above, but some oth‐
1332 ers could show up in addition to those.
1333
1335 * Non-standard fonts (e.g. TeX bitmap fonts) are mapped to a de‐
1336 fault font which can be changed using the -df option. pstoedit
1337 chooses the size of the replacement font such that the width of
1338 the string in the original font is the same as with the replace‐
1339 ment font. This is done for each text fragment displayed. Spe‐
1340 cial character encoding support is limited in this case. If a
1341 character cannot be mapped into the target format, pstoedit dis‐
1342 plays a '#' instead. See also the -uchar option.
1343 * pstoedit supports bitmap graphics only for some output format
1345 drivers.
1346 * Some output format drivers, e.g. the Gnuplot output format
1348 driver or the 3D output format driver (rpl, lwo, rib) do not
1349 support text.
1350 * For most output format drivers pstoedit does not support clip‐
1352 ping (mainly due to limitations in the target format). You can
1353 try to use the -sclip option to simulate clipping. However, this
1354 does not work in all cases as expected.
1355 * Special note about the Java output format drivers (java1 and
1357 java2). The java output format drivers generate a java source
1358 file that needs other files in order to be compiled and usable.
1359 These other files are Java classes (one applet and support
1360 classes) that allow stepping through the individual pages of a
1361 converted PostScript document. This applet can easily be acti‐
1362 vated from a HTML-document. See the con‐
1363 trib/java/java1/readme_java1.txt or con‐
1364 trib/java/java2/readme_java2.htm files for more details.
1365
1367 1. Why do letters like O or B get strange if converted to TGIF/XFIG
1368 using the -dt option?
1369 Most output format drivers do not support composite paths with interme‐
1371 diate gaps (moveto's) and second do not support very well the (eo)fill
1372 operators of PostScript (winding rule). For such objects pstoedit
1373 breaks them into smaller objects whenever such a gap is found. This re‐
1374 sults in the "hole" being filled with black color instead of being
1375 transparent. Since version 3.11 you can try the -ssp option in combina‐
1376 tion with the XFIG output format driver.
1377 2. Why does pstoedit produce ugly results from PostScript files
1379 generated by dvips?
1380 This is because TeX documents usually use bitmap fonts. Such fonts can‐
1382 not be used as native font in other format. So pstoedit replaces the
1383 TeX font with another native font. Of course, the replacement font will
1384 in most cases produce another look, especially if mathematical symbols
1385 are used. Try to use PostScript fonts instead of the bitmap fonts when
1386 generating a PostScript file from TeX or LaTeX.
1387
1389 Wolfgang Glunz, wglunz35_AT_pstoedit.net,
1390 https://de.linkedin.com/in/wolfgangglunz
1391
1393 http://www.pstoedit.net/pstoedit/
1394 At this site you also find more information about pstoedit and related
1396 programs and hints how to subscribe to a mailing list in order to get
1397 informed about new releases and bug-fixes.
1398 If you like pstoedit - please express so also at Facebook
1400 https://www.facebook.com/pstoedit.
1401
1403 * Klaus Steinberger Klaus.Steinberger_AT_physik.uni-muenchen.de
1404 wrote the initial version of this man-page.
1405 * Lar Kaufman revised the increasingly complex command syntax dia‐
1407 grams and updated the structure and content of this man-page
1408 following release 2.5.
1409 * David B. Rosen rosen_AT_unr.edu provided ideas and some Post‐
1411 Script code from his ps2aplot program.
1412 * Ian MacPhedran Ian_MacPhedran_AT_engr.USask.CA provided the XFIG
1414 output format driver.
1415 * Carsten Hammer chammer_AT_hermes.hrz.uni-bielefeld.de provided
1417 the Gnuplot output format driver and the initial DXF output for‐
1418 mat driver.
1419 * Christoph Jaeschke provided the OS/2 metafile (MET) output for‐
1421 mat driver. Thomas Hoffmann thoffman_AT_zappa.sax.de did some
1422 further updates on the OS/2 part.
1423 * Jens Weber rz47b7_AT_PostAG.DE provided the MS Windows metafile
1425 (WMF) output format driver, and a graphical user interface
1426 (GUI).
1427 * G. Edward Johnson lorax_AT_nist.gov provided the CGM Draw li‐
1429 brary used in the CGM output format driver.
1430 * Gerhard Kircher kircher_AT_edvz.tuwien.ac.at provided some bug
1432 fixes.
1433 * Bill Cheng bill.cheng_AT_acm.org provided help with the TGIF
1435 format and some changes to TGIF to make the output format driver
1436 easier to implement.
1437 * Reini Urban rurban_AT_sbox.tu-graz.ac.at provided input for the
1439 extended DXF output format driver.
1440 * Glenn M. Lewis glenn_AT_gmlewis.com provided RenderMan (RIB),
1442 Real3D (RPL), and LightWave 3D (LWO) output format drivers.
1443 * Piet van Oostrum piet_AT_cs.ruu.nl made several bug fixes.
1445 * Lutz Vieweg lkv_AT_mania.robin.de provided several bug fixes and
1447 suggestions for improvements.
1448 * Derek B. Noonburg derekn_AT_vw.ece.cmu.edu and Rainer Dorsch
1450 rd_AT_berlepsch.wohnheim.uni-ulm.de isolated and resolved a
1451 Linux-specific core dump problem.
1452 * Rob Warner rcw2_AT_ukc.ac.uk made pstoedit compile under RiscOS.
1454 * Patrick Gosling jpmg_AT_eng.cam.ac.uk made some suggestions re‐
1456 garding the usage of pstoedit in Ghostscript's SAFER mode.
1457 * Scott Pakin scott+ps2ed_AT_pakin.org for the Idraw output format
1459 driver and the autoconf support.
1460 * Peter Katzmann p.katzmann_AT_thiesen.com for the HPGL output
1462 format driver.
1463 * Chris Cox ccox_AT_airmail.net contributed the Tcl/Tk output for‐
1465 mat driver.
1466 * Thorsten Behrens Thorsten_Behrens_AT_public.uni-hamburg.de and
1468 Bjoern Petersen for reworking the WMF output format driver.
1469 * Leszek Piotrowicz leszek_AT_sopot.rodan.pl implemented the image
1471 support for the XFIG driver and a JAVA based GUI.
1472 * Egil Kvaleberg egil_AT_kvaleberg.no contributed the pic output
1474 format driver.
1475 * Kai-Uwe Sattler kus_AT_iti.cs.uni-magdeburg.de implemented the
1477 output format driver for Kontour.
1478 * Scott Pakin, scott+ps2ed_AT_pakin.org provided the MetaPost and
1480 LaTeX2e and MS PowerPoint output format driver.
1481 * The MS PowerPoint driver uses the libzip library -
1483 http://www.nih.at/libzip. Under MS Windows, this library is
1484 linked into the provided binary statically. Thanks to the whole
1485 libzip team.
1486 * Burkhard Plaum plaum_AT_IPF.Uni-Stuttgart.de added support for
1488 complex filled paths for the XFIG output format driver.
1489 * Bernhard Herzog herzog_AT_online.de contributed the output for‐
1491 mat driver for sketch ( http://www.skencil.org/ )
1492 * Rolf Niepraschk (niepraschk_AT_ptb.de) converted the HTML man
1494 page to LaTeX format. This allows generating the UNIX style and
1495 the HTML manual from this base format.
1496 * Several others sent smaller bug fixed and bug reports. Sorry if
1498 I do not mention them all here.
1499 * Gisbert W. Selke (gisbert_AT_tapirsoft.de) for the Java 2 output
1501 format driver.
1502 * Robert S. Maier (rsm_AT_math.arizona.edu) for many improvements
1504 on the libplot output format driver and for libplot itself.
1505 * The authors of pstotext (mcjones_AT_pa.dec.com and bir‐
1507 rell_AT_pa.dec.com) for giving me the permission to use their
1508 simple PostScript code for performing rotation.
1509 * Daniel Gehriger gehriger_AT_linkcad.com for his help concerning
1511 the handling of Splines in the DXF format.
1512 * Allen Barnett libemf_AT_lignumcomputing.com for his work on the
1514 libEMF which allows creating WMF/EMF files under *nix systems.
1515 * Dave dave_AT_opaque.net for providing the libming which is a
1517 multiplatform library for generating SWF files.
1518 * Masatake Yamoto for the introduction of autoconf, automake and
1520 libtool into pstoedit
1521 * Bob Friesenhahn for his help and the building of the Magick++
1523 API to ImageMagick.
1524 * But most important: Peter Deutsch ghost_AT_aladdin.com and Rus‐
1526 sell Lang gsview_AT_ghostgum.com.au for their help and answers
1527 regarding Ghostscript and gsview.
1528
1530 Trademarks mentioned are the property of their respective owners.
1531 Some code incorporated in the pstoedit package is subject to copyright
1533 or other intellectual property rights or restrictions including attri‐
1534 bution rights. See the notes in individual files.
1535 pstoedit is controlled under the Free Software Foundation GNU Public
1537 License (GPL). However, this does not apply to importps and the addi‐
1538 tional plugins.
1539 Ghostscript is a redistributable software package with copyright re‐
1541 strictions controlled by Artifex https://artifex.com/.
1542 pstoedit has no other relation to Ghostscript besides calling it in a
1544 subprocess.
1545 The authors, contributors, and distributors of pstoedit are not respon‐
1547 sible for its use for any purpose, or for the results generated
1548 thereby.
1549 Restrictions such as the foregoing may apply in other countries accord‐
1551 ing to international conventions and agreements.
1552Conversion Tools 18 June 2023 PSTOEDIT(1)