-
Show log
Commit
-
Hash : 4e56c0d8
Author :
Date : 2004-06-23T19:29:58
Simple ChangeLog update: 2004-06-23 David Turner <david@freetype.org> * include/freetype/internal/ftmemory.h, src/base/ftutil.c, src/base/ftmemdbg.c: introducing the new FT_QAlloc and FT_QRealloc functions that do perform allocation without zero-ing out the corresponding blocks. Corresponding macros like FT_QALLOC, FT_QNEW, etc.. have been defined too * include/freetype/config/ftmodule.h: changed the order of modules in order to _dramatically_ improve the performance of face open/close operations. For example, putting the TrueType driver first in the list results in a 5X speedup when opening Vera.ttf !! The problem is really that the PCF and/or BDF drivers are broken and do a lot more than necessary simply to detect that they cannot handle the font file. * src/sfnt/ttload.c: small optimization in the kerning table verifier, speeds up TrueType face opening by about 7%. Also changed code to use the new FT_QNEW_ARRAY call when appropriate to slightly improve performance.
-
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
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.9 ============== 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.9.tar.bz2 ftp://ftp.freetype.org/freetype/freetype2/ftdocs-2.1.9.tar.gz ftp://ftp.freetype.org/freetype/freetype2/ftdoc219.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