1. 12 May, 2015 1 commit
  2. 11 May, 2015 1 commit
  3. 30 Apr, 2015 1 commit
  4. 22 Apr, 2015 2 commits
  5. 20 Apr, 2015 1 commit
  6. 09 Apr, 2015 1 commit
    • LRN's avatar
      W32: Support cache paths relative to the root directory · f6e6a8a2
      LRN authored
      Paths starting with '/' don't make sense on W32 as-is,
      prepend the installation root directory to them.
      
      This allows the cache to be contained within a particular
      fontconfig installation (as long as the default
      --with-cache-dir= is overriden at configure time).
      f6e6a8a2
  7. 30 Mar, 2015 1 commit
  8. 25 Mar, 2015 1 commit
  9. 23 Mar, 2015 2 commits
  10. 09 Mar, 2015 3 commits
  11. 06 Mar, 2015 2 commits
  12. 05 Mar, 2015 1 commit
    • Akira TAGOH's avatar
      Improve the performance on searching blanks · 96a3f687
      Akira TAGOH authored
      After the change of d6a5cc66
      we have a lot of code points in FcBlanks. doing the linear search
      on the array isn't comfortable anymore.
      So re-implementing FcBlanksIsMember() to use the binary search.
      
      Figuring out how much improved after this change depends on
      how many fonts proceed with fc-cache say though, it's about 20 times
      faster here on testing. which sounds good enough for
      improvement.
      96a3f687
  13. 04 Mar, 2015 2 commits
  14. 03 Mar, 2015 1 commit
  15. 02 Mar, 2015 2 commits
  16. 27 Feb, 2015 3 commits
  17. 26 Feb, 2015 2 commits
  18. 25 Feb, 2015 1 commit
  19. 24 Feb, 2015 2 commits
  20. 23 Feb, 2015 1 commit
  21. 21 Jan, 2015 1 commit
    • Behdad Esfahbod's avatar
      Fix symbol cmap handling · d6d5adeb
      Behdad Esfahbod authored
      A while back we removed Apple Roman encoding support.  This broke
      symbol fonts (Wingdings, etc) because those fonts come with two
      cmaps:
      
        1) platform=1,encoding=0, aka Apple Roman, which maps identity,
        2) platform=3,encoding=0, aka MS Symbol font
      
      Now, the reason the Apple Roman removal "broke" these fonts is
      obvious, and for the better: these fonts were mapping ASCII and
      other Latin chars to symbols.
      
      The reason the fonts didn't work anymore, however, is that we were
      mishandling the MS symbol-font cmaps.  In their modern incarnation
      they are like regular non-symbol-font cmap that map PUA codepoints
      to symbols.  We want to expose those as such.  Hence, this change
      just removes the special-handling for that.
      
      Now, the reason this confusion happened, if I was to guess, is either
      that FreeType docs are wrong saying that FT_ENCODING_MS_SYMBOL is
      the "Microsoft Symbol encoding, used to encode mathematical symbols":
      
        http://www.kostis.net/charsets/symbol.htm
      
      or maybe it started that way, but turned into also mapping MS symbol-
      font cmaps, which is a completely different thing.  At any rate, I
      don't know if there are any fonts that use this thing these days, but
      the code here didn't seem to produce charset for any font.  By now I'm
      convinced that this change is the Right Thing to do.  The MS Symbol
      thing was called AdobeSymbol in our code by the way.
      
      This fixes the much-reported bug that windings, etc are not usable
      with recent fontconfig:
      https://bugs.freedesktop.org/show_bug.cgi?id=58641
      
      Now I see PUA mappings reported for Wingdings.
      
      This also fixes:
      Bug 48947 - Drop the non-Unicode cmap support gradually
      https://bugs.freedesktop.org/show_bug.cgi?id=48947
      since the AdobeSymbol was the last non-Unicode cmap we were
      trying to parse (very incorrectly).
      
      Lots of code around this change can be simplified.  I'll push those
      out (including removing the table itself) in subsequent changes.
      d6d5adeb
  22. 20 Jan, 2015 1 commit
  23. 19 Jan, 2015 2 commits
  24. 13 Jan, 2015 1 commit
  25. 06 Jan, 2015 1 commit
  26. 25 Dec, 2014 3 commits