collidoscope reports on situations where paths overlap in a shaped piece of
text.
This software tries every combination of glyphs within a specified Unicode range
and up to a specified length of string and outputs a report of all situations
where the glyphs collide. It has a number of collision tests:
- Paths in non-adjacent glyphs are never allowed to collide.
- If the cursive test is turned on, then paths with a cursive attachment anchor
are allowed to overlap with paths in an adjacent glyph which also contain a
cursive attachment anchor, but are not allowed to overlap with a path without
a cursive attachment anchor.
- If the area test is turned on, then paths in adjacent glyphs may collide so
long as the area of overlap does not exceed a given percentage of the smallest
path's area. i.e. if the area percentage is set to 25%, then two strokes may
connect, because the overlap is likely to be quite small compared to the size
of the paths involved. But if a stroke significantly overlaps a nukta, it will
be reported as a collision. (Of course, this will not detect strokes which
merely graze a nukta.)
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 py39-collidoscope listed in the above command, you can pick from the names under the Packages section.
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>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
print: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* Akinori MUSHA aka knu <knu@idaemons.org>
* Alan Eldridge <alane@geeksrus.net>
* Alex Dupre <ale@FreeBSD.org>
* Alex Dupre <sysadmin@alexdupre.com>
* Alexander Vereeken <Alexander88207@protonmail.com>
* Alexey Dokuchaev <danfe@FreeBSD.org>
* Alonso Cardenas Marquez <acm@FreeBSD.org>
* Andreas Klemm <andreas@FreeBSD.org>
* Andreas Klemm <andreas@klemm.gtn.com>
* Andrew Pantyukhin <infofarmer@FreeBSD.org>
* Anish Mistry <amistry@am-productions.biz>
(Only the first 15 lines of the commit message are shown above )
print/py-collidoscope: Add py-collidoscope 0.0.6
collidoscope reports on situations where paths overlap in a shaped piece of
text.
This software tries every combination of glyphs within a specified Unicode range
and up to a specified length of string and outputs a report of all situations
where the glyphs collide. It has a number of collision tests:
- Paths in non-adjacent glyphs are never allowed to collide.
- If the cursive test is turned on, then paths with a cursive attachment anchor
are allowed to overlap with paths in an adjacent glyph which also contain a
cursive attachment anchor, but are not allowed to overlap with a path without
a cursive attachment anchor.
- If the area test is turned on, then paths in adjacent glyphs may collide so
long as the area of overlap does not exceed a given percentage of the smallest
path's area. i.e. if the area percentage is set to 25%, then two strokes may
connect, because the overlap is likely to be quite small compared to the size
of the paths involved. But if a stroke significantly overlaps a nukta, it will
be reported as a collision. (Of course, this will not detect strokes which
merely graze a nukta.)
WWW: https://github.com/simoncozens/collidoscope
