sync with OpenBSD -current

This commit is contained in:
purplerain 2024-08-06 22:23:11 +00:00
parent acb2a22980
commit 455fea1627
Signed by: purplerain
GPG key ID: F42C07F07E2E35B7
229 changed files with 25075 additions and 13981 deletions

View file

@ -1,3 +1,57 @@
CHANGES BETWEEN 2.13.1 and 2.13.2 (2023-Aug-25)
I. MISCELLANEOUS
- Better support for CFF2 variation fonts.
- TrueType interpreter version 38 (also known as 'Infinality') has
been removed.
- Improved OpenVMS support.
======================================================================
CHANGES BETWEEN 2.13.0 and 2.13.1 (2023-Jun-24)
I. MISCELLANEOUS
- New function `FT_Get_Default_Named_Instance` to get the index of
the default named instance of an OpenType Variation Font.
- A new load flag `FT_LOAD_NO_SVG` to make FreeType ignore glyphs in
an 'SVG ' table.
- New function `FT_GlyphSlot_AdjustWeight` to adjust the glyph
weight either horizontally or vertically. This is part of the
`ftsynth.h` header file, which is still considered to be in alpha
stage.
- TrueType interpreter version 38 (also known as 'Infinality') has
been deactivated; the value of `TT_INTERPRETER_VERSION_38` is now
the same as `TT_INTERPRETER_VERSION_40`.
- Updated OpenVMS support.
- The base API documentation has been modularized for easier
handling.
- Switching named instances on and off in Variation Fonts was buggy
if the design coordinates didn't change.
- `ftbench` has a new command-line option `-a` to apply design
coordinates.
- `ftview` can now flip SVG rendering on and off using the 'Z' key.
- In `ftmulti` it is now possible to toggle the fill rule and
overlap flag used for rendering glyphs using the 'F3' and 'F4'
keys, respectively. Toggling the anti-aliased mode has been
changed to the 'TAB' key.
======================================================================
CHANGES BETWEEN 2.12.1 and 2.13.0 (2023-Feb-09)
I. IMPORTANT CHANGES
@ -12,7 +66,7 @@ CHANGES BETWEEN 2.12.1 and 2.13.0 (2023-Feb-09)
https://learn.microsoft.com/en-us/typography/opentype/spec/colr
III. MISCELLANEOUS
II. MISCELLANEOUS
- For OpenType Variable Fonts, `avar` table format 2.0 is now
supported. The code was contributed by Behdad Esfahbod.
@ -75,6 +129,10 @@ CHANGES BETWEEN 2.12.1 and 2.13.0 (2023-Feb-09)
af_debug_hints_
```
- The internal zlib library was updated to version 1.2.13. Note,
however, that FreeType is *not* affected by CVE-2022-37434 since
it doesn't use the `inflateGetHeader` function.
======================================================================
@ -2420,7 +2478,7 @@ CHANGES BETWEEN 2.3.8 and 2.3.7
is provided for x86 and ARM. See FT_CONFIG_OPTION_INLINE_MULFIX
and FT_CONFIG_OPTION_NO_ASSEMBLER (in ftoption.h) for more.
- The handling of `tricky' fonts (this is, fonts which don't work
- The handling of `tricky' fonts (that is, fonts which don't work
with the autohinter, needing the font format's hinting engine)
has been generalized and changed slightly:
@ -2877,7 +2935,7 @@ CHANGES BETWEEN 2.2 and 2.1.10
II. IMPORTANT CHANGES
- Version 2.2 no longer exposes its internals, this is, the header
- Version 2.2 no longer exposes its internals, that is, the header
files located in the `include/freetype/internal' directory of
the source package are not copied anymore by the `make install'
command. Consequently, a number of rogue clients which directly

View file

@ -270,12 +270,12 @@ to access them.
`FT2_DEBUG' environment variable. Use this function to override
the value with `level'. Use value `NULL' to disable tracing.
FT_Trace_Set_Default_Level():
FT_Trace_Set_Default_Level( void )
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 ):
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
@ -290,7 +290,7 @@ to access them.
first argument of `FT_TRACE' or `FT_ERROR', and `args' holds the
remaining arguments.
FT_Set_Default_Log_Handler():
FT_Set_Default_Log_Handler( void )
Reset the log handler to the default version.

View file

@ -1,23 +1,23 @@
How to build the FreeType 2 library on VMS
-----------------------------------------
How to build the FreeType library on VMS
----------------------------------------
It is actually very straightforward to install the FreeType 2 library.
Just execute vms_make.com from the toplevel directory to build the
It is actually very straightforward to install the FreeType library.
Just execute `vms_make.com from` the toplevel directory to build the
library. This procedure currently accepts the following options:
DEBUG
* `DEBUG`
Build the library with debug information and without optimization.
lopts=<value>
Options to pass to the link command e.g. lopts=/traceback
* `lopts=<value>`
Options to pass to the link command, e.g., `lopts=/traceback`.
ccopt=<value>
Options to pass to the C compiler e.g. ccopt=/float=ieee
* `ccopt=<value>`
Options to pass to the C compiler, e.g., `ccopt=/float=ieee`.
In case you did download the demos, place them in a separate directory
sharing the same top level as the directory of FreeType 2 and follow
the same instructions as above for the demos from there. The build
process relies on this to figure out the location of the FreeType 2
sharing the same top level as the directory of FreeType and follow the
same instructions as above for the demos from there. The build
process relies on this to figure out the location of the FreeType
include files.
@ -28,24 +28,31 @@ The library is available in the directory
[.LIB]
To compile applications using FreeType 2 you have to define the
logical FREETYPE pointing to the directory
To compile applications using FreeType you have to define the logical
`FREETYPE` pointing to the directory
[.INCLUDE.FREETYPE]
i.e., if the directory in which this INSTALL.VMS file is located is
$disk:[freetype] then define the logical with
i.e., if the directory in which this `INSTALL.VMS` file is located is
`$disk:[freetype.docs]`, then define the logical with
define freetype $disk:[freetype.include.freetype]
This version has been tested with Compaq C V6.2-006 on OpenVMS Alpha
V7.2-1.
See http://nchrem.tnw.tudelft.nl/openvms/software2.html#Freetype for
the packages FreeType depends on.
The latest versions were tested using
- VSI C V7.4-002 and DECWindows V1.7-F on OpenVMS Alpha V8.4-2L1
- VSI C V7.4-001 and DECWindows V1.7-E on OpenVMS IA64 V8.4-2L3
Any problems can be reported to
Any problems can be reported to
Jouk Jansen <joukj@hrem.stm.tudelft.nl> or
Martin P.J. Zinser <zinser@zinser.no-ip.info>
Jouk Jansen <joukj@hrem.nano.tudelft.nl> or
Orginal version of the build procedures was created by
Martin P.J. Zinser <zinser@zinser.no-ip.info>
------------------------------------------------------------------------

