dvisvgm version history

- Removed PDF-1.x file restriction and improved opacity computation in PDF handler - Enhanced `--page` option with `%P` expansion and arithmetic expressions - Fixed character map lookup and preview package height/depth values - Updated bundled brotli library to version 1.2.0

- Fonts are now embedded in deterministic rather than random order (#288). - Different glyphs now always get distinct Unicode code points to avoid collisions, even if they represent the same character (#287). - Fixed font-related segmentation faults caused by malformed DVI files (#289). - DVI error messages now also mention the byte position where the error occurred in the DVI file. - The evaluation of PostScript operators has been improved and should be more stable now. - Many code refactorings and improvements.

- Extended the computation of Unicode points by looking for known glyph names. - Added some common glyph names not yet covered by the AGL table. - Added a warning shown if unsupported PDF specials have been ignored. - Some additions to the [manual page](https://dvisvgm.de/Manpage). - Several code improvements.

- Fixed an index error in PS operator `colorimage` (#279). - Updated the bundled [xxHash](https://xxhash.com) library to version 0.8.3. - Minor changes to the [manual page](https://dvisvgm.de/Manpage).

- Fixed the evaluation of Unicode data performed when converting PDF files (#276) - Fixed the horizontal character positioning in the PDF handler to prevent exceeding text lines. (#276) - Fixed the drawing of single-colored tensor product patches to also get correct shapes if parts of the surface overlap. - TTF/WOFF data written to SVG files now use a static creation and modification date to ensure identical SVG files for unchanged input files (#120). - Slightly improved formatting and wording of the [manual page](https://dvisvgm.de/Manpage).

This is just a small maintenance release with these changes: - When converting PDF files, dvisvgm now shows the number of the page being processed. - Added missing #include statement required as of GCC 15 (#273).

- Option `--embed-bitmaps` is now also applied to images included with special `dvisvgm:img` (#229). - Added macro `{?cmyk(c,m,y,k)}` to allow for directly specifying CMYK colors in literal SVG fragments. - Extended the dvips color specials to distinguish between fill and stroke colors. For further information see the [manual page](https://dvisvgm.de/Manpage#specials-dvisvgm:raw). - Added color special `color set` to replace the current color without pushing a new value onto the color stack. See the [manual page](https://dvisvgm.de/Manpage#specials-color) for more details. - Added macros `{?fillcolor}` and `{?strokecolor}` to retrieve the current fill and stroke color, respectively. The former macro `{?color}` equals `{?fillcolor}` and is still available too. - Replaced millimeter units with big point (bp) units in the message showing the extent of the generated SVG file. TeX's _big points_ equal SVG, PostScript, and PDF points (1in = 72bp), while TeX points are slightly smaller (1in = 72.27pt). ``` $ dvisvgm -d2 frktest pre-processing DVI file (format version 2) processing page 1 graphic size: 398.34pt x 456.34pt (396.85bp x 454.63bp) outpu

- Added file `dvisvgm.map` to the default font map files being looked up automatically. It can be used to add font mappings which should always be taken into account when dvisvgm is called. - Added evaluation of `#include` and `#includefirst` present in font map files to allow for including the contents of other map files. - The conversion of CMYK colors to RGB has been modified so that the resulting colors are now close to those created by Ghostscript and most PDF viewers. Previously, a simple mapping of the color components, like $\mathrm{cmyk}(1,0,1,0)=\mathrm{rgb}(0,1,0)$ for _green_, was used. Ghostscript, in contrast, applies ICC profiles to display colors as produced by a designated printer.\ Here's an example showing the results of the old (left) and the new CMYK to RGB color conversion applied to a Coons shading patch: <p align="center"> <img src="https://github.com/mgieseki/dvisvgm/assets/3620467/66254d2e-f599-4076-8da8-33f27efa880f"/> <img src="https://github.com/mgieseki/dvisvgm/assets/3620467/7410de82-4767-4326-9043-5265cace6d12"/> </p> - Fixed the initialization of a transformation matrix which led to invalid bounding boxes when converting a sequence of DVI

Due to the [removal of some Ghostscript-specific operators](https://cgit.ghostscript.com/cgi-bin/cgit.cgi/ghostpdl.git/commit/?id=08d75b62ffd9ae89797f351aae608c288e61b33f) from GS version 10.02.1, dvisvgm fails to extract bitmaps embedded in PS/EPS files when using the latest GS releases (also see #264). This release replaces the involved operators and should fix the issue.

- The Ghostscript library is now only loaded when the first PostScript special is processed. This slightly speeds up the conversion of DVI files that don't contain PS specials (#262). - Applied some changes required for TeX Live builds (patches by Karl Berry, #259, #260). - Added more details to some DVI warning messages. - Added some further information to the [manual page](https://dvisvgm.de/Manpage).