buildservice-autocommit accepted request 484908 from Fridrich Strba (fstrba) about 7 years ago (revision 126)

baserev update by copy to link target

• Files Changed
• Browse Source

Fridrich Strba (fstrba) committed about 7 years ago (revision 125)

bsc#1031678

• Files Changed
• Browse Source

buildservice-autocommit accepted request 448411 from Hrvoje Senjan (sumski) over 7 years ago (revision 124)

baserev update by copy to link target

• Files Changed
• Browse Source

Hrvoje Senjan (sumski) accepted request 448387 from Ismail Dönmez (namtrac) over 7 years ago (revision 123)

- Update to version 2.7.1:
  * IMPORTANT CHANGES
    + 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.
  * IMPORTANT BUG FIXES
    + Handling of raw CID fonts was partially broken (bug introduced
      in 2.6.4).
  * MISCELLANEOUS
    + 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

• Files Changed
• Browse Source

buildservice-autocommit accepted request 426327 from Hrvoje Senjan (sumski) over 7 years ago (revision 122)

baserev update by copy to link target

• Files Changed
• Browse Source

Hillwood Yang (hillwood) accepted request 428969 from Ismail Dönmez (namtrac) over 7 years ago (revision 121)

- Also build ftinspect

• Files Changed
• Browse Source

Hrvoje Senjan (sumski) accepted request 426182 from Andrei Dziahel (develop7) over 7 years ago (revision 120)

update to version 2.7

also removed freetype2-subpixel.patch in favor of newly introduced FREETYPE_PROPERTIES environment variable

• Files Changed
• Browse Source

buildservice-autocommit accepted request 408226 from Marguerite Su (MargueriteSu) almost 8 years ago (revision 119)

baserev update by copy to link target

• Files Changed
• Browse Source

Marguerite Su (MargueriteSu) accepted request 408213 from Dominique Leuenberger (dimstar) almost 8 years ago (revision 118)

Update to 2.6.5 - addresses regression of 2.6.4 (like gd test suite failure)

• Files Changed
• Browse Source

Fridrich Strba (fstrba) accepted request 407235 from Dominique Leuenberger (dimstar) almost 8 years ago (revision 117)

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

- Update to version 2.6.4:
  + Sync with freetype 2.6.4.

• Files Changed
• Browse Source

buildservice-autocommit accepted request 380703 from Fridrich Strba (fstrba) about 8 years ago (revision 116)

baserev update by copy to link target

• Files Changed
• Browse Source

Fridrich Strba (fstrba) accepted request 380640 from Ismail Dönmez (namtrac) about 8 years ago (revision 115)

- Update to version 2.6.3
  * IMPORTANT CHANGES
    - Khmer,  Myanmar, Bengali,  and Kannada  script support  has been
      added to the auto-hinter.
  
  * MISCELLANEOUS
    - 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
      `random'.
    - 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.

• Files Changed
• Browse Source

buildservice-autocommit accepted request 346715 from Fuminobu Takeyama (ftake) over 8 years ago (revision 114)

baserev update by copy to link target

• Files Changed
• Browse Source

Fuminobu Takeyama (ftake) accepted request 346714 from Ismail Dönmez (namtrac) over 8 years ago (revision 113)

- Update to version 2.6.2
  * IMPORTANT CHANGES
    - 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
      release.
    - 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.
  * MISCELLANEOUS
    - The default  LCD filter  has been changed  to be  normalized and
      color-balanced.
    - For    better    compatibility   with    FontConfig,    function
      `FT_Library_SetLcdFilter'  accepts   a  new   enumeration  value
      `FT_LCD_FILTER_LEGACY1'   (which  has   the   same  meaning   as
      `FT_LCD_FILTER_LEGACY').
    - 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!

• Files Changed
• Browse Source

buildservice-autocommit accepted request 340705 from Takashi Iwai (tiwai) over 8 years ago (revision 112)

baserev update by copy to link target

• Files Changed
• Browse Source

Takashi Iwai (tiwai) accepted request 340688 from Stefan Brüns (StefanBruens) over 8 years ago (revision 111)

• Files Changed
• Browse Source

buildservice-autocommit accepted request 336416 from Hrvoje Senjan (sumski) over 8 years ago (revision 110)

baserev update by copy to link target

• Files Changed
• Browse Source

Hrvoje Senjan (sumski) accepted request 336413 from Stanislav Baiduzhyi (TheIndifferent) over 8 years ago (revision 109)

Updating to 2.6.1, refreshing the patches.

• Files Changed
• Browse Source

buildservice-autocommit accepted request 330455 from Marguerite Su (MargueriteSu) over 8 years ago (revision 108)

baserev update by copy to link target

• Files Changed
• Browse Source

Marguerite Su (MargueriteSu) accepted request 330451 from Bjørn Lie (Zaitor) over 8 years ago (revision 107)

Fix cut off fonts that appear in some cases. Patch based on git commit upstream.

• Files Changed
• Browse Source