│ │ │ - autotrace
│ │ │ - Ps2ai
│ │ │ - MetaPost
│ │ │ - Context Free - CFDG
│ │ │ @@ -1606,69 +1606,15 @@
│ │ │
│ │ │
│ │ │
│ │ │
│ │ │ 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. This binary of pstoedit was compiled against version 7.1.2 of ImageMagick.
│ │ │
│ │ │ No format specific options
│ │ │ -
│ │ │ -
│ │ │ -The following driver specific options are available:
│ │ │ -
│ │ │ -- [-m]
│ │ │ -
│ │ │ --
│ │ │ -
│ │ │ -map to Arial
│ │ │ -
│ │ │ -
│ │ │ -- [-nf]
│ │ │ -
│ │ │ --
│ │ │ -
│ │ │ -emulate narrow fonts
│ │ │ -
│ │ │ -
│ │ │ -- [-drawbb]
│ │ │ -
│ │ │ --
│ │ │ -
│ │ │ -draw bounding box
│ │ │ -
│ │ │ -
│ │ │ -- [-p]
│ │ │ -
│ │ │ --
│ │ │ -
│ │ │ -prune line ends
│ │ │ -
│ │ │ -
│ │ │ -- [-nfw]
│ │ │ -
│ │ │ --
│ │ │ -
│ │ │ -Newer versions of MS Windows (2000, XP, Vista, 7, ...) 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 MS 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 option 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 MS Windows anyway. In that case the output is portable but nevertheless not split and still looks fine.
│ │ │ -
│ │ │ -
│ │ │ -- [-winbb]
│ │ │ -
│ │ │ --
│ │ │ -
│ │ │ -let the MS Windows API calculate the Bounding Box (MS Windows only)
│ │ │ -
│ │ │ -
│ │ │ -- [-OO]
│ │ │ -
│ │ │ --
│ │ │ -
│ │ │ -generate OpenOffice compatible EMF file
│ │ │ -
│ │ │ -
│ │ │ -
│ │ │ -
│ │ │ +
│ │ │
│ │ │ This is the format used internally by Microsoft PowerPoint. LibreOffice can also read/write PowerPoint files albeit with some lack of functionality.
│ │ │
│ │ │ The following driver specific options are available:
│ │ │
│ │ │ - [-colors string]
│ │ │
│ │ │ @@ -1695,15 +1641,15 @@
│ │ │
│ │ │ -
│ │ │
│ │ │ do not remove the temporary PNG image files.
│ │ │
│ │ │
│ │ │
│ │ │ -
│ │ │ +
│ │ │
│ │ │ This group consists of the following variants:
│ │ │
│ │ │ - gmfa:
│ │ │ - ASCII GNU metafile.
│ │ │
│ │ │ - gmfb:
│ │ │ @@ -1746,14 +1692,68 @@
│ │ │
│ │ │ -
│ │ │
│ │ │ plotutil format to generate
│ │ │
│ │ │
│ │ │
│ │ │ +
│ │ │ +
│ │ │ +The following driver specific options are available:
│ │ │ +
│ │ │ +- [-m]
│ │ │ +
│ │ │ +-
│ │ │ +
│ │ │ +map to Arial
│ │ │ +
│ │ │ +
│ │ │ +- [-nf]
│ │ │ +
│ │ │ +-
│ │ │ +
│ │ │ +emulate narrow fonts
│ │ │ +
│ │ │ +
│ │ │ +- [-drawbb]
│ │ │ +
│ │ │ +-
│ │ │ +
│ │ │ +draw bounding box
│ │ │ +
│ │ │ +
│ │ │ +- [-p]
│ │ │ +
│ │ │ +-
│ │ │ +
│ │ │ +prune line ends
│ │ │ +
│ │ │ +
│ │ │ +- [-nfw]
│ │ │ +
│ │ │ +-
│ │ │ +
│ │ │ +Newer versions of MS Windows (2000, XP, Vista, 7, ...) 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 MS 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 option 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 MS Windows anyway. In that case the output is portable but nevertheless not split and still looks fine.
│ │ │ +
│ │ │ +
│ │ │ +- [-winbb]
│ │ │ +
│ │ │ +-
│ │ │ +
│ │ │ +let the MS Windows API calculate the Bounding Box (MS Windows only)
│ │ │ +
│ │ │ +
│ │ │ +- [-OO]
│ │ │ +
│ │ │ +-
│ │ │ +
│ │ │ +generate OpenOffice compatible EMF file
│ │ │ +
│ │ │ +
│ │ │ +
│ │ │
│ │ │
│ │ │
│ │ │
│ │ │
│ │ │
│ │ │ pstoedit cooperates with autotrace. Autotrace can now produce a dump file
│ │ │ ├── html2text {}
│ │ │ │ @@ -1,10 +1,10 @@
│ │ │ │ ************ PPSSTTOOEEDDIITT ************
│ │ │ │ ****** DDrr.. WWoollffggaanngg GGlluunnzz ******
│ │ │ │ - ****** 1144 DDeecceemmbbeerr 22002255 ******
│ │ │ │ + ****** 1166 MMaarrcchh 22002266 ******
│ │ │ │ ****** VVeerrssiioonn 44..33 ******
│ │ │ │ pstoedit - a tool converting PostScript files into various vector graphic
│ │ │ │ formats
│ │ │ │ ******** TTaabbllee ooff CCoonntteennttss ********
│ │ │ │ * _S_y_n_o_p_s_i_s
│ │ │ │ o _F_r_o_m_ _a_ _c_o_m_m_a_n_d_ _s_h_e_l_l
│ │ │ │ o _F_r_o_m_ _P_s_t_o_e_d_i_t_Q_t_G_u_i
│ │ │ │ @@ -53,18 +53,18 @@
│ │ │ │ o _g_n_u_p_l_o_t_ _-_ _g_n_u_p_l_o_t_ _f_o_r_m_a_t
│ │ │ │ o _t_g_i_f_ _-_ _T_g_i_f_ _._o_b_j_ _f_o_r_m_a_t
│ │ │ │ o _F_o_r_m_a_t_ _g_r_o_u_p_:_ _f_i_g_ _x_f_i_g_ _t_f_i_g
│ │ │ │ o _i_d_r_a_w_ _-_ _I_n_t_e_r_v_i_e_w_s_ _d_r_a_w_ _f_o_r_m_a_t_ _(_E_P_S_)
│ │ │ │ o _s_a_m_p_l_e_ _-_ _s_a_m_p_l_e_ _d_r_i_v_e_r
│ │ │ │ o _m_a_g_i_c_k_ _-_ _M_A_G_I_C_K_ _d_r_i_v_e_r_ _c_o_m_p_a_t_i_b_l_e_ _w_i_t_h_ _v_e_r_s_i_o_n_ _7_._1_._2_ _o_f
│ │ │ │ _I_m_a_g_e_M_a_g_i_c_k_.
│ │ │ │ - o _e_m_f_ _-_ _E_n_h_a_n_c_e_d_ _M_S_ _W_i_n_d_o_w_s_ _M_e_t_a_f_i_l_e
│ │ │ │ o _p_p_t_x_ _-_ _P_r_e_s_e_n_t_a_t_i_o_n_M_L_ _(_P_o_w_e_r_P_o_i_n_t_)_ _f_o_r_m_a_t
│ │ │ │ o _F_o_r_m_a_t_ _g_r_o_u_p_:_ _g_m_f_a_ _g_m_f_b_ _p_l_o_t_ _p_l_o_t_-_p_n_m_ _p_l_o_t_-_c_g_m_ _p_l_o_t_-_a_i_ _p_l_o_t_-_s_v_g
│ │ │ │ _p_l_o_t_-_p_s_ _p_l_o_t_-_f_i_g_ _p_l_o_t_-_p_c_l_ _p_l_o_t_-_h_p_g_l_ _p_l_o_t_-_t_e_k
│ │ │ │ + o _e_m_f_ _-_ _E_n_h_a_n_c_e_d_ _M_S_ _W_i_n_d_o_w_s_ _M_e_t_a_f_i_l_e
│ │ │ │ * _N_O_T_E_S_ _O_N_ _S_P_E_C_I_F_I_C_ _F_O_R_M_A_T_S_ _A_N_D_ _D_R_I_V_E_R_S
│ │ │ │ o _a_u_t_o_t_r_a_c_e
│ │ │ │ o _P_s_2_a_i
│ │ │ │ o _M_e_t_a_P_o_s_t
│ │ │ │ o _C_o_n_t_e_x_t_ _F_r_e_e_ _-_ _C_F_D_G
│ │ │ │ o _L_a_T_e_X_2_e
│ │ │ │ o _C_r_e_a_t_i_n_g_ _a_ _n_e_w_ _o_u_t_p_u_t_ _f_o_r_m_a_t_ _d_r_i_v_e_r
│ │ │ │ @@ -797,45 +797,14 @@
│ │ │ │ ****** mmaaggiicckk -- MMAAGGIICCKK ddrriivveerr ccoommppaattiibbllee wwiitthh vveerrssiioonn 77..11..22 ooff IImmaaggeeMMaaggiicckk.. ******
│ │ │ │ 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. This
│ │ │ │ binary of pstoedit was compiled against version 7.1.2 of ImageMagick.
│ │ │ │ No format specific options
│ │ │ │ -****** eemmff -- EEnnhhaanncceedd MMSS WWiinnddoowwss MMeettaaffiillee ******
│ │ │ │ -The following driver specific options are available:
│ │ │ │ - [--mm]
│ │ │ │ - map to Arial
│ │ │ │ - [--nnff]
│ │ │ │ - emulate narrow fonts
│ │ │ │ - [--ddrraawwbbbb]
│ │ │ │ - draw bounding box
│ │ │ │ - [--pp]
│ │ │ │ - prune line ends
│ │ │ │ - [--nnffww]
│ │ │ │ - Newer versions of MS Windows (2000, XP, Vista, 7, ...) 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 MS 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
│ │ │ │ - option 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 MS Windows anyway. In that case the output is
│ │ │ │ - portable but nevertheless not split and still looks fine.
│ │ │ │ - [--wwiinnbbbb]
│ │ │ │ - let the MS Windows API calculate the Bounding Box (MS Windows only)
│ │ │ │ - [--OOOO]
│ │ │ │ - generate OpenOffice compatible EMF file
│ │ │ │ ****** ppppttxx -- PPrreesseennttaattiioonnMMLL ((PPoowweerrPPooiinntt)) ffoorrmmaatt ******
│ │ │ │ This is the format used internally by Microsoft PowerPoint. LibreOffice can
│ │ │ │ also read/write PowerPoint files albeit with some lack of functionality.
│ │ │ │ The following driver specific options are available:
│ │ │ │ [--ccoolloorrss string]
│ │ │ │ "original" to retain original colors (default), "theme" to convert
│ │ │ │ randomly to theme colors, or "theme-lum" also to vary luminance
│ │ │ │ @@ -872,14 +841,45 @@
│ │ │ │ plot-hpgl:
│ │ │ │ hpgl via GNU libplot.
│ │ │ │ plot-tek:
│ │ │ │ tek via GNU libplot.
│ │ │ │ The following driver specific options are available in this group:
│ │ │ │ [--pplloottffoorrmmaatt string]
│ │ │ │ plotutil format to generate
│ │ │ │ +****** eemmff -- EEnnhhaanncceedd MMSS WWiinnddoowwss MMeettaaffiillee ******
│ │ │ │ +The following driver specific options are available:
│ │ │ │ + [--mm]
│ │ │ │ + map to Arial
│ │ │ │ + [--nnff]
│ │ │ │ + emulate narrow fonts
│ │ │ │ + [--ddrraawwbbbb]
│ │ │ │ + draw bounding box
│ │ │ │ + [--pp]
│ │ │ │ + prune line ends
│ │ │ │ + [--nnffww]
│ │ │ │ + Newer versions of MS Windows (2000, XP, Vista, 7, ...) 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 MS 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
│ │ │ │ + option 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 MS Windows anyway. In that case the output is
│ │ │ │ + portable but nevertheless not split and still looks fine.
│ │ │ │ + [--wwiinnbbbb]
│ │ │ │ + let the MS Windows API calculate the Bounding Box (MS Windows only)
│ │ │ │ + [--OOOO]
│ │ │ │ + generate OpenOffice compatible EMF file
│ │ │ │ ********** NNOOTTEESS OONN SSPPEECCIIFFIICC FFOORRMMAATTSS AANNDD DDRRIIVVEERRSS **********
│ │ │ │ ****** aauuttoottrraaccee ******
│ │ │ │ pstoedit cooperates with autotrace. Autotrace can now produce a dump file for
│ │ │ │ further processing by pstoedit using the --bboo (back-end only) option. Autotrace
│ │ │ │ is a program written by a group around Martin Weber and can be found at _h_t_t_p_s_:_/
│ │ │ │ _/_s_o_u_r_c_e_f_o_r_g_e_._n_e_t_/_p_r_o_j_e_c_t_s_/_a_u_t_o_t_r_a_c_e_/.
│ │ │ │ ****** PPss22aaii ******
│ │ ├── ./usr/share/doc/pstoedit/pstoedit.pdf
│ │ │ ├── pdftotext {} -
│ │ │ │ @@ -1,10 +1,10 @@
│ │ │ │ PSTOEDIT
│ │ │ │ Dr. Wolfgang Glunz
│ │ │ │ -December 14, 2025
│ │ │ │ +March 16, 2026
│ │ │ │ Version 4.3
│ │ │ │
│ │ │ │ Abstract
│ │ │ │ pstoedit - a tool converting PostScript files into various vector graphic
│ │ │ │ formats
│ │ │ │
│ │ │ │ 1
│ │ │ │ @@ -912,62 +912,26 @@
│ │ │ │ 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. This
│ │ │ │ binary of pstoedit was compiled against version 7.1.2 of ImageMagick.
│ │ │ │ No format specific options
│ │ │ │
│ │ │ │ 4.37
│ │ │ │
│ │ │ │ -emf - Enhanced MS Windows Metafile
│ │ │ │ -
│ │ │ │ -The following driver specific options are available:
│ │ │ │ -[-m] map to Arial
│ │ │ │ -[-nf ] emulate narrow fonts
│ │ │ │ -[-drawbb] draw bounding box
│ │ │ │ -[-p] prune line ends
│ │ │ │ -[-nfw] Newer versions of MS Windows (2000, XP, Vista, 7, ...) 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 MS 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 option 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
│ │ │ │ -MS Windows anyway. In that case the output is portable but nevertheless
│ │ │ │ -not split and still looks fine.
│ │ │ │ -[-winbb] let the MS Windows API calculate the Bounding Box (MS Windows
│ │ │ │ -only)
│ │ │ │ -[-OO] generate OpenOffice compatible EMF file
│ │ │ │ -
│ │ │ │ -4.38
│ │ │ │ -
│ │ │ │ pptx - PresentationML (PowerPoint) format
│ │ │ │
│ │ │ │ This is the format used internally by Microsoft PowerPoint. LibreOffice can
│ │ │ │ also read/write PowerPoint files albeit with some lack of functionality.
│ │ │ │ The following driver specific options are available:
│ │ │ │ [-colors string ] ”original” to retain original colors (default), ”theme” to convert randomly to theme colors, or ”theme-lum” also to vary luminance
│ │ │ │ -
│ │ │ │ -17
│ │ │ │ -
│ │ │ │ - 4.39 Format group: gmfa gmfb plot plot-pnm plot-cgm plot-ai plot-svg
│ │ │ │ -plot-ps plot-fig plot-pcl5 plot-hpgl
│ │ │ │ -NOTES plot-tek
│ │ │ │ -ON SPECIFIC FORMATS AND DRIVERS
│ │ │ │ [-fonts string ] use ”windows” fonts (default), ”native” fonts, or convert to the
│ │ │ │ ”theme” font
│ │ │ │ [-embed string ] embed fonts, specified as a comma-separated list of EOTformat font files
│ │ │ │ [-keepimagefiles] do not remove the temporary PNG image files.
│ │ │ │
│ │ │ │ -4.39
│ │ │ │ +4.38
│ │ │ │
│ │ │ │ Format group: gmfa gmfb plot plot-pnm plot-cgm
│ │ │ │ plot-ai plot-svg plot-ps plot-fig plot-pcl plot-hpgl
│ │ │ │ plot-tek
│ │ │ │
│ │ │ │ This group consists of the following variants:
│ │ │ │ gmfa: ASCII GNU metafile.
│ │ │ │ @@ -980,14 +944,51 @@
│ │ │ │ plot-ps: ps via GNU libplot.
│ │ │ │ plot-fig: fig via GNU libplot.
│ │ │ │ plot-pcl: pcl via GNU libplot.
│ │ │ │ plot-hpgl: hpgl via GNU libplot.
│ │ │ │ plot-tek: tek via GNU libplot.
│ │ │ │ The following driver specific options are available in this group:
│ │ │ │ [-plotformat string ] plotutil format to generate
│ │ │ │ +17
│ │ │ │ +
│ │ │ │ + 4.39
│ │ │ │ +
│ │ │ │ +4.39
│ │ │ │ +
│ │ │ │ +emf - Enhanced 5MSNOTES
│ │ │ │ +Windows
│ │ │ │ +ONMetafile
│ │ │ │ +SPECIFIC FORMATS AND DRIVERS
│ │ │ │ +
│ │ │ │ +emf - Enhanced MS Windows Metafile
│ │ │ │ +
│ │ │ │ +The following driver specific options are available:
│ │ │ │ +[-m] map to Arial
│ │ │ │ +[-nf ] emulate narrow fonts
│ │ │ │ +[-drawbb] draw bounding box
│ │ │ │ +[-p] prune line ends
│ │ │ │ +[-nfw] Newer versions of MS Windows (2000, XP, Vista, 7, ...) 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 MS 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 option 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
│ │ │ │ +MS Windows anyway. In that case the output is portable but nevertheless
│ │ │ │ +not split and still looks fine.
│ │ │ │ +[-winbb] let the MS Windows API calculate the Bounding Box (MS Windows
│ │ │ │ +only)
│ │ │ │ +[-OO] generate OpenOffice compatible EMF file
│ │ │ │
│ │ │ │ 5
│ │ │ │
│ │ │ │ NOTES ON SPECIFIC FORMATS AND
│ │ │ │ DRIVERS
│ │ │ │
│ │ │ │ 5.1
│ │ │ │ @@ -995,34 +996,34 @@
│ │ │ │ autotrace
│ │ │ │
│ │ │ │ pstoedit cooperates with autotrace. Autotrace can now produce a dump file for
│ │ │ │ further processing by pstoedit using the -bo (back-end only) option. Autotrace
│ │ │ │ is a program written by a group around Martin Weber and can be found at
│ │ │ │ https://sourceforge.net/projects/autotrace/.
│ │ │ │
│ │ │ │ -18
│ │ │ │ -
│ │ │ │ - 5.2
│ │ │ │ -
│ │ │ │ -Ps2ai
│ │ │ │ -
│ │ │ │ 5.2
│ │ │ │
│ │ │ │ -5
│ │ │ │ -
│ │ │ │ -NOTES ON SPECIFIC FORMATS AND DRIVERS
│ │ │ │ -
│ │ │ │ Ps2ai
│ │ │ │
│ │ │ │ The ps2ai output format driver is not a native pstoedit output format driver.
│ │ │ │ It does not use the pstoedit PostScript 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.
│ │ │ │ However, lot’s of files do not 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
│ │ │ │ +18
│ │ │ │ +
│ │ │ │ + 5.3
│ │ │ │ +
│ │ │ │ +MetaPost
│ │ │ │ +
│ │ │ │ +5
│ │ │ │ +
│ │ │ │ +NOTES ON SPECIFIC FORMATS AND DRIVERS
│ │ │ │ +
│ │ │ │ format is usable for example by Mayura Draw (http://www.mayura.com). Also
│ │ │ │ a driver to the Mayura native format would be nice.
│ │ │ │ An alternative to the ps2ai based driver is available via the -f plot:ai format
│ │ │ │ if the libplot(ter) is installed.
│ │ │ │ You should use a version of Ghostscript greater than or equal to 6.00 for
│ │ │ │ using the ps2ai output format driver.
│ │ │ │
│ │ │ │ @@ -1061,29 +1062,29 @@
│ │ │ │ "\usepackage{xcolor}". And if a figure contains rotated text, the
│ │ │ │ top-level document will need to do a "\usepackage{rotating}".
│ │ │ │ All lengths, coordinates, and font sizes output by the output format driver
│ │ │ │ are in terms of \unitlength, so scaling a figure is simply a matter of doing
│ │ │ │ a "\setlength{\unitlength}{...}".
│ │ │ │ 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.
│ │ │ │ + Why is this output format driver useful? One answer is portability; any
│ │ │ │ +LATEX2e system can handle the picture environment, even if it cannot handle PostScript graphics. (pdfLATEX comes to mind here.) A second answer is that pictures can be edited easily to contain any arbitrary LATEX2e
│ │ │ │
│ │ │ │ 19
│ │ │ │
│ │ │ │ 5.6
│ │ │ │
│ │ │ │ Creating a new output format driver
│ │ │ │
│ │ │ │ 7
│ │ │ │
│ │ │ │ TROUBLE SHOOTING
│ │ │ │
│ │ │ │ -sizes to the nearest integer. This makes hand-editing the picture a little
│ │ │ │ -nicer.
│ │ │ │ - Why is this output format driver useful? One answer is portability; any
│ │ │ │ -LATEX2e system can handle the picture environment, even if it cannot 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).
│ │ │ │
│ │ │ │ 5.6
│ │ │ │
│ │ │ │ @@ -1122,25 +1123,26 @@
│ │ │ │ front-end. 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.
│ │ │ │ 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 operators in the new meaning and does not use the original ones anymore.
│ │ │ │ +However, when run under the control of pstoedit, these operators are expected
│ │ │ │ +to work with the original semantics.
│ │ │ │ +So far I’ve seen redefinitions for:
│ │ │ │ + lt - ”less-then” to mean ”draw a line to”
│ │ │ │ + string - ”create a string object” to mean ”draw a string”
│ │ │ │ +
│ │ │ │ 20
│ │ │ │
│ │ │ │ 9
│ │ │ │
│ │ │ │ FAQS
│ │ │ │
│ │ │ │ -However, when run under the control of pstoedit, these operators are expected
│ │ │ │ -to work with the original semantics.
│ │ │ │ -So far I’ve seen redefinitions for:
│ │ │ │ - lt - ”less-then” to mean ”draw a line to”
│ │ │ │ - string - ”create a string object” to mean ”draw a string”
│ │ │ │ length - ”get the length of e.g. a string” to a ”float constant”
│ │ │ │
│ │ │ │ I’ve included work-arounds for the ones mentioned above, but some others
│ │ │ │ could show up in addition to those.
│ │ │ │
│ │ │ │ 8
│ │ │ │
│ │ │ │ @@ -1173,26 +1175,26 @@
│ │ │ │ FAQs
│ │ │ │ 1. Why do letters like O or B get strange if converted to TGIF/XFIG using
│ │ │ │ the -dt option?
│ │ │ │ Most output format drivers do not support composite paths with intermediate gaps (moveto’s) and second do not support very well the (eo)fill
│ │ │ │ operators of PostScript (winding rule). For such objects pstoedit breaks
│ │ │ │ them into smaller objects whenever such a gap is found. This results in
│ │ │ │ the ”hole” being filled with black color instead of being transparent. Since
│ │ │ │ -21
│ │ │ │ -
│ │ │ │ - 12
│ │ │ │ -
│ │ │ │ -ACKNOWLEDGMENTS
│ │ │ │ -
│ │ │ │ version 3.11 you can try the -ssp option in combination with the XFIG
│ │ │ │ output format driver.
│ │ │ │ 2. Why does pstoedit produce ugly results from PostScript files generated by
│ │ │ │ dvips?
│ │ │ │ This is because TEX documents usually use bitmap fonts. Such fonts
│ │ │ │ cannot be used as native font in other format. So pstoedit replaces the
│ │ │ │ +21
│ │ │ │ +
│ │ │ │ + 12
│ │ │ │ +
│ │ │ │ +ACKNOWLEDGMENTS
│ │ │ │ +
│ │ │ │ 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.
│ │ │ │
│ │ │ │ 10
│ │ │ │
│ │ │ │ @@ -1228,27 +1230,27 @@
│ │ │ │ Christoph Jaeschke provided the OS/2 metafile (MET) output format
│ │ │ │ driver. Thomas Hoffmann thoffman AT zappa.sax.de did some further
│ │ │ │ updates on the OS/2 part.
│ │ │ │ Jens Weber rz47b7 AT PostAG.DE provided the MS Windows metafile
│ │ │ │ (WMF) output format driver, and a graphical user interface (GUI).
│ │ │ │ G. Edward Johnson lorax AT nist.gov provided the CGM Draw library
│ │ │ │ used in the CGM output format driver.
│ │ │ │ + Gerhard Kircher kircher AT edvz.tuwien.ac.at provided some bug
│ │ │ │ +fixes.
│ │ │ │ + Bill Cheng bill.cheng AT acm.org provided help with the TGIF format
│ │ │ │ +and some changes to TGIF to make the output format driver easier to
│ │ │ │ +implement.
│ │ │ │ + Reini Urban rurban AT sbox.tu-graz.ac.at provided input for the extended DXF output format driver.
│ │ │ │
│ │ │ │ 22
│ │ │ │
│ │ │ │ 12
│ │ │ │
│ │ │ │ ACKNOWLEDGMENTS
│ │ │ │
│ │ │ │ - Gerhard Kircher kircher AT edvz.tuwien.ac.at provided some bug
│ │ │ │ -fixes.
│ │ │ │ - Bill Cheng bill.cheng AT acm.org provided help with the TGIF format
│ │ │ │ -and some changes to TGIF to make the output format driver easier to
│ │ │ │ -implement.
│ │ │ │ - Reini Urban rurban AT sbox.tu-graz.ac.at provided input for the extended DXF output format driver.
│ │ │ │ Glenn M. Lewis glenn AT gmlewis.com provided RenderMan (RIB),
│ │ │ │ Real3D (RPL), and LightWave 3D (LWO) output format drivers.
│ │ │ │ Piet van Oostrum piet AT cs.ruu.nl made several bug fixes.
│ │ │ │ Lutz Vieweg lkv AT mania.robin.de provided several bug fixes and suggestions for improvements.
│ │ │ │ Derek B. Noonburg derekn AT vw.ece.cmu.edu and Rainer Dorsch
│ │ │ │ rd AT berlepsch.wohnheim.uni-ulm.de isolated and resolved a Linuxspecific core dump problem.
│ │ │ │ Rob Warner rcw2 AT ukc.ac.uk made pstoedit compile under RiscOS.
│ │ │ │ @@ -1272,29 +1274,29 @@
│ │ │ │ Under MS Windows, libzip and libz are linked statically into the driver
│ │ │ │ DLL. Thanks to the whole libzip team. The libzip license is explained
│ │ │ │ here https://libzip.org/license.
│ │ │ │ Burkhard Plaum plaum AT IPF.Uni-Stuttgart.de added support for
│ │ │ │ complex filled paths for the XFIG output format driver.
│ │ │ │ Bernhard Herzog herzog AT online.de contributed the output format
│ │ │ │ driver for sketch ( http://www.skencil.org/ )
│ │ │ │ -
│ │ │ │ -23
│ │ │ │ -
│ │ │ │ - 13
│ │ │ │ -
│ │ │ │ -LEGAL NOTICES
│ │ │ │ -
│ │ │ │ Rolf Niepraschk (niepraschk AT ptb.de) converted the HTML man page
│ │ │ │ to LATEX format. This allows generating the UNIX style and the HTML
│ │ │ │ manual from this base format.
│ │ │ │ Several others sent smaller bug fixed and bug reports. Sorry if I do not
│ │ │ │ mention them all here.
│ │ │ │ Gisbert W. Selke (gisbert AT tapirsoft.de) for the Java 2 output format driver.
│ │ │ │ Robert S. Maier (rsm AT math.arizona.edu) for many improvements on
│ │ │ │ the libplot output format driver and for libplot itself.
│ │ │ │ +
│ │ │ │ +23
│ │ │ │ +
│ │ │ │ + 13
│ │ │ │ +
│ │ │ │ +LEGAL NOTICES
│ │ │ │ +
│ │ │ │ The authors of pstotext (mcjones AT pa.dec.com and birrell AT pa.dec.com)
│ │ │ │ for giving me the permission to use their simple PostScript code for performing rotation.
│ │ │ │ Daniel Gehriger gehriger AT linkcad.com for his help concerning the
│ │ │ │ handling of Splines in the DXF format.
│ │ │ │ Allen Barnett libemf AT lignumcomputing.com for his work on the
│ │ │ │ libEMF which allows creating WMF/EMF files under *nix systems.
│ │ │ │ Dave dave AT opaque.net for providing the libming which is a multiplatform library for generating SWF files.
│ │ ├── ./usr/share/man/man1/pstoedit.1.gz
│ │ │ ├── pstoedit.1
│ │ │ │ @@ -1,22 +1,22 @@
│ │ │ │ .\" *********************************** start of \input{version.tex}
│ │ │ │ .\" *********************************** end of \input{version.tex}
│ │ │ │ '\" t
│ │ │ │ -.\" Manual page created with latex2man.local on Sun Dec 14 15:54:27 2025
│ │ │ │ +.\" Manual page created with latex2man.local on Mon Mar 16 12:16:23 2026
│ │ │ │ .\" NOTE: This file is generated, DO NOT EDIT.
│ │ │ │ .de Vb
│ │ │ │ .ft CW
│ │ │ │ .nf
│ │ │ │ ..
│ │ │ │ .de Ve
│ │ │ │ .ft R
│ │ │ │
│ │ │ │ .fi
│ │ │ │ ..
│ │ │ │ -.TH "PSTOEDIT" "1" "14 December 2025" "Conversion Tools " "Conversion Tools "
│ │ │ │ +.TH "PSTOEDIT" "1" "16 March 2026" "Conversion Tools " "Conversion Tools "
│ │ │ │ .SH NAME
│ │ │ │
│ │ │ │ pstoedit
│ │ │ │ \- a tool converting PostScript files into various
│ │ │ │ vector graphic formats
│ │ │ │ .PP
│ │ │ │ .SH SYNOPSIS
│ │ │ │ @@ -1161,51 +1161,14 @@
│ │ │ │ \"option\-sample\-sampleoption
│ │ │ │ just an example
│ │ │ │ .PP
│ │ │ │ .SS MAGICK \- MAGICK DRIVER COMPATIBLE WITH VERSION 7.1.2 OF IMAGEMAGICK.
│ │ │ │ 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. This binary of pstoedit was compiled against version 7.1.2 of ImageMagick.
│ │ │ │ .PP
│ │ │ │ No format specific options
│ │ │ │ -.SS EMF \- ENHANCED MS WINDOWS METAFILE
│ │ │ │ -The following driver specific options are available:
│ │ │ │ -.TP
│ │ │ │ -[\fB\-m\fP]
│ │ │ │ - \"option\-emf\-m
│ │ │ │ -map to Arial
│ │ │ │ -.PP
│ │ │ │ -.TP
│ │ │ │ -[\fB\-nf\fP]
│ │ │ │ - \"option\-emf\-nf
│ │ │ │ -emulate narrow fonts
│ │ │ │ -.PP
│ │ │ │ -.TP
│ │ │ │ -[\fB\-drawbb\fP]
│ │ │ │ - \"option\-emf\-drawbb
│ │ │ │ -draw bounding box
│ │ │ │ -.PP
│ │ │ │ -.TP
│ │ │ │ -[\fB\-p\fP]
│ │ │ │ - \"option\-emf\-p
│ │ │ │ -prune line ends
│ │ │ │ -.PP
│ │ │ │ -.TP
│ │ │ │ -[\fB\-nfw\fP]
│ │ │ │ - \"option\-emf\-nfw
│ │ │ │ -Newer versions of MS Windows (2000, XP, Vista, 7, \&.\&.\&.) 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 MS 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 option 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 MS Windows anyway. In that case the output is portable but nevertheless not split and still looks fine.
│ │ │ │ -.PP
│ │ │ │ -.TP
│ │ │ │ -[\fB\-winbb\fP]
│ │ │ │ - \"option\-emf\-winbb
│ │ │ │ -let the MS Windows API calculate the Bounding Box (MS Windows only)
│ │ │ │ -.PP
│ │ │ │ -.TP
│ │ │ │ -[\fB\-OO\fP]
│ │ │ │ - \"option\-emf\-OO
│ │ │ │ -generate OpenOffice compatible EMF file
│ │ │ │ -.PP
│ │ │ │ .SS PPTX \- PRESENTATIONML (POWERPOINT) FORMAT
│ │ │ │ This is the format used internally by Microsoft PowerPoint. LibreOffice can also read/write PowerPoint files albeit with some lack of functionality.
│ │ │ │ .PP
│ │ │ │ The following driver specific options are available:
│ │ │ │ .TP
│ │ │ │ [\fB\-colors\fP\fI string\fP]
│ │ │ │ \"option\-pptx\-colors
│ │ │ │ @@ -1267,14 +1230,51 @@
│ │ │ │ .PP
│ │ │ │ The following driver specific options are available in this group:
│ │ │ │ .TP
│ │ │ │ [\fB\-plotformat\fP\fI string\fP]
│ │ │ │ \"option\-gmfa\-plotformat
│ │ │ │ plotutil format to generate
│ │ │ │ .PP
│ │ │ │ +.SS EMF \- ENHANCED MS WINDOWS METAFILE
│ │ │ │ +The following driver specific options are available:
│ │ │ │ +.TP
│ │ │ │ +[\fB\-m\fP]
│ │ │ │ + \"option\-emf\-m
│ │ │ │ +map to Arial
│ │ │ │ +.PP
│ │ │ │ +.TP
│ │ │ │ +[\fB\-nf\fP]
│ │ │ │ + \"option\-emf\-nf
│ │ │ │ +emulate narrow fonts
│ │ │ │ +.PP
│ │ │ │ +.TP
│ │ │ │ +[\fB\-drawbb\fP]
│ │ │ │ + \"option\-emf\-drawbb
│ │ │ │ +draw bounding box
│ │ │ │ +.PP
│ │ │ │ +.TP
│ │ │ │ +[\fB\-p\fP]
│ │ │ │ + \"option\-emf\-p
│ │ │ │ +prune line ends
│ │ │ │ +.PP
│ │ │ │ +.TP
│ │ │ │ +[\fB\-nfw\fP]
│ │ │ │ + \"option\-emf\-nfw
│ │ │ │ +Newer versions of MS Windows (2000, XP, Vista, 7, \&.\&.\&.) 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 MS 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 option 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 MS Windows anyway. In that case the output is portable but nevertheless not split and still looks fine.
│ │ │ │ +.PP
│ │ │ │ +.TP
│ │ │ │ +[\fB\-winbb\fP]
│ │ │ │ + \"option\-emf\-winbb
│ │ │ │ +let the MS Windows API calculate the Bounding Box (MS Windows only)
│ │ │ │ +.PP
│ │ │ │ +.TP
│ │ │ │ +[\fB\-OO\fP]
│ │ │ │ + \"option\-emf\-OO
│ │ │ │ +generate OpenOffice compatible EMF file
│ │ │ │ +.PP
│ │ │ │ .\" *********************************** end of \input{driverhelp.tex}
│ │ │ │ .SH NOTES ON SPECIFIC FORMATS AND DRIVERS
│ │ │ │
│ │ │ │ .SS AUTOTRACE
│ │ │ │ pstoedit cooperates with autotrace. Autotrace can now produce a dump file
│ │ │ │ for further processing by pstoedit using the \fB\-bo\fP
│ │ │ │ (back\-end only) option.