Index index by Group index by Distribution index by Vendor index by creation date index by Name Mirrors Help Search

freetype2-devel-2.10.1-4.8.1 RPM for x86_64

From OpenSuSE Leap 15.4 for x86_64

Name: freetype2-devel Distribution: SUSE Linux Enterprise 15
Version: 2.10.1 Vendor: SUSE LLC <>
Release: 4.8.1 Build date: Wed Oct 21 10:14:00 2020
Group: Development/Libraries/C and C++ Build host: goat12
Size: 5543560 Source RPM: freetype2-2.10.1-4.8.1.src.rpm
Summary: Development environment for the freetype2 TrueType font library
This package contains all necessary include files, libraries and
documentation needed to develop applications that require the freetype2
TrueType font library.

It also contains a small tutorial for using that library.




SUSE-Freetype OR GPL-2.0-or-later


* Tue Oct 20 2020
  - Add CVE-2020-15999.patch to fix a heap buffer overflow has been
    found  in the handling of embedded PNG bitmaps
    CVE-2020-15999 bsc#1177914
* Wed Oct 09 2019
  - Use the compiler default C std, since 2012 gcc defaults
    have changed, we now only need to get rid of ANSIFLAGS, override
    that variable instead.
* Tue Jul 02 2019
  - Update to version 2.10.1
    * The bytecode hinting of OpenType variation fonts was flawed, since
      the data in the `CVAR' table wasn't correctly applied.
    * Auto-hinter support for Mongolian.
    * The handling of  the default character in PCF fonts as  introduced
      in version 2.10.0 was partially broken, causing premature abortion
      of charmap iteration for many fonts.
    * If  `FT_Set_Named_Instance' was  called  with  the same  arguments
      twice in a row, the function  returned an incorrect error code the
      second time.
    * Direct   rendering   using  FT_RASTER_FLAG_DIRECT   crashed   (bug
      introduced in version 2.10.0).
    * Increased  precision  while  computing  OpenType  font   variation
    * The  flattening  algorithm of  cubic  Bezier  curves was  slightly
      changed to make  it faster.  This can cause  very subtle rendering
      changes, which aren't noticeable by the eye, however.
    * The  auto-hinter  now  disables hinting  if there  are blue  zones
      defined for a `style' (i.e., a certain combination of a script and
      its related typographic features) but the font doesn't contain any
      characters needed to set up at least one blue zone.
  - Add tarball signatures and freetype2.keyring
* Mon Jun 24 2019
  - Update to version 2.10.0
    * A bunch of new functions has been added to access and process
      COLR/CPAL data of OpenType fonts with color-layered glyphs.
    * As a GSoC 2018 project, Nikhil Ramakrishnan completely
      overhauled and modernized the API reference.
    * The logic for computing the global ascender, descender, and
      height of OpenType fonts has been slightly adjusted for
    * `TT_Set_MM_Blend' could fail if called repeatedly with the same
    * The precision of handling deltas in Variation Fonts has been
      increased.The problem did only show up with multidimensional
    * New function `FT_Library_SetLcdGeometry' to set up the geometry
      of LCD subpixels.
    * FreeType now uses the `defaultChar' property of PCF fonts to set
      the  glyph for  the undefined  character  at glyph  index 0  (as
      FreeType already does for all other supported font formats).  As
      a consequence, the order of glyphs of a PCF font if accessed
      with  FreeType can be different now compared to previous
      This change doesn't affect PCF font access with cmaps.
    * `FT_Select_Charmap' has been changed to allow  parameter value
      `FT_ENCODING_NONE', which is valid for BDF, PCF, and Windows FNT
      formats to access built-in cmaps that don't have a predefined
      `FT_Encoding' value.
    * A previously reserved field in the `FT_GlyphSlotRec' structure
      now holds the glyph index.
    * The usual round of fuzzer bug fixes to better reject malformed
    * `FT_Outline_New_Internal' and `FT_Outline_Done_Internal' have
      been removed.These two functions were public by oversight only
      and were never documented.
    * A new function `FT_Error_String' returns descriptions of error
      codes if configuration macro FT_CONFIG_OPTION_ERROR_STRINGS is
    * `FT_Set_MM_WeightVector' and `FT_Get_MM_WeightVector' are new
      functions limited to Adobe MultiMaster fonts to directly set and
      get the weight vector.
