1. 13 Jan, 2015 1 commit
  2. 06 Jan, 2015 1 commit
  3. 25 Dec, 2014 3 commits
  4. 24 Dec, 2014 1 commit
  5. 16 Dec, 2014 1 commit
  6. 15 Dec, 2014 1 commit
    • Nick Alcock's avatar
      Generate documentation for FcWeight* functions. · af586441
      Nick Alcock authored
      The SGML for these functions exists, and they are named as manpages,
      but because they are not mentioned in fontconfig-devel.sgml, no
      documentation is ever generated, and installation under --enable-docs
      fails.
      
      (The documentation I have written in fontconfig-devel.sgml is boilerplate
      so I can get the manpages generated. It's probably wrong.)
      af586441
  7. 14 Dec, 2014 2 commits
    • Behdad Esfahbod's avatar
      Treat color fonts as scalable · 66db69a6
      Behdad Esfahbod authored
      All color fonts are designed to be scaled, even if they only have
      bitmap strikes.  Client is responsible to scale the bitmaps.  This
      is in constrast to non-color strikes...
      
      Clients can still use FC_OUTLINE to distinguish bitmap vs outline
      fonts.  Previously FC_OUTLINE and FC_SCALABLE always had the same
      value.  Now FC_SCALABLE is set to (FC_OUTLINE || FC_COLOR).
      
      Fixes:
      https://bugs.freedesktop.org/show_bug.cgi?id=87122
      66db69a6
    • Behdad Esfahbod's avatar
      Add FC_COLOR · dbc7c4a2
      Behdad Esfahbod authored
      Only adds "color" to pattern if FreeType version supports color.
      
      Based on patch from Jungshik Shin.
      dbc7c4a2
  8. 13 Dec, 2014 1 commit
  9. 09 Dec, 2014 1 commit
  10. 06 Nov, 2014 1 commit
  11. 03 Oct, 2014 1 commit
  12. 25 Sep, 2014 1 commit
  13. 20 Aug, 2014 1 commit
    • Behdad Esfahbod's avatar
      Revert "[fcmatch] When matching, reserve score 0 for when elements don't exist" · 286cdc9c
      Behdad Esfahbod authored
      This reverts commit a5a384c5.
      
      I don't remember what I had in mind for "We will use this property later.", but
      the change was wrong.  If a font pattern doesn't have any value for element,
      it must be interpretted as "it matches any value perfectly.  And "perfectly"
      must have a score of 0 for that to happen.
      
      This was actually affecting bitmap fonts (in a bad way), as the change made
      an outline font to always be preferred over a (otherwise equal) bitmap font,
      even for the exact size of the bitmap font.  That probably was never noticed
      by anyone, but with the font range support this has become clear (and worked
      around by Akira).  To clean that up, I'm reverting this so I can land the
      rest of patches for bug 80873.
      
      https://bugs.freedesktop.org/show_bug.cgi?id=80873#c10
      286cdc9c
  14. 13 Aug, 2014 1 commit
  15. 12 Aug, 2014 2 commits
  16. 11 Aug, 2014 1 commit
  17. 06 Aug, 2014 4 commits
  18. 27 Jul, 2014 1 commit
  19. 26 Jul, 2014 1 commit
  20. 25 Jul, 2014 3 commits
  21. 24 Jul, 2014 6 commits
  22. 23 Jul, 2014 3 commits
  23. 19 Jul, 2014 1 commit
  24. 11 Jul, 2014 1 commit