summaryrefslogtreecommitdiff
path: root/freetype
Commit message (Collapse)AuthorAgeFilesLines
* Update fretype to 2.13.0Chris Liddell2023-02-10687-4406/+30852
|
* oss-fuzz 50057: freetype: [base, type1] Better handling of out-of-memory ↵Chris Liddell2022-08-222-2/+5
| | | | | | | situations. Committed upstream: https://gitlab.freedesktop.org/freetype/freetype/-/commit/37b718d5899bc4a85425fcc548a7636871808f96
* Have freetype properly reset the FT_GlyphLoader on errorChris Liddell2022-07-041-4/+10
| | | | | | | | | | | | Some of the error exit code paths in FT_GlyphLoader_CheckPoints() skipped the code that reset the FT_GlyphLoader, meaning a subsequent glyph creation would attempt to use a partially initialised FT_GlyphLoader and potentially crash. Stems from, and replaces original fix for, oss-fuzz: 44994 Change included upstream: https://gitlab.freedesktop.org/freetype/freetype/-/commit/1a242558be670626ed2ec62efb1909c000b2cae7
* Make FT_EXPORT and FT_EXPORT_DEF definitions conditionalChris Liddell2022-06-012-1/+4
| | | | | This is required so we can use our own definitions, and hide the Freetype symbols inside our .so build.
* Update freetype to 2.12.1Chris Liddell2022-05-05685-4864/+28426
|
* Update freetype to 2.11.1Chris Liddell2021-12-07750-54248/+84284
|
* Update freetype to 2.10.4 (for real, this time!)Chris Liddell2021-01-05718-92445/+6525
| | | | (with zlib "Diagnostic functions" hack/fix in freetype/src/zutil.h)
* Update freetype to 2.10.4Chris Liddell2020-10-23119-0/+89590
| | | | | | | Also includes: Work around a change in the zlib API for 1.2.11 where it's used in the Freetype/zlib interface debugging code.
* Update Freetype to 2.4.10Chris Liddell2019-11-26825-89115/+131502
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Plus makefile updates to support it Bug 701288: Handle SEAC ligature glyph metrics correctly. As originally intended, a Type 1 SEAC charstring would be used for an accented glyph (like an a-caron, or u-umlaut) where the advance with of the SEAC glyph is the same as that of the 'base' glyph ('a' or 'u'). It this case, it is not uncommon for the SEAC to skip using an (H)SBW op code and rely on the one from the base glyph. But out of spec fonts also use SEAC glyphs ligature glyphs (like 'oe' or 'fi'), and in those cases the overall advance width is greater than that of the 'base' glyph. In this case, we have to allow for the SEAC glyph having included an (H)SBW and if it has, retain those values, rather than those from the base glyph. Rename file and make file change to match Avoids file name clash with freetype 2.4.10 Work around a change in the zlib API for 1.2.11 where it's used in the Freetype/zlib interface debugging code.
* Bug 701288: Handle SEAC ligature glyph metrics correctly.Chris Liddell2019-07-041-6/+16
| | | | | | | | | | | | | | | | As originally intended, a Type 1 SEAC charstring would be used for an accented glyph (like an a-caron, or u-umlaut) where the advance with of the SEAC glyph is the same as that of the 'base' glyph ('a' or 'u'). It this case, it is not uncommon for the SEAC to skip using an (H)SBW op code and rely on the one from the base glyph. But out of spec fonts also use SEAC glyphs ligature glyphs (like 'oe' or 'fi'), and in those cases the overall advance width is greater than that of the 'base' glyph. In this case, we have to allow for the SEAC glyph having included an (H)SBW and if it has, retain those values, rather than those from the base glyph.
* Bug 700460: Fix Freetype Type1 path segment closepathChris Liddell2019-01-091-2/+1
| | | | | | | | | | | | | | | * src/psaux/psintrp.c: correctly close a contour All of the Type 1 path building is done with code common to the revised CFF engine, with the exception of closepath, which was still calling ps_builder_close_contour(), thus previously cached segments were not always written to the path, and glyph corruption, or even invalid outlines were possible. Switch to calling cf2_glyphpath_closeOpenPath() Committed upstream: http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b75abeb5e6561024d182ccdc0eb36a7d2630310e
* Add a setweightvector analogue in FreetypeChris Liddell2018-11-288-74/+339
| | | | | | | Avoids the need to recreate the FT font everytime the weightvector changes. These Freetype changes have been accepted upstream: http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=78a1e69517ca067224d6e33beffd25e2ec8361d2
* Bug 697545 : Prevent SEGV by propagating error code in af_loader_load_glyph.Shailesh Mistry2018-11-011-1/+5
| | | | | | | Propagate error by checking for return code. Error created using :- MEMENTO_FAILAT=31598 ./membin/gpcl6 -sDEVICE=pbmraw -dMaxBitmap=2000 -o /dev/null ./tests_private/pcl/pcl5cfts/fts.0270
* Fix for small glyph distortionChris Liddell2018-05-181-19/+13
| | | | | | | | | | | | | Glyphs with very few pixels (i.e. lower case "i" in 9pt text rendered at 72dpi) we being distorted due to the specific rules applied by Freetype's dropout compensation. This isn't a full solution but resolves the change in behaviour between 2.7.x and 2.9.x (the change was due to different rounding being applied). This fix is from upstream: http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=f1458d2e44d8 So should be in future Freetype releases, and not need re-applied here.
* Work around a behaviour change in freetype > 2.8Chris Liddell2018-05-18716-44558/+58695
| | | | | | | | | | | | | | | | Freetype will throw an error when we try to retrieve the glyph if the x/y advance values are too big to fit in a 16.16 fixed point value. Since we have no need of those values, set them to zero, and avoid the error. Bring freetype up to 2.9.1 Plus the gs makefile changes to support the new version. Reapply "Work around a change in the zlib API for 1.2.11" for Freetype commit: 08482c582115a1396d0fd9186011008f889a61c5
* Bug 697545 : Prevent SEGV in freetype if running out of memory.Shailesh Mistry2018-05-163-22/+75
| | | | | | | | Prevent SEGV when trying to use buffer after memory failure. This patch has been accepted by the freetype team as commit e0015f7612cf07ff80561475321ce1f98c7c2b88 Error created using :- MEMENTO_FAILAT=17104 ./membin/gpcl6 -sDEVICE=pbmraw -dMaxBitmap=2000 -o /dev/null ./tests_private/pcl/pcl5cfts/fts.0051
* Work around a change in the zlib API for 1.2.11Chris Liddell2018-03-061-9/+6
| | | | where it's used in the Freetype/zlib interface debugging code.
* Update freetype to 2.7.0Chris Liddell2016-11-22712-20996/+37262
| | | | | | Tweak makefile for new freetype version Force use of the v35 Freetype bytecode interpreter
* Commit of build_consolidation branchChris Liddell2015-07-20751-0/+345937
Squashed into one commit (see branch for details of the evolution of the branch). This brings gpcl6 and gxps into the Ghostscript build system, and a shared set of graphics library object files for all the interpreters. Also, brings the same configuration options to the pcl and xps products as we have for Ghostscript.
View Lorry Controller Status