Update Ghostscript from 9.26 to 9.27 #1074
Merged
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[Release notes][1]: > IMPORTANT: It is our intention, within the next 12 months (ideally > sooner, in time for the next release) to make SAFER the default mode of > operation. For many users this will have no effect, since they use SAFER > explicitly, but some niche uses which rely on SAFER being disabled may > need to start explicitly adding the "-dNOSAFER" option. > > Highlights in this release include: > > * We have extensively cleaned up the Postscript name space: removing > access to internal and/or undocumented Postscript operators, procedures > and data. This has benefits for security and maintainability. > > * We have added a new "product": "gpdl". This is a rethink/redesign of > the old "language_switch" product (pspcl6), and includes all the > interpreters we develop based on the Ghostscript graphics library: > Postscript, PDF, PCL6, PXL and XPS. This is experimental, and should be > considered of beta testing quality, and thus is not built by default: it > can be built by using the "experimental" target. > > * gpdl uses a heuristic to judge the file type being passed to it. In > general, it supports most of the widely used command line options for > each interpreter, but compatibility is not complete (the practicalities > of swapping interpreters means it is unlikely that full parity of > command line options will be possible). > > * Fontmap can now reference invidual fonts in a TrueType Collection > for font subsitution. Previously, a Fontmap entry could only reference a > TrueType collection and use the default (first) font. Now, the Fontmap > syntax allows for specifying a specific index in a TTC. See the comments > at the top of (the default) Fontmap.GS for details. > > * IMPORTANT: We are in the process of forking LittleCMS. LCMS2 is not > thread safe, and cannot be made thread safe without breaking the ABI. > Our fork will be thread safe, and include performance enhancements > (these changes have all be been offered and rejected upstream). We will > maintain compatibility between Ghostscript and LCMS2 for a time, but not > in perpetuity. Our fork will be available as its own package separately > from Ghostscript (and MuPDF). > > * The usual round of bug fixes, compatibility changes, and incremental > improvements. [1]: https://www.ghostscript.com/doc/9.27/News.htm
pmenzel
changed the title
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tested on pummeluff.