* Sat Oct 27 2018
  - Remove old ppc64 parts in spec file
  - Refresh patches:
    + bugzilla-308961-cmex-workaround.patch
    + don-t-mark-libpng-as-required-library.patch
    + enable-long-family-names-by-default.patch
  - Enable subpixel rendering with infinality config:
    + enable-subpixel-rendering.patch
    + enable-infinality-subpixel-hinting.patch
* Mon May 14 2018
  - Re-enable freetype-config, there is just too many fallouts.
* Wed May 02 2018
  - Update to version 2.9.1
    * Type 1 fonts containing flex features were not rendered
      correctly (bug introduced in version 2.9).
    * CVE-2018-6942: Older FreeType versions can crash with certain
      malformed variation fonts.
    * Bug fix: Multiple calls to `FT_Get_MM_Var' returned garbage.
    * Emboldening of bitmaps didn't work correctly sometimes, showing
      various artifacts (bug introduced in version 2.8.1).
    * The auto-hinter script ranges have  been updated for Unicode 11.
      No support for new scripts have been added, however,  with the
      exception of Georgian Mtavruli.
  - freetype-config is now deprecated by upstream and not enabled
    by default.
  - Drop upstreamed patches:
    * bnc1079600.patch
    * psaux-flex.patch
    * 0001-src-truetype-ttinterp.c-Ins_GETVARIATION-Avoid-NULL-.patch
    * 0001-truetype-Better-protection-against-invalid-VF-data.patch
* Thu Mar 08 2018
  - Add bnc1079600.patch: Fix several integer overflow issues in
    truetype/ttinterp.c (bsc#1079600)
* Tue Mar 06 2018
  - Refresh spec-file via spec-cleaner.
  - Add shell script in separate package
    freetype2-profile-tti35 in order to be able to set TrueType
    interpreter version 35 (boo#1084085).
* Fri Feb 09 2018
  - Added patch:
    * enable-long-family-names-by-default.patch
      + Define PCF_CONFIG_OPTION_LONG_FAMILY_NAMES to obtain 2.7.1
* Wed Feb 07 2018
  - Added patches:
    * 0001-src-truetype-ttinterp.c-Ins_GETVARIATION-Avoid-NULL-.patch
      + Upstream fix for bsc#1079603: Avoid NULL reference in
    * 0001-truetype-Better-protection-against-invalid-VF-data.patch
      + Upstream fix for bsc#1079601: Protection against invalid VF
* Wed Jan 10 2018
  - Add psaux-flex.patch to fix a regression in Type1 rendering
* Tue Jan 09 2018
  - Update to version 2.9
    * Advance width values of variation fonts were often wrong.
    * More fixes for variation font support; you should update to
      this version if you want to support them.
    * As a GSoC project, Ewald Hew extended the new (Adobe) CFF
      engine to handle Type 1 fonts also, thus greatly improving
      the rendering of this format. This is the new default.
    * A new function, `FT_Set_Named_Instance', can be used to set
      or change the current named instance.
    * Starting with this FreeType version, resetting variation
      coordinates will return to the currently selected named
      instance. Previously, FreeType returned to the base font
      (i.e., no instance set).
    * Some fuzzer fixes to better reject malformed fonts.
