OpenType fonts are "programmed" using features, which are normally authored in
Adobe's feature file format. This like source code to a computer program: it's a
user-friendly, but computer-unfriendly, way to represent the features.
Inside a font, the features are compiled in an efficient internal format. This
is like the binary of a computer program: computers can use it, but they can't
do else anything with it, and people can't read it.
The purpose of this library is to provide a middle ground for representing
features in a machine-manipulable format, kind of like the abstract syntax tree
of a computer programmer. This is so that:
- features can be represented in a structured human-readable and
machine-readable way, analogous to the XML files of the Unified Font Object
format.
- features can be more directly authored by programs (such as font editors),
rather than them having to output AFDKO feature file format.
- features can be easily manipulated by programs - for example, features from
two files merged together, or lookups moved between languages.
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above. NOTE: This is a Python port. Instead of py312-fontfeatures listed in the above command, you can pick from the names under the Packages section.
===> The following configuration options are available for py312-fontfeatures-1.9.0:
SHAPER=off: Unicode shaping engine support
===> Use 'make config' to modify these settings
*/*: switch dependency from devel/py-lxml5 to devel/py-lxml
Currently, there are two versions of python XML processing library
which conflict each other in the ports tree, namely:
- devel/py-lxml5 (now at version 5.4.0)
- devel/py-lxml (now at version 6.0.1)
To avoid the situation that some ports depend on py-lxml5 and some
others do on py-lxml (by switching dependencies individually), this
commit switches the dependencies from py-lxml5 to py-lxml at once.
Additional note: There are still two ports (textproc/py-rdflib and
www/py-draftjs-exporter) depending on py-lxml5 since they limit upper
version to less than 6.
PR: 289491
Approved by: Michiel van Baak Jansen <michiel@vanbaak.eu>, arrowd,
crees, madpilot, delphij, marcus, nivit, kai,
skreuzer, fluffy, bofh, thierry, stephen, sunpoet,
0mp, Eric Camachat <eric@camachat.org>
*/*: update dependency on devel/py-lxml to devel/py-lxml5
www/py-beautifulsoup has switched dependency on devel/py-lxml to
devel/py-lxml5.
Ports which directly or indirectly depends on both
www/py-beautifulsoup and devel/py-lxml must also switch their
dependencies on devel/py-lxml to devel/py-lxml5 to avoid conflicts.
PR: 288047
Approved by: portmgr (chase dependency change)
filesystems: add new category for file systems and related utilities
The filesystems category houses file systems and file system utilities.
It is added mainly to turn the sysutils/fusefs-* pseudo-category into
a proper one, but is also useful for the sundry of other file systems
related ports found in the tree.
Ports that seem like they belong there are moved to the new category.
Two ports, sysutils/fusefs-funionfs and sysutils/fusefs-fusepak are
not moved as they currently don't fetch and don't have TIMESTAMP set
in their distinfo, but that is required to be able to push a rename
of the port by the pre-receive hook.
Approved by: portmgr (rene)
Reviewed by: mat
Pull Request: https://github.com/freebsd/freebsd-ports/pull/302
PR: 281988
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
x11-fonts/py-fontfeatures: Add py-fontfeatures 1.7.3
OpenType fonts are "programmed" using features, which are normally authored in
Adobe's feature file format. This like source code to a computer program: it's a
user-friendly, but computer-unfriendly, way to represent the features.
Inside a font, the features are compiled in an efficient internal format. This
is like the binary of a computer program: computers can use it, but they can't
do else anything with it, and people can't read it.
The purpose of this library is to provide a middle ground for representing
features in a machine-manipulable format, kind of like the abstract syntax tree
of a computer programmer. This is so that:
- features can be represented in a structured human-readable and
machine-readable way, analogous to the XML files of the Unified Font Object
format.
- features can be more directly authored by programs (such as font editors),
rather than them having to output AFDKO feature file format.
- features can be easily manipulated by programs - for example, features from
two files merged together, or lookups moved between languages.