View file

@ -18,8 +18,6 @@ There are two ways to generate the documentation:
- This may or may not require internet access every time depending on
pip and system caching.
This also works with Jam: Just type `jam refdoc' in the main directory.
Some troubleshooting tips:
* Regularly run `pip install --upgrade docwriter' to check for updates which

View file

@ -60,6 +60,8 @@ found on _most_ systems, but not all of them:
release libtool so
-------------------------------
2.13.2 26.1.20 6.20.1
2.13.1 26.0.20 6.20.0
2.13.0 25.0.19 6.19.0
2.12.1 24.3.18 6.18.3
2.12.0 24.2.18 6.18.2

View file

@ -57,7 +57,7 @@ Notes
(`*') in the table below.
FreeType can be configured to support Mac files (on older Mac OS
versions, a `file' is stored as a data and a resource fork, this is,
versions, a `file' is stored as a data and a resource fork, that is,
within two separate data chunks). If a file can't be opened as a
font, FreeType then checks whether it is a resource fork, trying to
extract the contained font data from either a `POST' or `sfnt'
@ -77,8 +77,8 @@ which isn't supported yet please send a mail too.
--- BDF --- --- bdf 5005.BDF_Spec.pdf, X11
SFNT PS TYPE_1 --- type1 Type 1 GX Font Format
(for the Mac) [3]
SFNT PS TYPE_1 --- type1 Type 1 GX Font Format [7]
(for the Mac; not supported)
SFNT PS TYPE_1 CID cid 5180.sfnt.pdf (for the Mac) [3]
SFNT PS CFF --- cff OT spec, 5176.CFF.pdf
(`OTTO' format)
@ -198,6 +198,12 @@ which isn't supported yet please send a mail too.
[6] Supported font formats are TrueType and OpenType fonts as
defined in the OpenType specification 1.6 and newer.
[7] `The Type 1 GX Font Format' (dated 1995-09-27) was distributed in
Apple Developer CD-ROM in those days. The content of `TYP1' table
is a PostScript Type 1 font without the eexec encryption. Current
versions of FreeType don't not support this format, but FontForge
can load it.
------------------------------------------------------------------------
Copyright (C) 2004-2023 by

View file

@ -1,4 +1,4 @@
.TH FREETYPE-CONFIG 1 "February 2023" "FreeType 2.13.0"
.TH FREETYPE-CONFIG 1 "August 2023" "FreeType 2.13.2"
.
.
.SH NAME

View file

@ -15,33 +15,53 @@ How to prepare a new release
. docs/VERSIONS.TXT: Document changed `version_info`.
. Clone the git archive to another directory with
. Update the 'dlg' submodule with
git clone -l -s . ../freetype.test
git submodule foreach git pull origin master
or something like this and run
. Copy the submodule code with
make distclean; make devel; make
make distclean; make devel; make multi
make distclean; make devel CC=g++; make CC=g++
make distclean; make devel CC=g++; make multi CC=g++
make copy_submodule
and run
make distclean && make devel && make
make distclean && make devel && make multi
make distclean && make devel CC=g++ && make CC=g++ ANSIFLAGS=""
make distclean && make devel CC=g++ && make multi CC=g++ ANSIFLAGS=""
sh autogen.sh
make distclean; ./configure CC=g++; make
make distclean && ./configure CC=g++ && make ANSIFLAGS=""
in the cloned repository to test compilation with both gcc and g++.
to test compilation with both gcc and g++ (you might also add the `-j`
flag to `make` for parallel compilation).
Note that it is normally not necessary to test standard C
compilation with the `configure`, `meson`, and `cmake` build tools
since this is done by the CI process of 'gitlab.freetype.org' for
since this is done by the CI process of 'gitlab.freedesktop.org' for
every commit.
. Test C++ compilation for 'freetype-demos' too (using `git clone` as
above).
. Test C++ compilation for 'freetype-demos' too; this needs a compiled
FreeType library as described in the `README` file.
make distclean && make
make distclean && make CC=g++ ANSIFLAGS=""
. Run `src/tools/chktrcmp.py` and check that there are no undefined
`trace_XXXX` macros.
. Update meson subproject files (for both the 'freetype' and
'freetype-demos' git repositories) with
meson subprojects update
. Test meson compilation (for both the 'freetype' and 'freetype-demos'
git repositories) with
meson setup builddir && meson compile -C builddir
. Commit everything.
. After pushing the new release, tag the git repositories ('freetype',
'freetype-demos') with