Almost all uses, if not all of them, are wrong, according to the
semantics of BUILD_DEPENDS (packages built for target available for
use _by_ tools at build-time) and TOOL_DEPEPNDS (packages built for
host available for use _as_ tools at build-time).
No change to BUILD_DEPENDS as used correctly inside buildlink3.
As proposed on tech-pkg:
https://mail-index.netbsd.org/tech-pkg/2023/06/03/msg027632.html
Changelog taken from http://pelulamu.net/unscii/:
In 2020-03-10, the new Unicode version 13.0 added 214 graphics
characters for "legacy computing" (including, among all, the missing
PETSCII characters, and a majority of missing Teletext/Videotex
characters). Most of these were already included in Unscii 1.x, but
now I have been able to give them proper Unicode mappings as
well. This is the main reason for the Unscii 2.0 release.
Additionally, Unscii 2.0 fixes errors in some characters, legibility
in some others and adds a bunch of new ones.
Unscii is a set of bitmapped Unicode fonts based on classic system
fonts. Unscii attempts to support character cell art well while also
being suitable for terminal and programming use.
The two main variants are unscii-8 (8x8) and unscii-16 (8x16). There
are also several alternative styles for unscii-8, as well as a 8x16
"full" variant that incorporates missing Unicode glyphs from Fixedsys
Excelsior and GNU Unifont. "unscii-16-full" falls under GPL because of
how Unifont is licensed; the other variants are in the Public Domain.
HEX and PCF are the only actual bitmapped formats here. HEX is the
same simple hexdump format as used by the Unifont project.
TTF, OTF and WOFF are vectorized because the bitmapped TTF fonts
generated by FontForge didn't seem to work anywhere. Fixes to this
problem are appreciated.
