| ftadvanc.c |
this must be the same scaling as to get linear{Hori,Vert}Advance |
4906 |
| ftbase.c |
END |
980 |
| ftbase.h |
MacOS resource fork cannot exceed 16MB at least for Carbon code; |
2651 |
| ftbbox.c |
This component has a _single_ role: to compute exact outline bounding
boxes.
|
14346 |
| ftbdf.c |
documentation is in ftbdf.h |
2177 |
| ftbitmap.c |
The macro FT_COMPONENT is used in trace mode. It is an implicit
parameter of the FT_TRACE() and FT_ERROR() macros, used to print/log
messages during execution.
|
28296 |
| ftcalc.c |
Support for 1-complement arithmetic has been totally dropped in this
release. You can still write your own code if you need it.
|
27531 |
| ftcid.c |
documentation is in ftcid.h |
2540 |
| ftcolor.c |
documentation is in ftcolor.h |
3416 |
| ftdbgmem.c |
`Keep alive' means that freed blocks aren't released
to the heap. This is useful to detect double-frees
or weird heap corruption, but it uses large amounts of
memory, however.
|
23926 |
| ftdebug.c |
This component contains various macros and functions used to ease the
debugging of the FreeType engine. Its main purpose is in assertion
checking, tracing, and error detection.
There are now three debugging modes:
- trace mode
Error and trace messages are sent to the log file (which can be the
standard error output).
- error mode
Only error messages are generated.
- release mode:
No error message is sent or generated. The code is free from any
debugging parts.
|
14105 |
| fterrors.c |
documentation is in fterrors.h |
1267 |
| ftfntfmt.c |
documentation is in ftfntfmt.h |
1203 |
| ftfstype.c |
documentation is in freetype.h |
1551 |
| ftgasp.c |
ensure that we don't have spurious bits |
1355 |
| ftgloadr.c |
/
/************************************************************************ |
11421 |
| ftglyph.c |
This file contains the definition of several convenience functions
that can be used by client applications to easily retrieve glyph
bitmaps and outlines from a given face.
These functions should be optional if you are writing a font server
or text layout engine on top of FreeType. However, they are pretty
handy for many other simple uses of the library.
|
24220 |
| ftgxval.c |
gxvalid is derived from both gxlayout module and otvalid module.
Development of gxlayout is supported by the Information-technology
Promotion Agency(IPA), Japan.
|
3125 |
| fthash.c |
fthash.c
Hashing functions (body).
|
6657 |
| ftinit.c |
The purpose of this file is to implement the following two
functions:
FT_Add_Default_Modules():
This function is used to add the set of default modules to a
fresh new library object. The set is taken from the header file
`freetype/config/ftmodule.h'. See the document `FreeType 2.0
Build System' for more information.
FT_Init_FreeType():
This function creates a system object for the current platform,
builds a library out of it, then calls FT_Default_Drivers().
Note that even if FT_Init_FreeType() uses the implementation of the
system object defined at build time, client applications are still
able to provide their own `ftsystem.c'.
|
6339 |
| ftlcdfil.c |
define USE_LEGACY to implement the legacy filter |
11455 |
| ftmac.c |
Notes
Mac suitcase files can (and often do!) contain multiple fonts. To
support this I use the face_index argument of FT_(Open|New)_Face()
functions, and pretend the suitcase file is a collection.
Warning: fbit and NFNT bitmap resources are not supported yet. In old
sfnt fonts, bitmap glyph data for each size is stored in each `NFNT'
resources instead of the `bdat' table in the sfnt resource. Therefore,
face->num_fixed_sizes is set to 0, because bitmap data in `NFNT'
resource is unavailable at present.
The Mac FOND support works roughly like this:
- Check whether the offered stream points to a Mac suitcase file. This
is done by checking the file type: it has to be 'FFIL' or 'tfil'. The
stream that gets passed to our init_face() routine is a stdio stream,
which isn't usable for us, since the FOND resources live in the
resource fork. So we just grab the stream->pathname field.
- Read the FOND resource into memory, then check whether there is a
TrueType font and/or(!) a Type 1 font available.
- If there is a Type 1 font available (as a separate `LWFN' file), read
its data into memory, massage it slightly so it becomes PFB data, wrap
it into a memory stream, load the Type 1 driver and delegate the rest
of the work to it by calling FT_Open_Face(). (XXX TODO: after this
has been done, the kerning data from the FOND resource should be
appended to the face: On the Mac there are usually no AFM files
available. However, this is tricky since we need to map Mac char
codes to ps glyph names to glyph ID's...)
- If there is a TrueType font (an `sfnt' resource), read it into memory,
wrap it into a memory stream, load the TrueType driver and delegate
the rest of the work to it, by calling FT_Open_Face().
- Some suitcase fonts (notably Onyx) might point the `LWFN' file to
itself, even though it doesn't contains `POST' resources. To handle
this special case without opening the file an extra time, we just
ignore errors from the `LWFN' and fallback to the `sfnt' if both are
available.
|
31521 |
| ftmm.c |
The macro FT_COMPONENT is used in trace mode. It is an implicit
parameter of the FT_TRACE() and FT_ERROR() macros, used to print/log
messages during execution.
|
18084 |
| ftobjs.c |
for SFNT_Load_Table_Func |
161908 |
| ftotval.c |
documentation is in ftotval.h |
2216 |
| ftoutln.c |
The macro FT_COMPONENT is used in trace mode. It is an implicit
parameter of the FT_TRACE() and FT_ERROR() macros, used to print/log
messages during execution.
|
28599 |
| ftpatent.c |
documentation is in freetype.h |
1245 |
| ftpfr.c |
check the format |
3730 |
| ftpsprop.c |
The macro FT_COMPONENT is used in trace mode. It is an implicit
parameter of the FT_TRACE() and FT_ERROR() macros, used to print/log
messages during execution.
|
7500 |
| ftrfork.c |
Development of the code in this file is support of
Information-technology Promotion Agency, Japan.
|
29493 |
| ftsnames.c |
documentation is in ftsnames.h |
4580 |
| ftstream.c |
The macro FT_COMPONENT is used in trace mode. It is an implicit
parameter of the FT_TRACE() and FT_ERROR() macros, used to print/log
messages during execution.
|
19461 |
| ftstroke.c |
declare an extern to access `ft_outline_glyph_class' globally |
64724 |
| ftsynth.c |
The macro FT_COMPONENT is used in trace mode. It is an implicit
parameter of the FT_TRACE() and FT_ERROR() macros, used to print/log
messages during execution.
|
5374 |
| ftsystem.c |
This file contains the default interface used by FreeType to access
low-level, i.e. memory management, i/o access as well as thread
synchronisation. It can be replaced by user-specific routines if
necessary.
|
8149 |
| fttrigon.c |
This is a fixed-point CORDIC implementation of trigonometric
functions as well as transformations between Cartesian and polar
coordinates. The angles are represented as 16.16 fixed-point values
in degrees, i.e., the angular resolution is 2^-16 degrees. Note that
only vectors longer than 2^16*180/pi (or at least 22 bits) on a
discrete Cartesian grid can have the same or better angular
resolution. Therefore, to maintain this precision, some functions
require an interim upscaling of the vectors, whereas others operate
with 24-bit long vectors directly.
|
10565 |
| fttype1.c |
documentation is in t1tables.h |
3047 |
| ftutil.c |
The macro FT_COMPONENT is used in trace mode. It is an implicit
parameter of the FT_TRACE() and FT_ERROR() macros, used to print/log
messages during execution.
|
10171 |
| ftver.rc |
|
2543 |
| ftwinfnt.c |
documentation is in ftwinfnt.h |
1306 |
| md5.c |
The basic MD5 functions.
F and G are optimized compared to their RFC 1321 definitions for
architectures that lack an AND-NOT instruction, just like in Colin Plumb's
implementation.
|
8743 |
| md5.h |
This is an OpenSSL-compatible implementation of the RSA Data Security, Inc.
MD5 Message-Digest Algorithm (RFC 1321).
Homepage:
http://openwall.info/wiki/people/solar/software/public-domain-source-code/md5
Author:
Alexander Peslyak, better known as Solar Designer <solar at openwall.com>
This software was written by Alexander Peslyak in 2001. No copyright is
claimed, and the software is hereby placed in the public domain.
In case this attempt to disclaim copyright and place the software in the
public domain is deemed null and void, then the software is
Copyright (c) 2001 Alexander Peslyak and it is hereby released to the
general public under the following terms:
Redistribution and use in source and binary forms, with or without
modification, are permitted.
There's ABSOLUTELY NO WARRANTY, express or implied.
See md5.c for more information.
|
1410 |
| rules.mk |
|
3222 |