GNU Unifont

GNU Unifont is a free Unicode bitmap font using an intermediate bitmapped font format created by Roman Czyborra. The main Unifont covers all of the Basic Multilingual Plane (BMP). The "upper" companion covers significant parts of the Supplementary Multilingual Plane (SMP). The "Unifont JP" companion contains Japanese kanji present in the JIS X 0213 character set.

GNU Unifont
Unifont name in own typeface.png
CategoryUnicode, Bitmap, Sans-serif
ClassificationDuospace
Designer(s)Roman Czyborra, Paul Hardy
Date created1998
Glyphs2,096,578
LicenseSource code: GPL-2.0-or-later
Font: GPL-2.0-or-later with Font-exception-2.0
Manual: GFDL-1.3-or-later
Unifont sample v13.0.06.png
Sample
Shown here13.0.06
See all characters
Websiteunifoundry.com/unifont/index.html
savannah.gnu.org/projects/unifont
Latest release version13.0.06[1] Edit this on Wikidata
Latest release date13 February 2021; 5 months ago (13 February 2021)

It is present in most free operating systems and windowing systems such as Linux, XFree86 or the X.Org Server and some embedded firmware such as RockBox. The source code is released under the GPL-2.0-or-later license. The font is released under the GPL-2.0-or-later license with Font-exception-2.0 (embedding the font in a document does not require the document to be placed under the same license). The manual is released under the GFDL-1.3-or-later license.

It became a GNU package in October 2013. The current maintainer is Paul Hardy.

StatusEdit

The Unicode Basic Multilingual Plane covers 216 (65,536) code points. Of this number, 2,048 are reserved for special use as UTF-16 surrogate pairs and 6,400 are reserved for private use. This leaves 57,088 code points to which glyphs can be assigned. Some of these code points are special values that do not have an assigned glyph, but most do have assigned glyphs.

As of May 2019, the GNU Unifont has complete coverage of the Basic Multilingual Plane as defined in Unicode 12.1.0. Its companion fonts, Unifont Upper and Unifont CSUR, have significant coverage of the Supplementary Multilingual Plane and the ConScript Unicode Registry, respectively.

For version 12.1.02, Unifont JP was released, which covers 10,000 Japanese kanji present in the JIS X 0213 character set, some of which are in the Supplementary Ideographic Plane. It is derived from Jiskan16, a public domain font.

Scripts that are less than 100% complete can be augmented by any contributor.

The large block of about 20,000 CJK ideographs has been copied from WenQuanYi's Unibit font with permission.[2](Wen Quan Yi: Spring of Letters)

However, despite its coverage, Unifont stores only one glyph per printable Unicode code point.Because of this, it does not feature the OpenType features needed to render scripts with complex layouts correctly and correctly position the combining diacritics with base letters if these combinations are not encoded in Unicode in their pre-combined form; as well the contextual forms (including joining types, and subjoined clusters) are not handled. This increases the number of glyphs to include in the basic font and it's not possible currently (because of current OpenType limitations) to encode all the needed glyphs to represent all the required combinations that can exist in a single Unicode plane (this is also true for Chinese fonts that cannot cover completely all ideograms currently encoded in two planes, and also in a third plane). Unifont can then only be used as a "last resort" default font, suitable for simple alphabetic scripts, or to render isolated characters, but will make actual texts difficult or sometimes impossible to read correctly. For correctly rendering Indic abugidas (and Semitic abjads if they are written with their optional combining diacritics), other fonts should be specified in stylesheets before this one, and additional fonts will be needed to cover Han ideographs encoded in supplementary planes, or to render most historic (or minority modern) scripts not encoded in the BMP.

DistributionEdit

 
Sample in Japanese and Chinese

Unifont, as of version 12.0.0, is available in vector TTF, BDF, and PCF formats for the "standard build". Only the TrueType build is split into Unifont and two companion fonts.[2]

A few "specialized versions" have been built by request and made available by Paul Hardy. These include a bitmap TTF (SBIT) with empty glyphs filled with code-point values for FontForge users to read, a PSF bitmap with glyphs for APL programmers, and single-file versions in Roman's .hex format (see below).[2] The actual organization of the source consists of smaller .hex files to be stitched together and converted to other formats in a build.[3]

VectorizationEdit

Luis Alejandro González Miranda wrote scripts to vectorize and convert the BDF font to TrueType format using FontForge.[4] Paul Hardy adjusted these scripts to handle combining characters (accents, etc.) for the latest TrueType versions.[2](TrueType Font Generation)

.hex formatEdit

The GNU Unifont .hex format defines its glyphs as either 8 or 16 pixels in width by 16 pixels in height. Most Western script glyphs can be defined as 8 pixels wide, while other glyphs (notably the Chinese–Japanese–Korean, or CJK set) are typically defined as 16 pixels wide.

The unifont.hex file contains one line for each glyph. Each line consists of a four-digit Unicode hexadecimal code point, a colon, and the bitmap string. The bit string is 32 hexadecimal digits for an 8-pixel-wide glyph or 64 hexadecimal digits for a 16-pixel-wide glyph. The goal is to create an intermediate format that would facilitate adding new glyphs.

A 1 bit in the bit string corresponds to an 'on' pixel. The pixel's bits are stored top to bottom, left to right.

ExampleEdit

This is an example font containing one glyph, for ASCII capital 'A'.

0041:0000000018242442427E424242420000

The first number is the hexadecimal Unicode code point, with range 0000 through FFFF. Hexadecimal 0041 is decimal 65, the code point for the letter 'A'. The colon separates the code point from the bitmap. In this example, the glyph is 8 pixels wide, so the bit string is 32 hexadecimal digits long.

The bit string begins with 8 zeros, so the top 4 rows will be empty (2 hexadecimal digits per 8 bit byte, with 8 bits per row for an 8 pixel-wide glyph). The bit string also ends with 4 zeros, so the bottom 2 rows will be empty. It is implicit from this that the default font descender is 2 rows below the baseline, and the capital height is 10 rows above the baseline. This is the case in the GNU Unifont with Latin glyphs.

Over time, a number of ways have been created to handle the format. The earliest way is the hexdraw Perl script, which converts the string into an ASCII art representation to be edited in a text editor. Another method involves generating a bitmap image grid for an entire range of code points and working with an image editor. In either case, the edited glyphs are later converted back into .hex files for storage.[3]

HistoryEdit

Roman Czyborra created the Unifont format in 1998[5] after earlier efforts dating to 1994.

In 2008, Luis Alejandro González Miranda wrote a program to convert Unifont into a TrueType font. Paul Hardy modified it later to support combining characters in the TrueType version.

Later, Richard Stallman published Unifont as a GNU package in October 2013, with Paul Hardy as its maintainer.

ReferencesEdit

  1. ^ https://ftp.gnu.org/gnu/unifont/unifont-13.0.06/; retrieved: 3 July 2021.
  2. ^ a b c d GNU Unifont Glyphs
  3. ^ a b "Unifoundry Unicode Utilities". unifoundry.com. Retrieved 16 April 2019.
  4. ^ GNU Unifont in TrueType format, archived from the original on 2016-02-01
  5. ^ Roman Czyborra's GNU Unifont page
  • The Unicode Consortium: The Unicode 5.0 Standard. 5th, Addison Wesley 2007; ISBN 0-321-48091-0.

External linksEdit