diff options
Diffstat (limited to 'src/3rdparty/freetype/docs')
-rw-r--r-- | src/3rdparty/freetype/docs/CHANGES | 305 | ||||
-rw-r--r-- | src/3rdparty/freetype/docs/CUSTOMIZE | 2 | ||||
-rw-r--r-- | src/3rdparty/freetype/docs/DEBUG | 96 | ||||
-rw-r--r-- | src/3rdparty/freetype/docs/LICENSE.TXT | 39 | ||||
-rw-r--r-- | src/3rdparty/freetype/docs/TODO | 2 |
5 files changed, 365 insertions, 79 deletions
diff --git a/src/3rdparty/freetype/docs/CHANGES b/src/3rdparty/freetype/docs/CHANGES index 3bd5291ae1..3ad7ec4333 100644 --- a/src/3rdparty/freetype/docs/CHANGES +++ b/src/3rdparty/freetype/docs/CHANGES @@ -1,4 +1,235 @@ -CHANGES BETWEEN 2.10.3 and 2.10.4 +CHANGES BETWEEN 2.12.0 and 2.12.1 + + I. IMPORTANT BUG FIXES + + - Loading CFF fonts sometimes made FreeType crash (bug introduced in + version 2.12.0) + + - Loading a fully hinted TrueType glyph a second time (without + caching) sometimes yielded different rendering results if TrueType + hinting was active (bug introduced in version 2.12.0). + + - The generation of the pkg-config file `freetype2.pc` was broken if + the build was done with cmake (bug introduced in version 2.12.0). + + + II. MISCELLANEOUS + + - New option `--with-librsvg` for the `configure` script for better + FreeType demo support. + + - The meson build no longer enforces both static and dynamic + versions of the library by default. + + - The internal zlib library was updated to version 1.2.12. Note, + however, that FreeType is *not* affected by CVE-2018-25032 since + it only does decompression. + + +====================================================================== + +CHANGES BETWEEN 2.11.1 and 2.12.0 + + I. IMPORTANT CHANGES + + - FreeType now handles OT-SVG fonts, to be controlled with + `FT_CONFIG_OPTION_SVG` configuration macro. By default, it can + only load the 'SVG ' table of an OpenType font. However, by using + the `svg-hooks` property of the new 'ot-svg' module it is possible + to register an external SVG rendering engine. The FreeType demo + programs have been set up to use 'librsvg' as the rendering + library. + + This work was Moazin Khatti's GSoC 2019 project. + + + II. MISCELLANEOUS + + - The handling of fonts with an 'sbix' table has been improved. + + - Corrected bitmap offsets. + + - A new tag `FT_PARAM_TAG_IGNORE_SBIX` for `FT_Open_Face` makes + FreeType ignore an 'sbix' table in a font, allowing applications + to access the font's outline glyphs. + + - `FT_FACE_FLAG_SBIX` and `FT_FACE_FLAG_SBIX_OVERLAY` together + with their corresponding preprocessor macros `FT_HAS_SBIX` and + `FT_HAS_SBIX_OVERLAY` enable applications to treat 'sbix' tables + as described in the OpenType specification. + + - The internal 'zlib' code has been updated to be in sync with the + current 'zlib' version (1.2.11). + + - The previously internal load flag `FT_LOAD_SBITS_ONLY` is now + public. + + - Some minor improvements of the building systems, in particular + handling of the 'zlib' library (internal vs. external). + + - Support for non-desktop Universal Windows Platform. + + - Various other minor bug and documentation fixes. + + - The `ftdump` demo program shows more information for Type1 fonts + if option `-n` is given. + + - `ftgrid` can now display embedded bitmap strikes. + + +====================================================================== + +CHANGES BETWEEN 2.11.0 and 2.11.1 + + I. IMPORTANT CHANGES + + - Some fields in the `CID_FaceDictRec`, `CID_FaceInfoRec`, and + `FT_Data` structures have been changed from signed to unsigned + type, which better reflects the actual usage. It is also an + additional means to protect against malformed input. + + + II. MISCELLANEOUS + + - Cmake support has been further improved. To do that various + backward-incompatible changes were necessary; please see file + `CMakeLists.txt` for more details. + + - Since version 2.11.0, a C99 compiler is necessary to compile + FreeType. + + - The experimental 'COLR' v1 API has been updated to the latest + OpenType standard 1.9. + + - The `apinames` tool got a new option `-wV` to output an OpenVMS + Linker Option File. + + - VMS support was updated. + + - MS Visual Studio support was added to build the demo programs. + + +====================================================================== + +CHANGES BETWEEN 2.10.4 and 2.11.0 + + I. IMPORTANT CHANGES + + - A new rendering module has been added to create 8-bit Signed + Distance Field (SDF) bitmaps for both outline and bitmap glyphs. + The new rendering mode is called `FT_RENDER_MODE_SDF`, the pixel + mode is `FT_PIXEL_MODE_GRAY8`, and the corresponding raster flag + is `FT_RASTER_FLAG_SDF`. + + This work was Anuj Verma's GSoC 2020 project. + + - A new, experimental API is now available for surfacing properties + of 'COLR' v1 color fonts (as the name says, this is an extension + to the 'COLR' table for outline color fonts using the SFNT + container format). 'COLR' v1 fonts are a recently proposed + addition to OFF and OpenType; specification work currently happens + in + + https://github.com/googlefonts/colr-gradients-spec/ + + 'COLR' v1 is expected to be merged to OpenType; the ISO + standardisation process for adding 'COLR' v1 as an amendment to + OFF is underway. + + Functions similar to the already existing 'COLR' API have been + added to access the corresponding data. + + FT_Get_Color_Glyph_Paint + Retrieve the root paint for a given glyph ID. + + FT_Get_Paint_Layers + Access the layers of a `PaintColrLayers` table. + + FT_Get_Colorline_Stops + Retrieve the 'color stops' on a color line. As an input, a + color stop iterator gets used, which in turn is retrieved from + a paint. + + FT_Get_Paint + Dereference an `FT_OpaquePaint` object and retrieve the + corresponding `FT_COLR_Paint` object, which contains details + on how to draw the respective 'COLR' v1 `Paint` table. + + + II. MISCELLANEOUS + + - FreeType has moved its infrastructure to + + https://gitlab.freedesktop.org/freetype + + A side effect is that the git repositories are now called + `freetype.git` and `freetype-demos.git`, which by default expand + to the directories `freetype` and `freetype-demos`, respectively. + The documentation has been updated accordingly. + + FreeType's Savannah repositories will stay; they are now mirrors + of the 'freedesktop.org' repositories. + + - A new function `FT_Get_Transform` returns the values set by + `FT_Set_Transform`. + + - A new configuration macro `FT_DEBUG_LOGGING` is available. It + provides extended debugging capabilities for FreeType, for example + showing a time stamp or displaying the component a tracing message + comes from. See file `docs/DEBUG` for more information. + + This work was Priyesh Kumar's GSoC 2020 project. + + - The legacy Type 1 and CFF engines are further demoted due to lack + of CFF2 charstring support. You now need to use `FT_Property_Set` + to enable them besides the `T1_CONFIG_OPTION_OLD_ENGINE` and + `CFF_CONFIG_OPTION_OLD_ENGINE` options, respectively. + + - The experimental 'warp' mode (AF_CONFIG_OPTION_USE_WARPER) for the + auto-hinter has been removed. + + - The smooth rasterizer performance has been improved by >10%. Note + that due to necessary code changes there might be very subtle + differences in rendering. They are not visible by the eye, + however. + + - PCF bitmap fonts compressed with LZW (these are usually files with + the extension `.pcf.Z`) are now handled correctly. + + - Improved Meson build files, including support to build the + FreeType demo programs. + + - A new demo program `ftsdf` is available to display Signed Distance + Fields of glyphs. + + - The `ftlint` demo program has been extended to do more testing of + its input. In particular, it can display horizontal and vertical + acutances for quality assessment, together with computing MD5 + checksums of rendered glyphs. + + [The acutance measures how sharply the pixel coverage changes at + glyph edges. For monochrome bitmaps, it is always 2.0 in either + X or Y direction. For anti-aliased bitmaps, it depends on the + hinting and the shape of a glyph and might approach or even reach + value 2.0 for glyphs like 'I', 'L', '+', '-', or '=', while it + might be lower for glyphs like 'O', 'S', or 'W'.] + + - The `ttdebug` demo program didn't show changed point coordinates + (bug introduced in version 2.10.3). + + - It is now possible to adjust the axis increment for variable fonts + in the `ftmulti` demo program. + + - It is now possible to change the hinting engine in the `ftstring` + demo program. + + - The graphical demo programs work better now in native color depth + on win32 and x11. + + +====================================================================== + +CHANGES BETWEEN 2.10.3 and 2.10.4 (2020-Oct-20) I. IMPORTANT BUG FIXES @@ -13,7 +244,7 @@ CHANGES BETWEEN 2.10.3 and 2.10.4 ====================================================================== -CHANGES BETWEEN 2.10.2 and 2.10.3 +CHANGES BETWEEN 2.10.2 and 2.10.3 (2020-Oct-10) I. IMPORTANT CHANGES @@ -63,7 +294,7 @@ CHANGES BETWEEN 2.10.2 and 2.10.3 ====================================================================== -CHANGES BETWEEN 2.10.1 and 2.10.2 +CHANGES BETWEEN 2.10.1 and 2.10.2 (2020-May-09) I. IMPORTANT CHANGES @@ -100,7 +331,7 @@ CHANGES BETWEEN 2.10.1 and 2.10.2 ====================================================================== -CHANGES BETWEEN 2.10.0 and 2.10.1 +CHANGES BETWEEN 2.10.0 and 2.10.1 (2019-Jul-01) I. IMPORTANT BUG FIXES @@ -154,7 +385,7 @@ CHANGES BETWEEN 2.10.0 and 2.10.1 ====================================================================== -CHANGES BETWEEN 2.9.1 and 2.10.0 +CHANGES BETWEEN 2.9.1 and 2.10.0 (2019-Mar-15) I. IMPORTANT CHANGES @@ -280,7 +511,7 @@ CHANGES BETWEEN 2.9.1 and 2.10.0 ====================================================================== -CHANGES BETWEEN 2.9 and 2.9.1 +CHANGES BETWEEN 2.9 and 2.9.1 (2019-May-01) I. IMPORTANT BUG FIXES @@ -328,7 +559,7 @@ CHANGES BETWEEN 2.9 and 2.9.1 ====================================================================== -CHANGES BETWEEN 2.8.1 and 2.9 +CHANGES BETWEEN 2.8.1 and 2.9 (2018-Jan-08) I. IMPORTANT BUG FIXES @@ -418,7 +649,7 @@ CHANGES BETWEEN 2.8.1 and 2.9 ====================================================================== -CHANGES BETWEEN 2.8 and 2.8.1 +CHANGES BETWEEN 2.8 and 2.8.1 (2017-Sep-16) I. IMPORTANT BUG FIXES @@ -501,7 +732,7 @@ CHANGES BETWEEN 2.8 and 2.8.1 ====================================================================== -CHANGES BETWEEN 2.7.1 and 2.8 +CHANGES BETWEEN 2.7.1 and 2.8 (2017-May-13) I. IMPORTANT CHANGES @@ -622,7 +853,7 @@ CHANGES BETWEEN 2.7.1 and 2.8 ====================================================================== -CHANGES BETWEEN 2.7 and 2.7.1 +CHANGES BETWEEN 2.7 and 2.7.1 (2016-Dec-30) I. IMPORTANT CHANGES @@ -699,7 +930,7 @@ CHANGES BETWEEN 2.7 and 2.7.1 ====================================================================== -CHANGES BETWEEN 2.6.5 and 2.7 +CHANGES BETWEEN 2.6.5 and 2.7 (2016-Sep-08) I. IMPORTANT CHANGES @@ -763,7 +994,7 @@ CHANGES BETWEEN 2.6.5 and 2.7 ====================================================================== -CHANGES BETWEEN 2.6.4 and 2.6.5 +CHANGES BETWEEN 2.6.4 and 2.6.5 (2016-Jul-12) I. IMPORTANT BUG FIXES @@ -783,7 +1014,7 @@ CHANGES BETWEEN 2.6.4 and 2.6.5 ====================================================================== -CHANGES BETWEEN 2.6.3 and 2.6.4 +CHANGES BETWEEN 2.6.3 and 2.6.4 (2016-Jul-05) I. IMPORTANT CHANGES @@ -849,7 +1080,7 @@ CHANGES BETWEEN 2.6.3 and 2.6.4 ====================================================================== -CHANGES BETWEEN 2.6.2 and 2.6.3 +CHANGES BETWEEN 2.6.2 and 2.6.3 (2016-Feb-08) I. IMPORTANT CHANGES @@ -898,7 +1129,7 @@ CHANGES BETWEEN 2.6.2 and 2.6.3 ====================================================================== -CHANGES BETWEEN 2.6.1 and 2.6.2 +CHANGES BETWEEN 2.6.1 and 2.6.2 (2015-Nov-28) I. IMPORTANT CHANGES @@ -958,7 +1189,7 @@ CHANGES BETWEEN 2.6.1 and 2.6.2 ====================================================================== -CHANGES BETWEEN 2.6 and 2.6.1 +CHANGES BETWEEN 2.6 and 2.6.1 (2015-Oct-04) I. IMPORTANT BUG FIXES @@ -1039,7 +1270,7 @@ CHANGES BETWEEN 2.6 and 2.6.1 ====================================================================== -CHANGES BETWEEN 2.5.5 and 2.6 +CHANGES BETWEEN 2.5.5 and 2.6 (2015-Jun-07) I. IMPORTANT CHANGES @@ -1145,7 +1376,7 @@ CHANGES BETWEEN 2.5.5 and 2.6 ====================================================================== -CHANGES BETWEEN 2.5.4 and 2.5.5 +CHANGES BETWEEN 2.5.4 and 2.5.5 (2014-Dec-30) I. IMPORTANT BUG FIXES @@ -1155,7 +1386,7 @@ CHANGES BETWEEN 2.5.4 and 2.5.5 ====================================================================== -CHANGES BETWEEN 2.5.3 and 2.5.4 +CHANGES BETWEEN 2.5.3 and 2.5.4 (2014-Dec-06) I. IMPORTANT BUG FIXES @@ -1226,7 +1457,7 @@ CHANGES BETWEEN 2.5.3 and 2.5.4 ====================================================================== -CHANGES BETWEEN 2.5.2 and 2.5.3 +CHANGES BETWEEN 2.5.2 and 2.5.3 (2014-Mar-06) I. IMPORTANT BUG FIXES @@ -1294,7 +1525,7 @@ CHANGES BETWEEN 2.5.2 and 2.5.3 ====================================================================== -CHANGES BETWEEN 2.5.1 and 2.5.2 +CHANGES BETWEEN 2.5.1 and 2.5.2 (2013-Dec-08) I. IMPORTANT BUG FIXES @@ -1318,7 +1549,7 @@ CHANGES BETWEEN 2.5.1 and 2.5.2 ====================================================================== -CHANGES BETWEEN 2.5 and 2.5.1 +CHANGES BETWEEN 2.5 and 2.5.1 (2013-Nov-25) I. IMPORTANT BUG FIXES @@ -1422,7 +1653,7 @@ CHANGES BETWEEN 2.5 and 2.5.1 ====================================================================== -CHANGES BETWEEN 2.4.12 and 2.5 +CHANGES BETWEEN 2.4.12 and 2.5 (2013-Jun-19) I. IMPORTANT BUG FIXES @@ -1502,7 +1733,7 @@ CHANGES BETWEEN 2.4.12 and 2.5 ====================================================================== -CHANGES BETWEEN 2.4.11 and 2.4.12 +CHANGES BETWEEN 2.4.11 and 2.4.12 (2013-May-08) - We have another CFF parsing and hinting engine! Written by Dave Arnold <darnold@adobe.com>, this work has been contributed by @@ -1590,7 +1821,7 @@ index ebcf189..3f2ce6b 100644 ====================================================================== -CHANGES BETWEEN 2.4.10 and 2.4.11 +CHANGES BETWEEN 2.4.10 and 2.4.11 (2012-Dec-20) I. IMPORTANT BUG FIXES @@ -1650,7 +1881,7 @@ CHANGES BETWEEN 2.4.10 and 2.4.11 ====================================================================== -CHANGES BETWEEN 2.4.9 and 2.4.10 +CHANGES BETWEEN 2.4.9 and 2.4.10 (2012-Jun-15) I. IMPORTANT BUG FIXES @@ -1675,7 +1906,7 @@ CHANGES BETWEEN 2.4.9 and 2.4.10 ====================================================================== -CHANGES BETWEEN 2.4.8 and 2.4.9 +CHANGES BETWEEN 2.4.8 and 2.4.9 (2012-Mar-08) I. IMPORTANT BUG FIXES @@ -1703,7 +1934,7 @@ CHANGES BETWEEN 2.4.8 and 2.4.9 ====================================================================== -CHANGES BETWEEN 2.4.7 and 2.4.8 +CHANGES BETWEEN 2.4.7 and 2.4.8 (2011-Nov-14) I. IMPORTANT BUG FIXES @@ -1719,7 +1950,7 @@ CHANGES BETWEEN 2.4.7 and 2.4.8 ====================================================================== -CHANGES BETWEEN 2.4.6 and 2.4.7 +CHANGES BETWEEN 2.4.6 and 2.4.7 (2011-Oct-18) I. IMPORTANT BUG FIXES @@ -1736,7 +1967,7 @@ CHANGES BETWEEN 2.4.6 and 2.4.7 ====================================================================== -CHANGES BETWEEN 2.4.5 and 2.4.6 +CHANGES BETWEEN 2.4.5 and 2.4.6 (2011-Jul-29) I. IMPORTANT BUG FIXES @@ -1775,7 +2006,7 @@ CHANGES BETWEEN 2.4.5 and 2.4.6 ====================================================================== -CHANGES BETWEEN 2.4.4 and 2.4.5 +CHANGES BETWEEN 2.4.4 and 2.4.5 (2011-Jun-25) I. IMPORTANT BUG FIXES @@ -1822,7 +2053,7 @@ CHANGES BETWEEN 2.4.4 and 2.4.5 ====================================================================== -CHANGES BETWEEN 2.4.3 and 2.4.4 +CHANGES BETWEEN 2.4.3 and 2.4.4 (2010-Nov-28) I. IMPORTANT BUG FIXES @@ -1847,7 +2078,7 @@ CHANGES BETWEEN 2.4.3 and 2.4.4 ====================================================================== -CHANGES BETWEEN 2.4.2 and 2.4.3 +CHANGES BETWEEN 2.4.2 and 2.4.3 (2010-Oct-03) I. IMPORTANT BUG FIXES @@ -1866,7 +2097,7 @@ CHANGES BETWEEN 2.4.2 and 2.4.3 ====================================================================== -CHANGES BETWEEN 2.4.1 and 2.4.2 +CHANGES BETWEEN 2.4.1 and 2.4.2 (2010-Aug-06) I. IMPORTANT BUG FIXES @@ -1890,7 +2121,7 @@ CHANGES BETWEEN 2.4.1 and 2.4.2 ====================================================================== -CHANGES BETWEEN 2.4.0 and 2.4.1 +CHANGES BETWEEN 2.4.0 and 2.4.1 (2010-Jul-18) I. IMPORTANT CHANGES @@ -1900,7 +2131,7 @@ CHANGES BETWEEN 2.4.0 and 2.4.1 ====================================================================== -CHANGES BETWEEN 2.3.12 and 2.4.0 +CHANGES BETWEEN 2.3.12 and 2.4.0 (2010-Jul-12) I. IMPORTANT CHANGES @@ -5299,7 +5530,7 @@ Extensions support: ------------------------------------------------------------------------ -Copyright (C) 2000-2020 by +Copyright (C) 2000-2022 by David Turner, Robert Wilhelm, and Werner Lemberg. This file is part of the FreeType project, and may only be used, diff --git a/src/3rdparty/freetype/docs/CUSTOMIZE b/src/3rdparty/freetype/docs/CUSTOMIZE index 0f92e70046..1a750825b2 100644 --- a/src/3rdparty/freetype/docs/CUSTOMIZE +++ b/src/3rdparty/freetype/docs/CUSTOMIZE @@ -139,7 +139,7 @@ IV. Overriding default configuration and module headers ---------------------------------------------------------------------- -Copyright (C) 2003-2020 by +Copyright (C) 2003-2022 by David Turner, Robert Wilhelm, and Werner Lemberg. This file is part of the FreeType project, and may only be used, diff --git a/src/3rdparty/freetype/docs/DEBUG b/src/3rdparty/freetype/docs/DEBUG index a96b5e27b8..fd2de134d5 100644 --- a/src/3rdparty/freetype/docs/DEBUG +++ b/src/3rdparty/freetype/docs/DEBUG @@ -44,6 +44,21 @@ located in the file `ftoption.h'. The macros are: When `FT2_DEBUG_MEMORY' isn't defined at runtime, the debugging memory manager is ignored, and performance is unaffected. + FT_DEBUG_LOGGING + + #define this macro for enhanced logging support; it automatically + sets `FT_DEBUG_LEVEL_TRACE' and `FT_DEBUG_LEVEL_ERROR'. + + If defined, `FT_TRACE' and `FT_ERROR' can send tracing and + debugging messages to a file. The location of the log file has to + be set with the `FT_LOGGING_FILE' environment variable (more on + this later). + + The main enhancements are the possibility of logging the time and + the name of the `FT_COMPONENT' macro together with the affected + `FT_TRACE' or `FT_ERROR' calls. See below how to activate this in + the `FT2_DEBUG' environment variable. + II. Debugging macros -------------------- @@ -150,6 +165,43 @@ behaviour of FreeType at runtime. the memory and io components, which are set to the trace levels 5 and 4, respectively. + If `FT_DEBUG_LOGGING' is defined, two more options are available. + + * -v: Print also the name of FreeType's component from which the + current log is produced, together with the tracing level. + + * -t: Print also the time. + + Here are some examples how the output might look like. + + FT2_DEBUG="any:7 memory:5 -vt" + + => [20:32:02:44969 ttload:2] table directory loaded + + FT2_DEBUG="any:7 memory:5 -t" + + => [20:32:02:44969] table directory loaded + + FT2_DEBUG="any:7 memory:5 -v" + + => [ttload:2] table directory loaded + + + FT_LOGGING_FILE + + This variable is only used if FreeType is built with the + `FT_DEBUG_LOGGING' macro defined. It contains the path to the + file where the user wants to put his log file. If it is not set, + FreeType uses stderr. + + Examples: + + On UNIX-like systems with bash: + export FT_LOGGING_FILE="/tmp/freetype2.log" + + On Windows: + set FT_LOGGING_FILE=C:\Users\AppData\Local\Temp\freetype2.log + FT2_DEBUG_MEMORY @@ -201,9 +253,51 @@ behaviour of FreeType at runtime. If it is undefined, or if its value is not strictly positive, freed blocks are released at runtime. + +IV. Additional Capabilities with `FT_DEBUG_LOGGING' +--------------------------------------------------- + +If `FT_DEBUG_LOGGING' is defined, four APIs are available to provide +additional debugging support. Use + + #include <freetype/ftlogging.h> + +to access them. + + FT_Trace_Set_Level( const char* level ) + + By default, FreeType uses the tracing levels set in the + `FT2_DEBUG' environment variable. Use this function to override + the value with `level'. Use value `NULL' to disable tracing. + + FT_Trace_Set_Default_Level(): + + Reset the tracing levels to the default value, i.e., the value of + the `FT2_DEBUG' environment variable or no tracing if not set. + + FT_Set_Log_Handler( ft_custom_log_handler handler ): + + Use `handler' as a custom handler for formatting tracing and error + messages. The `ft_custom_log_handler' typedef has the following + prototype. + + void + (*ft_custom_log_handler)( const char* ft_component, + const char* fmt, + va_list args ); + + `ft_component' is the current component like `ttload', `fmt' is the + first argument of `FT_TRACE' or `FT_ERROR', and `args' holds the + remaining arguments. + + FT_Set_Default_Log_Handler(): + + Reset the log handler to the default version. + + ------------------------------------------------------------------------ -Copyright (C) 2002-2020 by +Copyright (C) 2002-2022 by David Turner, Robert Wilhelm, and Werner Lemberg. This file is part of the FreeType project, and may only be used, diff --git a/src/3rdparty/freetype/docs/LICENSE.TXT b/src/3rdparty/freetype/docs/LICENSE.TXT deleted file mode 100644 index af5a1c50f6..0000000000 --- a/src/3rdparty/freetype/docs/LICENSE.TXT +++ /dev/null @@ -1,39 +0,0 @@ - -The FreeType 2 font engine is copyrighted work and cannot be used -legally without a software license. In order to make this project -usable to a vast majority of developers, we distribute it under two -mutually exclusive open-source licenses. - -This means that *you* must choose *one* of the two licenses described -below, then obey all its terms and conditions when using FreeType 2 in -any of your projects or products. - - - The FreeType License, found in the file `FTL.TXT', which is similar - to the original BSD license *with* an advertising clause that forces - you to explicitly cite the FreeType project in your product's - documentation. All details are in the license file. This license - is suited to products which don't use the GNU General Public - License. - - Note that this license is compatible to the GNU General Public - License version 3, but not version 2. - - - The GNU General Public License version 2, found in `GPLv2.TXT' (any - later version can be used also), for programs which already use the - GPL. Note that the FTL is incompatible with GPLv2 due to its - advertisement clause. - -The contributed BDF and PCF drivers come with a license similar to that -of the X Window System. It is compatible to the above two licenses (see -file src/bdf/README and src/pcf/README). The same holds for the files -`fthash.c' and `fthash.h'; their code was part of the BDF driver in -earlier FreeType versions. - -The gzip module uses the zlib license (see src/gzip/zlib.h) which too is -compatible to the above two licenses. - -The MD5 checksum support (only used for debugging in development builds) -is in the public domain. - - ---- end of LICENSE.TXT --- diff --git a/src/3rdparty/freetype/docs/TODO b/src/3rdparty/freetype/docs/TODO index 8b27e269a3..623866eab9 100644 --- a/src/3rdparty/freetype/docs/TODO +++ b/src/3rdparty/freetype/docs/TODO @@ -27,7 +27,7 @@ Other bugs have been registered at the savannah bugzilla of FreeType. ------------------------------------------------------------------------ -Copyright (C) 2001-2020 by +Copyright (C) 2001-2022 by David Turner, Robert Wilhelm, and Werner Lemberg. This file is part of the FreeType project, and may only be used, |