1. 13 Aug, 2017 1 commit
  2. 11 Jul, 2017 1 commit
  3. 07 Jul, 2017 1 commit
  4. 27 May, 2016 1 commit
  5. 12 Jan, 2016 1 commit
    • Patrick Haller's avatar
      Optimizations in FcStrSet · d570a841
      Patrick Haller authored
      Applied optimizations:
      - skip duplicate check in FcStrSetAppend for values originating from readdir()
      - grow FcStrSet in 64-element bulks for local FcStrSets (FcConfig layout unaltered)
      
      Starting gedit is measured to
      
                              Unoptimized     Optimized
      user[s]                         0,806         0,579
      sys[s]                          0,062         0,062
      Total Instr Fetch Cost: 1.658.683.750   895.069.820
      Cachegrind D Refs:        513.917.619   312.000.436
      Cachegrind Dl Misses:       8.605.632     4.954.639
      d570a841
  6. 17 Jun, 2015 1 commit
  7. 27 May, 2015 2 commits
  8. 22 May, 2015 3 commits
  9. 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
  10. 25 Mar, 2015 1 commit
  11. 24 Feb, 2015 1 commit
  12. 30 Jun, 2014 1 commit
  13. 17 Jun, 2014 1 commit
  14. 26 Mar, 2014 1 commit
    • Akira TAGOH's avatar
      Bug 71287 - size specific design selection support in OS/2 table version 5 · 3cd573fc
      Akira TAGOH authored
      This feature requires the FreeType 2.5.1 or later at the build time.
      
      Besides <range> element allows <double> elements with this changes.
      
      This may breaks the cache but not bumping in this change sets at this moment.
      please be aware if you want to try it and run fc-cache before/after to
      avoid the weird thing against it.
      3cd573fc
  15. 11 Nov, 2013 1 commit
    • Akira TAGOH's avatar
      Fix typo · 38acb08d
      Akira TAGOH authored
      Use FcTypeUnknown instead of -1 with type casting.
      This seems missed when it was changed.
      
      Patch from brian porter
      38acb08d
  16. 31 Oct, 2013 1 commit
  17. 02 Sep, 2013 1 commit
  18. 24 Aug, 2013 1 commit
  19. 07 Aug, 2013 1 commit
  20. 09 Jul, 2013 1 commit
  21. 04 Jul, 2013 1 commit
  22. 28 Jun, 2013 2 commits
  23. 01 Feb, 2013 1 commit
    • Akira TAGOH's avatar
      Bug 23757 - Add mode="delete" to <edit> · 20191810
      Akira TAGOH authored
      Add two edit mode, "delete" and "delete_all".
      what values are being deleted depends on <test> as documented.
      if the target object is same to what is tested, matching value there
      will be deleted. otherwise all of values in the object will be deleted.
      so this would means both edit mode will not take any expressions.
      
      e.g.
      
      Given that the testing is always true here, the following rules:
      
        <match>
          <test name="foo" compare="eq">
            <string>bar</string>
          </test>
          <edit name="foo" mode="delete"/>
        </match>
      
      will removes "bar" string from "foo" object. and:
      
        <match>
          <test name="foo" compare="eq">
            <string>foo</string>
          </test>
          <edit name="bar" mode="delete"/>
        </match>
      
      will removes all of values in "bar" object.
      20191810
  24. 31 Jan, 2013 1 commit
    • Akira TAGOH's avatar
      Bug 59385 - Do the right thing for intermixed edit and test elements · d26fb23c
      Akira TAGOH authored
      This changes allows to have multiple mathcing rules in one <match> block
      in the same order.
      After this changes, the following thing will works as two matching rules:
      
      	<match>
      		<!-- rule 1 -->
      		<test name="family" compare="eq">
      			<string>foo</string>
      		</test>
      		<edit name="foo" mode="append">
      			<string>foo</string>
      		</edit>
      		<!-- rule 2 -->
      		<test name="foo" compare="eq">
      			<string>foo</string>
      		</test>
      		<edit name="foo" mode="append">
      			<string>bar</string>
      		</edit>
      	</match>
      d26fb23c
  25. 08 Jan, 2013 1 commit
  26. 02 Jan, 2013 4 commits
  27. 31 Dec, 2012 2 commits
    • Behdad Esfahbod's avatar
      Don't warn if an unknown element is used in an expression · 1fbb0b3b
      Behdad Esfahbod authored
      The type will be resolved at runtime...
      
      For example, we can do this now without getting a warning:
      
      <match target="font">
        <test name="scalable" compare="eq">
          <bool>false</bool>
        </test>
        <edit name="pixelsizefixupfactor" mode="assign">
          <divide>
            <name target="pattern">pixelsize</name>
            <name target="font"   >pixelsize</name>
          </divide>
        </edit>
        <edit name="matrix" mode="assign">
          <times>
            <name>matrix</name>
            <matrix>
              <name>pixelsizefixupfactor</name> <double>0</double>
              <double>0</double> <name>pixelsizefixupfactor</name>
             </matrix>
          </times>
        </edit>
        <edit name="size" mode="assign">
          <divide>
            <name>size</name>
            <name>pixelsizefixupfactor</name>
          </divide>
        </edit>
      </match>
      
      Previously the last edit was generating:
      
      Fontconfig warning: "/home/behdad/.local/etc/fonts/conf.d/00-scale-bitmap-fonts.conf", line 29: saw unknown, expected number
      1fbb0b3b
    • Behdad Esfahbod's avatar
      Allow target="font/pattern/default" in <name> elements · 51b00446
      Behdad Esfahbod authored
      Based on idea from Raimund Steger.
      
      For example, one can do something like this:
      
      <match target="font">
        <test name="scalable" compare="eq">
          <bool>false</bool>
        </test>
        <edit name="pixelsizefixupfactor" mode="assign">
          <divide>
            <name target="pattern">pixelsize</name>
            <name target="font"   >pixelsize</name>
          </divide>
        </edit>
        <edit name="matrix" mode="assign">
          <times>
            <name>matrix</name>
            <matrix>
              <name>pixelsizefixupfactor</name> <double>0</double>
              <double>0</double> <name>pixelsizefixupfactor</name>
             </matrix>
          </times>
        </edit>
      </match>
      
      Part of work to make bitmap font scaling possible.  See thread
      discussion:
      
      http://lists.freedesktop.org/archives/fontconfig/2012-December/004498.html
      51b00446
  28. 30 Dec, 2012 5 commits