1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<!-- Manual page created with latex2man on Son Dez 30 21:33:28 CET 2001 --
-- Author of latex2man: Juergen.Vollmer@acm.org --
-- 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>2001/12/30</h4>
<h4 align=center>Version 3.31</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>
<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>
<li><a href="#section_10">Options </a></li>
<li><a href="#section_11">BACK END-SPECIFIC OPTIONS </a>
<ul>
<li><a href="#section_12">NOTES </a></li>
<li><a href="#section_13">ENVIRONMENT VARIABLES </a></li>
<li><a href="#section_14">SYSTEM SPECIFIC NOTES </a></li>
<li><a href="#section_15">TROUBLE SHOOTING </a></li>
<li><a href="#section_16">RESTRICTIONS </a></li>
<li><a href="#section_17">FAQs </a></li>
<li><a href="#section_18">NOTICES </a></li>
<li><a href="#section_19">AUTHOR </a></li>
<li><a href="#section_20">CANONICAL ARCHIVE SITE </a></li>
<li><a href="#section_21">ACKNOWLEDGEMENTS </a></li>
<li><a href="#section_22">LEGAL NOTICES </a></li>
</ul>
</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> ]
<p>
<tt>pstoedit</tt>
[ <b>-adt</b> ]
[ <b>-df</b><i> fontname</i> ]
[ <b>-dis</b> ]
[ <b>-dt</b> ]
[ <b>-flat</b><i> number</i> ]
[ <b>-fontmap</b><i> file</i> ]
[ <b>-include</b><i> includefile</i> ]
[ <b>-merge</b> ]
[ <b>-nb</b> ]
[ <b>-nfr</b> ]
[ <b>-nomaptoisolatin1</b> ]
[ <b>-nq</b> ]
[ <b>-page</b><i> number</i> ]
[ <b>-pagesize</b><i> string</i> ]
[ <b>-psarg</b><i> string</i> ]
[ <b>-pti or -pta</b> ]
[ <b>-rgb</b> ]
[ <b>-rotate</b><i> angle (0-360)</i> ]
[ <b>-scale</b><i> factor</i> ]
[ <b>-sclip</b> ]
[ <b>-ssp</b> ]
[ <b>-split</b> ]
[ <b>-t2fontsast1</b> ]
[ <b>-uchar</b><i> character</i> ]
[ <b>-v</b> ]
<b>-f</b><i> "format[:options]"</i>
[<i>inputfile</i>
[ <i>outputfile</i> ]]
<p>
<tt>pstoedit</tt>
[ <b>-scale</b><i> factor</i> ]
<b>-f</b><i> "format[:options]"</i>
<b>-bo</b>
<i>input-file</i>
[ <i>output-file</i> ]
<p>
<h4><a name="section_3">From Gsview</a></h4>
<p>
From within gsview pstoedit can be called 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 95/97,2000, 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.31 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.
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 two basic painting operators of
PostScript, <strong>stroke</strong>
and <strong>show</strong>
(bitmaps drawn by the image
operator are not supported by all backends.) 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" processing
of prepared files by specifying the <b>-bo</b>
option for debugging or limited
filtering. See "BACK END-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 back end driver, or 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 4.03 or later is
recommended for processing PDF (and PostScript Level 2) files.
<p>
<h2><a name="section_10">Options</a></h2>
<p>
<dl compact>
<p>
<dt><b>-dt</b>
<dd> Draw text - Text is drawn as polygons. This might produce a large output file. This option is automatically
switched on if the selected backend does not support this, e.g.
<em>gnuplot</em>(1).
<p>
</dd>
<dt><b>-adt</b>
<dd> Automatic Draw text - This option turns on the -dt option selectively for fonts that seem to be no normal text fonts, e.g. Symbol..
<p>
</dd>
<dt><b>-t2fontsast1</b>
<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>-pti or -pta</b>
<dd> Precision text - 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. 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 backends of
pstoedit. They cannot represent text with arbitray inter-letter spacing which is easily
possible in PDF and PostScript. The downside of "precision text" is a bigger file size and hard to edit
text.
<p>
</dd>
<dt><b>-nfr</b>
<dd> In normal mode pstoedit replaces bitmap fonts with a font as defined by the <b>-df</b>
option. This is done, because most backends 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>-dis</b>
<dd> Open a display during processing by Ghostscript. Some files
only work correctly this way.
<p>
</dd>
<dt><b>-psarg</b><i> string</i>
<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 <b>-display</b>
is set.)
<p>
</dd>
</dl>
<p>
You can switch Ghostscript into PostScript Level 1 only mode by
<b>-psarg "level1.ps"</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.
<p>
If you want to pass multiple options to Ghostscript you must 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>
<dl compact>
<p>
<dt><b>-merge</b>
<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, 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>-merge</b>.
<p>
</dd>
<dt><b>-page</b><i> page number</i>
<dd>Select a single page from a multi page
PostScript or PDF file.
<p>
</dd>
<dt><b>-rotate</b><i> angle (0-360)</i>
<dd>Rotage image by angle.
<p>
</dd>
<dt><b>-rgb</b>
<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>-split</b>
<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 backends that don't
support multiple pages within one file, e.g. fig or gnuplot.
<p>
</dd>
<dt><b>-uchar</b><i> character</i>
<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>-df</b><i> fontname</i>
<dd> Sometimes fonts embedded in a PostScript
programs 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>-include</b><i> name of a PostScript file to be included</i>
<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>-fontmap</b><i> name of font map file for pstoedit</i>
<dd> The font map is a
simple text file containing lines in the following format:
<p>
<tt>document_font_name target_font_name</tt> <br>
<tt>% lines beginning with </tt> <tt>% are comments</tt> <br>
<tt>% if a font name contains spaces, use</tt> <br>
<tt>% the "font name with spaces" notation.</tt>
<p>
Each font name found in the document is checked agains 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>
<tt><</tt>
<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 TeX
equivalents. 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 backend are provided by Scott Pakin
(<a href ="mailto:pakin@cs.uiuc.edu"><tt>pakin@cs.uiuc.edu</tt></a>).
<p>
Another example is wemf.fmp to be used under Windows. See the misc
directory of the pstoedit distribution.
<p>
</dd>
<dt><b>-f</b><i> format</i>
<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 "BACK
END-SPECIFIC OPTIONS" below for an explanation of the [ <i>:options</i> ]
to
<b>-f</b>
format.
<p>
</dd>
<dt><b>-scale</b><i> factor</i>
<dd> scale by the specified factor. (Currently used with
<b>-f tgif</b>
backend only.)
<p>
</dd>
<dt><b>-ssp</b>
<dd> simulate sub paths <br>
Several backend 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 backends. 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>-sclip</b>
<dd> simulate clipping <br>
Most backends 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 backends. However, this
results in curves being replaces 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>
<dt><b>-pagesize</b><i>string</i>
<dd> set page size for output medium <br>
This option sets the page size for the output medium. Currently this
is just used by the libplot backend, but might be used by other
backends in future. The page size is specified in terms of the usual
page size names, e.g. letter or a4.
<p>
</dd>
<dt><b>-bo</b>
<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>-flat</b><i> number</i>
<dd> If the backend 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>-nb</b>
<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. 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>-nc</b>
<dd> no curves <br>
Normally pstoedit tries to keep curves from the input and transfers them to
the output if the output format supports curves. If the backend 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 backends that originally support curves. This
can be forced via the <b>-nc</b>
option.
<p>
</dd>
<dt><b>-nq</b>
<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>
<dd> Switch on verbose mode. Some additional information is shown
during processing.
<p>
</dd>
<dt><b>-nomaptoisolatin1</b>
<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.
<p>
</dd>
<dt><i>input-file</i>
<dd> input file. If a "-" is given, standard input is used.
<p>
</dd>
<dt><i>output-file</i>
<dd> output file. If no output file or "-" is given as argument,
<tt>pstoedit</tt>
writes the result to standard output.
<p>
</dd>
</dl>
<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.
<p>
<h2><a name="section_11">BACK END-SPECIFIC OPTIONS</a></h2>
<p>
<tt>pstoedit</tt>
allows you to pass individual options to a backend. 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 backend, 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>
<p>
The following description is it not up to date at the moment. Sorry! Please use the above command
to get a current list of options supported by the specific format.
<p>
Currently <em>met</em>,
<em>java</em>,
<em>dxf</em>,
<em>pic</em>,
<em>fig</em>,
<em>metapost</em>,
<em>LaTeX2e</em>,
<em>mif</em>,
<em>emf</em>,
and <em>wmf</em>
are the only drivers accepting specific options.
Other options may be asserted through environment variables. See "ENVIRONMENT
VARIABLES" below.
<p>
The <em>wmf</em>
and the <em>emf</em>
driver supports the following backend specific options:
<p>
<dl compact>
<p>
<dt><b>-f wmf:m</b>
<dd> Maps all fonts in the document to Arial (should be
available on every Windows installation)
</dd>
<dt><b>-f wmf:n</b>
<dd> Emulate narrow fonts by shrinking fonts horizontally
(sometimes does not look that good, but it's the only chance, when
requested font weight is not available. And this is quite common for
off-the-shelf Windows installations)
</dd>
<dt><b>-f wmf:b</b>
<dd> DON'T draw two white border pixel (upper left and lower
right corner). They are normally drawn to keep content always within
bounding box (is sometimes clipped otherwise, i.e. Windows doesn't
respect pen thickness or rotated text extents).
This could be done more smarter for EMF, have to figure out...
<p>
</dd>
</dl>
<p>
The <em>java</em>
backend allows to specify the class name of the class that is
generated by pstoedit. The default is PSJava. You can change this using
<p>
<dl compact>
<p>
<dt><b>-f java:</b><i>anothername</i>
<dd>
<p>
</dd>
</dl>
<p>
The <em>dxf</em>
backend accepts the option <b>-lines</b>
which forces all
polygons and lines to be represented as LINEs in the generated DXF file. The
default is to use POLYLINEs.
<p>
Example:
<strong>-f</strong><strong> "</strong><strong>dxf:-lines</strong><strong>"</strong>
<p>
The <em>met</em>
backend allows the following single character options (without a
leading -)
<p>
<dl compact>
<p>
<dt><b>p</b>
<dd> Draw no geometric linewidths, all lines have a width of zero.
</dd>
<dt><b>l</b>
<dd> No filling of polygon interiors.
</dd>
<dt><b>c</b>
<dd> No colors, just greyscales.
</dd>
<dt><b>t</b>
<dd> Omit all text.
</dd>
<dt><b>g</b>
<dd> Omit all graphics.
</dd>
<dt><b>v</b>
<dd> Put verbose output to <tt>STDERR</tt>.
<p>
</dd>
</dl>
<p>
Example:
<strong>-f</strong><strong> "</strong><strong>met:lc</strong><strong>"</strong>
<p>
The <em>pic</em>
backend accepts the options:
<p>
<dl compact>
<p>
<dt><b>-troff</b>
<dd>
</dd>
<dt><b>-groff</b>
<dd>
which forces output to be compatible with troff and groff,
respectively. Groff mode is default, troff mode severely limiting
the choice of supported text fonts.
<p>
BUG: these options really does not belong in a backend
<p>
</dd>
<dt><b>-keep</b>
<dd>
makes the pic backend emit the full font name of fonts that does
not map to built-in groff fonts.
<p>
</dd>
<dt><b>-text</b>
<dd>
makes the pic backend attempt to recognize running text, and
treat it accordingly.
<p>
</dd>
<dt><b>-landscape</b>
<dd>
</dd>
<dt><b>-portrait</b>
<dd>
to compensate for the postscript orientation. Portrait mode is
default.
<p>
Example:
<strong>-f</strong><strong> "</strong><strong>pic:-troff -text -landscape</strong><strong>"</strong>
<p>
</dd>
</dl>
<p>
The <em>fig</em>
driver accepts the following options:
<p>
<dl compact>
<p>
<dt><b>-startdepth</b>
<dd>
Fig knows about 999 layers (0 is the topmost, 999 the backmost). Per
default, pstoedit starts with layer 999 and then places all subsequent
objects on lower layers (on top of the previous objects). This can result
in problems if you want to put something "below" all the objects that
were created by pstoedit. In such a case you should define a lower number
to leave some space behind.
<p>
</dd>
<dt><b>-depth</b>
<dd>
depth in inches. Sets the paper width to the specified size in inches.
<p>
</dd>
</dl>
<p>
The <em>ps2ai</em>
driver provides an option to select to old AI-88 format
instead of the default AI-3
<p>
<dl compact>
<p>
<dt><b>-88</b>
<dd> selects the AI-88 format.
<p>
Example: <b>-f ps2ai:-88</b>
<p>
</dd>
</dl>
<p>
The <em>tgif</em>
driver provides option to control the conversion of text
strings into hyperlink attributes.
<p>
<dl compact>
<p>
<dt><b>-ta</b>
<dd>
enables the conversion of text into boxes with hyperlink attributes. More
options allowing finer control about this new feature will follow in
future versions.
<p>
</dd>
</dl>
<p>
The <em>tk</em>
driver supports the following backend specific options:
<p>
<dl compact>
<p>
<dt><b>-f tk:I</b>
<dd> Disables ImPress specific formatting. Only canvas
objects will be output.
</dd>
<dt><b>-f tk:N tagname</b>
<dd> Adds a specific tag to all objects. If ImPress
formatting is enabled, the items will be grouped.
</dd>
<dt><b>-f tk:n tagname</b>
<dd> Deprecated option. Behaves like N.
</dd>
<dt><b>-f tk:R</b>
<dd> If ImPress formatting is enabled, swap the Width and
Height associated with the pagesize.
<p>
</dd>
</dl>
<p>
The <em>mif</em>
backend allows the following options:
<p>
<dl compact>
<p>
<dt><b>-f mif:-nopage</b>
<dd> Generates an anchored frame instead of a full page.
This is useful, if you want to insert a figure into an existing document.
<p>
</dd>
<dt><b>-f mif:-imagesaspng</b>
<dd> Bitmap images are written as PNG files instead
of EPS. This is still experimental but should work for non rotated bitmaps.
<p>
</dd>
</dl>
<p>
The GNU libplot driver (<em>gmfa</em>,
<em>gmfb</em>,
<em>plot</em>)
provides a huge
set of options. All these are described in the header of the drvlplot.cpp file.
<p>
<h4><a name="section_12">NOTES</a></h4>
<p>
<dl compact>
<p>
<dt>autotrace:
<dd>
<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>
</dd>
<dt>Ps2ai:
<dd>
<p>
The ps2ai backend is not a native pstoedit backend. 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>
If you have a version of GhostScript older than 5.60, then
you have to apply the following simple patch to the
<tt>ps2ai.ps</tt>
file in order to make this driver work.
This patch is already included in newer versions of GhostScript.
<p>
After the line "<tt>/vers {2.13} def</tt>" insert:
<p>
<tt>/cdef { 1 index where { pop pop pop } { def } ifelse } def</tt>
<p>
Replace the lines:
<p>
"<tt>/jout false def</tt>"
<p>
with
<p>
"<tt>/jout false cdef</tt>"
<p>
(notice the cdef instead of def)
<p>
"<tt>/joutput (ps2ai.out.aips) def</tt>"
<p>
with
<p>
"<tt>/joutput (ps2ai.out.aips) cdef</tt>"
<p>
"<tt>/joutln false def</tt>"
<p>
with
<p>
"<tt>/joutln false cdef</tt>"
<p>
and the line
<p>
"<tt>/jtxt3 true def</tt>"
<p>
with
<p>
"<tt>/jtxt3 true cdef</tt>"
<p>
Note: If you already patched <em>ps2ai</em>
for pstoedit version 3.02. you
have to change to the patch above. This version is different but it better
fits the ideas of Peter L. Deutsch. Sorry for the confusion, but this way
chances are better that this version will go into the GhostScript
distribution.
<p>
</dd>
<dt>MetaPost:
<dd>
<p>
Note that, as far as Scott knows, MetaPost does not support PostScript's
eofill. My backend 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>
</dd>
<dt>LaTeX2e:
<dd> <br>
<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 backend 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 backend currently supports one backend-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 backend 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 backend -- hyperlinks to the
surrounding document (with help from the hyperref package).
</li>
</ul>
<p>
</dd>
<dt>creating a new backend:
<dd>
<p>
To implement a new backend 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 backend.
<p>
</dd>
</dl>
<p>
<h4><a name="section_13">ENVIRONMENT VARIABLES</a></h4>
<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>
<h4><a name="section_14">SYSTEM SPECIFIC NOTES</a></h4>
<p>
<dl compact>
<p>
<dt>DOS/WINDOWS
<dd>
<p>
pstoedit compiled with MS-Visual C++ or Borland C++ runs under 32-bit
only. It might run under WIN32s, but certainly does not run under plain
16-bit DOS.
<p>
<tt>pstoedit</tt>
works best if you installed at least version 5.50 of
GhostScript and version 2.72 of gsview. Using older version of
GhostScript is possible but requires the setting of some environment
variables.
<p>
</dd>
</dl>
<p>
<h4><a name="section_15">TROUBLE SHOOTING</a></h4>
<p>
If you have problems with <tt>pstoedit</tt>
first try whether Ghostscript
successfully displays your file. If yes 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 backend 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>
<h4><a name="section_16">RESTRICTIONS</a></h4>
<p>
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>
pstoedit supports bitmap graphics only for some backends.
<p>
The Gnuplot backend and the 3D backends (rpl, lwo, rib) do not support text.
<p>
Generally, pstoedit does not support clipping. You can try to use the
<b>-sclip</b>
option to simulate clipping. However, this doesn't work in all cases
as expected.
<p>
Special note about the Java backends (java1 and java2)
<p>
The java backends 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>java/java1/readme_java1.txt</tt>
or
<tt>java/java2/readme_java2.htm</tt>
file for more details.
<p>
<h4><a name="section_17">FAQs</a></h4>
<p>
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 backends 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
backend.
<p>
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.
<p>
<h4><a name="section_18">NOTICES</a></h4>
<p>
<h4><a name="section_19">AUTHOR</a></h4>
<p>
Wolfgang Glunz, <a href ="mailto:wglunz@pstoedit.net"><tt>wglunz@pstoedit.net</tt></a>
<p>
<h4><a name="section_20">CANONICAL ARCHIVE SITE</a></h4>
<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>
<h4><a name="section_21">ACKNOWLEDGEMENTS</a></h4>
<p>
<ul compact>
<p>
<li>Klaus Steinberger <a href ="mailto:Klaus.Steinberger@physik.uni-muenchen.de"><tt>Klaus.Steinberger@physik.uni-muenchen.de</tt></a>
wrote the initial version of this manpage.
<p>
</li>
<li>Lar Kaufman <a href ="mailto:lark@walden.com"><tt>lark@walden.com</tt></a> revised the increasingly complex
command syntax diagrams and updated the structure and content of this
manpage following release 2.5. (<a href ="http://www.walden.com/ lark/"><tt>http://www.walden.com/ lark/</tt></a>)
<p>
</li>
<li>David B. Rosen <a href ="mailto:rosen@unr.edu"><tt>rosen@unr.edu</tt></a> provided ideas and some PostScript
code from his ps2aplot program.
<p>
</li>
<li>Ian MacPhedran <a href ="mailto:Ian_MacPhedran@engr.USask.CA"><tt>Ian_MacPhedran@engr.USask.CA</tt></a> provided the xfig
backend.
<p>
</li>
<li>Carsten Hammer <a href ="mailto:chammer@hermes.hrz.uni-bielefeld.de"><tt>chammer@hermes.hrz.uni-bielefeld.de</tt></a> provided the
gnuplot backend and the initial DXF backend.
<p>
</li>
<li>Christoph Jaeschke provided the OS/2 metafile (MET) backend.
Thomas Hoffmann <a href ="mailto:thoffman@zappa.sax.de"><tt>thoffman@zappa.sax.de</tt></a>
did some further updates on the OS/2 part.
<p>
</li>
<li>Jens Weber <a href ="mailto:rz47b7@PostAG.DE"><tt>rz47b7@PostAG.DE</tt></a> provided the Windows metafile (WMF)
backend, and a graphical user interface (GUI).
<p>
</li>
<li>G. Edward Johnson <a href ="mailto:lorax@nist.gov"><tt>lorax@nist.gov</tt></a> provided the CGM Draw library
used in the CGM backend.
<p>
</li>
<li>Gerhard Kircher <a href ="mailto:kircher@edvz.tuwien.ac.at"><tt>kircher@edvz.tuwien.ac.at</tt></a> provided some bug
fixes.
<p>
</li>
<li>Bill Cheng <a href ="mailto:william@cs.columbia.edu"><tt>william@cs.columbia.edu</tt></a> provided help with the tgif
format and some changes to tgif to make the backend easier to implement.
URL:<a href ="http://www.cs.columbia.edu/ william"><tt>http://www.cs.columbia.edu/ william</tt></a>
<p>
</li>
<li>Reini Urban <a href ="mailto:rurban@sbox.tu-graz.ac.at"><tt>rurban@sbox.tu-graz.ac.at</tt></a> provided input for the
extended DXF backend.(<a href ="http://xarch.tu-graz.ac.at/autocad/"><tt>http://xarch.tu-graz.ac.at/autocad/</tt></a>)
<p>
</li>
<li>Glenn M. Lewis <a href ="mailto:glenn@gmlewis.com"><tt>glenn@gmlewis.com</tt></a> provided RenderMan (RIB),
Real3D (RPL), and LightWave 3D (LWO) backends.
(<a href ="http://www.gmlewis.com/"><tt>http://www.gmlewis.com/</tt></a>)
<p>
</li>
<li>Piet van Oostrum <a href ="mailto:piet@cs.ruu.nl"><tt>piet@cs.ruu.nl</tt></a> made several bug fixes.
<p>
</li>
<li>Lutz Vieweg <a href ="mailto:lkv@mania.robin.de"><tt>lkv@mania.robin.de</tt></a> provided several bug fixes and
suggestions for improvements.
<p>
</li>
<li>Derek B. Noonburg <a href ="mailto:derekn@vw.ece.cmu.edu"><tt>derekn@vw.ece.cmu.edu</tt></a> and Rainer Dorsch
<a href ="mailto:rd@berlepsch.wohnheim.uni-ulm.de"><tt>rd@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@ukc.ac.uk"><tt>rcw2@ukc.ac.uk</tt></a> made pstoedit compile under RiscOS.
<p>
</li>
<li>Patrick Gosling <a href ="mailto:jpmg@eng.cam.ac.uk"><tt>jpmg@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:pakin@cs.uiuc.edu"><tt>pakin@cs.uiuc.edu</tt></a> for the Idraw backend and the
autoconf support.
<p>
</li>
<li>Peter Katzmann <a href ="mailto:p.katzmann@thiesen.com"><tt>p.katzmann@thiesen.com</tt></a> for the HPGL backend.
<p>
</li>
<li>Chris Cox <a href ="mailto:ccox@airmail.net"><tt>ccox@airmail.net</tt></a> contributed the Tcl/Tk backend.
<p>
</li>
<li>Thorsten Behrens <a href ="mailto:Thorsten_Behrens@public.uni-hamburg.de"><tt>Thorsten_Behrens@public.uni-hamburg.de</tt></a> and
Bjoern Petersen for reworking the WMF backend.
<p>
</li>
<li>Leszek Piotrowicz <a href ="mailto:leszek@sopot.rodan.pl"><tt>leszek@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@kvaleberg.no"><tt>egil@kvaleberg.no</tt></a> contributed the pic backend.
<p>
</li>
<li>Kai-Uwe Sattler <a href ="mailto:kus@iti.cs.uni-magdeburg.de"><tt>kus@iti.cs.uni-magdeburg.de</tt></a> implemented the
backend for Kontour.
<p>
</li>
<li>Scott Pakin, pakin@cs.uiuc.edu provided the MetaPost and LaTeX2e backend.
<p>
</li>
<li>Burkhard Plaum (<a href ="mailto:plaum@IPF.Uni-Stuttgart.de"><tt>plaum@IPF.Uni-Stuttgart.de</tt></a>) added support for
complex filled paths for the xfig backend.
<p>
</li>
<li>Bernhard Herzog (<a href ="mailto:herzog@online.de"><tt>herzog@online.de</tt></a>) contributed the backend for
sketch ( <a href ="http://sketch.sourceforge.net/"><tt>http://sketch.sourceforge.net/</tt></a>
)
<p>
</li>
<li>Rolf Niepraschk (<a href ="mailto:niepraschk@ptb.de"><tt>niepraschk@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@tapirsoft.de"><tt>gisbert@tapirsoft.de</tt></a>) for the Java 2 backend.
<p>
</li>
<li>Robert S. Maier (<a href ="mailto:rsm@math.arizona.edu"><tt>rsm@math.arizona.edu</tt></a>) for many improvements on
the libplot backend and for libplot itself.
</li>
<li>The authors of pstotext (<a href ="mailto:mcjones@pa.dec.com"><tt>mcjones@pa.dec.com</tt></a> and <a href ="mailto:birrell@pa.dec.com"><tt>birrell@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@linkcad.com"><tt>gehriger@linkcad.com</tt></a> for his help concerning the handling of Splines in the DXF format.
</li>
<li>Allen Barnett <a href ="mailto:libemf@lignumcomputing.com"><tt>libemf@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@opaque.net"><tt>dave@opaque.net</tt></a> for providing the libming which is a multiplatform library for generating SWF files.
</li>
<li>But most important: Peter Deutsch <a href ="mailto:ghost@aladdin.com"><tt>ghost@aladdin.com</tt></a> and Russell
Lang <a href ="mailto:gsview@ghostgum.com.au"><tt>gsview@ghostgum.com.au</tt></a>
for their help and answers regarding
GhostScript and gsview.
<p>
</li>
</ul>
<p>
<h4><a name="section_22">LEGAL NOTICES</a></h4>
<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. -->
|
