1. 26 12月, 2015 1 次提交
  2. 17 12月, 2015 2 次提交
    • B
      Improve ligature-component handling · 2f02fc79
      Behdad Esfahbod 提交于
      We use three bits for lig_id these days, so we finally got a report of
      two separate ligatures with the same lig_id happening adjacent to each
      other, and then the component-handling code was breaking things.
      Protect against that by ignoring same-lig-id but lig-comp=0 glyphs after
      a new ligature.
      
      Fixes https://github.com/behdad/harfbuzz/issues/198
      2f02fc79
    • B
      [use] Fix halant detection · 2ab0de9f
      Behdad Esfahbod 提交于
      Before, we were just checking the use_category().  This detects as
      halant a ligature that had the halant as first glyph (as seen in
      NotoSansBalinese.)  Change that to use the is_ligated() glyph prop
      bit.  The font is forming this ligature in ccmp, which is before
      the rphf / pref tests.  So we need to make sure the "ligated" bit
      survives those tests.  Since those only check the "substituted" bit,
      we now only clear that bit for them and "ligated" survives.
      
      Fixes https://github.com/behdad/harfbuzz/issues/180
      2ab0de9f
  3. 27 11月, 2015 1 次提交
  4. 20 11月, 2015 1 次提交
  5. 19 11月, 2015 1 次提交
    • B
      Add tests for previous two commits · 85062e3b
      Behdad Esfahbod 提交于
      To fully test what these are supposed to test, they should be run
      against libharfbuzz-fuzzing.la instead of libharfbuzz.la, but for
      now just record the files.
      85062e3b
  6. 06 11月, 2015 1 次提交
  7. 05 11月, 2015 2 次提交
    • B
      Add tests for hyphen fallback · 04fd8517
      Behdad Esfahbod 提交于
      U+2011 is <noBreak> equivaent of U+2010, so we should do the fallback
      for it.  Currently fails.
      04fd8517
    • B
      Normalize various spaces to space if font doesn't support · 7793aad9
      Behdad Esfahbod 提交于
      This resurrects the space fallback feature, after I disabled
      the compatibility decomposition.  Now I can release HarfBuzz
      again without breaking Pango!
      
      It also remembers which space character it was, such that later
      on we can approximate the width of this particular space
      character.  That part is not implemented yet.
      
      We normalize all GC=Zs chars except for U+1680 OGHA SPACE MARK,
      which is better left alone.
      7793aad9
  8. 04 11月, 2015 1 次提交
  9. 15 10月, 2015 1 次提交
  10. 13 10月, 2015 1 次提交
  11. 12 10月, 2015 1 次提交
  12. 10 10月, 2015 1 次提交
  13. 01 9月, 2015 1 次提交
  14. 26 8月, 2015 1 次提交
  15. 09 8月, 2015 1 次提交
  16. 23 7月, 2015 2 次提交
  17. 11 12月, 2014 1 次提交
    • B
      [indic] Allow ZWJ/ZWNJ before SM · e6f80fa1
      Behdad Esfahbod 提交于
      In Oriya, a ZWJ/ZWNJ might be added before candrabindu to encourage
      or stop ligation of the candrabindu.  This is clearly specified in
      the Unicode section on Oriya.  Allow it there.  Note that Uniscribe
      doesn't allow this.
      
      Micro tests added using Noto Sans Oriya draft.
      
      No changes in numbers.  Currently at:
      
      BENGALI: 353725 out of 354188 tests passed. 463 failed (0.130722%)
      DEVANAGARI: 707307 out of 707394 tests passed. 87 failed (0.0122987%)
      GUJARATI: 366349 out of 366457 tests passed. 108 failed (0.0294714%)
      GURMUKHI: 60732 out of 60747 tests passed. 15 failed (0.0246926%)
      KANNADA: 951190 out of 951913 tests passed. 723 failed (0.0759523%)
      KHMER: 299070 out of 299124 tests passed. 54 failed (0.0180527%)
      MALAYALAM: 1048147 out of 1048334 tests passed. 187 failed (0.0178378%)
      ORIYA: 42320 out of 42329 tests passed. 9 failed (0.021262%)
      SINHALA: 271662 out of 271847 tests passed. 185 failed (0.068053%)
      TAMIL: 1091753 out of 1091754 tests passed. 1 failed (9.15957e-05%)
      TELUGU: 970555 out of 970573 tests passed. 18 failed (0.00185457%)
      e6f80fa1
  18. 06 8月, 2014 1 次提交
  19. 01 8月, 2014 1 次提交
  20. 27 7月, 2014 2 次提交
  21. 24 7月, 2014 1 次提交
  22. 19 7月, 2014 2 次提交
  23. 18 7月, 2014 2 次提交
  24. 17 7月, 2014 1 次提交
    • B
      Fix Mongolian Variation Selectors for fonts without GDEF · 3b861421
      Behdad Esfahbod 提交于
      Originally we fixed those in 79d1007a.
      However, fonts like MongolianWhite don't have GDEF, but have IgnoreMarks
      in their LigatureSubstitute init/etc features.  We were synthesizing a
      GDEF class of mark for Mongolian Variation Selectors and as such the
      ligature lookups where not matching.  Uniscribe doesn't do that.
      
      I tried with more sophisticated fixes, like, if there is no GDEF and
      a lookup-flag mismatch happens, instead of rejecting a match, try
      skipping that glyph.  That surely produces some interesting behavior,
      but since we don't want to support fonts missing GDEF more than we have
      to, I went for this simpler fix which is to always mark
      default-ignorables as base when synthesizing GDEF.
      
      Micro-test added.
      
      Fixes rest of https://bugs.freedesktop.org/show_bug.cgi?id=65258
      3b861421
  25. 13 6月, 2014 1 次提交