* Mon Sep 18 2017
  - Update to version 2.8.1
    * B/W  hinting   of  TrueType   fonts  didn't  work   properly  if
      interpreter version 38 or 40 was selected.
    * Some severe  problems within the handling  of TrueType Variation
      Fonts were found and fixed.
    * Function `FT_Set_Var_Design_Coordinates' didn't correctly handle
      the case with less input coordinates than axes.
    * By default,  FreeType  now offers  high  quality  LCD-optimized
      output  without resorting to ClearType techniques of resolution
      tripling and filtering.  In this method,  called Harmony,  each
      color channel is generated separately  after shifting the glyph
      outline,  capitalizing on the fact  that the color grids on LCD
      panels  are  shifted  by  a third  of  a pixel.  This output is
      indistinguishable from ClearType with a light 3-tap filter.
    * Using the  new function `FT_Get_Var_Axis_Flags',  an application
      can access the `flags' field  of a variation axis (introduced in
      OpenType version 1.8.2)
    * FreeType  now synthesizes  a  missing Unicode  cmap for  (older)
      TrueType fonts also if glyph names are available.
    * The warping option  has moved  from `light'  to `normal' hinting
      where  it replaces  the original hinting algorithm.  The `light'
      mode is now always void of any hinting in x-direction.
* Mon May 15 2017
  - Update to version 2.8
    * Support for OpenType Variation Fonts is now complete. The last
      missing part was handling the `VVAR' and `MVAR' tables, which is
      available with this release.
    * A new  function `FT_Face_Properties' allows the  control of some
      module  and   library  properties  per  font.    Currently,  the
      following properties can be  handled: stem darkening, LCD filter
      weights, and the random seed for the `random' CFF operator.
    * The PCF change to show more `colourful' family names (introduced
      in version 2.7.1) was too radical; it can now be configured with
      PCF_CONFIG_OPTION_LONG_FAMILY_NAMES   at   compile   time.    If
      activated, it can  be switched off at run time  with the new pcf
      property  `no-long-family-names'.  If  the `FREETYPE_PROPERTIES'
      environment variable is available, you can say
    * Support  for  the  following  scripts  has  been  added  to  the
      Adlam, Avestan, Bamum, Buhid, Carian, Chakma, Coptic, Cypriot,
      Deseret, Glagolitic, Gothic, Kayah, Lisu, N'Ko, Ol Chiki, Old
      Turkic, Osage, Osmanya, Saurashtra, Shavian, Sundanese, Tai
      Viet, Tifinagh, Unified Canadian Syllabics, Vai
    * `Light' auto-hinting  mode no  longer uses TrueType  metrics for
      TrueType  fonts.   This bug  was  introduced  in version  2.4.6,
      causing   horizontal  scaling   also.    Almost  all   GNU/Linux
      distributions (with Fedora as  a notable exception) disabled the
      corresponding patch for good reasons; chances are thus high that
      you won't notice a difference.
    * If a TrueType font gets loaded with FT_LOAD_NO_HINTING, FreeType
      now scales  the font linearly  again (bug introduced  in version
    * Fixed CVE-2017-8105,  CVE-2017-8287:  Older   FreeType  versions
      have out-of-bounds  writes  caused  by  heap-based  buffer  overflows
      related to Type 1 fonts. (boo#1035807, boo#1036457)
  - See for
    the complete changelog.
* Sun Jan 01 2017
  - Update to version 2.7.1:
      + Support for the new CFF2 font format as introduced with
      OpenType 1.8 has been contributed by Dave Arnolds from Adobe.
      + Preliminary support for variation fonts as specified in
      OpenType 1.8 (in addition to the already existing support for
      Adobe's MM and Apple's GX formats). Dave Arnolds contributed
      handling of advance width change variation; more will come in
      the next version.
      + Handling of raw CID fonts was partially broken (bug introduced
      in 2.6.4).
      + Some limits for TrueType bytecode execution have been tightened
      to speed up FreeType's handling of malformed fonts, in
      particular to quickly abort endless loops.
      + The number of twilight points can no longer be set to an
      arbitrarily large value.
      + The total number of jump opcode instructions (like JMPR) with
      negative arguments is dynamically restricted; the same holds
      for the total number of iterations in LOOPCALL opcodes.
      + The dynamic limits are based on the number of points in a glyph
      and the number of CVT entries. Please report if you encounter a
      font where the selected values are not adequate.
      + PCF family names are made more `colourful'; they now include the
      foundry and information whether they contain wide characters.
      For example, you no longer get `Fixed' but rather `Sony Fixed'
      or `Misc Fixed Wide'.
      + A new function `FT_Get_Var_Blend_Coordinates' (with its alias
      name `FT_Get_MM_Blend_Coordinates') to retrieve the normalized
      blend coordinates of the currently selected variation instance
      has been added to the Multiple Masters interface.
      + A new function `FT_Get_Var_Design_Coordinates' to retrieve the
      design coordinates of the currently selected variation instance
      has been added to the Multiple Masters interface.
      + A new load flag `FT_LOAD_BITMAP_METRICS_ONLY' to retrieve bitmap
      information without loading the (embedded) bitmap itself.
      + Retrieving advance widths from bitmap strikes (using
      `FT_Get_Advance' and `FT_Get_Advances') have been sped up.
      + The usual round of fuzzer fixes to better reject malformed
  - Drop freetype2-bitmap-foundry.patch, merged upstream.
