{"diffoscope-json-version": 1, "source1": "/srv/reproducible-results/rbuild-debian/r-b-build.RdKiT2hS/b1/pstoedit_3.78-2_arm64.changes", "source2": "/srv/reproducible-results/rbuild-debian/r-b-build.RdKiT2hS/b2/pstoedit_3.78-2_arm64.changes", "unified_diff": null, "details": [{"source1": "Files", "source2": "Files", "unified_diff": "@@ -1,6 +1,6 @@\n \n 8f4df3cb91c00e1865ae131858d24e70 63264 libdevel optional libpstoedit-dev_3.78-2_arm64.deb\n 007236787278a9c3aba29e1840ced938 3357364 debug optional libpstoedit0c2a-dbgsym_3.78-2_arm64.deb\n 526128ef370b4d5a2890a83ecd72fbcf 369328 libs optional libpstoedit0c2a_3.78-2_arm64.deb\n cc9f38a84eafad98578918de71ac21d8 10932 debug optional pstoedit-dbgsym_3.78-2_arm64.deb\n- a6cf81c18d6c5b2b0c1e969dd5439c87 417308 graphics optional pstoedit_3.78-2_arm64.deb\n+ 098ae1cad85d79eb29e34b41f238a7f0 417756 graphics optional pstoedit_3.78-2_arm64.deb\n"}, {"source1": "pstoedit_3.78-2_arm64.deb", "source2": "pstoedit_3.78-2_arm64.deb", "unified_diff": null, "details": [{"source1": "file list", "source2": "file list", "unified_diff": "@@ -1,3 +1,3 @@\n -rw-r--r-- 0 0 0 4 2022-09-20 18:39:23.000000 debian-binary\n -rw-r--r-- 0 0 0 1692 2022-09-20 18:39:23.000000 control.tar.xz\n--rw-r--r-- 0 0 0 415424 2022-09-20 18:39:23.000000 data.tar.xz\n+-rw-r--r-- 0 0 0 415872 2022-09-20 18:39:23.000000 data.tar.xz\n"}, {"source1": "control.tar.xz", "source2": "control.tar.xz", "unified_diff": null, "details": [{"source1": "control.tar", "source2": "control.tar", "unified_diff": null, "details": [{"source1": "./control", "source2": "./control", "unified_diff": "@@ -1,12 +1,12 @@\n Package: pstoedit\n Version: 3.78-2\n Architecture: arm64\n Maintainer: Barak A. Pearlmutter \n-Installed-Size: 1047\n+Installed-Size: 1048\n Depends: libc6 (>= 2.34), libpstoedit0c2a (>= 3.78), libstdc++6 (>= 4.1.1), ghostscript\n Suggests: xfig | ivtools-bin | tgif | transfig\n Section: graphics\n Priority: optional\n Homepage: http://www.pstoedit.net/\n Description: PostScript and PDF files to editable vector graphics converter\n pstoedit converts Postscript and PDF files to various editable\n"}, {"source1": "./md5sums", "source2": "./md5sums", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "comments": ["Files differ"], "unified_diff": null}]}]}]}, {"source1": "data.tar.xz", "source2": "data.tar.xz", "unified_diff": null, "details": [{"source1": "data.tar", "source2": "data.tar", "unified_diff": null, "details": [{"source1": "file list", "source2": "file list", "unified_diff": "@@ -25,20 +25,20 @@\n -rw-r--r-- 0 root (0) root (0) 4655 2018-04-16 12:26:28.000000 ./usr/share/doc/pstoedit/examples/oneimg.ps\n -rw-r--r-- 0 root (0) root (0) 434 2018-04-16 12:26:28.000000 ./usr/share/doc/pstoedit/examples/pathtest.ps\n -rw-r--r-- 0 root (0) root (0) 1755 2018-04-16 12:26:28.000000 ./usr/share/doc/pstoedit/examples/spiral.ps\n -rw-r--r-- 0 root (0) root (0) 860 2018-04-16 12:26:28.000000 ./usr/share/doc/pstoedit/examples/textmat.ps\n -rw-r--r-- 0 root (0) root (0) 2449 2018-04-16 12:26:28.000000 ./usr/share/doc/pstoedit/examples/twopages.ps\n -rw-r--r-- 0 root (0) root (0) 480 2018-04-16 12:26:28.000000 ./usr/share/doc/pstoedit/examples/woglim.ps\n -rw-r--r-- 0 root (0) root (0) 71484 2022-09-20 18:39:23.000000 ./usr/share/doc/pstoedit/pstoedit.htm\n--rw-r--r-- 0 root (0) root (0) 299920 2022-09-20 18:39:23.000000 ./usr/share/doc/pstoedit/pstoedit.pdf\n+-rw-r--r-- 0 root (0) root (0) 300219 2022-09-20 18:39:23.000000 ./usr/share/doc/pstoedit/pstoedit.pdf\n drwxr-xr-x 0 root (0) root (0) 0 2022-09-20 18:39:23.000000 ./usr/share/doc-base/\n -rw-r--r-- 0 root (0) root (0) 331 2021-09-04 18:55:20.000000 ./usr/share/doc-base/pstoedit.pstoedit-man\n drwxr-xr-x 0 root (0) root (0) 0 2022-09-20 18:39:23.000000 ./usr/share/man/\n drwxr-xr-x 0 root (0) root (0) 0 2022-09-20 18:39:23.000000 ./usr/share/man/man1/\n--rw-r--r-- 0 root (0) root (0) 17574 2022-09-20 18:39:23.000000 ./usr/share/man/man1/pstoedit.1.gz\n+-rw-r--r-- 0 root (0) root (0) 17575 2022-09-20 18:39:23.000000 ./usr/share/man/man1/pstoedit.1.gz\n drwxr-xr-x 0 root (0) root (0) 0 2022-09-20 18:39:23.000000 ./usr/share/pstoedit/\n -rw-r--r-- 0 root (0) root (0) 333 2022-09-20 18:39:23.000000 ./usr/share/pstoedit/drvhpgl.pencolors\n -rw-r--r-- 0 root (0) root (0) 315 2022-09-20 18:39:23.000000 ./usr/share/pstoedit/examplefigmap.fmp\n -rw-r--r-- 0 root (0) root (0) 211231 2022-09-20 18:39:23.000000 ./usr/share/pstoedit/latex2e.fmp\n -rw-r--r-- 0 root (0) root (0) 296447 2022-09-20 18:39:23.000000 ./usr/share/pstoedit/mpost.fmp\n -rw-r--r-- 0 root (0) root (0) 360 2022-09-20 18:39:23.000000 ./usr/share/pstoedit/safer.ps\n -rw-r--r-- 0 root (0) root (0) 1096 2022-09-20 18:39:23.000000 ./usr/share/pstoedit/svg.fmp\n"}, {"source1": "./usr/share/doc/pstoedit/pstoedit.htm", "source2": "./usr/share/doc/pstoedit/pstoedit.htm", "unified_diff": "@@ -1,11 +1,11 @@\n \n \n \n-\n \n PSTOEDIT\n \n

\n PSTOEDIT \n@@ -38,51 +38,51 @@\n
  • Drawing related options
    • \n
  • Debug options
    • \n
  • Input and outfile file arguments
    • \n \n
  • Available formats and their specific options \n \n
    • \n \n
  • NOTES \n
      \n
    • autotrace
      • \n
    • Ps2ai
      • \n@@ -749,20 +749,25 @@\n
      any device that Ghostscript provides - use gs:format, e.g. gs:pdfwrite. \n
      \n
      ps2ai:
      \n
      Adobe Illustrator via ps2ai.ps of Ghostscript. \n
      \n \n No format specific options \n-
      gcode - emc2 gcode format
      \n+
      magick - MAGICK driver compatible with version 6.9.11 of ImageMagick.
      \n+\n+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 6.9.11 of ImageMagick. \n+

      \n+No format specific options \n+

      gcode - emc2 gcode format
      \n \n See also: http://linuxcnc.org/\n

      \n No format specific options \n-

      cairo - cairo driver
      \n+
      cairo - cairo driver
      \n \n generates compilable c code for rendering with cairo \n

      \n The following format specific options are available: \n

      \n
      [-pango]\n
      \n@@ -779,24 +784,24 @@\n
      [-header string]\n
      \n
      \n sets the output file name for the generated C header file. e.g. myfig.h \n

      \n

      \n
      \n-
      lwo - LightWave 3D object format
      \n+
      lwo - LightWave 3D object format
      \n \n No format specific options \n-
      rib - RenderMan Interface Bytestream
      \n+
      rib - RenderMan Interface Bytestream
      \n \n No format specific options \n-
      rpl - Real3D Programming Language format
      \n+
      rpl - Real3D Programming Language format
      \n \n No format specific options \n-
      Format group: dxf dxf_14 dxf_s
      \n+
      Format group: dxf dxf_14 dxf_s
      \n \n This group consists of the following variants: \n
      \n
      dxf:
      \n
      CAD exchange format version 9 - only limited features. Consider using dxf_14 instead.. \n
      \n
      dxf_14:
      \n@@ -889,43 +894,43 @@\n
      [-layerfilter string]\n
      \n
      \n layers to be hidden (comma separated list of layer names, no space) \n

      \n

      \n
      \n-
      java1 - java 1 applet source code
      \n+
      java1 - java 1 applet source code
      \n \n The following format specific options are available: \n
      \n
      [java class name string]\n
      \n
      \n name of java class to generate \n

      \n

      \n
      \n-
      java2 - java 2 source code
      \n+
      java2 - java 2 source code
      \n \n The following format specific options are available: \n
      \n
      [java class name string]\n
      \n
      \n name of java class to generate \n

      \n

      \n
      \n-
      pdf - Adobe's Portable Document Format
      \n+
      pdf - Adobe's Portable Document Format
      \n \n No format specific options \n-
      kil - .kil format for Kontour
      \n+
      kil - .kil format for Kontour
      \n \n No format specific options \n-
      text - text in different forms
      \n+
      text - text in different forms
      \n \n The following format specific options are available: \n
      \n
      [-height number]\n
      \n
      \n page height in terms of characters \n@@ -940,46 +945,46 @@\n
      [-dump]\n
      \n
      \n dump text pieces \n

      \n

      \n
      \n-
      sk - Sketch format
      \n+
      sk - Sketch format
      \n \n No format specific options \n-
      mpost - MetaPost format
      \n+
      mpost - MetaPost format
      \n \n No format specific options \n-
      asy - Asymptote Format
      \n+
      asy - Asymptote Format
      \n \n No format specific options \n-
      mma - Mathematica graphics
      \n+
      mma - Mathematica graphics
      \n \n The following format specific options are available: \n
      \n
      [-eofillfills]\n
      \n
      \n Filling is used for eofill (default is not to fill) \n

      \n

      \n
      \n-
      latex2e - LaTeX2e picture format
      \n+
      latex2e - LaTeX2e picture format
      \n \n The following format specific options are available: \n
      \n
      [-integers]\n
      \n
      \n round all coordinates to the nearest integer \n

      \n

      \n
      \n-
      noixml - Nemetschek NOI XML format
      \n+
      noixml - Nemetschek NOI XML format
      \n \n Nemetschek Object Interface XML format \n

      \n The following format specific options are available: \n

      \n
      [-r string]\n
      \n@@ -990,15 +995,15 @@\n
      [-bsl number]\n
      \n
      \n Bezier Split Level (default 3) \n

      \n

      \n
      \n-
      pic - PIC format for troff et.al.
      \n+
      pic - PIC format for troff et.al.
      \n \n The following format specific options are available: \n
      \n
      [-troff]\n
      \n
      \n troff mode (default is groff) \n@@ -1031,15 +1036,15 @@\n
      [-debug]\n
      \n
      \n enable debug output \n

      \n

      \n
      \n-
      Format group: hpgl pcl
      \n+
      Format group: hpgl pcl
      \n \n This group consists of the following variants: \n
      \n
      hpgl:
      \n
      HPGL code. \n
      \n
      pcl:
      \n@@ -1093,21 +1098,21 @@\n
      [-rot270]\n
      \n
      \n rotate hpgl by 270 degrees \n

      \n

      \n
      \n-
      pcbi - engrave data - insulate/PCB format
      \n+
      pcbi - engrave data - insulate/PCB format
      \n \n See http://home.vr-web.de/~hans-juergen-jahn/software/devpcb.html\n for more details. \n

      \n No format specific options \n-

      pcb - pcb format
      \n+
      pcb - pcb format
      \n \n See also: http://pcb.sourceforge.net\n and http://www.penguin.cz/~utx/pstoedit-pcb/\n

      \n The following format specific options are available: \n

      \n
      [-grid missing arg name]\n@@ -1155,20 +1160,20 @@\n
      [-forcepoly]\n
      \n
      \n force all objects to be interpreted as polygons \n

      \n

      \n
      \n-
      pcbfill - pcb format with fills
      \n+
      pcbfill - pcb format with fills
      \n \n See also: http://pcb.sourceforge.net\n

      \n No format specific options \n-

      pcb-rnd - pcb-rnd format
      \n+
      pcb-rnd - pcb-rnd format
      \n \n See also: http://repo.hu/pcb-rnd\n and http://www.penguin.cz/~utx/pstoedit-pcb/\n

      \n The following format specific options are available: \n

      \n
      [-grid missing arg name]\n@@ -1210,25 +1215,25 @@\n
      [-forcepoly]\n
      \n
      \n force all objects to be interpreted as polygons \n

      \n

      \n
      \n-
      gschem - gschem format
      \n+
      gschem - gschem format
      \n \n See also: http://www.geda.seul.org/tools/gschem/\n

      \n No format specific options \n-

      cfdg - Context Free Design Grammar
      \n+
      cfdg - Context Free Design Grammar
      \n \n Context Free Design Grammar, usable by Context Free Art (http://www.contextfreeart.org/) \n

      \n No format specific options \n-

      tk - tk and/or tk applet source code
      \n+
      tk - tk and/or tk applet source code
      \n \n The following format specific options are available: \n
      \n
      [-R]\n
      \n
      \n swap HW \n@@ -1243,28 +1248,28 @@\n
      [-n string]\n
      \n
      \n tagnames \n

      \n

      \n
      \n-
      vtk - VTK driver: if you do not want to see this, uncomment the corresponding line in makefile and make again
      \n+
      vtk - VTK driver: if you do not want to see this, uncomment the corresponding line in makefile and make again
      \n \n this is a long description for the VTKe driver \n

      \n The following format specific options are available: \n

      \n
      [-VTKeoption integer]\n
      \n
      \n just an example \n

      \n

      \n
      \n-
      svm - StarView/OpenOffice.org metafile
      \n+
      svm - StarView/OpenOffice.org metafile
      \n \n StarView/OpenOffice.org metafile, readable from OpenOffice.org 1.0/StarOffice 6.0 and above. \n

      \n The following format specific options are available: \n

      \n
      [-m]\n
      \n@@ -1275,29 +1280,29 @@\n
      [-nf]\n
      \n
      \n emulate narrow fonts \n

      \n

      \n
      \n-
      gnuplot - gnuplot format
      \n+
      gnuplot - gnuplot format
      \n \n No format specific options \n-
      tgif - Tgif .obj format
      \n+
      tgif - Tgif .obj format
      \n \n The following format specific options are available: \n
      \n
      [-ta]\n
      \n
      \n text as attribute \n

      \n

      \n
      \n-
      Format group: fig xfig tfig
      \n+
      Format group: fig xfig tfig
      \n \n This group consists of the following variants: \n
      \n
      fig:
      \n
      .fig format for xfig. \n
      \n
      xfig:
      \n@@ -1347,83 +1352,31 @@\n
      [-depth number]\n
      \n
      \n set the page depth in inches (default 11) \n

      \n

      \n
      \n-
      idraw - Interviews draw format (EPS)
      \n+
      idraw - Interviews draw format (EPS)
      \n \n No format specific options \n-
      sample - sample driver: if you do not want to see this, uncomment the corresponding line in makefile and make again
      \n+
      sample - sample driver: if you do not want to see this, uncomment the corresponding line in makefile and make again
      \n \n This is a long description for the sample driver \n

      \n The following format specific options are available: \n

      \n
      [-sampleoption integer]\n
      \n
      \n just an example \n

      \n

      \n
      \n-
      magick - MAGICK driver compatible with version 6.9.11 of ImageMagick.
      \n-\n-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 6.9.11 of ImageMagick. \n-

      \n-No format specific options \n-

      emf - Enhanced MS Windows Metafile
      \n-\n-The following format specific options are available: \n-
      \n-
      [-m]\n-
      \n-
      \n-map to Arial \n-

      \n-

      \n-
      [-nf]\n-
      \n-
      \n-emulate narrow fonts \n-

      \n-

      \n-
      [-drawbb]\n-
      \n-
      \n-draw bounding box \n-

      \n-

      \n-
      [-p]\n-
      \n-
      \n-prune line ends \n-

      \n-

      \n-
      [-nfw]\n-
      \n-
      \n-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. \n-

      \n-

      \n-
      [-winbb]\n-
      \n-
      \n-let the MS Windows API calculate the Bounding Box (MS Windows only) \n-

      \n-

      \n-
      [-OO]\n-
      \n-
      \n-generate OpenOffice compatible EMF file \n-

      \n-

      \n-
      \n-
      pptx - PresentationML (PowerPoint) format
      \n+
      pptx - PresentationML (PowerPoint) format
      \n \n This is the format used internally by Microsoft PowerPoint. LibreOffice can also read/write PowerPoint files albeit with some lack of functionality. \n

      \n The following format specific options are available: \n

      \n
      [-colors string]\n
      \n@@ -1440,15 +1393,15 @@\n
      [-embed string]\n
      \n
      \n embed fonts, specified as a comma-separated list of EOT-format font files \n

      \n

      \n
      \n-
      Format group: gmfa gmfb plot plot-pnm plot-cgm plot-ai plot-svg plot-ps plot-fig plot-pcl plot-hpgl plot-tek
      \n+
      Format group: gmfa gmfb plot plot-pnm plot-cgm plot-ai plot-svg plot-ps plot-fig plot-pcl plot-hpgl plot-tek
      \n \n This group consists of the following variants: \n
      \n
      gmfa:
      \n
      ASCII GNU metafile . \n
      \n
      gmfb:
      \n@@ -1490,14 +1443,61 @@\n
      [-plotformat string]\n
      \n
      \n plotutil format to generate \n

      \n

      \n
      \n+
      emf - Enhanced MS Windows Metafile
      \n+\n+The following format specific options are available: \n+
      \n+
      [-m]\n+
      \n+
      \n+map to Arial \n+

      \n+

      \n+
      [-nf]\n+
      \n+
      \n+emulate narrow fonts \n+

      \n+

      \n+
      [-drawbb]\n+
      \n+
      \n+draw bounding box \n+

      \n+

      \n+
      [-p]\n+
      \n+
      \n+prune line ends \n+

      \n+

      \n+
      [-nfw]\n+
      \n+
      \n+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. \n+

      \n+

      \n+
      [-winbb]\n+
      \n+
      \n+let the MS Windows API calculate the Bounding Box (MS Windows only) \n+

      \n+

      \n+
      [-OO]\n+
      \n+
      \n+generate OpenOffice compatible EMF file \n+

      \n+

      \n+
      \n \n

      \n

      NOTES

      \n \n

      \n

      autotrace

      \n \n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -21,14 +21,16 @@\n o General_options\n o Text_and_font_handling_related_options\n o Drawing_related_options\n o Debug_options\n o Input_and_outfile_file_arguments\n * Available_formats_and_their_specific_options\n o Format_group:_psf_ps_debug_dump_gs_ps2ai\n+ o magick_-_MAGICK_driver_compatible_with_version_6.9.11_of\n+ ImageMagick.\n o gcode_-_emc2_gcode_format\n o cairo_-_cairo_driver\n o lwo_-_LightWave_3D_object_format\n o rib_-_RenderMan_Interface_Bytestream\n o rpl_-_Real3D_Programming_Language_format\n o Format_group:_dxf_dxf_14_dxf_s\n o java1_-_java_1_applet_source_code\n@@ -56,20 +58,18 @@\n o svm_-_StarView/OpenOffice.org_metafile\n o gnuplot_-_gnuplot_format\n o tgif_-_Tgif_.obj_format\n o Format_group:_fig_xfig_tfig\n o idraw_-_Interviews_draw_format_(EPS)\n o sample_-_sample_driver:_if_you_do_not_want_to_see_this,_uncomment\n the_corresponding_line_in_makefile_and_make_again\n- o magick_-_MAGICK_driver_compatible_with_version_6.9.11_of\n- ImageMagick.\n- o emf_-_Enhanced_MS_Windows_Metafile\n o pptx_-_PresentationML_(PowerPoint)_format\n o Format_group:_gmfa_gmfb_plot_plot-pnm_plot-cgm_plot-ai_plot-svg\n plot-ps_plot-fig_plot-pcl_plot-hpgl_plot-tek\n+ o emf_-_Enhanced_MS_Windows_Metafile\n NOTES\n * autotrace\n * Ps2ai\n * MetaPost\n * Context_Free_-_CFDG\n * LaTeX2e\n * Creating_a_new_output_format_driver\n@@ -457,14 +457,21 @@\n dump:\n for test purposes (same as debug).\n gs:\n any device that Ghostscript provides - use gs:format, e.g. gs:pdfwrite.\n ps2ai:\n Adobe Illustrator via ps2ai.ps of Ghostscript.\n No format specific options\n+** magick - MAGICK driver compatible with version 6.9.11 of ImageMagick. **\n+This driver uses the C++ API of ImageMagick or GraphicsMagick to finally\n+produce different output formats. The output format is determined automatically\n+by Image-/GraphicsMagick based on the suffix of the output filename. So an\n+output file test.png will force the creation of an image in PNG format. This\n+binary of pstoedit was compiled against version 6.9.11 of ImageMagick.\n+No format specific options\n ** gcode - emc2 gcode format **\n See also: http://linuxcnc.org/\n No format specific options\n ** cairo - cairo driver **\n generates compilable c code for rendering with cairo\n The following format specific options are available:\n [-pango]\n@@ -717,52 +724,14 @@\n No format specific options\n ** sample - sample driver: if you do not want to see this, uncomment the\n corresponding line in makefile and make again **\n This is a long description for the sample driver\n The following format specific options are available:\n [-sampleoption\u00a0integer]\n just an example\n-** magick - MAGICK driver compatible with version 6.9.11 of ImageMagick. **\n-This driver uses the C++ API of ImageMagick or GraphicsMagick to finally\n-produce different output formats. The output format is determined automatically\n-by Image-/GraphicsMagick based on the suffix of the output filename. So an\n-output file test.png will force the creation of an image in PNG format. This\n-binary of pstoedit was compiled against version 6.9.11 of ImageMagick.\n-No format specific options\n-** emf - Enhanced MS Windows Metafile **\n-The following format specific options are available:\n- [-m]\n- map to Arial\n- [-nf]\n- emulate narrow fonts\n- [-drawbb]\n- draw bounding box\n- [-p]\n- prune line ends\n- [-nfw]\n- Newer versions of MS Windows (2000, XP, Vista, 7, ...) will not accept\n- WMF/EMF files generated when this option is set and the input contains\n- text. But if this option is not set, then the WMF/EMF driver will\n- estimate interletter spacing of text using a very coarse heuristic. This\n- may result in ugly looking output. On the other hand, OpenOffice can\n- still read EMF/WMF files where pstoedit delegates the calculation of the\n- inter letter spacing to the program reading the WMF/EMF file. So if the\n- generated WMF/EMF file shall never be processed under MS Windows, use\n- this option. If WMF/EMF files with high precision text need to be\n- generated under *nix the only option is to use the -pta option of\n- pstoedit. However that causes every text to be split into single\n- characters which makes the text hard to edit afterwards. Hence the -nfw\n- option provides a sort of compromise between portability and nice to edit\n- but still nice looking text. Again - this option has no meaning when\n- pstoedit is executed under MS Windows anyway. In that case the output is\n- portable but nevertheless not split and still looks fine.\n- [-winbb]\n- let the MS Windows API calculate the Bounding Box (MS Windows only)\n- [-OO]\n- generate OpenOffice compatible EMF file\n ** pptx - PresentationML (PowerPoint) format **\n This is the format used internally by Microsoft PowerPoint. LibreOffice can\n also read/write PowerPoint files albeit with some lack of functionality.\n The following format specific options are available:\n [-colors\u00a0string]\n \"original\" to retain original colors (default), \"theme\" to convert\n randomly to theme colors, or \"theme-lum\" also to vary luminance\n@@ -797,14 +766,45 @@\n plot-hpgl:\n hpgl via GNU libplot.\n plot-tek:\n tek via GNU libplot.\n The following format specific options are available:\n [-plotformat\u00a0string]\n plotutil format to generate\n+** emf - Enhanced MS Windows Metafile **\n+The following format specific options are available:\n+ [-m]\n+ map to Arial\n+ [-nf]\n+ emulate narrow fonts\n+ [-drawbb]\n+ draw bounding box\n+ [-p]\n+ prune line ends\n+ [-nfw]\n+ Newer versions of MS Windows (2000, XP, Vista, 7, ...) will not accept\n+ WMF/EMF files generated when this option is set and the input contains\n+ text. But if this option is not set, then the WMF/EMF driver will\n+ estimate interletter spacing of text using a very coarse heuristic. This\n+ may result in ugly looking output. On the other hand, OpenOffice can\n+ still read EMF/WMF files where pstoedit delegates the calculation of the\n+ inter letter spacing to the program reading the WMF/EMF file. So if the\n+ generated WMF/EMF file shall never be processed under MS Windows, use\n+ this option. If WMF/EMF files with high precision text need to be\n+ generated under *nix the only option is to use the -pta option of\n+ pstoedit. However that causes every text to be split into single\n+ characters which makes the text hard to edit afterwards. Hence the -nfw\n+ option provides a sort of compromise between portability and nice to edit\n+ but still nice looking text. Again - this option has no meaning when\n+ pstoedit is executed under MS Windows anyway. In that case the output is\n+ portable but nevertheless not split and still looks fine.\n+ [-winbb]\n+ let the MS Windows API calculate the Bounding Box (MS Windows only)\n+ [-OO]\n+ generate OpenOffice compatible EMF file\n ***** NOTES *****\n *** autotrace ***\n pstoedit cooperates with autotrace. Autotrace can now produce a dump file for\n further processing by pstoedit using the -bo (backend only) option. Autotrace\n is a program written by a group around Martin Weber and can be found at http://\n sourceforge.net/projects/autotrace/.\n *** Ps2ai ***\n"}]}, {"source1": "./usr/share/doc/pstoedit/pstoedit.pdf", "source2": "./usr/share/doc/pstoedit/pstoedit.pdf", "unified_diff": null, "details": [{"source1": "pdftotext {} -", "source2": "pdftotext {} -", "unified_diff": "@@ -455,51 +455,61 @@\n debug: for test purposes.\n dump: for test purposes (same as debug).\n gs: any device that Ghostscript provides - use gs:format, e.g. gs:pdfwrite.\n ps2ai: Adobe Illustrator via ps2ai.ps of Ghostscript.\n No format specific options\n 4.0.2\n \n+magick - MAGICK driver compatible with version 6.9.11 of\n+ImageMagick.\n+\n+This driver uses the C++ API of ImageMagick or GraphicsMagick to finally\n+produce different output formats. The output format is determined automatically by Image-/GraphicsMagick based on the suffix of the output filename. So\n+an output file test.png will force the creation of an image in PNG format. This\n+binary of pstoedit was compiled against version 6.9.11 of ImageMagick.\n+No format specific options\n+\n+9\n+\n+\f4\n+\n+4.0.3\n+\n+AVAILABLE FORMATS AND THEIR SPECIFIC OPTIONS\n+\n gcode - emc2 gcode format\n \n See also: http://linuxcnc.org/\n No format specific options\n-4.0.3\n+4.0.4\n \n cairo - cairo driver\n \n generates compilable c code for rendering with cairo\n The following format specific options are available:\n [-pango] use pango for font rendering\n-\n-9\n-\n-\f4\n-\n-AVAILABLE FORMATS AND THEIR SPECIFIC OPTIONS\n-\n [-funcname string ] sets the base name for the generated functions and variables. e.g. myfig\n [-header string ] sets the output file name for the generated C header file. e.g.\n myfig.h\n-4.0.4\n+4.0.5\n \n lwo - LightWave 3D object format\n \n No format specific options\n-4.0.5\n+4.0.6\n \n rib - RenderMan Interface Bytestream\n \n No format specific options\n-4.0.6\n+4.0.7\n \n rpl - Real3D Programming Language format\n \n No format specific options\n-4.0.7\n+4.0.8\n \n Format group: dxf dxf 14 dxf s\n \n This group consists of the following variants:\n dxf: CAD exchange format version 9 - only limited features. Consider using\n dxf 14 instead..\n dxf 14: CAD exchange format version 14 supporting splines and linetypes.\n@@ -508,146 +518,146 @@\n [-polyaslines] use LINE instead of POLYLINE in DXF\n [-mm] use mm coordinates instead of points in DXF (mm=pt/72*25.4)\n [-ctl] map colors to layers\n [-filltohatch] generate hatch objects from fill operations (still experimental)\n [-splineaspolyline] approximate splines with PolyLines (only for -f dxf s)\n [-splineasnurb] experimental (only for -f dxf s)\n [-splineasbspline] experimental (only for -f dxf s)\n-[-splineassinglespline] experimental (only for -f dxf s)\n-[-splineasmultispline] experimental (only for -f dxf s)\n-[-splineasbezier] use Bezier splines in DXF format (only for -f dxf s)\n-[-splineprecision number ] number of samples to take from spline curve\n-when doing approximation with -splineaspolyline or -splineasmultispline\n-- should be =2 (default 5)\n-[-dumplayernames] dump all layer names found to standard output\n \n 10\n \n \f4\n \n AVAILABLE FORMATS AND THEIR SPECIFIC OPTIONS\n \n+[-splineassinglespline] experimental (only for -f dxf s)\n+[-splineasmultispline] experimental (only for -f dxf s)\n+[-splineasbezier] use Bezier splines in DXF format (only for -f dxf s)\n+[-splineprecision number ] number of samples to take from spline curve\n+when doing approximation with -splineaspolyline or -splineasmultispline\n+- should be =2 (default 5)\n+[-dumplayernames] dump all layer names found to standard output\n [-layers string ] layers to be shown (comma separated list of layer names, no\n space)\n [-layerfilter string ] layers to be hidden (comma separated list of layer names,\n no space)\n-4.0.8\n+4.0.9\n \n java1 - java 1 applet source code\n \n The following format specific options are available:\n [java class name string ] name of java class to generate\n-4.0.9\n+4.0.10\n \n java2 - java 2 source code\n \n The following format specific options are available:\n [java class name string ] name of java class to generate\n-4.0.10\n+4.0.11\n \n pdf - Adobe\u2019s Portable Document Format\n \n No format specific options\n-4.0.11\n+4.0.12\n \n kil - .kil format for Kontour\n \n No format specific options\n-4.0.12\n+4.0.13\n \n text - text in different forms\n \n The following format specific options are available:\n [-height number ] page height in terms of characters\n [-width number ] page width in terms of characters\n [-dump] dump text pieces\n-4.0.13\n+4.0.14\n \n sk - Sketch format\n \n No format specific options\n-4.0.14\n+4.0.15\n \n mpost - MetaPost format\n \n No format specific options\n-4.0.15\n+\n+11\n+\n+\f4\n+\n+4.0.16\n+\n+AVAILABLE FORMATS AND THEIR SPECIFIC OPTIONS\n \n asy - Asymptote Format\n \n No format specific options\n-4.0.16\n+4.0.17\n \n mma - Mathematica graphics\n \n The following format specific options are available:\n [-eofillfills] Filling is used for eofill (default is not to fill)\n-\n-11\n-\n-\f4\n-\n-4.0.17\n-\n-AVAILABLE FORMATS AND THEIR SPECIFIC OPTIONS\n+4.0.18\n \n latex2e - LATEX2e picture format\n \n The following format specific options are available:\n [-integers] round all coordinates to the nearest integer\n-4.0.18\n+4.0.19\n \n noixml - Nemetschek NOI XML format\n \n Nemetschek Object Interface XML format\n The following format specific options are available:\n [-r string ] Allplan resource file\n [-bsl number ] Bezier Split Level (default 3)\n-4.0.19\n+4.0.20\n \n pic - PIC format for troff et.al.\n \n The following format specific options are available:\n [-troff ] troff mode (default is groff)\n [-landscape] landscape output\n [-portrait] portrait output\n [-keepfont] print unrecognized literally\n [-text] try not to make pictures from running text\n [-debug] enable debug output\n-4.0.20\n+4.0.21\n \n Format group: hpgl pcl\n \n This group consists of the following variants:\n hpgl: HPGL code.\n pcl: PCL code.\n The following format specific options are available:\n [-penplotter] plotter is pen plotter (i.e. no support for specific line widths)\n [-pencolorsfromfile] read pen colors from file drvhpgl.pencolors in pstoedit\u2019s\n data directory\n [-pencolors number ] maximum number of pen colors to be used by pstoedit\n-(default 0) [-filltype string ] select fill type e.g. FT 1\n-[-hpgl2] Use HPGL/2 instead of HPGL/1\n-[-rot90] rotate hpgl by 90 degrees\n-[-rot180] rotate hpgl by 180 degrees\n-[-rot270] rotate hpgl by 270 degrees\n-12\n+(default 0) 12\n \n \f4\n \n-4.0.21\n-\n AVAILABLE FORMATS AND THEIR SPECIFIC OPTIONS\n \n+[-filltype string ] select fill type e.g. FT 1\n+[-hpgl2] Use HPGL/2 instead of HPGL/1\n+[-rot90] rotate hpgl by 90 degrees\n+[-rot180] rotate hpgl by 180 degrees\n+[-rot270] rotate hpgl by 270 degrees\n+4.0.22\n+\n pcbi - engrave data - insulate/PCB format\n \n See http://home.vr-web.de/\u223chans-juergen-jahn/software/devpcb.html\n for more details.\n No format specific options\n-4.0.22\n+4.0.23\n \n pcb - pcb format\n \n See also: http://pcb.sourceforge.net and http://www.penguin.cz/\u223cutx/pstoedit-pcb/\n The following format specific options are available:\n [-grid missing arg name] attempt to snap relevant output to grid (mils) and\n put failed objects to a different layer\n@@ -658,100 +668,101 @@\n [-tshifty missing arg name] additional y shift measured in target units\n (mils)\n [-grid missing arg name] attempt to snap relevant output to grid (mils) and\n put failed objects to a different layer\n [-mm] switch to metric units (mm)\n [-stdnames] use standard layer names instead of descriptive names\n [-forcepoly] force all objects to be interpreted as polygons\n-4.0.23\n+4.0.24\n \n pcbfill - pcb format with fills\n \n See also: http://pcb.sourceforge.net\n No format specific options\n-4.0.24\n+4.0.25\n \n pcb-rnd - pcb-rnd format\n \n See also: http://repo.hu/pcb-rnd and http://www.penguin.cz/\u223cutx/pstoedit-pcb/\n The following format specific options are available:\n [-grid missing arg name] attempt to snap relevant output to grid (mils) and\n put failed objects to a different layer\n+\n+13\n+\n+\f4\n+\n+AVAILABLE FORMATS AND THEIR SPECIFIC OPTIONS\n+\n [-snapdist missing arg name] grid snap distance ratio (0 \u00a1 snapdist \u00a1= 0.5,\n default 0.1)\n [-tshiftx missing arg name] additional x shift measured in target units\n (mils)\n [-tshifty missing arg name] additional y shift measured in target units\n (mils)\n [-grid missing arg name] attempt to snap relevant output to grid (mils) and\n put failed objects to a different layer\n-13\n-\n-\f4\n-\n-AVAILABLE FORMATS AND THEIR SPECIFIC OPTIONS\n-\n [-mm] switch to metric units (mm)\n [-forcepoly] force all objects to be interpreted as polygons\n-4.0.25\n+4.0.26\n \n gschem - gschem format\n \n See also: http://www.geda.seul.org/tools/gschem/\n No format specific options\n-4.0.26\n+4.0.27\n \n cfdg - Context Free Design Grammar\n \n Context Free Design Grammar, usable by Context Free Art (http://www.contextfreeart.org/)\n No format specific options\n-4.0.27\n+4.0.28\n \n tk - tk and/or tk applet source code\n \n The following format specific options are available:\n [-R] swap HW\n [-I] no impress\n [-n string ] tagnames\n-4.0.28\n+4.0.29\n \n vtk - VTK driver: if you do not want to see this, uncomment\n the corresponding line in makefile and make again\n \n this is a long description for the VTKe driver\n The following format specific options are available:\n [-VTKeoption integer ] just an example\n-4.0.29\n+4.0.30\n \n svm - StarView/OpenOffice.org metafile\n \n StarView/OpenOffice.org metafile, readable from OpenOffice.org 1.0/StarOffice\n 6.0 and above.\n The following format specific options are available:\n [-m] map to Arial\n [-nf ] emulate narrow fonts\n-4.0.30\n+\n+14\n+\n+\f4\n+\n+4.0.31\n+\n+AVAILABLE FORMATS AND THEIR SPECIFIC OPTIONS\n \n gnuplot - gnuplot format\n \n No format specific options\n-4.0.31\n+4.0.32\n \n tgif - Tgif .obj format\n \n The following format specific options are available:\n [-ta] text as attribute\n-\n-14\n-\n-\f4\n-\n-4.0.32\n-\n-AVAILABLE FORMATS AND THEIR SPECIFIC OPTIONS\n+4.0.33\n \n Format group: fig xfig tfig\n \n This group consists of the following variants:\n fig: .fig format for xfig.\n xfig: .fig format for xfig.\n tfig: .fig format for xfig - test only version.\n@@ -771,90 +782,45 @@\n for a list of legal font names\n The following format specific options are available:\n [-startdepth number ] set the initial depth (default 999)\n [-metric] switch to centimeter display (default inches)\n [-usecorrectfontsize] do not scale fonts for xfig. Use this if you also use this\n option with xfig\n [-depth number ] set the page depth in inches (default 11)\n-4.0.33\n+4.0.34\n \n idraw - Interviews draw format (EPS)\n \n No format specific options\n-4.0.34\n-\n-sample - sample driver: if you do not want to see this, uncomment the corresponding line in makefile and make again\n-\n-This is a long description for the sample driver\n-The following format specific options are available:\n-[-sampleoption integer ] just an example\n \n 15\n \n \f4\n \n 4.0.35\n \n AVAILABLE FORMATS AND THEIR SPECIFIC OPTIONS\n \n-magick - MAGICK driver compatible with version 6.9.11 of\n-ImageMagick.\n-\n-This driver uses the C++ API of ImageMagick or GraphicsMagick to finally\n-produce different output formats. The output format is determined automatically by Image-/GraphicsMagick based on the suffix of the output filename. So\n-an output file test.png will force the creation of an image in PNG format. This\n-binary of pstoedit was compiled against version 6.9.11 of ImageMagick.\n-No format specific options\n-4.0.36\n-\n-emf - Enhanced MS Windows Metafile\n+sample - sample driver: if you do not want to see this, uncomment the corresponding line in makefile and make again\n \n+This is a long description for the sample driver\n The following format specific options are available:\n-[-m] map to Arial\n-[-nf ] emulate narrow fonts\n-[-drawbb] draw bounding box\n-[-p] prune line ends\n-[-nfw] Newer versions of MS Windows (2000, XP, Vista, 7, ...) will not accept\n-WMF/EMF files generated when this option is set and the input contains\n-text. But if this option is not set, then the WMF/EMF driver will estimate\n-interletter spacing of text using a very coarse heuristic. This may result\n-in ugly looking output. On the other hand, OpenOffice can still read\n-EMF/WMF files where pstoedit delegates the calculation of the inter letter\n-spacing to the program reading the WMF/EMF file. So if the generated\n-WMF/EMF file shall never be processed under MS Windows, use this\n-option. If WMF/EMF files with high precision text need to be generated\n-under *nix the only option is to use the -pta option of pstoedit. However\n-that causes every text to be split into single characters which makes the\n-text hard to edit afterwards. Hence the -nfw option provides a sort of\n-compromise between portability and nice to edit but still nice looking\n-text. Again - this option has no meaning when pstoedit is executed under\n-MS Windows anyway. In that case the output is portable but nevertheless\n-not split and still looks fine.\n-[-winbb] let the MS Windows API calculate the Bounding Box (MS Windows\n-only)\n-[-OO] generate OpenOffice compatible EMF file\n-4.0.37\n+[-sampleoption integer ] just an example\n+4.0.36\n \n pptx - PresentationML (PowerPoint) format\n \n This is the format used internally by Microsoft PowerPoint. LibreOffice can\n also read/write PowerPoint files albeit with some lack of functionality.\n The following format specific options are available:\n [-colors string ] \u201doriginal\u201d to retain original colors (default), \u201dtheme\u201d to convert randomly to theme colors, or \u201dtheme-lum\u201d also to vary luminance\n-\n-16\n-\n-\f5\n-\n-NOTES\n-\n [-fonts string ] use \u201dwindows\u201d fonts (default), \u201dnative\u201d fonts, or convert to the\n \u201dtheme\u201d font\n [-embed string ] embed fonts, specified as a comma-separated list of EOTformat font files\n-4.0.38\n+4.0.37\n \n Format group: gmfa gmfb plot plot-pnm plot-cgm plot-ai\n plot-svg plot-ps plot-fig plot-pcl plot-hpgl plot-tek\n \n This group consists of the following variants:\n gmfa: ASCII GNU metafile .\n gmfb: binary GNU metafile .\n@@ -867,47 +833,83 @@\n plot-fig: fig via GNU libplot.\n plot-pcl: pcl via GNU libplot.\n plot-hpgl: hpgl via GNU libplot.\n plot-tek: tek via GNU libplot.\n The following format specific options are available:\n [-plotformat string ] plotutil format to generate\n \n+16\n+\n+\f5\n+\n+4.0.38\n+\n+NOTES\n+\n+emf - Enhanced MS Windows Metafile\n+\n+The following format specific options are available:\n+[-m] map to Arial\n+[-nf ] emulate narrow fonts\n+[-drawbb] draw bounding box\n+[-p] prune line ends\n+[-nfw] Newer versions of MS Windows (2000, XP, Vista, 7, ...) will not accept\n+WMF/EMF files generated when this option is set and the input contains\n+text. But if this option is not set, then the WMF/EMF driver will estimate\n+interletter spacing of text using a very coarse heuristic. This may result\n+in ugly looking output. On the other hand, OpenOffice can still read\n+EMF/WMF files where pstoedit delegates the calculation of the inter letter\n+spacing to the program reading the WMF/EMF file. So if the generated\n+WMF/EMF file shall never be processed under MS Windows, use this\n+option. If WMF/EMF files with high precision text need to be generated\n+under *nix the only option is to use the -pta option of pstoedit. However\n+that causes every text to be split into single characters which makes the\n+text hard to edit afterwards. Hence the -nfw option provides a sort of\n+compromise between portability and nice to edit but still nice looking\n+text. Again - this option has no meaning when pstoedit is executed under\n+MS Windows anyway. In that case the output is portable but nevertheless\n+not split and still looks fine.\n+[-winbb] let the MS Windows API calculate the Bounding Box (MS Windows\n+only)\n+[-OO] generate OpenOffice compatible EMF file\n+\n 5\n \n NOTES\n \n 5.1\n \n autotrace\n \n pstoedit cooperates with autotrace. Autotrace can now produce a dump file for\n further processing by pstoedit using the -bo (backend only) option. Autotrace\n is a program written by a group around Martin Weber and can be found at\n http://sourceforge.net/projects/autotrace/.\n \n-17\n-\n-\f5.2\n-\n-Ps2ai\n-\n 5.2\n \n-5\n-\n-NOTES\n-\n Ps2ai\n \n The ps2ai output format driver is not a native pstoedit output format driver.\n It does not use the pstoedit PostScript flattener, instead it uses the PostScript\n program ps2ai.ps which is installed in the Ghostscript distribution directory. It\n is included to provide the same \u201dlook-and-feel\u201d for the conversion to AI. The\n additional benefit is that this conversion is now available also via the \u201dconvertto-vector\u201d menu of Gsview. However, lot\u2019s of files do not convert nicely or at\n all using ps2ai.ps. So a native pstoedit driver would be much better. Anyone\n+\n+17\n+\n+\f5.3\n+\n+MetaPost\n+\n+5\n+\n+NOTES\n+\n out there to take this? The AI format is usable for example by Mayura Draw\n (http://www.mayura.com). Also a driver to the Mayura native format would\n be nice.\n An alternative to the ps2ai based driver is available via the -f plot:ai format\n if the libplot(ter) is installed.\n You should use a version of Ghostscript greater than or equal to 6.00 for\n using the ps2ai output format driver.\n@@ -945,31 +947,31 @@\n but can be handled by external packages. If a figure uses color,\n the top-level document will need to do a \"\\usepackage{color}\" or\n \"\\usepackage{xcolor}\". And if a figure contains rotated text, the\n top-level document will need to do a \"\\usepackage{rotating}\".\n \u0088 All lengths, coordinates, and font sizes output by the output format driver\n are in terms of \\unitlength, so scaling a figure is simply a matter of doing\n a \"\\setlength{\\unitlength}{...}\".\n+\u0088 The output format driver currently supports one output format driver\n+specific option, \u201dintegers\u201d, which rounds all lengths, coordinates, and font\n+sizes to the nearest integer. This makes hand-editing the picture a little\n+nicer.\n+\u0088 Why is this output format driver useful? One answer is portability; any\n+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\n \n 18\n \n \f5.6\n \n Creating a new output format driver\n \n 7\n \n TROUBLE SHOOTING\n \n-\u0088 The output format driver currently supports one output format driver\n-specific option, \u201dintegers\u201d, which rounds all lengths, coordinates, and font\n-sizes to the nearest integer. This makes hand-editing the picture a little\n-nicer.\n-\u0088 Why is this output format driver useful? One answer is portability; any\n-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\n code. For instance, the text in a figure can be modified to contain complex\n mathematics, non-Latin alphabets, bibliographic citations, or \u2013 the real\n reason Scott wrote the LATEX2e output format driver \u2013 hyperlinks to the\n surrounding document (with help from the hyperref package).\n \n 5.6\n \n@@ -1006,27 +1008,28 @@\n whether testfile.ps still displays correctly using Ghostscript. If this file does\n not look correctly then there seems to be a problem with pstoedit\u2019s PostScript\n frontend. If this file looks good but the output for a specific format is wrong,\n the problem is probably in the output format driver for the specific format. In\n either case send bug fixes and reports to the author.\n A common problem with PostScript files is that the PostScript file redefines\n one of the standard PostScript operators inconsistently. There is no effect of\n-19\n-\n-\f9\n-\n-FAQS\n-\n this if you just print the file since the original PostScript \u201dprogram\u201d uses these\n new operators in the new meaning and does not use the original ones anymore.\n However, when run under the control of pstoedit, these operators are expected\n to work with the original semantics.\n So far I\u2019ve seen redefinitions for:\n \u0088 lt - \u201dless-then\u201d to mean \u201ddraw a line to\u201d\n \u0088 string - \u201dcreate a string object\u201d to mean \u201ddraw a string\u201d\n+\n+19\n+\n+\f9\n+\n+FAQS\n+\n \u0088 length - \u201dget the length of e.g. a string\u201d to a \u201dfloat constant\u201d\n \n I\u2019ve included work-arounds for the ones mentioned above, but some others\n could show up in addition to those.\n \n 8\n \n@@ -1057,28 +1060,28 @@\n 9\n \n FAQs\n 1. Why do letters like O or B get strange if converted to tgif/xfig using the\n -dt option?\n Most output format drivers do not support composite paths with intermediate gaps (moveto\u2019s) and second do not support very well the (eo)fill\n operators of PostScript (winding rule). For such objects pstoedit breaks\n-20\n-\n-\f12\n-\n-ACKNOWLEDGMENTS\n-\n them into smaller objects whenever such a gap is found. This results\n in the \u201dhole\u201d being filled with black color instead of being transparent.\n Since version 3.11 you can try the -ssp option in combination with the\n xfig output format driver.\n 2. Why does pstoedit produce ugly results from PostScript files generated by\n dvips?\n This is because TEX documents usually use bitmap fonts. Such fonts\n cannot be used as native font in other format. So pstoedit replaces the\n+20\n+\n+\f12\n+\n+ACKNOWLEDGMENTS\n+\n TEX font with another native font. Of course, the replacement font will\n in most cases produce another look, especially if mathematical symbols\n are used. Try to use PostScript fonts instead of the bitmap fonts when\n generating a PostScript file from TEX or LATEX.\n \n 10\n \n@@ -1113,26 +1116,26 @@\n \u0088 Christoph Jaeschke provided the OS/2 metafile (MET) output format\n driver. Thomas Hoffmann thoffman AT zappa.sax.de did some further\n updates on the OS/2 part.\n \u0088 Jens Weber rz47b7 AT PostAG.DE provided the MS Windows metafile\n (WMF) output format driver, and a graphical user interface (GUI).\n \u0088 G. Edward Johnson lorax AT nist.gov provided the CGM Draw library\n used in the CGM output format driver.\n+\u0088 Gerhard Kircher kircher AT edvz.tuwien.ac.at provided some bug\n+fixes.\n+\u0088 Bill Cheng bill.cheng AT acm.org provided help with the tgif format\n+and some changes to tgif to make the output format driver easier to implement. http://bourbon.usc.edu:8001/\n+\u0088 Reini Urban rurban AT sbox.tu-graz.ac.at provided input for the extended DXF output format driver.(http://autocad.xarch.at/)\n \n 21\n \n \f12\n \n ACKNOWLEDGMENTS\n \n-\u0088 Gerhard Kircher kircher AT edvz.tuwien.ac.at provided some bug\n-fixes.\n-\u0088 Bill Cheng bill.cheng AT acm.org provided help with the tgif format\n-and some changes to tgif to make the output format driver easier to implement. http://bourbon.usc.edu:8001/\n-\u0088 Reini Urban rurban AT sbox.tu-graz.ac.at provided input for the extended DXF output format driver.(http://autocad.xarch.at/)\n \u0088 Glenn M. Lewis glenn AT gmlewis.com provided RenderMan (RIB),\n Real3D (RPL), and LightWave 3D (LWO) output format drivers.\n (http://www.gmlewis.com/)\n \u0088 Piet van Oostrum piet AT cs.ruu.nl made several bug fixes.\n \u0088 Lutz Vieweg lkv AT mania.robin.de provided several bug fixes and suggestions for improvements.\n \u0088 Derek B. Noonburg derekn AT vw.ece.cmu.edu and Rainer Dorsch\n rd AT berlepsch.wohnheim.uni-ulm.de isolated and resolved a Linuxspecific core dump problem.\n@@ -1155,29 +1158,29 @@\n LATEX2e and MS PowerPoint output format driver.\n \u0088 The MS PowerPoint driver uses the libzip library - http://www.nih.at/libzip.\n Under MS Windows, this library is linked into the provided binary statically. Thanks to the whole libzip team.\n \u0088 Burkhard Plaum plaum AT IPF.Uni-Stuttgart.de added support for\n complex filled paths for the xfig output format driver.\n \u0088 Bernhard Herzog herzog AT online.de contributed the output format\n driver for sketch ( http://www.skencil.org/ )\n-\n-22\n-\n-\f13\n-\n-LEGAL NOTICES\n-\n \u0088 Rolf Niepraschk (niepraschk AT ptb.de) converted the HTML man page\n to LATEX format. This allows generating the UNIX style and the HTML\n manual from this base format.\n \u0088 Several others sent smaller bug fixed and bug reports. Sorry if I do not\n mention them all here.\n \u0088 Gisbert W. Selke (gisbert AT tapirsoft.de) for the Java 2 output format driver.\n \u0088 Robert S. Maier (rsm AT math.arizona.edu) for many improvements on\n the libplot output format driver and for libplot itself.\n+\n+22\n+\n+\f13\n+\n+LEGAL NOTICES\n+\n \u0088 The authors of pstotext (mcjones AT pa.dec.com and birrell AT pa.dec.com)\n for giving me the permission to use their simple PostScript code for performing rotation.\n \u0088 Daniel Gehriger gehriger AT linkcad.com for his help concerning the\n handling of Splines in the DXF format.\n \u0088 Allen Barnett libemf AT lignumcomputing.com for his work on the\n libEMF which allows creating WMF/EMF files under *nix systems.\n \u0088 Dave dave AT opaque.net for providing the libming which is a multiplatform library for generating SWF files.\n"}]}, {"source1": "./usr/share/man/man1/pstoedit.1.gz", "source2": "./usr/share/man/man1/pstoedit.1.gz", "unified_diff": null, "details": [{"source1": "pstoedit.1", "source2": "pstoedit.1", "unified_diff": "@@ -1,11 +1,11 @@\n .\\\" *********************************** start of \\input{version.tex}\n .\\\" *********************************** end of \\input{version.tex}\n '\\\" t\n-.\\\" Manual page created with latex2man on Sun Jan 7 12:54:32 2024\n+.\\\" Manual page created with latex2man on Sun Jan 7 12:57:22 2024\n .\\\" NOTE: This file is generated, DO NOT EDIT.\n .de Vb\n .ft CW\n .nf\n ..\n .de Ve\n .ft R\n@@ -538,14 +538,18 @@\n gs: \n any device that Ghostscript provides \\- use gs:format, e.g. gs:pdfwrite. \n .TP\n ps2ai: \n Adobe Illustrator via ps2ai.ps of Ghostscript. \n .PP\n No format specific options \n+.SS magick \\- MAGICK driver compatible with version 6.9.11 of ImageMagick.\n+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 6.9.11 of ImageMagick. \n+.PP\n+No format specific options \n .SS gcode \\- emc2 gcode format\n See also: \\fBhttp://linuxcnc.org/\\fP\n .PP\n No format specific options \n .SS cairo \\- cairo driver\n generates compilable c code for rendering with cairo \n .PP\n@@ -946,48 +950,14 @@\n This is a long description for the sample driver \n .PP\n The following format specific options are available: \n .TP\n [\\fB\\-sampleoption\\fP\\fI integer\\fP]\n just an example \n .PP\n-.SS magick \\- MAGICK driver compatible with version 6.9.11 of ImageMagick.\n-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 6.9.11 of ImageMagick. \n-.PP\n-No format specific options \n-.SS emf \\- Enhanced MS Windows Metafile\n-The following format specific options are available: \n-.TP\n-[\\fB\\-m\\fP]\n- map to Arial \n-.PP\n-.TP\n-[\\fB\\-nf\\fP]\n- emulate narrow fonts \n-.PP\n-.TP\n-[\\fB\\-drawbb\\fP]\n- draw bounding box \n-.PP\n-.TP\n-[\\fB\\-p\\fP]\n- prune line ends \n-.PP\n-.TP\n-[\\fB\\-nfw\\fP]\n- 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. \n-.PP\n-.TP\n-[\\fB\\-winbb\\fP]\n- let the MS Windows API calculate the Bounding Box (MS Windows only) \n-.PP\n-.TP\n-[\\fB\\-OO\\fP]\n- generate OpenOffice compatible EMF file \n-.PP\n .SS pptx \\- PresentationML (PowerPoint) format\n This is the format used internally by Microsoft PowerPoint. LibreOffice can also read/write PowerPoint files albeit with some lack of functionality. \n .PP\n The following format specific options are available: \n .TP\n [\\fB\\-colors\\fP\\fI string\\fP]\n \"original\" to retain original colors (default), \"theme\" to convert randomly to theme colors, or \"theme\\-lum\" also to vary luminance \n@@ -1040,14 +1010,44 @@\n tek via GNU libplot. \n .PP\n The following format specific options are available: \n .TP\n [\\fB\\-plotformat\\fP\\fI string\\fP]\n plotutil format to generate \n .PP\n+.SS emf \\- Enhanced MS Windows Metafile\n+The following format specific options are available: \n+.TP\n+[\\fB\\-m\\fP]\n+ map to Arial \n+.PP\n+.TP\n+[\\fB\\-nf\\fP]\n+ emulate narrow fonts \n+.PP\n+.TP\n+[\\fB\\-drawbb\\fP]\n+ draw bounding box \n+.PP\n+.TP\n+[\\fB\\-p\\fP]\n+ prune line ends \n+.PP\n+.TP\n+[\\fB\\-nfw\\fP]\n+ 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. \n+.PP\n+.TP\n+[\\fB\\-winbb\\fP]\n+ let the MS Windows API calculate the Bounding Box (MS Windows only) \n+.PP\n+.TP\n+[\\fB\\-OO\\fP]\n+ generate OpenOffice compatible EMF file \n+.PP\n .\\\" *********************************** end of \\input{driverhelp.tex}\n .SH NOTES\n \n .PP\n .SS AUTOTRACE\n .PP\n pstoedit cooperates with autotrace. Autotrace can now produce a dump file \n"}]}]}]}]}]}