- spec-cleaner

- Move ftpdump from ft2demos to freetype - it's required by other
  packages and doesn't require any of the toolkits, so move its
  build early

- drop revert-ft212-subpixel-hinting-change.patch: upstream

- Update to 2.12.1:
  - Loading CFF fonts sometimes made FreeType crash (bug introduced in
    version 2.12.0)
  - Loading  a fully  hinted  TrueType glyph  a  second time  (without
    caching) sometimes yielded different rendering results if TrueType
    hinting was active (bug introduced in version 2.12.0).
  - The generation of the pkg-config file `freetype2.pc` was broken if
    the build was done with cmake (bug introduced in version 2.12.0).
  - The  meson  build  no  longer enforces  both  static  and  dynamic
    versions of the library by default.
  - The internal  zlib library was  updated to version  1.2.12.  Note,
    however, that  FreeType is *not* affected  by CVE-2018-25032 since
    it only does decompression.
- Drop freetype-2.12.0-cff_slot_load-segfault.patch
- Drop 079a22da037835daf5be2bd9eccf7bc1eaa2e783.patch

- add revert-ft212-subpixel-hinting-change.patch (bsc#1198536)
- add 079a22da037835daf5be2bd9eccf7bc1eaa2e783.patch to avoid
  an integer overflow occuring during fuzzing

- fix segfault in some applications boo#1198497
  add freetype-2.12.0-cff_slot_load-segfault.patch

• Files Changed
• Browse Source

- 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.

- 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
    instances.
  * 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

- 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.

• Files Changed
• Browse Source

- update to version 2.7:
  * IMPORTANT CHANGES
    + As announced earlier, the 2.7.x series now uses the new subpixel
      hinting  mode as  the  default, emulating  a  modern version  of
      ClearType.
      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
      information.
    - 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 \
                            autofitter:warping=1
      This allows to select, say, the subpixel hinting mode at runtime
      for a given application.  See file `ftoption.h' for more.
  * IMPORTANT BUG FIXES
    + 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
      documented.
  * MISCELLANEOUS
    + 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

• Files Changed
• Browse Source

• Files Changed
• Browse Source

• Browse Source