* Fri Sep 09 2016
  - update to version 2.7:
      + As announced earlier, the 2.7.x series now uses the new subpixel
      hinting  mode as  the  default, emulating  a  modern version  of
      This change inevitably leads to different rendering results, and
      you   might   change   the   `TT_CONFIG_OPTION_SUBPIXEL_HINTING'
      configuration option to  adapt it to your taste (or  use the new
      `FREETYPE_PROPERTIES'    environment    variable).    See    the
      corresponding entry  below for  version 2.6.4, which  gives more
      + A new option  `FT_CONFIG_OPTION_ENVIRONMENT_PROPERTIES' has been
      introduced.   If  set (which  is  the  default), an  environment
      variable  `FREETYPE_PROPERTIES' can  be used  to control  driver
      properties.  Example:
      FREETYPE_PROPERTIES=truetype:interpreter-version=35 \
      cff:no-stem-darkening=1 \
      This allows to select, say, the subpixel hinting mode at runtime
      for a given application.  See file `ftoption.h' for more.
      + After  loading a  named instance  of  a GX  variation font,  the
      `face_index'  value  in  the returned  `FT_Face'  structure  now
      correctly holds the named instance  index in the upper 16bits as
      + A new macro `FT_IS_NAMED_INSTANCE' to  test whether a given face
      is a named instance.
      + More fixes to GX font handling.
      + Apple's   `GETVARIATION'  bytecode   operator  (needed   for  GX
      variation font support) has been implemented.
      + Another round  of fuzzer fixes,  mainly to reject  invalid fonts
      + Handling of raw CID fonts  was broken (bug introduced in version
      + The smooth rasterizer has been streamlined  to make it faster by
      approx. 20%.
      + The `ftgrid'  demo program now  understands command  line option
      `-d' to give start-up design coordinates.
      + The `ftdump' demo program has  a new command line option `-p' to
      dump TrueType bytecode instructions.
  - removed freetype2-subpixel.patch in favor of above
    FREETYPE_PROPERTIES environment variable
* Wed Jul 13 2016
  - Update to version 2.6.5:
    + Compilation works again  on Mac OS X (bug introduced in version
    + The new  subpixel hinting  mode is now  disabled by  default; it
      will  be enabled  by default  in the  forthcoming 2.7.x  series.
      Main reason for reverting this feature is the principle of least
      surprise: a  sudden change in  appearance of all fonts  (even if
      the rendering improves  for almost all recent  fonts) should not
      be expected in a new micro version of a series.
  - Rebase freetype2-subpixel.patch.
* Fri Jul 08 2016
  - Upadte to version 2.6.4:
    * A new subpixel hinting mode, which is now the default rendering
      mode for TrueType fonts. It implements (almost everything of)
      version 40 of the bytecode engine. The existing code base in
      FreeType (the `Infinality code') was stripped to the bare
      minimum and all configurability removed in the name of speed
      and simplicity. The configurability was mainly aimed at legacy
      fonts like Arial, Times New Roman, or Courier. [Legacy fonts
      are fonts that modify vertical stems to achieve clean
      black-and-white bitmaps.] The new mode focuses on applying a
      minimal set of rules to all fonts indiscriminately so that
      modern and web fonts render well while legacy fonts render
      okay. Activation of the subpixel hinting support can be
      controlled with the `TT_CONFIG_OPTION_SUBPIXEL_HINTING'
      configuration option at compile time: If set to value 1, you
      get the old Infinality mode (which was never the default due to
      its slowness). Value 2 activates the new subpixel hinting mode,
      and value 3 activates both. The default is value 2. At run
      time, you can select the subpixel hinting mode with the
      `interpreter-version' property (provided you have compiled in
      the corresponding hinting mode); see `ftttdrv.h' for more.
    * Support for the following scripts has been added to the
      auto-hinter: Armenian, Cherokee, Ethiopic, Georgian, Gujarati,
      Gurmukhi, Malayalam, Sinhala, Tamil.
  - Rebase freetype2-subpixel.patch.
* Mon Mar 28 2016
  - Update to version 2.6.3
    - Khmer,  Myanmar, Bengali,  and Kannada  script support  has been
      added to the auto-hinter.
    - Better  support of  Indic  scripts like  Devanagari  by using  a
      top-to-bottom hinting flow.
    - All  FreeType macros  starting  with two  underscores have  been
      renamed to  avoid a violation of  both the C and  C++ standards.
      Example: Header  macros of the  form `__FOO_H__' are  now called
      `FOO_H_'.  In most cases,  this should be completely transparent
      to the user.   The exception to this  is `__FTERRORS_H__', which
      must be  sometimes undefined by  the user to get  FreeType error
      strings:  Both this  form and  the new  `FTERRORS_H_' macro  are
      accepted for backwards compatibility.
    - Minor improvements mainly to the Type 1 driver.
    - The  new CFF  engine now  supports all  Type 2  operators except
    - The macro `_STANDALONE_', used for  compiling the B/W and smooth
      rasterizers  as   stand-alone  modules,  has  been   renamed  to
      `STANDALONE_', since macro names starting with an underscore and
      followed by an uppercase letter are reserved in both C and C++.
    - Function  `FT_Library_SetLcdFilterWeights'  now  also  activates
      custom LCD filter weights (instead of just adjusting them).
    - Support for  `unpatented hinting'  has been  completely removed:
      Consequently,  the two  functions `FT_Face_CheckTrueTypePatents'
      and  `FT_Face_SetUnpatentedHinting'  now  return  always  false,
      doing nothing.
* Sun Nov 29 2015
  - Update to version 2.6.2
    - The auto-hinter now supports stem darkening, to be controlled by
      the    new   `no-stem-darkening'    and   `darkening-parameters'
      properties.   This is  an  experimental  feature contributed  by
      Nikolaus Waxweiler, and  the interface might change  in a future
    - By default, stem darkening is now switched off (for both the CFF
      engine and the  auto-hinter).  The main reason is  that you need
      linear  alpha  blending  and  gamma correction  to  get  correct
      rendering results, and  the latter is not yet  available in most
      freely  available  rendering  stacks like  X11.   Applying  stem
      darkening without proper gamma correction  leads to far too dark
      rendering results.
    - The   meaning  of   `FT_RENDER_MODE_LIGHT'  has   been  slightly
      modified.   It  now  essentially  means `no  hinting  along  the
      horizontal  axis'; in  particular,  no change  of glyph  advance
      widths.  Consequently, the auto-hinter  is used for all scalable
      font  formats  except  for  CFF.    It  is  planned  that  other
      font-specific rendering engines (TrueType, Type 1) will follow.
    - The default  LCD filter  has been changed  to be  normalized and
    - For    better    compatibility   with    FontConfig,    function
      `FT_Library_SetLcdFilter'  accepts   a  new   enumeration  value
      `FT_LCD_FILTER_LEGACY1'   (which  has   the   same  meaning   as
    - A large number of bugs have been detected by using the libFuzzer
      framework,  which should  further  improve  handling of  invalid
      fonts.  Thanks again to Kostya Serebryany and Bungeman!
    - `TT_CONFIG_OPTION_MAX_RUNNABLE_OPCODES',  a   new  configuration
      option, controls the maximum number of executed opcodes within a
      bytecode program.  You don't want to change this except for very
      special  situations (e.g.,  making a  library fuzzer  spend less
      time to handle broken fonts).
    - The smooth renderer has been made faster.
* Sun Oct 04 2015
  - Update to version 2.6.1
    - It turned  out that for CFFs  only the advance widths  should be
      taken from the  `htmx' table, not the side  bearings.  This bug,
      introduced in  version 2.6.0, makes  it necessary to  upgrade if
      you are using  CFFs; otherwise, you get cropped  glyphs with GUI
      interfaces like GTK or Qt.
    - Accessing Type 42 fonts returned  incorrect results if the glyph
      order of the embedded TrueType font differs from the glyph order
      of the Type 42 charstrings table.
    - The header  file layout  has been  changed (again),  moving  all
      header files except `ft2build.h' into a subdirectory tree.
      Doing so  reduces the  possibility of  header file  name clashes
      (e.g., FTGL's  `FTGlyph.h' with FreeType's `ftglyph.h')  on case
      insensitive file systems like Mac OS X or Windows.
      Applications  that  use  (a)  the  `freetype-config'  script  or
      FreeType's `freetype2.pc' file for pkg-config to get the include
      directory  for the  compiler,  and (b)  the  documented way  for
      header inclusion like
      [#]include <ft2build.h>
      [#]include FT_FREETYPE_H
      don't need any change to the source code.
    - Simple access  to named instances  in GX variation fonts  is now
      available (in addition to the  previous method via FreeType's MM
      interface).   In  the `FT_Face'  structure,  bits  16-30 of  the
      `face_index' field hold the current named instance index for the
      given face  index, and bits  16-30 of `style_flags'  contain the
      number of  instances for  the given face  index.  `FT_Open_Face'
      and friends also understand the  extended bits of the face index
      You need to enable  TT_CONFIG_OPTION_GX_VAR_SUPPORT for this new
      feature.  Otherwise, bits  16-30 of the two fields  are zero (or
      are ignored).
    - Lao script support has been added to the auto-hinter.
    - The auto-hinter's Arabic script support has been enhanced.
    - Superscript-like and  subscript-like glyphs  as used  by various
      phonetic alphabets like the IPA  are now better supported by the
    - The TrueType bytecode interpreter now runs slightly faster.
    - Improved support for builds with cmake.
    - The  function  `FT_CeilFix'  now   always  rounds  towards  plus
    - The  function  `FT_FloorFix'  now always  rounds  towards  minus
    - A  new load  flag `FT_LOAD_COMPUTE_METRICS'  has been  added; it
      makes FreeType  ignore pre-computed  metrics, as needed  by font
      validating  or  font  editing  programs.  Right  now,  only  the
      TrueType  module supports  it  to ignore  data  from the  `hdmx'
    - Another round of bug fixes  to better handle broken fonts, found
      by Kostya Serebryany <>.
  - Dropping upstreamed patch Dont-use-hmtx-table-for-LSB.patch.
* Fri Sep 11 2015
  - Add Dont-use-hmtx-table-for-LSB.patch: Fixes gnu#45520, cut off
    fonts in gtk and qt. Taken from upstream git.
* Thu Jun 11 2015
  - Update to version 2.6
    * Thread safety improvements
    * Thai script support has been added to the auto-hinter.
    * Arabic script support has been added to the auto-hinter.
    * Following OpenType version 1.7,  advance widths and side bearing
      values in  CFFs (wrapped  in an SFNT  structure) are  now always
      taken from the `hmtx' table.
    * Following OpenType  version 1.7, the  PostScript font name  of a
      CFF font (wrapped in an SFNT structure) is now always taken from
      the `name'  table.  This is  also true for  OpenType Collections
      (i.e., TTCs using  CFFs subfonts instead of TTFs),  where it may
      have a significant difference.
    * Fonts natively hinted for  ClearType are now supported, properly
      handling selector index 3 of the INSTCTRL bytecode instruction.
    * Major improvements to the GX TrueType variation font handling.
* Tue Jun 09 2015
  - Merge with the version 2.5.5 from openSUSE:Factory
  - Removed patches:
    * CVE-2014-9656.patch
    * CVE-2014-9657.patch
    * CVE-2014-9658.patch
    * CVE-2014-9659.patch
    * CVE-2014-9660.patch
    * CVE-2014-9661.patch
    * CVE-2014-9662.patch
    * CVE-2014-9663.patch
    * CVE-2014-9664.patch
    * CVE-2014-9665.patch
    * CVE-2014-9666.patch
    * CVE-2014-9667.patch
    * CVE-2014-9668.patch
    * CVE-2014-9669.patch
    * CVE-2014-9670.patch
    * CVE-2014-9671.patch
    * CVE-2014-9672.patch
    * CVE-2014-9673.patch
    * CVE-2014-9674.patch
    * CVE-2014-9675.patch
    - Integrated in the 2.5.5 release
  - Modified patches:
    * don-t-mark-libpng-as-required-library.patch
    * bugzilla-308961-cmex-workaround.patch
    * freetype2-subpixel.patch
    * freetype2-bitmap-foundry.patch
    * overflow.patch
    - Adapt to the new version of sources
* Wed Jun 03 2015
  - Modified patch:
    * CVE-2014-9671.patch
    - Adapt the code to correspond to the current git master of
      freetype2 (fixes bsc#933247)
* Fri Apr 10 2015
  - Enable the bz2 compression in freetype2
  - Remove patch overflow.patch from freetype2.spec where it is not
  - Run spec-cleaner on the spec file.
* Fri Feb 20 2015
  - fixed vulnerabilities (bnc#916847, bnc#916856, bnc#916857,
    bnc#916858, bnc#916859, bnc#916860, bnc#916861, bnc#916862,
    bnc#916863, bnc#916864, bnc#916865, bnc#916867, bnc#916868,
    bnc#916870, bnc#916871, bnc#916872, bnc#916873, bnc#916874,
    bnc#916879, bnc#916881)
    - CVE-2014-9656.patch
    - CVE-2014-9657.patch
    - CVE-2014-9658.patch
    - CVE-2014-9659.patch
    - CVE-2014-9660.patch
    - CVE-2014-9661.patch
    - CVE-2014-9662.patch
    - CVE-2014-9663.patch
    - CVE-2014-9664.patch
    - CVE-2014-9665.patch
    - CVE-2014-9666.patch
    - CVE-2014-9667.patch
    - CVE-2014-9668.patch
    - CVE-2014-9669.patch
    - CVE-2014-9670.patch
    - CVE-2014-9671.patch
    - CVE-2014-9672.patch
    - CVE-2014-9673.patch
    - CVE-2014-9674.patch
    - CVE-2014-9675.patch
* Sat Jan 03 2015
  - Update to version 2.5.5
    - Handling of  uncompressed PCF files works again (bug
      introduced in version 2.5.4).
  - Drop freetype2-2.5.3-fix-pcf.patch, merged upstream
* Mon Dec 08 2014
  - Update to version 2.5.4
    - A variant of vulnerability CVE-2014-2240 was identified
      (cf. and fixed
      in  the new CFF driver.  All users should upgrade.
    - The new auto-hinter code using HarfBuzz crashed for some
      invalid fonts.
    - Many fixes to better protect against malformed input.
    - Full auto-hinter support of the Devanagari script.
    - Experimental auto-hinter support of the Telugu script.
    - CFF stem darkening behaviour can now be controlled at
      build time using the eight macros
    - Some fields in the `FT_Bitmap'  structure have been changed
      from signed to unsigned type, which better reflects
      the actual usage. It is also an additional means to
      protect against malformed input. This change doesn't break
      the ABI; however, it might cause compiler warnings.
    - Improvements to  the auto-hinter's algorithm to recognize
      stems and local extrema.
    - Function `FT_Get_SubGlyph_Info' always returned an error
      even in case of success.
    - Version  2.5.1 introduced major bugs in the cjk part of
      the auto-hinter, which are now fixed.
    - The `FT_Sfnt_Tag' enumeration values have been changed to
      uppercase,  e.g.  `FT_SFNT_HEAD'. The lowercase variants
      are deprecated. This is for orthogonality with all other
      enumeration (and enumeration-like) values in FreeType.
    - `cmake' now supports builds of FreeType as an OS X framework
      and for iOS.
    - Improved project files for vc2010,
      introducing a property file
    - The documentation generator for the API reference has been
      updated to produce  better HTML code (with proper  CSS).
      At the same time, the documentation got a better structure.
    - The FT_LOAD_BITMAP_CROP flag is obsolete; it is not used
      by any driver.
    - The TrueType DELTAP[123] bytecode instructions now work in
      subpixel hinting mode as described in the ClearType
      whitepaper (i.e., for touched points in the
      non-subpixel direction).
    - Many small improvements to the internal arithmetic routines.
  - Rebase don-t-mark-libpng-as-required-library.patch,
    bugzilla-308961-cmex-workaround.patch, freetype2-subpixel.patch,
    freetype2-bitmap-foundry.patch and overflow.patch
  - Add freetype2-2.5.3-fix-pcf.patch from upstream to resolve, "Freetype 2.5.4 does not
    load ungzipped PCF fonts"



Generated by rpm2html 1.8.1

Fabrice Bellet, Sun Jun 9 15:51:30 2024