[ ]unifont-smooth-mono-10.0.06--1.171-merged-with-dejavu-2.36-no-Han-Hangul.7z Monospaced version merged with DejaVu v2.36 (misses U+0000,U+0001,U+30fb and wide Han/Hangul; strokes 10% wider, baseline-or-BBox matched) (Recommended) [ ]unifont-smooth-mono-10.0.07--1.230-no-Han-Hangul.7z Monospaced version, all characters of unifont-10.0.07 except: U+0000, U+0001, U+30fb, wide characters of Han/Hangul, PUA (↑ Recommended if consistency of shapes is more important than quality) [ ]unifont-smooth-non-mono-10.0.06--1.171.7z Non-monospaced version, all non-PUA characters of unifont-10.0.07 (↑ Recommended if double-width glyphs are OK, and consistency is more important than quality) (use 7zip to uncompress; the first two work [even] with Windows’ console)
[ ]coverage-mono.txt - Notepad DejaVu Sans Mono Unifont 2.36--10.0.06--1.171 (size 15).pdf [ ]coverage-mono.txt - Notepad Unifont Smooth Mono 10.0.07--1.230 (size 19).pdf [ ]coverage-all.txt - Notepad Unifont Smooth 10.0.06--1.171 (size 19).pdf
[ ]index-1.171.html Access to the older builds
This is a not yet fully completed project to make GNU Unifont into a nice
scalable font; one of the primary considerations is to make it appropriate for console usage (and Windows’ console is very picky, with pickiness being mostly undefined). The
variants supplied above are monospaced; they are accepted by Windows
console (as well as they may be used by any TrueType capable
application — except for combining marks, which currently combine only
in DejaVu version). (The non-monospaced version is a well-behaved
TrueType font, so it may be used as a fallback font for Unicode content.)
For combining characters, the monospaced version uses the same strategy as the DejaVu Sans Mono: they are monospaced, but use OpenType instructions to behave as if they were 0-width (in OpenType applications - do not know how to test this…). All the (non-PUA) characters available in GNU Unifont 10.0.06 are supplied, with the following omissions in the monospaced version:
As a result, all Unicode 10.0 BMP characters (except
U+30FB/Han/Hangul) are available in the “mono” versions. (If your
architecture’s console supports non-BMP characters, they would be also
available if one can draw them on a 16×16 grid.) The total is
24418 characters, with 15751 in BMP (and
.notdef/.null/nonmarkingreturn). The non-monospace
version has characters of widths 0, 1, or 2 units, and supports all 63902
Unicode 10.0 characters which may be drawn on a 16×16 grid.
Instructions for installation of fonts into Windows console are available here. The gist is:
For these versions of the fonts, the Family Name to use is
reg export "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Console\TrueTypeFont" console-ttf.reg copy console-ttf.reg console-ttf-new.reg ## Edit console-ttf-new.reg reg import console-ttf-new.reg
Unifont Smooth Unifont Smooth Mono
for the merged version).
DejaVu Sans Mono Unifont
The standard distribution of the TrueType version of Unifont has a very serious defect (at least as of July 2014): it contains “fake” glyphs for characters not supported by the font. Such a design error is unexcusable for TrueType fonts; such fake glyphs get in the way when an application tries to find the best way to show a character.
Please note that the fonts distributed here are derived works. The “modified” part is distributed “under the same terms as Perl itself” (either Artistic license, or GPL v1, or GPL later version, based on your choice; but this may be constrained by viral parts of other applicable licenses) with the exception that embedding the font in a document does not in itself constitute a violation of the license.
The fonts on which these fonts are based are distributed under their own licenses (Unifont and DejaVu). As of July 2014, Unifont uses GPL (v2 or later, with the same exception as above, see LICENSE.txt); DejaVu is based on Free License.
In plain words: if you do not (re)distribute my fonts, and just use them in your documents, everything should be OK. If you want more — you need to read the 3 licenses mentioned above.