2017-01-16 14:11:46 by Adam Ciarcinski | Files touched by this commit (2) |
Log message:
FreeType 2.7.1 has been released. The most important news is preliminary support \
of Adobe's new CFF2 font format and variation fonts as specified in the new \
OpenType specification version 1.8. It also fixes the handling of raw CID fonts \
(which might be found in PDF files)
|
2016-10-30 18:07:12 by Thomas Klausner | Files touched by this commit (1) |
Log message:
Add rpath to freetype-config script.
Bump PKGREVISION.
|
2016-09-12 20:06:44 by Thomas Klausner | Files touched by this commit (3) |
Log message:
Updated freetype2 to 2.7.
Remove subpixel option which is now on by default.
CHANGES BETWEEN 2.6.5 and 2.7
I. IMPORTANT CHANGES
- As announced earlier, the 2.7.x series now uses the new subpixel
hinting mode as the default, emulating a modern version of
ClearType.
This change inevitably leads to different rendering results, and
you might change the `TT_CONFIG_OPTION_SUBPIXEL_HINTING'
configuration option to adapt it to your taste (or use the new
`FREETYPE_PROPERTIES' environment variable). See the
corresponding entry below for version 2.6.4, which gives more
information.
- A new option `FT_CONFIG_OPTION_ENVIRONMENT_PROPERTIES' has been
introduced. If set (which is the default), an environment
variable `FREETYPE_PROPERTIES' can be used to control driver
properties. Example:
FREETYPE_PROPERTIES=truetype:interpreter-version=35 \
cff:no-stem-darkening=1 \
autofitter:warping=1
This allows to select, say, the subpixel hinting mode at runtime
for a given application. See file `ftoption.h' for more.
II. IMPORTANT BUG FIXES
- After loading a named instance of a GX variation font, the
`face_index' value in the returned `FT_Face' structure now
correctly holds the named instance index in the upper 16bits as
documented.
III. MISCELLANEOUS
- A new macro `FT_IS_NAMED_INSTANCE' to test whether a given face
is a named instance.
- More fixes to GX font handling.
- Apple's `GETVARIATION' bytecode operator (needed for GX
variation font support) has been implemented.
- Another round of fuzzer fixes, mainly to reject invalid fonts
faster.
- Handling of raw CID fonts was broken (bug introduced in version
2.6.4).
- The smooth rasterizer has been streamlined to make it faster by
approx. 20%.
- The `ftgrid' demo program now understands command line option
`-d' to give start-up design coordinates.
- The `ftdump' demo program has a new command line option `-p' to
dump TrueType bytecode instructions.
|
2016-07-22 12:30:11 by Adam Ciarcinski | Files touched by this commit (2) |
Log message:
FreeType 2.6.5
This release is almost identical to the previous version, with two differences.
* It compiles again on Mac OS X, and
* it reverts the activation of subpixel hinting by default; it will be enabled \
by default in the forthcoming 2.7.x series. Main reason for reverting this \
feature is the principle of least surprise: a sudden change in appearance of all \
fonts (even if the rendering improves for almost all recent fonts) should not be \
expected in a new micro version of a series.
|
2016-07-09 14:23:16 by Adam Ciarcinski | Files touched by this commit (5) |
Log message:
Changes 2.6.4:
FreeType 2.6.4 has been released. The most important change is a new bytecode \
hinting mode for TrueType fonts that finally activates subpixel hinting (a.k.a. \
ClearType hinting) by default.
The new release also brings support for the following new scripts in the \
auto-hinter: Armenian, Cherokee, Ethiopic, Georgian, Gujarati, Gurmukhi, \
Malayalam, Sinhala, and Tamil.
|
2016-04-07 12:02:13 by Adam Ciarcinski | Files touched by this commit (3) |
Log message:
CHANGES BETWEEN 2.6.2 and 2.6.3
I. IMPORTANT CHANGES
- Khmer, Myanmar, Bengali, and Kannada script support has been
added to the auto-hinter.
II. MISCELLANEOUS
- Better support of Indic scripts like Devanagari by using a
top-to-bottom hinting flow.
- All FreeType macros starting with two underscores have been
renamed to avoid a violation of both the C and C++ standards.
Example: Header macros of the form `__FOO_H__' are now called
`FOO_H_'. In most cases, this should be completely transparent
to the user. The exception to this is `__FTERRORS_H__', which
must be sometimes undefined by the user to get FreeType error
strings: Both this form and the new `FTERRORS_H_' macro are
accepted for backwards compatibility.
- Minor improvements mainly to the Type 1 driver.
- The new CFF engine now supports all Type 2 operators except
`random'.
- The macro `_STANDALONE_', used for compiling the B/W and smooth
rasterizers as stand-alone modules, has been renamed to
`STANDALONE_', since macro names starting with an underscore and
followed by an uppercase letter are reserved in both C and C++.
- Function `FT_Library_SetLcdFilterWeights' now also activates
custom LCD filter weights (instead of just adjusting them).
- Support for `unpatented hinting' has been completely removed:
Consequently, the two functions `FT_Face_CheckTrueTypePatents'
and `FT_Face_SetUnpatentedHinting' now return always false,
doing nothing.
- The `ftgamma' demo program has been modernized; the gamma grid
display has been moved from `ftview' to this program.
- It is now possible to cycle through the available LCD fitlering
modes.
|
2016-03-14 07:08:11 by Darrin B. Jewell | Files touched by this commit (1) |
Log message:
set CHECK_BUILTIN.zlib:=yes so that zlib's builtin.mk won't create a fake zlib.pc
otherwise, freetype2 will add a Requires: for the fake .pc file to its own .pc file
|
2016-02-25 14:37:48 by Jonathan Perkin | Files touched by this commit (20) |
Log message:
Use OPSYSVARS.
|
2016-01-10 22:16:34 by Benny Siegert | Files touched by this commit (4) |
Log message:
Update freetype2 to 2.6.2. Include file layout changed yet again, please
test dependent packages.
CHANGES BETWEEN 2.6 and 2.6.1
I. IMPORTANT BUG FIXES
- It turned out that for CFFs only the advance widths should be
taken from the `htmx' table, not the side bearings. This bug,
introduced in version 2.6.0, makes it necessary to upgrade if
you are using CFFs; otherwise, you get cropped glyphs with GUI
interfaces like GTK or Qt.
- Accessing Type 42 fonts returned incorrect results if the glyph
order of the embedded TrueType font differs from the glyph order
of the Type 42 charstrings table.
II. IMPORTANT CHANGES
- The header file layout has been changed (again), moving all
header files except `ft2build.h' into a subdirectory tree.
Doing so reduces the possibility of header file name clashes
(e.g., FTGL's `FTGlyph.h' with FreeType's `ftglyph.h') on case
insensitive file systems like Mac OS X or Windows.
Applications that use (a) the `freetype-config' script or
FreeType's `freetype2.pc' file for pkg-config to get the include
directory for the compiler, and (b) the documented way for
header inclusion like
#include <ft2build.h>
#include FT_FREETYPE_H
...
don't need any change to the source code.
- Simple access to named instances in GX variation fonts is now
available (in addition to the previous method via FreeType's MM
interface). In the `FT_Face' structure, bits 16-30 of the
`face_index' field hold the current named instance index for the
given face index, and bits 16-30 of `style_flags' contain the
number of instances for the given face index. `FT_Open_Face'
and friends also understand the extended bits of the face index
parameter.
You need to enable TT_CONFIG_OPTION_GX_VAR_SUPPORT for this new
feature. Otherwise, bits 16-30 of the two fields are zero (or
are ignored).
- Lao script support has been added to the auto-hinter.
III. MISCELLANEOUS
- The auto-hinter's Arabic script support has been enhanced.
- Superscript-like and subscript-like glyphs as used by various
phonetic alphabets like the IPA are now better supported by the
auto-hinter.
- The TrueType bytecode interpreter now runs slightly faster.
- Improved support for builds with cmake.
- The function `FT_CeilFix' now always rounds towards plus
infinity.
- The function `FT_FloorFix' now always rounds towards minus
infinity.
- A new load flag `FT_LOAD_COMPUTE_METRICS' has been added; it
makes FreeType ignore pre-computed metrics, as needed by font
validating or font editing programs. Right now, only the
TrueType module supports it to ignore data from the `hdmx'
table.
- Another round of bug fixes to better handle broken fonts, found
by Kostya Serebryany <kcc@google.com>.
CHANGES BETWEEN 2.6.1 and 2.6.2
I. IMPORTANT CHANGES
- The auto-hinter now supports stem darkening, to be controlled by
the new `no-stem-darkening' and `darkening-parameters'
properties. This is an experimental feature contributed by
Nikolaus Waxweiler, and the interface might change in a future
release.
- By default, stem darkening is now switched off (for both the CFF
engine and the auto-hinter). The main reason is that you need
linear alpha blending and gamma correction to get correct
rendering results, and the latter is not yet available in most
freely available rendering stacks like X11. Applying stem
darkening without proper gamma correction leads to far too dark
rendering results.
- The meaning of `FT_RENDER_MODE_LIGHT' has been slightly
modified. It now essentially means `no hinting along the
horizontal axis'; in particular, no change of glyph advance
widths. Consequently, the auto-hinter is used for all scalable
font formats except for CFF. It is planned that other
font-specific rendering engines (TrueType, Type 1) will follow.
II. MISCELLANEOUS
- The default LCD filter has been changed to be normalized and
color-balanced.
- For better compatibility with FontConfig, function
`FT_Library_SetLcdFilter' accepts a new enumeration value
`FT_LCD_FILTER_LEGACY1' (which has the same meaning as
`FT_LCD_FILTER_LEGACY').
- A large number of bugs have been detected by using the libFuzzer
framework, which should further improve handling of invalid
fonts. Thanks again to Kostya Serebryany and Bungeman!
- `TT_CONFIG_OPTION_MAX_RUNNABLE_OPCODES', a new configuration
option, controls the maximum number of executed opcodes within a
bytecode program. You don't want to change this except for very
special situations (e.g., making a library fuzzer spend less
time to handle broken fonts).
- The smooth renderer has been made faster.
- The `ftstring' demo program now supports sub-pixel rendering;
use key `l' to cycle through the LCD modes.
- The `ftstring' demo program now supports colour rendering; use
the `space' key to cycle through various colour combinations.
- The graphical demo programs now use a default gamma value of 1.8
(instead of 1.2).
|
2015-11-03 22:34:36 by Alistair G. Crooks | Files touched by this commit (610) |
Log message:
Add SHA512 digests for distfiles for graphics category
Problems found with existing digests:
Package fotoxx distfile fotoxx-14.03.1.tar.gz
ac2033f87de2c23941261f7c50160cddf872c110 [recorded]
118e98a8cc0414676b3c4d37b8df407c28a1407c [calculated]
Package ploticus-examples distfile ploticus-2.00/plnode200.tar.gz
34274a03d0c41fae5690633663e3d4114b9d7a6d [recorded]
da39a3ee5e6b4b0d3255bfef95601890afd80709 [calculated]
Problems found locating distfiles:
Package AfterShotPro: missing distfile AfterShotPro-1.1.0.30/AfterShotPro_i386.deb
Package pgraf: missing distfile pgraf-20010131.tar.gz
Package qvplay: missing distfile qvplay-0.95.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
|