<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<!-- Manual page created with latex2man on Sun Apr 28 20:18:06 CEST 2013 --
-- Author of latex2man: Juergen.Vollmer@informatik-vollmer.de --
-- NOTE: This file is generated, DO NOT EDIT. -->
<html>
<head><title>PSTOEDIT</title></head>
<body bgcolor="white">
<h1 align=center>
PSTOEDIT
</h1>
<h4 align=center>Dr. Wolfgang Glunz </h4>
<h4 align=center>April 2013</h4>
<h4 align=center>Version 3.62</h4>
<tt>pstoedit</tt>
- a tool converting PostScript and PDF files into various
vector graphic formats
<h3>Table of Contents</h3>
<ul>
<li><a href="#section_1">Synopsis </a>
<ul>
<li><a href="#section_2">From the command shell </a></li>
<li><a href="#section_3">From Gsview </a></li>
<li><a href="#section_4">From programs that support the ALDUS graphic import filter interface </a></li>
</ul>
<li><a href="#section_5">Description </a>
<ul>
<li><a href="#section_6">RELEASE LEVEL </a></li>
<li><a href="#section_7">USE </a></li>
<li><a href="#section_8">PRINCIPLE OF CONVERSION </a></li>
<li><a href="#section_9">NOTES </a></li>
</ul>
<li><a href="#section_10">Options </a>
<ul>
<li><a href="#section_11">General options </a></li>
<li><a href="#section_12">Text and font handling related options </a></li>
<li><a href="#section_13">Debug options </a></li>
<li><a href="#section_14">Drawing related options </a></li>
<li><a href="#section_15">Input and outfile file arguments </a></li>
</ul>
<li><a href="#section_16">Available formats and their specific options </a>
<ul>
<li><a href="#section_17">psf - Flattened PostScript (no curves) </a></li>
<li><a href="#section_18">ps - Simplified PostScript with curves </a></li>
<li><a href="#section_19">debug - for test purposes </a></li>
<li><a href="#section_20">dump - for test purposes (same as debug) </a></li>
<li><a href="#section_21">gs - any device that GhostScript provides - use gs:format, e.g. gs:pdfwrite </a></li>
<li><a href="#section_22">ps2ai - Adobe Illustrator via ps2ai.ps of GhostScript </a></li>
<li><a href="#section_23">gmfa - ASCII GNU metafile </a></li>
<li><a href="#section_24">gmfb - binary GNU metafile </a></li>
<li><a href="#section_25">plot - GNU libplot output types, e.g. plot:-plotformat X </a></li>
<li><a href="#section_26">plot-cgm - cgm via GNU libplot </a></li>
<li><a href="#section_27">plot-ai - ai via GNU libplot </a></li>
<li><a href="#section_28">plot-svg - svg via GNU libplot </a></li>
<li><a href="#section_29">plot-ps - ps via GNU libplot </a></li>
<li><a href="#section_30">plot-fig - fig via GNU libplot </a></li>
<li><a href="#section_31">plot-pcl - pcl via GNU libplot </a></li>
<li><a href="#section_32">plot-hpgl - hpgl via GNU libplot </a></li>
<li><a href="#section_33">plot-tek - tek via GNU libplot </a></li>
<li><a href="#section_34">magick - MAGICK driver </a></li>
<li><a href="#section_35">swf - SWF driver: </a></li>
<li><a href="#section_36">svg - scalable vector graphics </a></li>
<li><a href="#section_37">xaml - eXtensible Application Markup Language </a></li>
<li><a href="#section_38">cgmb1 - CGM binary Format (V1) </a></li>
<li><a href="#section_39">cgmb - CGM binary Format (V3) </a></li>
<li><a href="#section_40">cgmt - CGM textual Format </a></li>
<li><a href="#section_41">mif - (Frame)Maker Intermediate Format </a></li>
<li><a href="#section_42">rtf - RTF Format </a></li>
<li><a href="#section_43">wemf - Wogls version of EMF </a></li>
<li><a href="#section_44">wemfc - Wogls version of EMF with experimental clip support </a></li>
<li><a href="#section_45">wemfnss - Wogls version of EMF - no subpathes </a></li>
<li><a href="#section_46">hpgl - HPGL code </a></li>
<li><a href="#section_47">pcl - PCL code </a></li>
<li><a href="#section_48">pic - PIC format for troff et.al. </a></li>
<li><a href="#section_49">asy - Asymptote Format </a></li>
<li><a href="#section_50">cairo - cairo driver </a></li>
<li><a href="#section_51">cfdg - Context Free Design Grammar </a></li>
<li><a href="#section_52">dxf - CAD exchange format </a></li>
<li><a href="#section_53">dxf_s - CAD exchange format with splines </a></li>
<li><a href="#section_54">fig - .fig format for xfig </a></li>
<li><a href="#section_55">xfig - .fig format for xfig </a></li>
<li><a href="#section_56">tfig - .fig format for xfig </a></li>
<li><a href="#section_57">gcode - emc2 gcode format </a></li>
<li><a href="#section_58">gnuplot - gnuplot format </a></li>
<li><a href="#section_59">gschem - gschem format </a></li>
<li><a href="#section_60">idraw - Interviews draw format (EPS) </a></li>
<li><a href="#section_61">java1 - java 1 applet source code </a></li>
<li><a href="#section_62">java2 - java 2 source code </a></li>
<li><a href="#section_63">kil - .kil format for Kontour </a></li>
<li><a href="#section_64">latex2e - LaTeX2e picture format </a></li>
<li><a href="#section_65">lwo - LightWave 3D Object Format </a></li>
<li><a href="#section_66">mma - Mathematica Graphics </a></li>
<li><a href="#section_67">mpost - MetaPost Format </a></li>
<li><a href="#section_68">noixml - Nemetschek NOI XML format </a></li>
<li><a href="#section_69">pcbi - engrave data - insulate/PCB format </a></li>
<li><a href="#section_70">pcb - pcb format </a></li>
<li><a href="#section_71">pcbfill - pcb format with fills </a></li>
<li><a href="#section_72">pdf - Adobe's Portable Document Format </a></li>
<li><a href="#section_73">pptx - PresentationML (PowerPoint) format </a></li>
<li><a href="#section_74">rib - RenderMan Interface Bytestream </a></li>
<li><a href="#section_75">rpl - Real3D Programming Language Format </a></li>
<li><a href="#section_76">sample - sample driver: if you don't want to see this, uncomment the corresponding line in makefile and make again </a></li>
<li><a href="#section_77">sk - Sketch Format </a></li>
<li><a href="#section_78">svm - StarView/OpenOffice.org metafile </a></li>
<li><a href="#section_79">text - text in different forms </a></li>
<li><a href="#section_80">tgif - Tgif .obj format </a></li>
<li><a href="#section_81">tk - tk and/or tk applet source code </a></li>
<li><a href="#section_82">vtk - VTK driver: if you don't want to see this, uncomment the corresponding line in makefile and make again </a></li>
<li><a href="#section_83">wmf - Windows metafile </a></li>
<li><a href="#section_84">emf - Enhanced Windows metafile </a></li>
</ul>
</li>
</ul>
<li><a href="#section_85">NOTES </a>
<ul>
<li><a href="#section_86">autotrace </a></li>
<li><a href="#section_87">Ps2ai </a></li>
<li><a href="#section_88">MetaPost </a></li>
<li><a href="#section_89">Context Free - CFDG </a></li>
<li><a href="#section_90">LaTeX2e </a></li>
<li><a href="#section_91">Creating a new output format driver </a></li>
</ul>
<li><a href="#section_92">ENVIRONMENT VARIABLES </a></li>
<li><a href="#section_93">TROUBLE SHOOTING </a></li>
<li><a href="#section_94">RESTRICTIONS </a></li>
<li><a href="#section_95">FAQs </a></li>
<li><a href="#section_96">AUTHOR </a></li>
<li><a href="#section_97">CANONICAL ARCHIVE SITE </a></li>
<li><a href="#section_98">ACKNOWLEDGEMENTS </a></li>
<li><a href="#section_99">LEGAL NOTICES </a></li>
</ul>
<p>
<h2><a name="section_1">Synopsis</a></h2>
<p>
<h4><a name="section_2">From the command shell</a></h4>
<p>
<tt>pstoedit</tt>
[<b>-v -help</b>]
<br>
<p>
<tt>pstoedit</tt>
[<b>-include</b><i> name of a PostScript file to be included</i>]
[<b>-df</b><i> font name</i>]
[<b>-nomaptoisolatin1</b>]
[<b>-dis</b>]
[<b>-pngimage</b><i> filename - for debugging purpose mainly. Write result of processing also to a PNG file.</i>]
[<b>-q</b>]
[<b>-nq</b>]
[<b>-nc</b>]
[<b>-nsp</b>]
[<b>-mergelines</b>]
[<b>-filledrecttostroke</b>]
[<b>-mergetext</b>]
[<b>-dt</b>]
[<b>-adt</b>]
[<b>-ndt</b>]
[<b>-dgbm</b>]
[<b>-correctdefinefont</b>]
[<b>-pti</b>]
[<b>-pta</b>]
[<b>-xscale</b><i> number</i>]
[<b>-yscale</b><i> number</i>]
[<b>-xshift</b><i> number</i>]
[<b>-yshift</b><i> number</i>]
[<b>-centered</b>]
[<b>-minlinewidth</b><i> number</i>]
[<b>-pagenumberformat</b><i> page number format specification</i>]
[<b>-split</b>]
[<b>-v</b>]
[<b>-usebbfrominput</b>]
[<b>-ssp</b>]
[<b>-uchar</b><i> character</i>]
[<b>-nb</b>]
[<b>-page</b><i> page number</i>]
[<b>-flat</b><i> flatness factor</i>]
[<b>-sclip</b>]
[<b>-ups</b>]
[<b>-rgb</b>]
[<b>-useagl</b>]
[<b>-noclip</b>]
[<b>-t2fontsast1</b>]
[<b>-keep</b>]
[<b>-debugfonthandling</b>]
[<b>-gstest</b>]
[<b>-nfr</b>]
[<b>-glyphs</b>]
[<b>-useoldnormalization</b>]
[<b>-rotate</b><i> angle (0-360)</i>]
[<b>-fontmap</b><i> name of font map file for pstoedit</i>]
[<b>-pagesize</b><i> page format</i>]
[<b>-help</b>]
[<b>-gs</b><i> path to the ghostscript executable/DLL </i>]
[<b>-bo</b>]
[<b>-psarg</b><i> argument string</i>]
[<b>-pslanguagelevel</b><i> PostScript Language Level to be used 1,2, or 3</i>]
<b>-f</b><i> "format[:options]"</i>
[<b>-gsregbase</b><i> GhostScript base registry path</i>]
[ inputfile [outputfile] ]
<p>
<h4><a name="section_3">From Gsview</a></h4>
<p>
Pstoedit can be called from within gsview via
"<strong>Edit | Convert to vector format</strong>"
<p>
<h4><a name="section_4">From programs that support the ALDUS graphic import filter interface</a></h4>
<p>
<tt>pstoedit</tt>
can also be used as PostScript and PDF graphic import filter for several programs including
MS-Office, PaintShop-Pro and PhotoLine. See
<a href ="http://www.pstoedit.net/importps/"><tt>http://www.pstoedit.net/importps/</tt></a>
for more
details.
<p>
<h2><a name="section_5">Description</a></h2>
<p>
<h4><a name="section_6">RELEASE LEVEL</a></h4>
<p>
This manpage documents release 3.62 of <tt>pstoedit</tt>.
<p>
<h4><a name="section_7">USE</a></h4>
<p>
<tt>pstoedit</tt>
converts PostScript and PDF files to various vector graphic
formats. The resulting files can be edited or imported into various drawing
packages. Type
<p>
<strong>pstoedit -help</strong>
<p>
to get a list of supported output formats. Pstoedit comes with a
large set of format drivers integrated in the binary. Additional drivers can be
installed as plugins and are available via
<a href ="http://www.pstoedit.net/plugins/"><tt>http://www.pstoedit.net/plugins/</tt></a>.
Just copy the plugins to the same directory where the pstoedit binary is installed or - under Unix like systems only - alternatively into the lib directory parallel to the bin directory where pstoedit is installed.
<p>
However, unless you also get a license key for the plugins, the additional
drivers will slightly distort the resulting graphics. See the documentation
provided with the plugins for further details.
<p>
<h4><a name="section_8">PRINCIPLE OF CONVERSION</a></h4>
<p>
<tt>pstoedit</tt>
works by redefining the some basic painting operators of
PostScript, e.g. <strong>stroke</strong>
or <strong>show</strong>
(bitmaps drawn by the image
operator are not supported by all output formats.) After
redefining these operators, the PostScript or PDF file that needs to be
converted is processed by a PostScript interpreter, e.g., Ghostscript
(<em>gs</em>(1)).
You normally need to have a PostScript interpreter installed in
order to use this program. However, you can perform some "back end only" processing
of files following the conventions of the pstoedit intermediate formate by specifying the <b>-bo</b>
option. See "Available formats and their specific options" below.
<p>
The output that is written by the interpreter due to the redefinition of the
drawing operators is a sort of 'flat' PostScript file that contains only simple
operations like moveto, lineto, show, etc. You can look at this file using the
<b>-f debug</b>
option.
<p>
This output is read by end-processing functions of <tt>pstoedit</tt>
and triggers
the drawing functions in the selected output format driver sometime called also "backend".
<p>
<h4><a name="section_9">NOTES</a></h4>
<p>
If you want to process PDF files directly, your PostScript interpreter must
provide this feature, as does Ghostscript. Aladdin Ghostscript is
recommended for processing PDF and PostScript files.
<p>
<h2><a name="section_10">Options</a></h2>
<p>
<h4><a name="section_11">General options</a></h4>
<dl compact>
<dt>[<b>-include</b><i> name of a PostScript file to be included</i>]
</dt>
<dd>
This options allows to specify an additional PostScript file that will be executed just before the normal input is read. This is helpful for including specific page settings or for disabling potentially unsafe PostScript operators, e.g., file, renamefile, or deletefile.
<p>
</dd>
<dt>[<b>-xscale</b><i> number</i>]
</dt>
<dd>
scale by a factor in x-direction
<p>
</dd>
<dt>[<b>-yscale</b><i> number</i>]
</dt>
<dd>
scale by a factor in y-direction
<p>
</dd>
<dt>[<b>-xshift</b><i> number</i>]
</dt>
<dd>
shift image in x-direction
<p>
</dd>
<dt>[<b>-yshift</b><i> number</i>]
</dt>
<dd>
shift image in y-direction
<p>
</dd>
<dt>[<b>-centered</b>]
</dt>
<dd>
center image before scaling or shifting
<p>
</dd>
<dt>[<b>-minlinewidth</b><i> number</i>]
</dt>
<dd>
minimal line width. All lines thinner than this will be drawn in this line width - especially zero-width lines
<p>
</dd>
<dt>[<b>-pagenumberformat</b><i> page number format specification</i>]
</dt>
<dd>
format specification for page numbers in file name if -split is used. The specification is used to create the page number using sprintf.The specification shall not include the leading
<p>
</dd>
<dt>[<b>-split</b>]
</dt>
<dd>
Create a new file for each page of the input. For this the output filename must contain a %d which is replaced with the current page number. This option is automatically switched on for output formats that don't support multiple pages within one file, e.g. fig or gnuplot.
<p>
</dd>
<dt>[<b>-usebbfrominput</b>]
</dt>
<dd>
If specified, pstoedit uses the BoundingBox as is (hopefully) found in the input file instead of one that is calculated by its own.
<p>
</dd>
<dt>[<b>-page</b><i> page number</i>]
</dt>
<dd>
Select a single page from a multi page PostScript or PDF file.
<p>
</dd>
<dt>[<b>-rgb</b>]
</dt>
<dd>
Since version 3.30 pstoedit uses the CMYK colors internally. The -rgb option turns on the old behavior to use RGB values.
<p>
</dd>
<dt>[<b>-useagl</b>]
</dt>
<dd>
use Adobe Glyph List instead of the IsoLatin1 table (this is experimental)
<p>
</dd>
<dt>[<b>-noclip</b>]
</dt>
<dd>
don't use clipping (relevant only if output format supports clipping at all)
<p>
</dd>
<dt>[<b>-rotate</b><i> angle (0-360)</i>]
</dt>
<dd>
Rotage image by angle.
<p>
</dd>
<dt>[<b>-pagesize</b><i> page format</i>]
</dt>
<dd>
set page size for output medium.
This option sets the page size for the output medium. Currently this is just used by the libplot output format driver, but might be used by other output format drivers in future. The page size is specified in terms of the usual page size names, e.g. letter or a4.
<p>
</dd>
<dt>[<b>-help</b>]
</dt>
<dd>
show the help information
<p>
</dd>
<dt>[<b>-gs</b><i> path to the ghostscript executable/DLL </i>]
</dt>
<dd>
tells pstoedit which ghostscript executable/DLL to use - overwrites the internal search heuristic
<p>
</dd>
<dt>[<b>-bo</b>]
</dt>
<dd>
You can run backend processing only (without the PostScript interpreter frontend) by first running <strong>pstoedit</strong>
<b>-f dump</b>
<i>infile</i>
<i>dumpfile</i>
and then running <strong>pstoedit</strong>
<b>-f</b><i> format</i>
<b>-bo</b>
<i>dumpfile</i>
<i>outfile</i>.
<p>
</dd>
<dt>[<b>-psarg</b><i> argument string</i>]
</dt>
<dd>
The string given with this option is passed directly to Ghostscript when Ghostscript is called to process the PostScript file for <tt>pstoedit</tt>.
For example: <strong>-psarg</strong><strong> "</strong><strong>-r300x300</strong><strong>"</strong>.
This causes the resolution to be changed to 300x300 dpi. (With older versions of GhostScript, changing the resolution this way has an effect only if the <b>-dis</b>
option is given.) If you want to pass multiple options to Ghostscript you can use multiple -psarg options <b>-psarg opt1</b>
<b>-psarg opt2</b>
<b>-psarg opt2</b>.
See the GhostScript manual for other possible options.
<p>
</dd>
<dt>[<b>-pslanguagelevel</b><i> PostScript Language Level to be used 1,2, or 3</i>]
</dt>
<dd>
PostScript Language Level to be used 1,2, or 3 You can switch Ghostscript into PostScript Level 1 only mode by <b>-pslanguagelevel 1</b>.
This can be useful for example if the PostScript file to be converted uses some Level 2 specific custom color models that are not supported by pstoedit. However, this requires that the PostScript program checks for the PostScript level supported by the interpreter and "acts" accordingly. The default language level is 3.
<p>
</dd>
<dt><b>-f</b><i> "format[:options]"</i>
</dt>
<dd>
target output format recognized by <tt>pstoedit</tt>.
Since other format drivers can be loaded dynamically, type <tt>pstoedit -help</tt>
to get a full list of formats. See "Available formats and their specific options " below for an explanation of the [<i>:options</i>]
to <b>-f</b>
format. If the format option is not given, pstoedit tries to guess the target format from the suffix of the output filename. However, in a lot of cases, this is not a unique mapping and hence pstoedit demands the <b>-f</b>
option.
<p>
</dd>
<dt>[<b>-gsregbase</b><i> GhostScript base registry path</i>]
</dt>
<dd>
registry path to use as a base path when searching GhostScript interpreter
This option provides means to specify a registry key under HKLM/Software where to search for GS interpreter key, version and <tt>GS_DLL / GS_LIB</tt> values. Example: "-gsregbase MyCompany" means that HKLM/Software/MyCompany/GPL GhostScript would be searched instead of HKLM/Software/GPL GhostScript.
<p>
</dd>
</dl>
<h4><a name="section_12">Text and font handling related options</a></h4>
<dl compact>
<dt>[<b>-df</b><i> font name</i>]
</dt>
<dd>
Sometimes fonts embedded in a PostScript program do not have a fontname. For example, this happens in PostScript files generated by <em>dvips</em>(1).
In such a case <tt>pstoedit</tt>
uses a replacement font. The default for this is Courier. Another font can be specified using the <b>-df</b>
option. <b>-df Helvetica</b>
causes all unnamed fonts to be replaced by Helvetica.
<p>
</dd>
<dt>[<b>-nomaptoisolatin1</b>]
</dt>
<dd>
Normally <tt>pstoedit</tt>
maps all character codes to the ones defined by the ISO-Latin1 encoding. If you specify <b>-nomaptoisolatin1</b>
then the encoding from the input PostScript is passed unchanged to the output. This may result in strange text output but on the other hand may be the only way to get some fonts converted appropriately. Try what fits best to your concrete case.
<p>
</dd>
<dt>[<b>-pngimage</b><i> filename - for debugging purpose mainly. Write result of processing also to a PNG file.</i>]
</dt>
<dd>
for debugging purpose mainly. Write result of processing also to a PNG file
<p>
</dd>
<dt>[<b>-dt</b>]
</dt>
<dd>
Draw text - Text is drawn as polygons. This might produce a large output file. This option is automatically switched on if the selected output format does not support text, e.g. <em>gnuplot</em>(1).
<p>
</dd>
<dt>[<b>-adt</b>]
</dt>
<dd>
Automatic Draw text - This option turns on the <b>-dt</b>
option selectively for fonts that seem to be no normal text fonts, e.g. Symbol..
<p>
</dd>
<dt>[<b>-ndt</b>]
</dt>
<dd>
Never Draw text - fully disable the heuristics used by pstoedit to decide when to "draw" text instead of showing it as text. This may produce incorrect results, but in some cases it might nevertheless be useful. "Use at own risk".
<p>
</dd>
<dt>[<b>-dgbm</b>]
</dt>
<dd>
experimental - draw also bitmaps generated by fonts/glyphs
<p>
</dd>
<dt>[<b>-correctdefinefont</b>]
</dt>
<dd>
Some PostScript files, e.g. such as generated by ChemDraw, use the PostScript definefont operator in way that is incompatible with pstoedit's assumptions. The new font is defined by copying an old font without changing the FontName of the new font. When this option is applied, some "patches" are done after a definefont in order to make it again compatible with pstoedit's assumptions. This option is not enabled per default, since it may break other PostScript file. It is tested only with ChemDraw generated files.
<p>
</dd>
<dt>[<b>-pti</b>]
</dt>
<dd>
Precision text - Normally a text string is drawn as it occurs in the input file. However, in some situations, this might produce wrongly positioned characters. This is due to limitiations in most output formats of pstoedit. They cannot represent text with arbitray inter-letter spacing which is easily possible in PDF and PostScript. With <b>-pta</b>,
each character of a text string is placed separately. With <b>-pti</b>,
this is done only in cases when there is a non zero inter-letter spacing. The downside of "precision text" is a bigger file size and hard to edit text.
<p>
</dd>
<dt>[<b>-pta</b>]
</dt>
<dd>
see -pti
<p>
</dd>
<dt>[<b>-uchar</b><i> character</i>]
</dt>
<dd>
Sometimes pstoedit cannot map a character from the encoding used by the PostScript file to the font encoding of the target format. In this case pstoedit replaces the input character by a special character in order to show all the places that couldn't be mapped correctly. The default for this is a "#". Using the <b>-uchar</b>
option it is possible to specify another character to be used instead. If you want to use a space, use -uchar " ".
<p>
</dd>
<dt>[<b>-t2fontsast1</b>]
</dt>
<dd>
Handle type 2 fonts same as type 1. Type 2 fonts sometimes occur as embedded fonts within PDF files. In the default mode, text using such fonts is drawn as polygons since pstoedit assumes that such a font is not available on the users machine. If this option is set, pstoedit assumes that the internal encoding follows the same as for a standard font and generates normal text output. This assumption may not be true in all cases. But it is nearly impossible for pstoedit to verify this assumption - it would have to do a sort of OCR.
<p>
</dd>
<dt>[<b>-nfr</b>]
</dt>
<dd>
In normal mode pstoedit replaces bitmap fonts with a font as defined by the <b>-df</b>
option. This is done, because most output formats can't handle such fonts. This behavior can be switched off using the <b>-nfr</b>
option but then it strongly depends on the application reading the the generated file whether the file is usable and correctly interpreted or not. Any problems are then out of control of pstoedit.
<p>
</dd>
<dt>[<b>-glyphs</b>]
</dt>
<dd>
pass glyph names to the output format driver. So far no output format driver really uses the glyph names, so this does not have any effect at the moment. It is a preparation for future work.
<p>
</dd>
<dt>[<b>-useoldnormalization</b>]
</dt>
<dd>
Just use this option in case the new heuristic introduced in 3.5 doesn't produce correct results - however, this normalization of font encoding will always be a best-effort approach since there is no real general solution to it with reasonable effort
<p>
</dd>
<dt>[<b>-fontmap</b><i> name of font map file for pstoedit</i>]
</dt>
<dd>
The font map is a simple text file containing lines in the following format:<br>
<p>
<tt>document_font_name target_font_name</tt> <br>
Lines beginning with <tt>%</tt> are considerd comments <br>
If a font name contains spaces, use the <tt>"font name with spaces"</tt> notation.
<p>
If a target_font_name starts with /, it is regarded as alias to a former entry.
<p>
Each font name found in the document is checked against this mapping and if there is a corresponding entry, the new name is used for the output.
<p>
If the <b>-fontmap</b>
option is not specified, <tt>pstoedit</tt>
automatically looks for the file <em>drivername</em>.fmp
in the installation directory and uses that file as a default fontmap file if available. The installation directory is:
<p>
<ul compact>
<p>
<li>Windows: The same directory where the <tt>pstoedit</tt> executable is
located
<p>
</li>
<li>Unix: <br>
<<em>The directory where the pstoedit executably is located</em>>
<tt>/../lib/</tt>
<p>
</li>
</ul>
<p>
The mpost.fmp in the misc directory of the pstoedit distibution is a sample map file with mappings from over 5000 PostScript font names to their TeXequivalents. This is useful because MetaPost is frequently used with TeX/LaTeX and those programs don't use standard font names. This file and the MetaPost output format driver are provided by Scott Pakin (<a href ="mailto:scott+ps2ed_AT_pakin.org"><tt>scott+ps2ed_AT_pakin.org</tt></a>).
Another example is wemf.fmp to be used under Windows. See the misc directory of the pstoedit source distribution.
After loading the implicit (based on driver name) or explicit (based on the -fontmap option) font map file, a system specific map file is searched and loaded from the installation directory (unix.fmp or windows.fmp). This file can be used to redirect certain fonts to system specific names using the /AliasName notation described above.
<p>
</dd>
</dl>
<h4><a name="section_13">Debug options</a></h4>
<dl compact>
<dt>[<b>-dis</b>]
</dt>
<dd>
Open a display during processing by Ghostscript. Some files only work correctly this way.
<p>
</dd>
<dt>[<b>-q</b>]
</dt>
<dd>
quiet mode - do not write startup message
<p>
</dd>
<dt>[<b>-nq</b>]
</dt>
<dd>
No exit from the PostScript interpreter. Normally Ghostscript exits after processing the pstoedit input-file. For debugging it can be useful to avoid this. If you do, you will have to type quit at the <tt>GS></tt> prompt to exit from Ghostscript.
<p>
</dd>
<dt>[<b>-v</b>]
</dt>
<dd>
Switch on verbose mode. Some additional information is shown during processing.
<p>
</dd>
<dt>[<b>-nb</b>]
</dt>
<dd>
Since version 3.10 <tt>pstoedit</tt>
uses the <tt>-dDELAYBIND</tt>
option when calling GhostScript. Previously the <tt>-dNOBIND</tt>
option was used instead but that sometimes caused problems if a user's PostScript file overloaded standard PostScript operator with totally new semantic, e.g. lt for lineto instead of the standard meaning of "less than". Using <b>-nb</b>
the old style can be activated again in case the <tt>-dDELAYBIND</tt>
gives different results as before. In such a case please also contact the author.
<p>
</dd>
<dt>[<b>-ups</b>]
</dt>
<dd>
write text as plain string instead of hex string in intermediate format - normally useful for trouble shooting and debugging only.
<p>
</dd>
<dt>[<b>-keep</b>]
</dt>
<dd>
keep the intermediate files produced by pstoedit - for debug purposes only
<p>
</dd>
<dt>[<b>-debugfonthandling</b>]
</dt>
<dd>
writes verbose messages related to internal font processing - for debug purposes only
<p>
</dd>
<dt>[<b>-gstest</b>]
</dt>
<dd>
perform a basic test for the interworking with GhostScript
<p>
</dd>
</dl>
<h4><a name="section_14">Drawing related options</a></h4>
<dl compact>
<dt>[<b>-nc</b>]
</dt>
<dd>
no curves.
Normally pstoedit tries to keep curves from the input and transfers them to the output if the output format supports curves. If the output format does not support curves, then pstoedit replaces curves by a series of lines (see also <b>-flat</b>
option). However, in some cases the user might wish to have this behavior also for output formats that originally support curves. This can be forced via the <b>-nc</b>
option.
<p>
</dd>
<dt>[<b>-nsp</b>]
</dt>
<dd>
normally subpathes are used if the output format support them. This option turns off subpathes.
<p>
</dd>
<dt>[<b>-mergelines</b>]
</dt>
<dd>
Some output formats permit the representation of filled polygons with edges that are in a different color than the fill color. Since PostScript does not support this by the standard drawing primitives directly, drawing programs typically generate two objects (the outline and the filled polygon) into the PostScript output. <tt>pstoedit</tt>
is able to recombine these, if they follow each other directly and you specify <b>-mergelines</b>.
However, this merging is not supported by all output formats due to restrictions in the target format.
<p>
</dd>
<dt>[<b>-filledrecttostroke</b>]
</dt>
<dd>
Rectangles filled with a solid color can be converted to a stroked line with a width that corresponds to the width of the rectangle. This is of primary interest for output formats which do not support filled polygons at all. But it is restricted to rectangles only, i.e. it is not supported for general polygons
<p>
</dd>
<dt>[<b>-mergetext</b>]
</dt>
<dd>
In order to produce nice looking text output, programs producing PostScript files often split words into smaller pieces which are then placed individually on adjacent positions. However, such split text is hard to edit later on and hence it is sometime better to recombine these pieces again to form a word (or even sequence of words). For this pstoedit implements some heuristics about what text pieces are to be considered parts of a split word. This is based on the geometrical proximity of the different parts and seems to work quite well so far. But there are certainly cases where this simple heuristic fails. So please check the results carefully.
<p>
</dd>
<dt>[<b>-ssp</b>]
</dt>
<dd>
simulate sub paths.
Several output formats don't support PostScript pathes containing sub pathes, i.e. pathes with intermediate movetos. In the normal case, each subpath is treated as an independent path for such output formats. This can lead to bad looking results. The most common case where this happens is if you use the <b>-dt</b>
option and show some text with letters like e, o, or b, i.e. letter that have a "hole". When the <b>-ssp</b>
option is set, pstoedit tries to eliminate these problems. However, this option is CPU time intensive!
<p>
</dd>
<dt>[<b>-flat</b><i> flatness factor</i>]
</dt>
<dd>
If the output format does not support curves in the way PostScript does or if the <b>-nc</b>
option is specified, all curves are approximated by lines. Using the <b>-flat</b>
option one can control this approximation. This parameter is directly converted to a PostScript <strong>setflat</strong>
command. Higher numbers, e.g. 10 give rougher, lower numbers, e.g. 0.1 finer approximations.
<p>
</dd>
<dt>[<b>-sclip</b>]
</dt>
<dd>
simulate clipping.
Most output formats of pstoedit don't have native support for clipping. For that <tt>pstoedit</tt>
offers an option to perform the clipping of the graphics directly without passing the clippath to the output driver. However, this results in curves being replaced by a lot of line segments and thus larger output files. So use this option only if your output looks different from the input due to clipping. In addition, this "simulated clipping" is not exactly the same as defined in PostScript. There might be lines drawn at the double size. Also clipping of text is not supported unless you also use the <b>-dt</b>
option.
<p>
</dd>
</dl>
<h4><a name="section_15">Input and outfile file arguments</a></h4>
[ inputfile [outputfile] ]
<p>
If neither an input nor an output file is given as argument, pstoedit works as filter reading from standard input and
writing to standard output.
The special filename "-" can also be used. It represents standard input if it is the first on the command line and standard output if it is the second. So "pstoedit - output.xxx" reads from standard input and writes to output.xxx
<p>
<h2><a name="section_16">Available formats and their specific options</a></h2>
<p>
<tt>pstoedit</tt>
allows passing individual options to a output format driver. This is done by
appending all options to the format specified after the <b>-f</b>
option. The format
specifier and its options must be separated by a colon (:). If more than one
option needs to be passed to the output format driver, the whole argument to <b>-f</b>
must be
enclosed within double-quote characters, thus:
<p>
<b>-f</b><i> "format[:option option ...]"</i>
<p>
To see which options are supported by a specific format, type:
<strong>pstoedit -f format:-help</strong>
<br>
<p>
The following description of the different formats supported by pstoedit is extracted from the source code of the individual drivers.
<p>
<h5><a name="section_17">psf - Flattened PostScript (no curves)</a></h5>
No driver specific options
<h5><a name="section_18">ps - Simplified PostScript with curves</a></h5>
No driver specific options
<h5><a name="section_19">debug - for test purposes</a></h5>
No driver specific options
<h5><a name="section_20">dump - for test purposes (same as debug)</a></h5>
No driver specific options
<h5><a name="section_21">gs - any device that GhostScript provides - use gs:format, e.g. gs:pdfwrite</a></h5>
No driver specific options
<h5><a name="section_22">ps2ai - Adobe Illustrator via ps2ai.ps of GhostScript</a></h5>
No driver specific options
<h5><a name="section_23">gmfa - ASCII GNU metafile </a></h5>
<dl compact>
<dt>[<b>-plotformat</b><i> string</i>]
</dt>
<dd>
plotutil format to generate
<p>
</dd>
</dl>
<h5><a name="section_24">gmfb - binary GNU metafile </a></h5>
<dl compact>
<dt>[<b>-plotformat</b><i> string</i>]
</dt>
<dd>
plotutil format to generate
<p>
</dd>
</dl>
<h5><a name="section_25">plot - GNU libplot output types, e.g. plot:-plotformat X</a></h5>
<dl compact>
<dt>[<b>-plotformat</b><i> string</i>]
</dt>
<dd>
plotutil format to generate
<p>
</dd>
</dl>
<h5><a name="section_26">plot-cgm - cgm via GNU libplot</a></h5>
<dl compact>
<dt>[<b>-plotformat</b><i> string</i>]
</dt>
<dd>
plotutil format to generate
<p>
</dd>
</dl>
<h5><a name="section_27">plot-ai - ai via GNU libplot</a></h5>
<dl compact>
<dt>[<b>-plotformat</b><i> string</i>]
</dt>
<dd>
plotutil format to generate
<p>
</dd>
</dl>
<h5><a name="section_28">plot-svg - svg via GNU libplot</a></h5>
<dl compact>
<dt>[<b>-plotformat</b><i> string</i>]
</dt>
<dd>
plotutil format to generate
<p>
</dd>
</dl>
<h5><a name="section_29">plot-ps - ps via GNU libplot</a></h5>
<dl compact>
<dt>[<b>-plotformat</b><i> string</i>]
</dt>
<dd>
plotutil format to generate
<p>
</dd>
</dl>
<h5><a name="section_30">plot-fig - fig via GNU libplot</a></h5>
<dl compact>
<dt>[<b>-plotformat</b><i> string</i>]
</dt>
<dd>
plotutil format to generate
<p>
</dd>
</dl>
<h5><a name="section_31">plot-pcl - pcl via GNU libplot</a></h5>
<dl compact>
<dt>[<b>-plotformat</b><i> string</i>]
</dt>
<dd>
plotutil format to generate
<p>
</dd>
</dl>
<h5><a name="section_32">plot-hpgl - hpgl via GNU libplot</a></h5>
<dl compact>
<dt>[<b>-plotformat</b><i> string</i>]
</dt>
<dd>
plotutil format to generate
<p>
</dd>
</dl>
<h5><a name="section_33">plot-tek - tek via GNU libplot</a></h5>
<dl compact>
<dt>[<b>-plotformat</b><i> string</i>]
</dt>
<dd>
plotutil format to generate
<p>
</dd>
</dl>
<h5><a name="section_34">magick - MAGICK driver</a></h5>
This driver uses the C++ API of ImageMagick or GraphicsMagick to finally produce different output formats. The output format is determined automatically by Image/GraphicsMagick based on the suffix of the output filename. So an output file test.png will force the creation of an image in PNG format.
<p>
No driver specific options
<h5><a name="section_35">swf - SWF driver: </a></h5>
<dl compact>
<dt>[<b>-cubic</b>]
</dt>
<dd>
cubic ???
<p>
</dd>
<dt>[<b>-trace</b>]
</dt>
<dd>
trace ???
<p>
</dd>
</dl>
<h5><a name="section_36">svg - scalable vector graphics</a></h5>
<dl compact>
<dt>[<b>-localdtd</b>]
</dt>
<dd>
use local DTD
<p>
</dd>
<dt>[<b>-standalone</b>]
</dt>
<dd>
create stand-alone type svg
<p>
</dd>
<dt>[<b>-withdtd</b>]
</dt>
<dd>
write DTD
<p>
</dd>
<dt>[<b>-withgrouping</b>]
</dt>
<dd>
write also ordinary save/restores as SVG group
<p>
</dd>
<dt>[<b>-nogroupedpath</b>]
</dt>
<dd>
do not write a group around pathes
<p>
</dd>
<dt>[<b>-noviewbox</b>]
</dt>
<dd>
don't write a view box
<p>
</dd>
<dt>[<b>-texmode</b>]
</dt>
<dd>
TeX Mode
<p>
</dd>
<dt>[<b>-imagetofile</b>]
</dt>
<dd>
write raster images to separate files instead of embedding them
<p>
</dd>
<dt>[<b>-notextrendering</b>]
</dt>
<dd>
do not write textrendering attribute
<p>
</dd>
<dt>[<b>-border</b><i> number</i>]
</dt>
<dd>
additional border to draw around bare bounding box (in percent of width and height)
<p>
</dd>
<dt>[<b>-title</b><i> string</i>]
</dt>
<dd>
text to use as title for the generated document
<p>
</dd>
</dl>
<h5><a name="section_37">xaml - eXtensible Application Markup Language</a></h5>
<dl compact>
<dt>[<b>-localdtd</b>]
</dt>
<dd>
use local DTD
<p>
</dd>
<dt>[<b>-standalone</b>]
</dt>
<dd>
create stand-alone type svg
<p>
</dd>
<dt>[<b>-withdtd</b>]
</dt>
<dd>
write DTD
<p>
</dd>
<dt>[<b>-withgrouping</b>]
</dt>
<dd>
write also ordinary save/restores as SVG group
<p>
</dd>
<dt>[<b>-nogroupedpath</b>]
</dt>
<dd>
do not write a group around pathes
<p>
</dd>
<dt>[<b>-noviewbox</b>]
</dt>
<dd>
don't write a view box
<p>
</dd>
<dt>[<b>-texmode</b>]
</dt>
<dd>
TeX Mode
<p>
</dd>
<dt>[<b>-imagetofile</b>]
</dt>
<dd>
write raster images to separate files instead of embedding them
<p>
</dd>
<dt>[<b>-notextrendering</b>]
</dt>
<dd>
do not write textrendering attribute
<p>
</dd>
<dt>[<b>-border</b><i> number</i>]
</dt>
<dd>
additional border to draw around bare bounding box (in percent of width and height)
<p>
</dd>
<dt>[<b>-title</b><i> string</i>]
</dt>
<dd>
text to use as title for the generated document
<p>
</dd>
</dl>
<h5><a name="section_38">cgmb1 - CGM binary Format (V1)</a></h5>
No driver specific options
<h5><a name="section_39">cgmb - CGM binary Format (V3)</a></h5>
No driver specific options
<h5><a name="section_40">cgmt - CGM textual Format</a></h5>
No driver specific options
<h5><a name="section_41">mif - (Frame)Maker Intermediate Format</a></h5>
<dl compact>
<dt>[<b>-nopage</b>]
</dt>
<dd>
do not add a separate Page entry
<p>
</dd>
</dl>
<h5><a name="section_42">rtf - RTF Format</a></h5>
No driver specific options
<h5><a name="section_43">wemf - Wogls version of EMF </a></h5>
<dl compact>
<dt>[<b>-df</b>]
</dt>
<dd>
write info about font processing
<p>
</dd>
<dt>[<b>-dumpfontmap</b>]
</dt>
<dd>
write info about font mapping
<p>
</dd>
<dt>[<b>-size:psbbox</b>]
</dt>
<dd>
use the bounding box as calculated by the PostScript frontent as size
<p>
</dd>
<dt>[<b>-size:fullpage</b>]
</dt>
<dd>
set the size to the size of a full page
<p>
</dd>
<dt>[<b>-size:automatic</b>]
</dt>
<dd>
let windows calculate the bounding box (default)
<p>
</dd>
<dt>[<b>-keepimages</b>]
</dt>
<dd>
debug option - keep the embedded bitmaps as external files
<p>
</dd>
<dt>[<b>-useoldpolydraw</b>]
</dt>
<dd>
do not use Windows PolyDraw but an emulation of it - sometimes needed for certain programs reading the EMF files
<p>
</dd>
<dt>[<b>-OO</b>]
</dt>
<dd>
generate OpenOffice compatible EMF file
<p>
</dd>
</dl>
<h5><a name="section_44">wemfc - Wogls version of EMF with experimental clip support</a></h5>
<dl compact>
<dt>[<b>-df</b>]
</dt>
<dd>
write info about font processing
<p>
</dd>
<dt>[<b>-dumpfontmap</b>]
</dt>
<dd>
write info about font mapping
<p>
</dd>
<dt>[<b>-size:psbbox</b>]
</dt>
<dd>
use the bounding box as calculated by the PostScript frontent as size
<p>
</dd>
<dt>[<b>-size:fullpage</b>]
</dt>
<dd>
set the size to the size of a full page
<p>
</dd>
<dt>[<b>-size:automatic</b>]
</dt>
<dd>
let windows calculate the bounding box (default)
<p>
</dd>
<dt>[<b>-keepimages</b>]
</dt>
<dd>
debug option - keep the embedded bitmaps as external files
<p>
</dd>
<dt>[<b>-useoldpolydraw</b>]
</dt>
<dd>
do not use Windows PolyDraw but an emulation of it - sometimes needed for certain programs reading the EMF files
<p>
</dd>
<dt>[<b>-OO</b>]
</dt>
<dd>
generate OpenOffice compatible EMF file
<p>
</dd>
</dl>
<h5><a name="section_45">wemfnss - Wogls version of EMF - no subpathes </a></h5>
<dl compact>
<dt>[<b>-df</b>]
</dt>
<dd>
write info about font processing
<p>
</dd>
<dt>[<b>-dumpfontmap</b>]
</dt>
<dd>
write info about font mapping
<p>
</dd>
<dt>[<b>-size:psbbox</b>]
</dt>
<dd>
use the bounding box as calculated by the PostScript frontent as size
<p>
</dd>
<dt>[<b>-size:fullpage</b>]
</dt>
<dd>
set the size to the size of a full page
<p>
</dd>
<dt>[<b>-size:automatic</b>]
</dt>
<dd>
let windows calculate the bounding box (default)
<p>
</dd>
<dt>[<b>-keepimages</b>]
</dt>
<dd>
debug option - keep the embedded bitmaps as external files
<p>
</dd>
<dt>[<b>-useoldpolydraw</b>]
</dt>
<dd>
do not use Windows PolyDraw but an emulation of it - sometimes needed for certain programs reading the EMF files
<p>
</dd>
<dt>[<b>-OO</b>]
</dt>
<dd>
generate OpenOffice compatible EMF file
<p>
</dd>
</dl>
<h5><a name="section_46">hpgl - HPGL code</a></h5>
<dl compact>
<dt>[<b>-penplotter</b>]
</dt>
<dd>
plotter is pen plotter (i.e. no support for specific line widths)
<p>
</dd>
<dt>[<b>-pencolorsfromfile</b>]
</dt>
<dd>
read pen colors from file drvhpgl.pencolors in pstoedit data directory
<p>
</dd>
<dt>[<b>-pencolors</b><i> number</i>]
</dt>
<dd>
maximum number of pen colors to be used by pstoedit (default 0) -
<p>
</dd>
<dt>[<b>-filltype</b><i> string</i>]
</dt>
<dd>
select fill type e.g. FT 1
<p>
</dd>
<dt>[<b>-hpgl2</b>]
</dt>
<dd>
Use HPGL/2 instead of HPGL/1
<p>
</dd>
<dt>[<b>-rot90</b>]
</dt>
<dd>
rotate hpgl by 90 degrees
<p>
</dd>
<dt>[<b>-rot180</b>]
</dt>
<dd>
rotate hpgl by 180 degrees
<p>
</dd>
<dt>[<b>-rot270</b>]
</dt>
<dd>
rotate hpgl by 270 degrees
<p>
</dd>
</dl>
<h5><a name="section_47">pcl - PCL code</a></h5>
<dl compact>
<dt>[<b>-penplotter</b>]
</dt>
<dd>
plotter is pen plotter (i.e. no support for specific line widths)
<p>
</dd>
<dt>[<b>-pencolorsfromfile</b>]
</dt>
<dd>
read pen colors from file drvhpgl.pencolors in pstoedit data directory
<p>
</dd>
<dt>[<b>-pencolors</b><i> number</i>]
</dt>
<dd>
maximum number of pen colors to be used by pstoedit (default 0) -
<p>
</dd>
<dt>[<b>-filltype</b><i> string</i>]
</dt>
<dd>
select fill type e.g. FT 1
<p>
</dd>
<dt>[<b>-hpgl2</b>]
</dt>
<dd>
Use HPGL/2 instead of HPGL/1
<p>
</dd>
<dt>[<b>-rot90</b>]
</dt>
<dd>
rotate hpgl by 90 degrees
<p>
</dd>
<dt>[<b>-rot180</b>]
</dt>
<dd>
rotate hpgl by 180 degrees
<p>
</dd>
<dt>[<b>-rot270</b>]
</dt>
<dd>
rotate hpgl by 270 degrees
<p>
</dd>
</dl>
<h5><a name="section_48">pic - PIC format for troff et.al.</a></h5>
<dl compact>
<dt>[<b>-troff</b>]
</dt>
<dd>
troff mode (default is groff)
<p>
</dd>
<dt>[<b>-landscape</b>]
</dt>
<dd>
landscape output
<p>
</dd>
<dt>[<b>-portrait</b>]
</dt>
<dd>
portrait output
<p>
</dd>
<dt>[<b>-keepfont</b>]
</dt>
<dd>
print unrecognized literally
<p>
</dd>
<dt>[<b>-text</b>]
</dt>
<dd>
try not to make pictures from running text
<p>
</dd>
<dt>[<b>-debug</b>]
</dt>
<dd>
enable debug output
<p>
</dd>
</dl>
<h5><a name="section_49">asy - Asymptote Format</a></h5>
No driver specific options
<h5><a name="section_50">cairo - cairo driver</a></h5>
generates compilable c code for rendering with cairo
<p>
<dl compact>
<dt>[<b>-pango</b>]
</dt>
<dd>
use pango for font rendering
<p>
</dd>
<dt>[<b>-funcname</b><i> string</i>]
</dt>
<dd>
sets the base name for the generated functions and variables. e.g. myfig
<p>
</dd>
<dt>[<b>-header</b><i> string</i>]
</dt>
<dd>
sets the output file name for the generated C header file. e.g. myfig.h
<p>
</dd>
</dl>
<h5><a name="section_51">cfdg - Context Free Design Grammar</a></h5>
Context Free Design Grammar, usable by Context Free Art (http://www.contextfreeart.org/)
<p>
No driver specific options
<h5><a name="section_52">dxf - CAD exchange format</a></h5>
<dl compact>
<dt>[<b>-polyaslines</b>]
</dt>
<dd>
use LINE instead of POLYLINE in DXF
<p>
</dd>
<dt>[<b>-mm</b>]
</dt>
<dd>
use mm coordinates instead of points in DXF (mm=pt/72*25.4)
<p>
</dd>
<dt>[<b>-ctl</b>]
</dt>
<dd>
map colors to layers
<p>
</dd>
<dt>[<b>-splineaspolyline</b>]
</dt>
<dd>
approximate splines with PolyLines (only for -f dxf_s)
<p>
</dd>
<dt>[<b>-splineasnurb</b>]
</dt>
<dd>
experimental (only for -f dxf_s)
<p>
</dd>
<dt>[<b>-splineasbspline</b>]
</dt>
<dd>
experimental (only for -f dxf_s)
<p>
</dd>
<dt>[<b>-splineassinglespline</b>]
</dt>
<dd>
experimental (only for -f dxf_s)
<p>
</dd>
<dt>[<b>-splineasmultispline</b>]
</dt>
<dd>
experimental (only for -f dxf_s)
<p>
</dd>
<dt>[<b>-splineasbezier</b>]
</dt>
<dd>
use Bezier splines in DXF format (only for -f dxf_s)
<p>
</dd>
<dt>[<b>-splineprecision</b><i> number</i>]
</dt>
<dd>
number of samples to take from spline curve when doing approximation with -splineaspolyline or -splineasmultispline - should be >= 2 (default 5)
<p>
</dd>
<dt>[<b>-dumplayernames</b>]
</dt>
<dd>
dump all layer names found to standard output
<p>
</dd>
<dt>[<b>-layers</b><i> string</i>]
</dt>
<dd>
layers to be shown (comma separated list of layer names, no space)
<p>
</dd>
<dt>[<b>-layerfilter</b><i> string</i>]
</dt>
<dd>
layers to be hidden (comma separated list of layer names, no space)
<p>
</dd>
</dl>
<h5><a name="section_53">dxf_s - CAD exchange format with splines</a></h5>
<dl compact>
<dt>[<b>-polyaslines</b>]
</dt>
<dd>
use LINE instead of POLYLINE in DXF
<p>
</dd>
<dt>[<b>-mm</b>]
</dt>
<dd>
use mm coordinates instead of points in DXF (mm=pt/72*25.4)
<p>
</dd>
<dt>[<b>-ctl</b>]
</dt>
<dd>
map colors to layers
<p>
</dd>
<dt>[<b>-splineaspolyline</b>]
</dt>
<dd>
approximate splines with PolyLines (only for -f dxf_s)
<p>
</dd>
<dt>[<b>-splineasnurb</b>]
</dt>
<dd>
experimental (only for -f dxf_s)
<p>
</dd>
<dt>[<b>-splineasbspline</b>]
</dt>
<dd>
experimental (only for -f dxf_s)
<p>
</dd>
<dt>[<b>-splineassinglespline</b>]
</dt>
<dd>
experimental (only for -f dxf_s)
<p>
</dd>
<dt>[<b>-splineasmultispline</b>]
</dt>
<dd>
experimental (only for -f dxf_s)
<p>
</dd>
<dt>[<b>-splineasbezier</b>]
</dt>
<dd>
use Bezier splines in DXF format (only for -f dxf_s)
<p>
</dd>
<dt>[<b>-splineprecision</b><i> number</i>]
</dt>
<dd>
number of samples to take from spline curve when doing approximation with -splineaspolyline or -splineasmultispline - should be >= 2 (default 5)
<p>
</dd>
<dt>[<b>-dumplayernames</b>]
</dt>
<dd>
dump all layer names found to standard output
<p>
</dd>
<dt>[<b>-layers</b><i> string</i>]
</dt>
<dd>
layers to be shown (comma separated list of layer names, no space)
<p>
</dd>
<dt>[<b>-layerfilter</b><i> string</i>]
</dt>
<dd>
layers to be hidden (comma separated list of layer names, no space)
<p>
</dd>
</dl>
<h5><a name="section_54">fig - .fig format for xfig</a></h5>
The xfig format driver supports special fontnames, which may be produced by using a fontmap file. The following types of names are supported : <br>
<pre>
General notation:
"Postscript Font Name" ((LaTeX|PostScript|empty)(::special)::)XFigFontName
Examples:
Helvetica LaTeX::SansSerif
Courier LaTeX::special::Typewriter
GillSans "AvantGarde Demi"
Albertus PostScript::special::"New Century Schoolbook Italic"
Symbol ::special::Symbol (same as Postscript::special::Symbol)
</pre>
See also the file examplefigmap.fmp in the misc directory of the pstoedit source distribution for an example font map file for xfig. Please note that the Fontname has to be among those supported by xfig. See - <a href ="http://www.xfig.org/userman/fig-format.html"><tt>http://www.xfig.org/userman/fig-format.html</tt></a>
for a list of legal font names
<p>
<dl compact>
<dt>[<b>-startdepth</b><i> number</i>]
</dt>
<dd>
Set the initial depth (default 999)
<p>
</dd>
<dt>[<b>-metric</b>]
</dt>
<dd>
Switch to centimeter display (default inches)
<p>
</dd>
<dt>[<b>-usecorrectfontsize</b>]
</dt>
<dd>
don't scale fonts for xfig. Use this if you also use this option with xfig
<p>
</dd>
<dt>[<b>-depth</b><i> number</i>]
</dt>
<dd>
Set the page depth in inches (default 11)
<p>
</dd>
</dl>
<h5><a name="section_55">xfig - .fig format for xfig</a></h5>
See fig format for more details.
<p>
<dl compact>
<dt>[<b>-startdepth</b><i> number</i>]
</dt>
<dd>
Set the initial depth (default 999)
<p>
</dd>
<dt>[<b>-metric</b>]
</dt>
<dd>
Switch to centimeter display (default inches)
<p>
</dd>
<dt>[<b>-usecorrectfontsize</b>]
</dt>
<dd>
don't scale fonts for xfig. Use this if you also use this option with xfig
<p>
</dd>
<dt>[<b>-depth</b><i> number</i>]
</dt>
<dd>
Set the page depth in inches (default 11)
<p>
</dd>
</dl>
<h5><a name="section_56">tfig - .fig format for xfig</a></h5>
Test only
<p>
<dl compact>
<dt>[<b>-startdepth</b><i> number</i>]
</dt>
<dd>
Set the initial depth (default 999)
<p>
</dd>
<dt>[<b>-metric</b>]
</dt>
<dd>
Switch to centimeter display (default inches)
<p>
</dd>
<dt>[<b>-usecorrectfontsize</b>]
</dt>
<dd>
don't scale fonts for xfig. Use this if you also use this option with xfig
<p>
</dd>
<dt>[<b>-depth</b><i> number</i>]
</dt>
<dd>
Set the page depth in inches (default 11)
<p>
</dd>
</dl>
<h5><a name="section_57">gcode - emc2 gcode format</a></h5>
See also: <a href ="http://linuxcnc.org/"><tt>http://linuxcnc.org/</tt></a>
<p>
No driver specific options
<h5><a name="section_58">gnuplot - gnuplot format</a></h5>
No driver specific options
<h5><a name="section_59">gschem - gschem format</a></h5>
See also: <a href ="http://www.geda.seul.org/tools/gschem/"><tt>http://www.geda.seul.org/tools/gschem/</tt></a>
<p>
No driver specific options
<h5><a name="section_60">idraw - Interviews draw format (EPS)</a></h5>
No driver specific options
<h5><a name="section_61">java1 - java 1 applet source code</a></h5>
<dl compact>
<dt>[<b>java class name</b><i> string</i>]
</dt>
<dd>
name of java class to generate
<p>
</dd>
</dl>
<h5><a name="section_62">java2 - java 2 source code</a></h5>
<dl compact>
<dt>[<b>java class name</b><i> string</i>]
</dt>
<dd>
name of java class to generate
<p>
</dd>
</dl>
<h5><a name="section_63">kil - .kil format for Kontour</a></h5>
No driver specific options
<h5><a name="section_64">latex2e - LaTeX2e picture format</a></h5>
<dl compact>
<dt>[<b>-integers</b>]
</dt>
<dd>
round all coordinates to the nearest integer
<p>
</dd>
</dl>
<h5><a name="section_65">lwo - LightWave 3D Object Format</a></h5>
No driver specific options
<h5><a name="section_66">mma - Mathematica Graphics</a></h5>
<dl compact>
<dt>[<b>-eofillfills</b>]
</dt>
<dd>
Filling is used for eofill (default is not to fill)
<p>
</dd>
</dl>
<h5><a name="section_67">mpost - MetaPost Format</a></h5>
No driver specific options
<h5><a name="section_68">noixml - Nemetschek NOI XML format</a></h5>
Nemetschek Object Interface XML format
<p>
<dl compact>
<dt>[<b>-r</b><i> string</i>]
</dt>
<dd>
Allplan resource file
<p>
</dd>
<dt>[<b>-bsl</b><i> number</i>]
</dt>
<dd>
Bezier Split Level (default 3)
<p>
</dd>
</dl>
<h5><a name="section_69">pcbi - engrave data - insulate/PCB format</a></h5>
See <a href ="http://home.vr-web.de/~hans-juergen-jahn/software/devpcb.html"><tt>http://home.vr-web.de/~hans-juergen-jahn/software/devpcb.html</tt></a>
for more details.
<p>
No driver specific options
<h5><a name="section_70">pcb - pcb format</a></h5>
See also: <a href ="http://pcb.sourceforge.net"><tt>http://pcb.sourceforge.net</tt></a>
and <a href ="http://www.penguin.cz/~utx/pstoedit-pcb/"><tt>http://www.penguin.cz/~utx/pstoedit-pcb/</tt></a>
<p>
<dl compact>
<dt>[<b>-grid</b><i> missing arg name</i>]
</dt>
<dd>
attempt to snap relevant output to grid (mils) and put failed objects to a different layer
<p>
</dd>
<dt>[<b>-snapdist</b><i> missing arg name</i>]
</dt>
<dd>
grid snap distance ratio (0 < snapdist <= 0.5, default 0.1)
<p>
</dd>
<dt>[<b>-tshiftx</b><i> missing arg name</i>]
</dt>
<dd>
additional x shift measured in target units (mils)
<p>
</dd>
<dt>[<b>-tshifty</b><i> missing arg name</i>]
</dt>
<dd>
additional y shift measured in target units (mils)
<p>
</dd>
<dt>[<b>-grid</b><i> missing arg name</i>]
</dt>
<dd>
attempt to snap relevant output to grid (mils) and put failed objects to a different layer
<p>
</dd>
<dt>[<b>-mm</b>]
</dt>
<dd>
Switch to metric units (mm)
<p>
</dd>
<dt>[<b>-stdnames</b>]
</dt>
<dd>
use standard layer names instead of descriptive names
<p>
</dd>
<dt>[<b>-forcepoly</b>]
</dt>
<dd>
force all objects to be interpreted as polygons
<p>
</dd>
</dl>
<h5><a name="section_71">pcbfill - pcb format with fills</a></h5>
See also: <a href ="http://pcb.sourceforge.net"><tt>http://pcb.sourceforge.net</tt></a>
<p>
No driver specific options
<h5><a name="section_72">pdf - Adobe's Portable Document Format</a></h5>
No driver specific options
<h5><a name="section_73">pptx - PresentationML (PowerPoint) format</a></h5>
This is the format used internally by Microsoft PowerPoint. LibreOffice can also read/write PowerPoint files albeit with some lack of functionality.
<p>
<dl compact>
<dt>[<b>-colors</b><i> string</i>]
</dt>
<dd>
"original" to retain original colors (default), "theme" to convert randomly to theme colors, or "theme-lum" also to vary luminance
<p>
</dd>
<dt>[<b>-fonts</b><i> string</i>]
</dt>
<dd>
use "windows" fonts (default), "native" fonts, or convert to the "theme" font
<p>
</dd>
<dt>[<b>-embed</b><i> string</i>]
</dt>
<dd>
embed fonts, specified as a comma-separated list of EOT-format font files
<p>
</dd>
</dl>
<h5><a name="section_74">rib - RenderMan Interface Bytestream</a></h5>
No driver specific options
<h5><a name="section_75">rpl - Real3D Programming Language Format</a></h5>
No driver specific options
<h5><a name="section_76">sample - sample driver: if you don't want to see this, uncomment the corresponding line in makefile and make again</a></h5>
this is a long description for the sample driver
<p>
<dl compact>
<dt>[<b>-sampleoption</b><i> integer</i>]
</dt>
<dd>
just an example
<p>
</dd>
</dl>
<h5><a name="section_77">sk - Sketch Format</a></h5>
No driver specific options
<h5><a name="section_78">svm - StarView/OpenOffice.org metafile</a></h5>
StarView/OpenOffice.org metafile, readable from OpenOffice.org 1.0/StarOffice 6.0 and above.
<p>
<dl compact>
<dt>[<b>-m</b>]
</dt>
<dd>
map to Arial
<p>
</dd>
<dt>[<b>-nf</b>]
</dt>
<dd>
emulate narrow fonts
<p>
</dd>
</dl>
<h5><a name="section_79">text - text in different forms </a></h5>
<dl compact>
<dt>[<b>-height</b><i> number</i>]
</dt>
<dd>
page height in terms of characters
<p>
</dd>
<dt>[<b>-width</b><i> number</i>]
</dt>
<dd>
page width in terms of characters
<p>
</dd>
<dt>[<b>-dump</b>]
</dt>
<dd>
dump text pieces
<p>
</dd>
</dl>
<h5><a name="section_80">tgif - Tgif .obj format</a></h5>
<dl compact>
<dt>[<b>-ta</b>]
</dt>
<dd>
text as attribute
<p>
</dd>
</dl>
<h5><a name="section_81">tk - tk and/or tk applet source code</a></h5>
<dl compact>
<dt>[<b>-R</b>]
</dt>
<dd>
swap HW
<p>
</dd>
<dt>[<b>-I</b>]
</dt>
<dd>
no impress
<p>
</dd>
<dt>[<b>-n</b><i> string</i>]
</dt>
<dd>
tagnames
<p>
</dd>
</dl>
<h5><a name="section_82">vtk - VTK driver: if you don't want to see this, uncomment the corresponding line in makefile and make again</a></h5>
this is a long description for the VTKe driver
<p>
<dl compact>
<dt>[<b>-VTKeoption</b><i> integer</i>]
</dt>
<dd>
just an example
<p>
</dd>
</dl>
<h5><a name="section_83">wmf - Windows metafile</a></h5>
<dl compact>
<dt>[<b>-m</b>]
</dt>
<dd>
map to Arial
<p>
</dd>
<dt>[<b>-nf</b>]
</dt>
<dd>
emulate narrow fonts
<p>
</dd>
<dt>[<b>-drawbb</b>]
</dt>
<dd>
draw bounding box
<p>
</dd>
<dt>[<b>-p</b>]
</dt>
<dd>
prune line ends
<p>
</dd>
<dt>[<b>-nfw</b>]
</dt>
<dd>
Newer versions of Windows (2000, XP, Vista) will not accept WMF/EMF files generated when this option is set and the input contains Text. But if this option is not set, then the WMF/EMF driver will estimate interletter spacing of text using a very coarse heuristic. This may result in ugly looking output. On the other hand, OpenOffice can still read EMF/WMF files where pstoedit delegates the calculation of the inter letter spacing to the program reading the WMF/EMF file. So if the generated WMF/EMF file shall never be processed under Windows, use this option. If WMF/EMF files with high precision text need to be generated under *nix the only option is to use the -pta option of pstoedit. However that causes every text to be split into single characters which makes the text hard to edit afterwards. Hence the -nfw options provides a sort of compromise between portability and nice to edit but still nice looking text. Again - this option has no meaning when pstoedit is executed under Windows anyway. In that case the output is portable but nevertheless not split and still looks fine.
<p>
</dd>
<dt>[<b>-winbb</b>]
</dt>
<dd>
let the Windows API calculate the Bounding Box (Windows only)
<p>
</dd>
<dt>[<b>-OO</b>]
</dt>
<dd>
generate OpenOffice compatible EMF file
<p>
</dd>
</dl>
<h5><a name="section_84">emf - Enhanced Windows metafile</a></h5>
<dl compact>
<dt>[<b>-m</b>]
</dt>
<dd>
map to Arial
<p>
</dd>
<dt>[<b>-nf</b>]
</dt>
<dd>
emulate narrow fonts
<p>
</dd>
<dt>[<b>-drawbb</b>]
</dt>
<dd>
draw bounding box
<p>
</dd>
<dt>[<b>-p</b>]
</dt>
<dd>
prune line ends
<p>
</dd>
<dt>[<b>-nfw</b>]
</dt>
<dd>
Newer versions of Windows (2000, XP, Vista) will not accept WMF/EMF files generated when this option is set and the input contains Text. But if this option is not set, then the WMF/EMF driver will estimate interletter spacing of text using a very coarse heuristic. This may result in ugly looking output. On the other hand, OpenOffice can still read EMF/WMF files where pstoedit delegates the calculation of the inter letter spacing to the program reading the WMF/EMF file. So if the generated WMF/EMF file shall never be processed under Windows, use this option. If WMF/EMF files with high precision text need to be generated under *nix the only option is to use the -pta option of pstoedit. However that causes every text to be split into single characters which makes the text hard to edit afterwards. Hence the -nfw options provides a sort of compromise between portability and nice to edit but still nice looking text. Again - this option has no meaning when pstoedit is executed under Windows anyway. In that case the output is portable but nevertheless not split and still looks fine.
<p>
</dd>
<dt>[<b>-winbb</b>]
</dt>
<dd>
let the Windows API calculate the Bounding Box (Windows only)
<p>
</dd>
<dt>[<b>-OO</b>]
</dt>
<dd>
generate OpenOffice compatible EMF file
<p>
</dd>
</dl>
<p>
<h2><a name="section_85">NOTES</a></h2>
<p>
<h4><a name="section_86">autotrace</a></h4>
<p>
pstoedit cooperates with autotrace. Autotrace can now produce a dump file
for further processing by pstoedit using the <b>-bo</b>
(backend only) option.
Autotrace is a program written by a group around Martin Weber and can be
found at <a href ="http://sourceforge.net/projects/autotrace/"><tt>http://sourceforge.net/projects/autotrace/</tt></a>.
<p>
<h4><a name="section_87">Ps2ai</a></h4>
<p>
The ps2ai output format driver is not a native pstoedit output format driver. It does not use the
pstoedit postcript flattener, instead it uses the PostScript program
ps2ai.ps which is installed in the GhostScript distribution directory. It
is included to provide the same "look-and-feel" for the conversion to AI.
The additional benefit is that this conversion is now available also via
the "convert-to-vector" menu of Gsview. However, lot's of files don't
convert nicely or at all using ps2ai.ps. So a native pstoedit driver would
be much better. Anyone out there to take this? The AI format is usable for
example by Mayura Draw (<a href ="http://www.mayura.com"><tt>http://www.mayura.com</tt></a>).
Also a driver to the
Mayura native format would be nice.
<p>
An alternative to the ps2ai based driver is available via the -f plot:ai format if the libplot(ter) is installed.
<p>
You should use a version of GhostScript greater than or equal to 6.00 for using the ps2ai output format driver.
<p>
<h4><a name="section_88">MetaPost</a></h4>
<p>
Note that, as far as Scott knows, MetaPost does not support PostScript's
eofill. The metapost output format driver just converts eofill to fill, and issues a warning if
verbose is set. Fortunately, very few PostScript programs rely on the
even-odd fill rule, even though many specify it.
<p>
For more on MetaPost see:
<p>
<a href ="http://cm.bell-labs.com/who/hobby/MetaPost.html"><tt>http://cm.bell-labs.com/who/hobby/MetaPost.html</tt></a>
<p>
<h4><a name="section_89">Context Free - CFDG</a></h4>
The driver for the CFDG format (drvcfdg) defines
one shape per page of PostScript, but only the first shape is actually
rendered (unless the user edits the generated CFDG code, of course).
CFDG doesn't support multi-page output, so this probably a reasonable thing to do.
<p>
For more on Context Free see:
<a href ="http://www.contextfreeart.org/"><tt>http://www.contextfreeart.org/</tt></a>
<p>
<h4><a name="section_90">LaTeX2e</a></h4>
<p>
<ul compact>
<li>LaTeX2e's picture environment is not very powerful. As a result, many
elementary PostScript constructs are ignored -- fills, line
thicknesses (besides "thick" and "thin"), and dash patterns, to name a
few. Furthermore, complex pictures may overrun TeX's memory capacity.
<p>
</li>
<li>Some PostScript constructs are not supported directly by "picture",
but can be handled by external packages. If a figure uses color, the
top-level document will need to do a <tt>"\usepackage{color}"</tt>. And if a
figure contains rotated text, the top-level document will need to do a
<tt>"\usepackage{rotating}"</tt>.
<p>
</li>
<li>All lengths, coordinates, and font sizes output by the output format driver are in
terms of <tt>\unitlength</tt>, so scaling a figure is simply a matter of doing
a <tt>"\setlength{\unitlength}{...}"</tt>.
<p>
</li>
<li>The output format driver currently supports one output format driver specific option,
"integers", which rounds all lengths, coordinates, and font sizes to
the nearest integer. This makes hand-editing the picture a little
nicer.
<p>
</li>
<li>Why is this output format driver useful? One answer is portability; any LaTeX2e
system can handle the picture environment, even if it can't handle
PostScript graphics. (pdfLaTeX comes to mind here.) A second answer
is that pictures can be edited easily to contain any arbitrary LaTeX2e
code. For instance, the text in a figure can be modified to contain
complex mathematics, non-Latin alphabets, bibliographic citations, or
-- the real reason Scott wrote the LaTeX2e output format driver -- hyperlinks to the
surrounding document (with help from the hyperref package).
</li>
</ul>
<p>
<h4><a name="section_91">Creating a new output format driver</a></h4>
<p>
To implement a new output format driver you can start from <tt>drvsampl.cpp</tt>
and
<tt>drvsampl.h</tt>.
See also comments in <tt>drvbase.h</tt>
and
<tt>drvfuncs.h</tt>
for an explanation of methods that should be implemented
for a new output format driver.
<p>
<h2><a name="section_92">ENVIRONMENT VARIABLES</a></h2>
<p>
A default PostScript interpreter to be called by pstoedit is specified at
compile time. You can overwrite the default by setting the GS environment
variable to the name of a suitable PostScript interpreter.
<p>
You can check which name of a PostScript interpreter was compiled into
pstoedit using: <strong>pstoedit</strong>
<b>-help -v</b>.
<p>
See the GhostScript manual for descriptions of environment variables used by
Ghostscript most importantly <tt>GS_FONTPATH</tt> and <tt>GS_LIB</tt>; other
environment variables also affect output to display, print, and additional
filtering and processing. See the related documentation.
<p>
<tt>pstoedit</tt>
allocates temporary files using the function <em>tempnam</em>(3).
Thus the location for temporary files might be controllable by other
environment variables used by this function. See the <em>tempnam</em>(3)
manpage
for descriptions of environment variables used. On UNIX like system this is
probably the <tt>TMPDIR</tt> variable, on DOS/WINDOWS either <tt>TMP</tt> or
<tt>TEMP</tt>.
<p>
<h2><a name="section_93">TROUBLE SHOOTING</a></h2>
<p>
If you have problems with <tt>pstoedit</tt>
first try whether Ghostscript
successfully displays your file. If yes, then try
<strong>pstoedit</strong>
<b>-f ps</b>
<i>infile.ps</i>
<i>testfile.ps</i>
and check whether <i>testfile.ps</i>
still displays correctly using
Ghostscript. If this file doesn't look correctly then there seems to be a
problem with <tt>pstoedit</tt>'s
PostScript frontend. If this file looks good
but the output for a specific format is wrong, the problem is probably in
the output format driver for the specific format. In either case send bug fixes and
reports to the author.
<p>
A common problem with PostScript files is that the PostScript file redefines
one of the standard PostScript operators inconsistently. There is no effect
of this if you just print the file since the original PostScript "program"
uses these new operator in the new meaning and does not use the original
ones anymoew. However, when run under the control of pstoedit, these
operators are expected to work with the original semantics.
<p>
So far I've seen redefinitions for:
<p>
<ul compact>
<p>
<li>lt - "less-then" to mean "draw a line to"
</li>
<li>string - "create a string object" to mean "draw a string"
</li>
<li>length - "get the length of e.g. a string" to a "float constant"
<p>
</li>
</ul>
<p>
I've included work-arounds for the ones mentioned above, but some others
could show up in addition to those.
<p>
<h2><a name="section_94">RESTRICTIONS</a></h2>
<p>
<ul compact>
<li>Non-standard fonts (e.g. TeXbitmap fonts) are mapped to a default font which
can be changed using the <b>-df</b>
option. <tt>pstoedit</tt>
chooses the size of
the replacement font such that the width of the string in the original font is
the same as in the replacement font. This is done for each text fragment
displayed. Special character encoding support is limited in this case. If a
character cannot be mapped into the target format, pstoedit displays a '#'
instead. See also the -uchar option.
<p>
</li>
<li>pstoedit supports bitmap graphics only for some output format drivers.
<p>
</li>
<li>Some output format drivers, e.g. the Gnuplot output format driver or the 3D output format driver (rpl, lwo, rib) do not support text.
<p>
</li>
<li>For most output format drivers pstoedit does not support clipping (mainly due to limitations in the target format). You can try to use the
<b>-sclip</b>
option to simulate clipping. However, this doesn't work in all cases
as expected.
<p>
</li>
<li>Special note about the Java output format drivers (java1 and java2).
The java output format drivers generate a java source file that needs other files in
order to be compiled and usable. These other files are Java classes (one
applet and support classes) that allow to step through the individual pages
of a converted PostScript document. This applet can easily be activated from
a html-document. See the <tt>contrib/java/java1/readme_java1.txt</tt>
or
<tt>contrib/java/java2/readme_java2.htm</tt>
file for more details.
<p>
</li>
</ul>
<p>
<h2><a name="section_95">FAQs</a></h2>
<p>
<ol compact>
<li value =1>Why do letters like O or B get strange if converted to tgif/xfig
using the <b>-dt</b>
option?
<p>
This is because most output format drivers don't support composite paths with
intermediate gaps (moveto's) and second don't support very well the (eo)fill
operators of PostScript (winding rule). For such objects <tt>pstoedit</tt>
breaks
them into smaller objects whenever such a gap is found. This results in the
"hole" beeing filled with black color instead of beeing transparent. Since
version 3.11 you can try the <b>-ssp</b>
option in combination with the xfig
output format driver.
<p>
</li>
<li value =2>Why does pstoedit produce ugly results from PostScript files generated
by dvips?
<p>
TeX documents usually use bitmap fonts. Such fonts cannot be used as native
font in other format. So pstoedit replaces the TeX font with another native
font. Of course, the replacement font will in most cases produce another
look, especially if mathematical symbols are used.
Try to use PostScript fonts instead of the bitmap fonts when generating a PostScript file from TeX or LaTeX.
<p>
</li>
</ol>
<p>
<h2><a name="section_96">AUTHOR</a></h2>
<p>
Wolfgang Glunz, <a href ="mailto:wglunz35_AT_pstoedit.net"><tt>wglunz35_AT_pstoedit.net</tt></a>,
<a href ="http://de.linkedin.com/in/wolfgangglunz"><tt>http://de.linkedin.com/in/wolfgangglunz</tt></a>
<p>
<h2><a name="section_97">CANONICAL ARCHIVE SITE</a></h2>
<p>
<a href ="http://www.pstoedit.net/pstoedit/"><tt>http://www.pstoedit.net/pstoedit/</tt></a>
<p>
At this site you also find more information about <tt>pstoedit</tt>
and related
programs and hints how to subscribe to a mailing list in order to get informed
about new releases and bug-fixes.
<p>
If you like pstoedit - please express so also at Facebook <a href ="http://www.facebook.com/pages/pstoedit/260606183958062"><tt>http://www.facebook.com/pages/pstoedit/260606183958062</tt></a>.
<p>
<h2><a name="section_98">ACKNOWLEDGEMENTS</a></h2>
<p>
<ul compact>
<p>
<li>Klaus Steinberger <a href ="mailto:Klaus.Steinberger_AT_physik.uni-muenchen.de"><tt>Klaus.Steinberger_AT_physik.uni-muenchen.de</tt></a>
wrote the initial version of this manpage.
<p>
</li>
<li>Lar Kaufman revised the increasingly complex
command syntax diagrams and updated the structure and content of this
manpage following release 2.5.
<p>
</li>
<li>David B. Rosen <a href ="mailto:rosen_AT_unr.edu"><tt>rosen_AT_unr.edu</tt></a> provided ideas and some PostScript
code from his ps2aplot program.
<p>
</li>
<li>Ian MacPhedran <a href ="mailto:Ian_MacPhedran_AT_engr.USask.CA"><tt>Ian_MacPhedran_AT_engr.USask.CA</tt></a> provided the xfig
output format driver.
<p>
</li>
<li>Carsten Hammer <a href ="mailto:chammer_AT_hermes.hrz.uni-bielefeld.de"><tt>chammer_AT_hermes.hrz.uni-bielefeld.de</tt></a> provided the
gnuplot output format driver and the initial DXF output format driver.
<p>
</li>
<li>Christoph Jaeschke provided the OS/2 metafile (MET) output format driver.
Thomas Hoffmann <a href ="mailto:thoffman_AT_zappa.sax.de"><tt>thoffman_AT_zappa.sax.de</tt></a>
did some further updates on the OS/2 part.
<p>
</li>
<li>Jens Weber <a href ="mailto:rz47b7_AT_PostAG.DE"><tt>rz47b7_AT_PostAG.DE</tt></a> provided the Windows metafile (WMF)
output format driver, and a graphical user interface (GUI).
<p>
</li>
<li>G. Edward Johnson <a href ="mailto:lorax_AT_nist.gov"><tt>lorax_AT_nist.gov</tt></a> provided the CGM Draw library
used in the CGM output format driver.
<p>
</li>
<li>Gerhard Kircher <a href ="mailto:kircher_AT_edvz.tuwien.ac.at"><tt>kircher_AT_edvz.tuwien.ac.at</tt></a> provided some bug
fixes.
<p>
</li>
<li>Bill Cheng <a href ="mailto:bill.cheng_AT_acm.org"><tt>bill.cheng_AT_acm.org</tt></a> provided help with the tgif
format and some changes to tgif to make the output format driver easier to implement.
<a href ="http://bourbon.usc.edu:8001/"><tt>http://bourbon.usc.edu:8001/</tt></a>
<p>
</li>
<li>Reini Urban <a href ="mailto:rurban_AT_sbox.tu-graz.ac.at"><tt>rurban_AT_sbox.tu-graz.ac.at</tt></a> provided input for the
extended DXF output format driver.(<a href ="http://autocad.xarch.at/"><tt>http://autocad.xarch.at/</tt></a>)
<p>
</li>
<li>Glenn M. Lewis <a href ="mailto:glenn_AT_gmlewis.com"><tt>glenn_AT_gmlewis.com</tt></a> provided RenderMan (RIB),
Real3D (RPL), and LightWave 3D (LWO) output format drivers.
(<a href ="http://www.gmlewis.com/"><tt>http://www.gmlewis.com/</tt></a>)
<p>
</li>
<li>Piet van Oostrum <a href ="mailto:piet_AT_cs.ruu.nl"><tt>piet_AT_cs.ruu.nl</tt></a> made several bug fixes.
<p>
</li>
<li>Lutz Vieweg <a href ="mailto:lkv_AT_mania.robin.de"><tt>lkv_AT_mania.robin.de</tt></a> provided several bug fixes and
suggestions for improvements.
<p>
</li>
<li>Derek B. Noonburg <a href ="mailto:derekn_AT_vw.ece.cmu.edu"><tt>derekn_AT_vw.ece.cmu.edu</tt></a> and Rainer Dorsch
<a href ="mailto:rd_AT_berlepsch.wohnheim.uni-ulm.de"><tt>rd_AT_berlepsch.wohnheim.uni-ulm.de</tt></a>
isolated and resolved a
Linux-specific core dump problem.
<p>
</li>
<li>Rob Warner <a href ="mailto:rcw2_AT_ukc.ac.uk"><tt>rcw2_AT_ukc.ac.uk</tt></a> made pstoedit compile under RiscOS.
<p>
</li>
<li>Patrick Gosling <a href ="mailto:jpmg_AT_eng.cam.ac.uk"><tt>jpmg_AT_eng.cam.ac.uk</tt></a> made some suggestions
regarding the usage of pstoedit in Ghostscript's SAFER mode.
<p>
</li>
<li>Scott Pakin <a href ="mailto:scott+ps2ed_AT_pakin.org"><tt>scott+ps2ed_AT_pakin.org</tt></a> for the Idraw output format driver and the
autoconf support.
<p>
</li>
<li>Peter Katzmann <a href ="mailto:p.katzmann_AT_thiesen.com"><tt>p.katzmann_AT_thiesen.com</tt></a> for the HPGL output format driver.
<p>
</li>
<li>Chris Cox <a href ="mailto:ccox_AT_airmail.net"><tt>ccox_AT_airmail.net</tt></a> contributed the Tcl/Tk output format driver.
<p>
</li>
<li>Thorsten Behrens <a href ="mailto:Thorsten_Behrens_AT_public.uni-hamburg.de"><tt>Thorsten_Behrens_AT_public.uni-hamburg.de</tt></a> and
Bjoern Petersen for reworking the WMF output format driver.
<p>
</li>
<li>Leszek Piotrowicz <a href ="mailto:leszek_AT_sopot.rodan.pl"><tt>leszek_AT_sopot.rodan.pl</tt></a> implemented the image
support for the xfig driver and a JAVA based GUI.
<p>
</li>
<li>Egil Kvaleberg <a href ="mailto:egil_AT_kvaleberg.no"><tt>egil_AT_kvaleberg.no</tt></a> contributed the pic output format driver.
<p>
</li>
<li>Kai-Uwe Sattler <a href ="mailto:kus_AT_iti.cs.uni-magdeburg.de"><tt>kus_AT_iti.cs.uni-magdeburg.de</tt></a> implemented the
output format driver for Kontour.
<p>
</li>
<li>Scott Pakin, <a href ="mailto:scott+ps2ed_AT_pakin.org"><tt>scott+ps2ed_AT_pakin.org</tt></a> provided the MetaPost and LaTeX2e and PowerPoint output format driver.
<p>
</li>
<li>The PowerPoint driver uses the libzip library - <a href ="http://www.nih.at/libzip"><tt>http://www.nih.at/libzip</tt></a>. Under Windows, this library is linked into the provided binary statically. Thanks to the whole libzip team.
<p>
</li>
<li>Burkhard Plaum <a href ="mailto:plaum_AT_IPF.Uni-Stuttgart.de"><tt>plaum_AT_IPF.Uni-Stuttgart.de</tt></a> added support for
complex filled paths for the xfig output format driver.
<p>
</li>
<li>Bernhard Herzog <a href ="mailto:herzog_AT_online.de"><tt>herzog_AT_online.de</tt></a> contributed the output format driver for
sketch ( <a href ="http://www.skencil.org/"><tt>http://www.skencil.org/</tt></a>
)
<p>
</li>
<li>Rolf Niepraschk (<a href ="mailto:niepraschk_AT_ptb.de"><tt>niepraschk_AT_ptb.de</tt></a>) converted the HTML man page
to LaTeX. This allows to generate the UNIX style and the HTML manual from this
base format.
<p>
</li>
<li>Several others sent smaller bug fixed and bug reports. Sorry if I don't
mention them all here.
<p>
</li>
<li>Gisbert W. Selke (<a href ="mailto:gisbert_AT_tapirsoft.de"><tt>gisbert_AT_tapirsoft.de</tt></a>) for the Java 2 output format driver.
<p>
</li>
<li>Robert S. Maier (<a href ="mailto:rsm_AT_math.arizona.edu"><tt>rsm_AT_math.arizona.edu</tt></a>) for many improvements on
the libplot output format driver and for libplot itself.
</li>
<li>The authors of pstotext (<a href ="mailto:mcjones_AT_pa.dec.com"><tt>mcjones_AT_pa.dec.com</tt></a> and <a href ="mailto:birrell_AT_pa.dec.com"><tt>birrell_AT_pa.dec.com</tt></a>)
for giving me the permission to use their simple PostScript code for
performing rotation.
</li>
<li>Daniel Gehriger <a href ="mailto:gehriger_AT_linkcad.com"><tt>gehriger_AT_linkcad.com</tt></a> for his help concerning the handling of Splines in the DXF format.
</li>
<li>Allen Barnett <a href ="mailto:libemf_AT_lignumcomputing.com"><tt>libemf_AT_lignumcomputing.com</tt></a> for his work on the libEMF which allows to create WMF/EMF files under *nix systems.
</li>
<li>Dave <a href ="mailto:dave_AT_opaque.net"><tt>dave_AT_opaque.net</tt></a> for providing the libming which is a multiplatform library for generating SWF files.
</li>
<li>Masatake Yamoto for the introduction of autoconf, automake and libtool into pstoedit
</li>
<li>Bob Friesenhahn for his help and the building of the Magick++ API to ImageMagick.
</li>
<li>But most important: Peter Deutsch <a href ="mailto:ghost_AT_aladdin.com"><tt>ghost_AT_aladdin.com</tt></a> and Russell
Lang <a href ="mailto:gsview_AT_ghostgum.com.au"><tt>gsview_AT_ghostgum.com.au</tt></a>
for their help and answers regarding
GhostScript and gsview.
<p>
</li>
</ul>
<p>
<h2><a name="section_99">LEGAL NOTICES</a></h2>
<p>
Trademarks mentioned are the property of their respective owners.
<p>
Some code incorporated in the pstoedit package is subject to copyright or
other intellectual property rights or restrictions including attribution
rights. See the notes in individual files.
<p>
<tt>pstoedit</tt>
is controlled under the Free Software Foundation GNU Public
License (GPL). However, this does not apply to importps and the additional
plugins.
<p>
Aladdin Ghostscript is a redistributable software package with copyright
restrictions controlled by Aladdin Software.
<p>
<tt>pstoedit</tt>
has no other relation to Ghostscript besides calling it in a
subprocess.
<p>
The authors, contributors, and distributors of pstoedit are not responsible
for its use for any purpose, or for the results generated thereby.
<p>
Restrictions such as the foregoing may apply in other countries according to
international conventions and agreements.
<p>
</body>
</html>
<!-- NOTE: This file is generated, DO NOT EDIT. -->
distrib
>
Mageia
>
5
>
i586
>
media
>
core-release
>
by-pkgid
>
46eb736e6359990330414f07e8f18852
>
files
>
20
