• Show log

    Commit

  • Hash : 22ad9ef0
    Author : Werner Lemberg
    Date : 2005-05-09T22:11:36

    Handle unsorted SFNT type 4 cmaps correctly (reported by Dirck
    Blaskey).
    
    * src/sfnt/ttcmap.h (TT_CMap): Add member `unsorted'.
    * src/sfnt/ttcmac.c: Use SFNT_Err_Ok where appropriate.
    
    (tt_cmap0_validate, tt_cmap2_validate, tt_cmap6_validate,
    tt_cmap8_validate, tt_cmap10_validate, tt_cmap12_validate): Use
    `FT_Error' as return type.
    (tt_cmap4_validate): Use `FT_Error' as return type.
    Return error code for unsorted cmap.
    (tt_cmap4_char_index, tt_cmap4_char_next): Use old code for unsorted
    cmaps.
    (tt_face_build_cmaps): Set `unsorted' variable in cmap.
    
    
    Minor formatting.
    

  • Properties

  • Git HTTP https://git.kmx.io/kc3-lang/freetype.git
    Git SSH git@git.kmx.io:kc3-lang/freetype.git
    Public access ? public
    Description
    Users
    thodg_m kc3_lang_org thodg_w www_kmx_io thodg thodg_l
    Tags

  • README

  •   Special notes to Unix users
      ===========================
    
      Please  read  the file  "docs/UPGRADE.UNX".   It contains  important
      information regarding the installation  of FreeType on Unix systems,
      especially GNU based operating systems like GNU/Linux.
    
      FreeType 2's  library is called `libfreetype',  FreeType 1's library
      is called `libttf'.  They are *not* compatible!
    
    
      FreeType 2.1.10
      ===============
    
      Please read the docs/CHANGES file, it contains IMPORTANT INFORMATION.
    
      Read the files "docs/INSTALL" for installation instructions.
    
      Note  that  the FreeType  2  documentation  is  now available  as  a
      separate package from our sites.  See:
    
        ftp://ftp.freetype.org/freetype/freetype2/ftdocs-2.1.10.tar.bz2
        ftp://ftp.freetype.org/freetype/freetype2/ftdocs-2.1.10.tar.gz
        ftp://ftp.freetype.org/freetype/freetype2/ftdoc2110.zip
    
    
      Bugs
      ====
    
      Please report bugs by  e-mail to `devel@freetype.org'.  Don't forget
      to send  a detailed explanation of  the problem --  there is nothing
      worse  than receiving  a terse  message that  only says  "it doesn't
      work".
    
    
      Enjoy!
    
    
        The FreeType Team