FreeType 1.31.1

2023-08-27 18:03:45 +02:00
commit 5edbb7a80a
454 changed files with 173977 additions and 0 deletions
--- a/docs/readme.txt
+++ b/docs/readme.txt
@@ -0,0 +1,106 @@
+Welcome to the documentation directory of FreeType.
+
+Here are short overview where you can find which information.
+
+
+  apiref.txt    FreeType high-level  API reference.  All  the types,
+                functions, and error codes of FreeType.
+
+  ..................................................................
+
+  apirefx.txt   The API reference  of FreeType extensions which come
+                with the library itself.
+
+  ..................................................................
+
+  bitmaps.txt   How to render a glyph outline into a bitmap.
+
+  ..................................................................
+
+  changes.txt   Guess what :-)
+
+  ..................................................................
+
+  convntns.txt  The  FreeType developer's conventions  guide.  Lists
+                the  design  and  coding  conventions  used  in  the
+                engine's  source  code.  This file is incomplete but
+                contains information  that  should  be  read  by any
+                person willing to hack the FreeType code.
+
+  ..................................................................
+
+  credits       A list of persons who have contributed to FreeType.
+
+  ..................................................................
+
+  glyphs.htm    An introduction  to glyphs in general,  its usage in
+  glyphs.txt    TrueType, and  how FreeType handles  them.  The file
+                `glyphs.txt'  is  a  simple  text  dump  (done  with
+                Netscape) of glyphs.htm.
+
+  ..................................................................
+
+  i18n.txt      A short introduction to the GNU gettext package.
+
+  ..................................................................
+
+  porting.txt   The  FreeType  porting   guide.   All  you  need  to
+                configure  and adapt  very  easily FreeType's source
+                code to tailor it to your own platform.
+
+                Learn how to provide your own memory, i/o, and mutex
+                components,  optimally fitted  to your  system.  See
+                how you can build a singly-threaded, thread-safe, or
+                re-entrant  version  of  the  engine from  the  same
+                source code!
+
+  ..................................................................
+
+  raster.txt    The  scan-line converter's internals explained.  The
+                document is  still incomplete but  presents many key
+                concepts.
+
+  ..................................................................
+
+  threads.txt   How to use threads with FreeType.
+
+  ..................................................................
+
+  user.txt      FreeType's  user  guide.    A  guide  to  FreeType's
+                concepts, a  step by step example, and  a note about
+                future works and projects.
+
+  ..................................................................
+
+  FAQ           The new up-to-date FreeType FAQ.  Look here first if 
+                you have problems with the library.
+
+  ..................................................................
+
+  TODO          Things which probably will come, which would be nice
+                to have, problems still here, etc.
+
+
+
+These  documents will probably  come later.
+
+  develop.txt   The FreeType developer's guide. All you need to know
+                in order to be able  to understand and even hack the
+                engine's core source code.
+
+  extend.txt    The FreeType extension writer's how-to. All you need
+                to be able to provide new extensions to the engine.
+
+  undoc.txt     Undocumented TrueType!
+
+                Yes,    ladies   and    gentlemen,    the   TrueType
+                specification  is  fuzzy  and misleading  enough  to
+                disband some serious commercial developers, but that
+                wasn't enough for us.  Even though it took some time
+                (aaargh...), we finally discovered through hard work
+                the real  meanings of  the specs, fixed  some errors
+                and even found  surprising undocumented behaviour or
+                features!
+
+
+--- end of readme.txt ---