Table of Contents
*****************

1 Introduction
2 Tutorial
  2.1 Unicode
  2.2 Unifont Structure
  2.3 Hex File Format
  2.4 Hex File Format
  2.5 Using Hexdraw
  2.6 Checking Coverage
  2.7 Custom Builds
  2.8 Seeing the Big Picture (Literally!)
  2.9 Combining Circles
  2.10 Installing Fonts on GNU/Linux
  2.11 Creating a Brand New Font
  2.12 Updates to Unicode
3 Reference
  3.1 bdfimplode
    3.1.1 bdfimplode NAME
    3.1.2 bdfimplode SYNOPSIS
    3.1.3 bdfimplode DESCRIPTION
    3.1.4 bdfimplode FILES
    3.1.5 bdfimplode SEE ALSO
    3.1.6 bdfimplode AUTHOR
    3.1.7 bdfimplode LICENSE
    3.1.8 bdfimplode BUGS
  3.2 hex2bdf
    3.2.1 hex2bdf NAME
    3.2.2 hex2bdf SYNOPSIS
    3.2.3 hex2bdf DESCRIPTION
    3.2.4 hex2bdf OPTIONS
    3.2.5 hex2bdf EXAMPLE
    3.2.6 hex2bdf FILES
    3.2.7 hex2bdf SEE ALSO
    3.2.8 hex2bdf AUTHOR
    3.2.9 hex2bdf LICENSE
    3.2.10 hex2bdf BUGS
  3.3 hex2sfd
    3.3.1 hex2sfd NAME
    3.3.2 hex2sfd SYNOPSIS
    3.3.3 hex2sfd DESCRIPTION
    3.3.4 hex2sfd FILES
    3.3.5 hex2sfd SEE ALSO
    3.3.6 hex2sfd AUTHOR
    3.3.7 hex2sfd LICENSE
    3.3.8 hex2sfd BUGS
  3.4 hexbraille
    3.4.1 hexbraille NAME
    3.4.2 hexbraille SYNOPSIS
    3.4.3 hexbraille DESCRIPTION
    3.4.4 hexbraille FILES
    3.4.5 hexbraille SEE ALSO
    3.4.6 hexbraille AUTHOR
    3.4.7 hexbraille LICENSE
    3.4.8 hexbraille BUGS
  3.5 hexdraw
    3.5.1 hexdraw NAME
    3.5.2 hexdraw SYNOPSIS
    3.5.3 hexdraw DESCRIPTION
    3.5.4 hexdraw FILES
    3.5.5 hexdraw SEE ALSO
    3.5.6 hexdraw AUTHOR
    3.5.7 hexdraw LICENSE
    3.5.8 hexdraw BUGS
  3.6 hexmerge
    3.6.1 hexmerge NAME
    3.6.2 hexmerge SYNOPSIS
    3.6.3 hexmerge DESCRIPTION
    3.6.4 hexmerge FILES
    3.6.5 hexmerge SEE ALSO
    3.6.6 hexmerge AUTHOR
    3.6.7 hexmerge LICENSE
    3.6.8 hexmerge BUGS
  3.7 johab2ucs2
    3.7.1 johab2ucs2 NAME
    3.7.2 johab2ucs2 SYNOPSIS
    3.7.3 johab2ucs2 DESCRIPTION
    3.7.4 johab2ucs2 FILES
    3.7.5 johab2ucs2 SEE ALSO
    3.7.6 johab2ucs2 AUTHOR
    3.7.7 johab2ucs2 LICENSE
    3.7.8 johab2ucs2 BUGS
  3.8 unibdf2hex
    3.8.1 unibdf2hex NAME
    3.8.2 unibdf2hex SYNOPSIS
    3.8.3 unibdf2hex DESCRIPTION
    3.8.4 unibdf2hex FILES
    3.8.5 unibdf2hex SEE ALSO
    3.8.6 unibdf2hex AUTHOR
    3.8.7 unibdf2hex LICENSE
    3.8.8 unibdf2hex BUGS
  3.9 unibmp2hex
    3.9.1 unibmp2hex NAME
    3.9.2 unibmp2hex SYNOPSIS
    3.9.3 unibmp2hex DESCRIPTION
    3.9.4 unibmp2hex OPTIONS
    3.9.5 unibmp2hex FILES
    3.9.6 unibmp2hex SEE ALSO
    3.9.7 unibmp2hex AUTHOR
    3.9.8 unibmp2hex LICENSE
    3.9.9 unibmp2hex BUGS
  3.10 unicoverage
    3.10.1 unicoverage NAME
    3.10.2 unicoverage SYNOPSIS
    3.10.3 unicoverage DESCRIPTION
    3.10.4 unicoverage OPTIONS
    3.10.5 unicoverage FILES
    3.10.6 unicoverage SEE ALSO
    3.10.7 unicoverage AUTHOR
    3.10.8 unicoverage LICENSE
    3.10.9 unicoverage BUGS
  3.11 unidup
    3.11.1 unidup NAME
    3.11.2 unidup SYNOPSIS
    3.11.3 unidup DESCRIPTION
    3.11.4 unidup FILES
    3.11.5 unidup SEE ALSO
    3.11.6 unidup AUTHOR
    3.11.7 unidup LICENSE
    3.11.8 unidup BUGS
  3.12 unifontchojung
    3.12.1 unifontchojung NAME
    3.12.2 unifontchojung SYNOPSIS
    3.12.3 unifontchojung DESCRIPTION
    3.12.4 unifontchojung FILES
    3.12.5 unifontchojung SEE ALSO
    3.12.6 unifontchojung AUTHOR
    3.12.7 unifontchojung LICENSE
    3.12.8 unifontchojung BUGS
  3.13 unifontksx
    3.13.1 unifontksx NAME
    3.13.2 unifontksx SYNOPSIS
    3.13.3 unifontksx DESCRIPTION
    3.13.4 unifontksx FILES
    3.13.5 unifontksx SEE ALSO
    3.13.6 unifontksx AUTHOR
    3.13.7 unifontksx LICENSE
    3.13.8 unifontksx BUGS
  3.14 unifontpic
    3.14.1 unifontpic NAME
    3.14.2 unifontpic SYNOPSIS
    3.14.3 unifontpic DESCRIPTION
    3.14.4 unifontpic OPTIONS
    3.14.5 unifontpic EXAMPLES
    3.14.6 unifontpic FILES
    3.14.7 unifontpic SEE ALSO
    3.14.8 unifontpic AUTHOR
    3.14.9 unifontpic LICENSE
    3.14.10 unifontpic BUGS
  3.15 unigencircles
    3.15.1 unigencircles NAME
    3.15.2 unigencircles SYNOPSIS
    3.15.3 unigencircles DESCRIPTION
    3.15.4 unigencircles EXAMPLE
    3.15.5 unigencircles FILES
    3.15.6 unigencircles SEE ALSO
    3.15.7 unigencircles AUTHOR
    3.15.8 unigencircles LICENSE
    3.15.9 unigencircles BUGS
  3.16 unigenwidth
    3.16.1 unigenwidth NAME
    3.16.2 unigenwidth SYNOPSIS
    3.16.3 unigenwidth DESCRIPTION
    3.16.4 unigenwidth EXAMPLE
    3.16.5 unigenwidth FILES
    3.16.6 unigenwidth SEE ALSO
    3.16.7 unigenwidth AUTHOR
    3.16.8 unigenwidth LICENSE
    3.16.9 unigenwidth BUGS
  3.17 unihex2bmp
    3.17.1 unihex2bmp NAME
    3.17.2 unihex2bmp SYNOPSIS
    3.17.3 unihex2bmp DESCRIPTION
    3.17.4 unihex2bmp OPTIONS
    3.17.5 unihex2bmp FILES
    3.17.6 unihex2bmp SEE ALSO
    3.17.7 unihex2bmp AUTHOR
    3.17.8 unihex2bmp LICENSE
    3.17.9 unihex2bmp BUGS
  3.18 unihex2png
    3.18.1 unihex2png NAME
    3.18.2 unihex2png SYNOPSIS
    3.18.3 unihex2png DESCRIPTION
    3.18.4 unihex2png OPTIONS
    3.18.5 unihex2png EXAMPLE
    3.18.6 unihex2png FILES
    3.18.7 unihex2png SEE ALSO
    3.18.8 unihex2png AUTHOR
    3.18.9 unihex2png LICENSE
    3.18.10 unihex2png BUGS
  3.19 unihexgen
    3.19.1 unihexgen NAME
    3.19.2 unihexgen SYNOPSIS
    3.19.3 unihexgen DESCRIPTION
    3.19.4 unihexgen OPTIONS
    3.19.5 unihexgen FILES
    3.19.6 unihexgen EXAMPLE
    3.19.7 unihexgen SEE ALSO
    3.19.8 unihexgen AUTHOR
    3.19.9 unihexgen LICENSE
    3.19.10 unihexgen BUGS
  3.20 unipagecount
    3.20.1 unipagecount NAME
    3.20.2 unipagecount SYNOPSIS
    3.20.3 unipagecount DESCRIPTION
    3.20.4 unipagecount OPTIONS
    3.20.5 unipagecount FILES
    3.20.6 unipagecount SEE ALSO
    3.20.7 unipagecount AUTHOR
    3.20.8 unipagecount LICENSE
    3.20.9 unipagecount BUGS
  3.21 unipng2hex
    3.21.1 unipng2hex NAME
    3.21.2 unipng2hex SYNOPSIS
    3.21.3 unipng2hex DESCRIPTION
    3.21.4 unipng2hex OPTIONS
    3.21.5 unipng2hex EXAMPLE
    3.21.6 unipng2hex FILES
    3.21.7 unipng2hex SEE ALSO
    3.21.8 unipng2hex AUTHOR
    3.21.9 unipng2hex LICENSE
    3.21.10 unipng2hex BUGS


1 Introduction
**************

This document describes the process of using the GNU Unifont utilities
to create a font.  The steps described in the "Using Graphical Tools"
section in the "Tutorial" chapter are more or less the steps that I
(Paul Hardy) followed to add thousands of glyphs to GNU Unifont, except
that I didn't have the luxury of just typing `make' to make a new font
while adding those glyphs.

I streamlined the font build process after I was done drawing the
Unicode 5.1 glyphs.

I know that plain ASCII text is *so* last millennium, especially for a
package related to Unicode.  Yet ASCII can be read with anything; hence
this format.

If you have questions, please email `unifoundry@unifoundry.com'.  You
can check for the latest Unifont news at
`http://savannah.gnu.org/projects/unifont' and `http://unifoundry.com'.
You can also submit a bug report through the
`http://savannah.gnu.org/projects/unifont' page.

DISCLAIMER: Donald Knuth warned in his Metafont book that if someone
started designing type, they would never again be able to look at a
page of text normally and just read its content.  There is a point of
no return beyond which a serious font designer begins looking at how
individual letters in a font on a page are drawn, and how they might be
improved.  Be warned!

-- Paul Hardy (`unifoundry@unifoundry.com')  2008, 2013

2 Tutorial
**********

This chapter provides a step-by-step tutorial on using the Unifont
utility programs to modify a font in the GNU Unifont format.

2.1 Unicode
===========

Unicode is an international standard to encode all the world's scripts
with one universal scheme.  Unicode is the default encoding for web
pages and is gaining popularity in many other applications.  To learn
more about Unicode, look at code charts, and see the latest
developments, check out

     http://unicode.org

Unifont follows the Unicode encoding scheme.  Unicode defines the
numeric value of a character, but does not define one particular font.
There can be (and are) many fonts that support a subset of Unicode
characters.

In 1998, Roman Czyborra observed that there was still no font, free or
commercial, with complete Unicode coverage.  He envisioned a
low-quality bitmapped font as an easy way to produce a font that
covered much of the Unicode standard.

2.2 Unifont Structure
=====================

GNU Unifont is a dual-width pixel font.  Roman Czyborra began this font
in 1998 with a goal of having one glyph rendered for each visible
character in the Unicode Basic Multilingual Plane (Plane 0, the first
65,536 characters).  His original writing on this is at
`http://czyborra.com/unifont/'.

(Note that the term "character" is used very loosely here for
simplicity; the Unicode Standard has a stricter definition of what
constitutes a character.)

The font is dual-width.  Each character is 16 pixels tall, and either 8
or 16 pixels wide.  The characters are stored in a unique .hex file
format invented by Roman Czyborra as a convenient way of giving each
character exactly a one line specification.  Conversion between this
.hex format and BDF font format is trivial.

2.3 Hex File Format
===================

By convention, files containing the Unifont native font format have the
extension ".hex".  Their format is extremely simple, consisting of two
fields separated with a colon (":") and ending with a newline.

The first field is the Unicode code point, in hexadecimal.  For all
Plane 0 code points, this is a four digit hexadecimal number.
Hexadecimal digits are (in order) 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B,
C, D, E, and F.  The Unicode Standard uses a hexadecimal number to
assign each character a location.  These locations are called "code
points" and their range is 0 through 10FFFF, inclusive.

The range 0 through FFFF, inclusive, is called the Basic Multilingual
Plane (BMP), or Plane 0.  This plane contains glyphs for most of the
world's modern writing scripts.

Because the original goal of GNU Unifont was to cover the entire
Unicode Basic Multilingual Plane, a four digit hexadecimal number
suffices.  In the future, I plan to allow the utilities to go beyond
the BMP now that coverage of the Unicode BMP is finally complete.

The programs will probably handle glyphs beyond the BMP properly, but
that capability is considered experimental, as the focus was to cover
the BMP.  The C programs allow up to an eight digit hexadecimal code
point, but not all the utilities have been thoroughly tested beyond the
BMP.

The second field is a string of hexadecimal digits.  There are 32
digits for a character that is 8 pixels wide, and 64 digits for a
character that is 16 pixels wide.

The good news is you don't have to worry about these long digit
strings.  Roman Czyborra wrote a utility, `hexdraw', to convert .hex
fonts to a form that can be edited with a plain text editor, then
converted back into .hex format.

Paul Hardy wrote two utilities to do the same thing except with
bitmapped graphics images for editing with a graphics editor:
`unihex2bmp' converts a block of 256 characters into a graphics file,
and `unibmp2hex' converts such a graphics file back into .hex format.
These bitmaps display the 256 characters in a block arranged in a 16 by
16 character grid.  The graphics editor must maintain the image as a
monochrome (black and white) file, with one bit per pixel.  After
conversion from a .bmp file back to a .hex file, the next step is
conversion to a BDF font file.  A BDF file can only encode a pixel
being on or off (i.e., black or white only with no intermediate shades
of gray).

Andrew Miller later converted `unihex2bmp' and `unibmp2hex' to Perl,
then transformed them into `unihex2png' and `unipng2hex', respectively.
These programs convert Unifont .hex files to and from Portable Network
Graphics files.

2.4 Hex File Format
===================

Let's look at an example.  Suppose you want to modify the Coptic letters
in the range U+2C80..U+2CFF ("U+" is Unicode shorthand).  These letters
are in the upper half of the block U+2C00..U+2CFF.  The Unicode
utilities in this package refer to this as "page" 2C.  ("Page" is not a
Unicode term -- it is just a term unique to this package to refer to a
block of 256 code points/characters).

The steps to follow will be:

  1. Convert .hex version of the page 2C range as a 16 by 16 bitmapped
     grid.

  2. Modify the bitmap in any graphics editor, being careful to re-save
     it as a Windows Bitmap (.bmp) or Wireless Bitmap file when
     finished.

  3. Convert the modified bitmap back into a .hex font file.

  4. Merge the results with the original `unifont.hex' file (or
     whatever its name might be).

  5. Run `unidup' on the resulting file to guard against duplicate
     character definitions.

  6. Create the new bitmapped version of the font.

  7. Check the compiled font for duplicates.

  8. If there are duplicates, remove them and go back to Step 5.

  9. Create the new TrueType version or other versions of the font.


*Step 1:* Convert the .hex range into a bitmap grid.  Assuming our font
file is named `unifont.hex', type

     unihex2bmp -p2C < unifont.hex > uni2C.bmp

*Step 2:* Modify `uni2C.bmp' with your favorite graphics editor.  Note
that whatever graphics editor you use must preserve the file as a black
and white bitmap (monochrome), with one bit per pixel.  During editing,
you can draw guidelines outside the actual 16x16 font pixel area; they
will be ignored when converting back into .hex format.  You can also
erase the grid borders between code points on purpose or by accident,
and it will have no effect on the generated .hex file.  Just don't
erase the code point numbers on the outer edges of the grid.  The
conversion from .bmp back to .hex only looks at the "U+0000" in the
upper left-hand corner of the bitmap graphic and other code point
numbers, and at each code point's 16x16 pixel area inside its 32x32
pixel grid area.  Every other artifact in the final graphics file
outside these areas is ignored.

If a new version of Unicode adds glyphs to a page that were previously
unassigned, be sure to remove the newly-assigned code points from the
`unassigned.hex' file because the code point is no longer unassigned.

*Step 3:* Convert the edited .bmp file back into .hex format:

     unibmp2hex < uni2C.bmp > uni2C.hex

Note that the conversion from a bitmap image to a .hex file can't
distinguish between a legitimate single- or double-width space
character and a code point that does not have an assigned value.
Therefore, space glyphs are separately contained in the `spaces.hex'
file.

*Step 4:* Merge the results with the original `unifont.hex' file.  This
requires several sub-steps:

   * Edit the original `unifont.hex' file and delete the lines that
     begin with "2C".

   * Insert the `uni2C.hex' file into `unifont.hex', either with a text
     editor such as `emacs' or `vi', or with a GNU/Linux command such
     as:

          sort uni2C.hex unifont.hex > new-unifont.hex

     This second option (using `sort') is preferred, because `unidup'
     (in Step 5) might miss duplicate code points if your final result
     isn't in proper order.


*Step 5:* Make sure there are no duplicates with `unidup':

     unidup < unifont.hex

or

     unidup < new-unifont.hex

depending on the name of your final font file.  If there is no output,
your modified font contains no duplicates.

This editing is best done on an input .hex file, such as
`unifont-base.hex'.

*Step 6:* Create the new bitmapped version of the font.  In the `font/'
directory, type

     make hex

*Step 7:* Check the compiled font for duplicates.  Change to the
`font/compiled/' directory and run

     unidup < mynewfontfile.hex

for whatever font file you created.

*Step 8:* If there are duplicates, remove them in the `font/' directory
and go back to Step 5.

*Step 9:* Create the new TrueType version of the font and all other
bitmapped versions.  From the `font/' directory, type

     make distclean && make

Then be prepared to wait a long time unless you are using a computer
with plenty of RAM and CPU horsepower.  Your computer should have at
least 256 Megabytes of virtual memory (RAM), and at least 250 Megabytes
of free disk space.

To only create a BDF font, in the `font/' directory just type

     make bdf

To only create a BDF and PCF font, in the `font/' directory type

     make pcf

Creating a BDF font is the first step in creating a PCF font (not
counting generating the compiled master ".hex" input file).  BDF fonts
can be created just with the tools in this package.  PCF fonts are
created by running `bdftopcf' on the BDF font.  TrueType fonts require
FontForge.

The Unifont package also includes two new programs for working with
Portable Network Graphics (PNG) files instead of BMP files.  These
utilities are `unihex2png' and `unipng2hex'.  They work in a similar
manner to the corresponding programs `unihex2bmp' and `unibmp2hex',
respectively.

To use `unihex2png' instead of `unihex2bmp', continuing the example of
the Coptic script in the U+2Cxx range, type:

     unihex2png -p2C -i unifont.hex -o uni2C.png

Note that with `unihex2bmp' specifying input and output files is
optional, while with `unihex2png' they must be specified explicitly.
More specifically, `unihex2png' will read a .hex file format input from
STDIN if no "-i" argument is specified, but the name of the binary PNG
file must always be specified with the "-o" option.

Then edit the resulting PNG file to your heart's content.  When done,
convert the file back into a `unifont.hex' format file.  In this
example, type:

     unipng2hex -i uni2C.png -o uni2C.hex

Similar to `unihex2png', the binary PNG file must be specified with
"-i" but the .hex format file will be written to STDOUT if the "-o"
option is omitted.

Finally, merge  your changes in with your main .hex font file as
described previously in this section.

2.5 Using Hexdraw
=================

Roman Czyborra's original utility to edit glyphs is the `hexdraw' Perl
script.  Using the same script as in the previous chapter, Coptic, here
are the steps for modifying `unifont.hex' using `hexdraw'.

First, realize that Unifont has tens of thousands of glyphs
(characters, using the term character loosely).  In this example, out
of the tens of thousands of glyphs, we want to modify the range
U+2C80..U+2CFF (only 128 glyphs).

The range U+2C80..U+2CFF could be extracted from `unifont.hex' by using
the `egrep' utility to look for lines beginning with "2C8" through
"2CF", or that range could be isolated by copying `unifont.hex' into
another file, and deleting all lines except the desired range.

The following steps will probably minimize typographical errors, but
they aren't the only way.

  1. "Grep" the desired block of 256 glyphs (using the `grep' utility)
     and convert this into a text representation for editing.

  2. Edit the block with a text editor, such as `emacs' or `vi'.

  3. Convert the edited text file back into .hex format.

  4. Delete the edited block range from the original font file.

  5. Merge the two .hex files into one file.

  6. Check for duplicates with `unidup'.

  7. Generate new fonts as described in the "Using Graphical Tools"
     section above.


*Step 1:* Extract the desired block with `grep':

     grep "^2C" unifont.hex | hexdraw > uni2C.txt

*Step 2:* Edit `uni2C.txt' with a text editor.

*Step 3:* Convert the text file back into .hex format:

     hexdraw < uni2C.txt > uni2C.hex

*Step 4:* Delete the lines in the original `unifont.hex' file that
begin with "2C".

*Step 5:* Merge the two files:

     sort unifont.hex uni2C.hex > new-unifont.hex

or use Roman's `hexmerge' utility:

     hexmerge unifont.hex uni2C.hex > new-unifont.hex

*Step 6:* Check for duplicates:

     unidup < new-unifont.hex

Of course, remove any reported duplicates.

*Step 7:* Build the font as in the "Using Graphical Tools" section
above.  This can be as simple as typing

     make

in the `font/' directory.

I (Paul Hardy) had only used `hexdraw' in the very beginning of my work
on Unifont.  Once I got my graphics programs working, I ignored it for
months.  Then I wanted to go through all of the Yi Syllables and Yi
Radicals -- over 1000 glyphs -- to fine-tune their horizontal alignment
after I drew them.  `hexdraw' turned out to be the perfect tool for
this.  By printing hyphens ("-") as place holders where a pixel is off,
it allowed me to verify space to the left and right of each character.
I later used `hexdraw' for similar fine-tuning of spacing on Hangul and
other glyphs.  It is ideal for the task.

2.6 Checking Coverage
=====================

There should never be duplicates in a .hex file.  If there are, remove
them before the .hex font is turned into a BDF or other font file.  The
recommendations above include making liberal use of `unidup' to avoid
such a situation.

The `unipagecount' program will print a hexadecimal number of code
points that have coverage within each 256 code point block.  The
hexadecimal number will therefore range from 0 (no coverage) to 100 (=
256 decimal; full coverage).  If a number is ever more than 100
hexadecimal, there's an extra character (glyph) for that page.

To further look at the coverage within just one 256 code point page
(using page 2C, containing Coptic, as our example) use

     unipagecount -p2C < unifont.hex

Note that the "page number" can use upper- or lower-case letters:
`-p2C' or `-p2c' will both work.  That will print a 16 x 16 grid of
U+2C00..U+2CFF.  Of course, without placeholder glyphs for the
unassigned code points from `unassigned.hex' in the U+2C00..U+2CFF
range, unipagecount can give a lower number than the true coverage.

Using the `-l' flag with `unipagecount' will produce an HTML table with
links to corresponding graphics images.  You can get an idea of how
this works in the `font/compiled/' directory after running `make'; the
`index.html' file in that directory will have a table with links to the
256 glyph maps in the `font/compiled/bmp/' subdirectory.

With `unipagecount', the background color of the cells will range from
red (for 0% complete in that 256 code point block) to orange (a little
coverage) to yellow (more coverage) to green (complete coverage).  If a
cell looks light red or pink, the corresponding code page probably has
duplicate characters.  Verify that with

     sort unifont.hex | unidup

(substituting the name of your .hex file for `unifont.hex').

To see the coverage of each Unicode script, copy the file
`font/coverage.dat' into the same directory as the `unifont.hex' file
you're examining.  Then run

     unicoverage < unifont.hex > coverage.out

This will give you all the scripts within the Unicode Basic
Multilingual Plane, in order, with a percentage (0.0% through 100.0%)
of each script's coverage.  Note that to get the true coverage of
assigned code points, you'll have to merge `unassigned.hex' with the
rest of `unifont.hex' if not done by default in your setup.

Using the .hex files in `font/hexsrc/', you can create a font with all
available glyphs with

     sort font/hexsrc/*.hex >unifont-whole.hex

and run `unicoverage' using the resulting `unifont-whole.hex' file.

2.7 Custom Builds
=================

The font can be built from within the `font/' directory by simply typing

     make

From the top-level directory (one level above the `font/' directory),
typing

     make BUILDFONT=1

will also build the font.  The font is not built by default by typing
`make' from the top-level directory, because a pre-built version
already exists in the `font/precompiled/' directory.  Font files are
architecture-independent, so the only reason to build the font is if
you modify its composition.

By default, source glyphs are read from the `font/hexsrc/' directory.
Glyphs for unassigned code points are built into the font by default,
but glyphs for Private Use Area code points are not built into the font.

All of the .hex file names can be replaced selectively on the `make'
command line to override their default values.  Their locations are
relative to the `font/' directory.  The list of component hex file
variables is:

`UNIFONTBASE'
     The bulk of Unifont scripts

`CJK'
     Most of the CJK Ideographs

`HANGUL'
     Hangul Syllables block

`SPACES'
     Space glyphs, single- and double-width

`UNASSIGNED'
     Glyphs for unassigned code points

`PUA'
     Glyphs for the Private Use Area


So, for example, to build a font that includes four-digit hexadecimal
code point glyphs (as white digits on a black background) for the
Private Use Area, type

     make PUA="hexsrc/pua.hex"

because those glyphs reside in the `font/hexsrc/pua.hex' file.

To build a font that includes your own special PUA glyphs, type

     make PUA="mycoolPUA.hex"

or whatever the name of your PUA glyph .hex file is named.

To create a build that includes the supplied PUA glyphs but not the
unassigned code point glyphs, type

     make PUA="hexsrc/pua.hex" UNASSIGNED=""

If you create a custom font build of your own in one gigantic file, you
can build with just this file by declaring all the ordinary files to be
null:

     make UNIFONTBASE="mycustomfont.hex" \

     CJK="" HANGUL="" UNASSIGNED="" PUA=""

Note that this command did not include an override for the glyphs for
spaces contained in the `font/hexsrc/spaces.hex' file; that is, the
variable SPACES was not redefined on the command line.  You could also
pass the argument SPACES="", but just be aware that those spaces glyphs
are in a separate file for a reason.  When graphical (".bmp") glyph
files are converted back into hex string (".hex") format, the
`unibmp2hex' utility doesn't know if a blank glyph area is a space
glyph or not, so it doesn't encode anything.  The
`font/hexsrc/spaces.hex' file contains glyphs that are strings of 0s,
with length depending on whether the space is nominally a single- or
double-width space.  (Unifont does not distinguish between finer
spacing used in traditional typesetting, such as a thin space, en space,
em space, or quad space; all spaces are either 8 pixels wide or 16
pixels wide.)

2.8 Seeing the Big Picture (Literally!)
=======================================

The GNU Unifont 6.3 release introduced a new program, `unifontpic'.
This produces a chart of all the Basic Multilingual Plane glyphs in
Unifont.  By default the chart is arranged as a 256-by-256 glyph table.
Specifying the `-l' option produces a chart that is 16 glyphs wide by
4,096 glyphs long.  See unifontpic(1) for more information.

The "long" version, created with `unifontpic -l', only produces 16
glyphs per row.  This is more useful for scrolling through on a
computer screen.

GIMP, the GNU Image Manipulation Program, will properly display the
resulting long .bmp file (at least under GNOME), but not all graphics
utilities can.  The output file is over 65,536 pixel rows tall, which
causes problems with some graphics programs.

To generate a chart with all your glyphs in one giant `unifont.hex'
file, type the command

     unifontpic < unifont.hex > unifont.bmp

The output is a monochrome Bitmap Graphics Format (.bmp) file.  If you
prefer PNG files, use your favorite graphics program or conversion
program to convert the BMP file to a PNG file.

This utility is especially useful if you're customizing the font, for
example if adding your own Private Use Area glyphs.

The default 256-by-256 code point chart will render satisfactorily on a
sheet of paper approximately 3 feet by 3 feet (1 meter by 1 meter) at
120 dots per inch.  Thus the square format is suitable for printing.

2.9 Combining Circles
=====================

The earliest versions of Unifont (before the 5.1 release) used glyphs
that showed dashed circles for combining characters.  This is how the
glyphs appear in The Unicode Standard code charts.  In version 5.1,
Paul Hardy was able to get combining characters to appear superimposed
correctly in the TrueType version of the font.  There are no plans to
try to get combining characters to work in a BDF or PCF version owing
to the limitations of those bitmapped font formats.

With combining characters working, Paul Hardy created variations of
Unifont with and without combining circles, the idea being that the
version without combining circles would be used to create the TrueType
font.  The variation with combining circles was kept for reference.

Unifont Version 6.2 simplified the build to produce only one font
variation, without combining circles.

Unifont Version 6.3 introduced a new utility, `unigencircles', to
superimpose combining circles over glyphs with code points in a
`combining.txt' file.

The latest Unifont release contains a parallel set of font files named
`unifont_sample.*'.  These "Unifont Sample" font files contain glyphs
with combining circles where appropriate.  The "Unifont Sample" font is
therefore not intended for general-purpose writing, but only for
illustrating each individual glyph as represented in The Unicode
Standard.

To run `unigencircles', start with the file `font/ttfsrc/combining.txt'
and type a command of this form:

     unigencircles combining.txt < unifont.hex > unifont-circles.hex

where `unifont.hex' is a single file containing all the glyphs you wish
to render.  You could create such a file from the `font/' directory
with the command

     sort hexsrc/*.hex >unifont.hex

Because the output is another .hex file, you can use all Unifont
utilities with this resulting file just as you would with the .hex files
in `font/hexsrc/'.

If you want to build a font from this generated `unifont.hex' file, you
could type

     make UNIFONTBASE="unifont-circles.hex" CJK="" HANGUL="" \

     UNASSIGNED="" PUA=""

as discussed above.  In this case, if you included
`font/hexsrc/spaces.hex' in the `unifont.hex' input file, you should
also set SPACES="" on the command line so that you only read in your
final custom `unifont-circles.hex' file.

2.10 Installing Fonts on GNU/Linux
==================================

The original standard font format of Unifont was a BDF font.  The newer
PCF font format loads much faster when a program begins, and so is
preferable for installations using the X Window System and similar
environments.

Compress PCF fonts using

     gzip -9 fontname.pcf

Copy the resulting `fontname.pcf.gz' file to
`/usr/share/fonts/X11/misc/' or place in a local font directory if your
windowing software supports that (for example, `~/.fonts/').

Copy TrueType fonts to `/usr/share/fonts/truetype/' uncompressed or
place in your local font directory.  Note: on some versions of Unix,
such as Solaris, the name of the TrueType directory might be TrueType
and might be under `/usr/share/fonts/X11/' -- examine the system fonts
directories, then modify the font `make install' rule accordingly.

On most flavors of GNU/Linux with the latest `xset' utility (including
the latest Debian and Red Hat releases), the following command should
allow you to start using the font immediately:

     xset fp rehash

The safest way to make sure the system knows about the new fonts will
be to restart the X Window System or even reboot.

2.11 Creating a Brand New Font
==============================

The original tools will only produce glyphs that are 16 pixels tall, and
either 8 or 16 pixels wide.  The utilities `unihex2png', `unipng2hex',
`hexdraw', and `hex2bdf' now also support glyph heights of 24 and 32
pixels, and glyph widths of up to 32 pixels, but this is not fully
tested.  These new dimensions are currently available for experimental
use.  See the respective sections for each of these programs in the
Reference chapter of this document, or their respective man pages.

This current release is furthermore only fully tested over the Unicode
Basic Multilingual Plane (code points from U+0000 through U+FFFF, with
none above that range -- this will change in the future).  The tools
can be used to create and manipulate any bitmapped font within those
constraints.

To create a brand new font (or even to add a new script to Unifont in
the future), plan out the basic dimensions of the characters:

   * How far above the lowest pixel will the baseline appear (in other
     words, how many rows are necessary for descenders such as in the
     glyphs for `g', `q', and `y')?

   * How many pixels must be empty on top and bottom for accents (in
     other words, what will the height of capital letters be)?

   * Must glyphs be centered, left-aligned, or right-aligned?

   * For a Latin font, what will the "x-height" be (the height of a
     lower-case "x" and related letters, such as "n" and "r")?


Consistent capital heights, x-heights, descender depths, and centering
will produce a better looking font.  Look over the entire script and
plan out a template grid that is consistent for the entire script.
Then use that template for each glyph you draw for the script.

Unifont characters for the most part leave the right-most column of
pixels blank if possible for left-to-right scripts.  Centering is done
around the fourth pixel (if a glyph is eight pixels wide) or around the
eighth pixel (if a glyph is 16 pixels wide).

Experimenting and (above all) having fun with these utilities is the
best way to learn.

2.12 Updates to Unicode
=======================

If a currently unassigned code point is assigned to a character in the
future, the font can be updated as follows:

  1. Delete the code point's entry from `font/hexsrc/unassigned.hex',
     as that code point will no longer be unassigned.

  2. Determine which existing .hex file should contain the newly
     defined character (examine the files to see which one contains
     other glyphs in the script.

        * `unifont-base.hex' contains most scripts

        * `wqy.hex' contains most CJK ideographs; its name pays homage
          to the Wen Quan Yi font, the source of almost all of its
          glyphs

        * `hangul-syllables.hex' contains the Hangul Syllables block
          (U+AC00..U+D7A3); this should never have new code points
          added as it covers the fixed range of the Unicode Hangul
          Syllables block

        * `spaces.hex' contains the list of single- and double-width
          spaces


     If in doubt (for example, if a new script is added to Unicode and
     you're not sure which .hex file to augment), add the new glyphs to
     `unifont-base.hex'.

  3. Update the appropriate .hex file.

  4. Consider if `font/coverage.dat' has to be updated.  Follow its
     existing format to insert a new script, being sure to change any
     previously unassigned ranges before or after the newly added
     script.

  5. Make a new .hex version of the font, and verify that you didn't
     introduce any duplicates.

  6. Run `unipagecount' and/or `unicoverage' as described previously to
     verify that you have not mistakenly deleted any existing
     characters.


Enjoy!

3 Reference
***********

3.1 bdfimplode
==============

3.1.1 bdfimplode NAME
---------------------

bdfimplode - Convert a BDF font into GNU Unifont .hex format

3.1.2 bdfimplode SYNOPSIS
-------------------------

bdfimplode < input-font.bdf > output-font.hex

3.1.3 bdfimplode DESCRIPTION
----------------------------

bdfimplode reads a BDF font from STDOUT and writes GNU Unifont .hex
conversion of the font to STDOUT.

3.1.4 bdfimplode FILES
----------------------

*.bdf font files

3.1.5 bdfimplode SEE ALSO
-------------------------

hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1), hexmerge(1),
johab2ucs2(1), unibdf2hex(1), unibmp2hex(1), unicoverage(1), unidup(1),
unifont(5), unifontchojung(1), unifontksx(1), unifontpic(1),
unigencircles(1), unigenwidth(1), unihex2bmp(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.1.6 bdfimplode AUTHOR
-----------------------

bdfimplode was written by Roman Czyborra.

3.1.7 bdfimplode LICENSE
------------------------

bdfimplode is Copyright (C) 1998 Roman Czyborra.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.1.8 bdfimplode BUGS
---------------------

bdfimplode was written to read a BDF file created by the hex2bdf
script.  It will not properly handle other BDF files with differing
bounding boxes.

3.2 hex2bdf
===========

3.2.1 hex2bdf NAME
------------------

hex2bdf - Convert a GNU Unifont .hex file into a BDF font

3.2.2 hex2bdf SYNOPSIS
----------------------

hex2bdf < input-font.hex > output-font.bdf

3.2.3 hex2bdf DESCRIPTION
-------------------------

hex2bdf reads a sorted GNU Unifont .hex file (sorted with the Unix sort
utility) from STDIN and writes a BDF version of the font to STDOUT.

3.2.4 hex2bdf OPTIONS
---------------------

`-f "font-name"'
     Specify the target font name.  If omitted, the default font name
     "Unifont" is assigned.

`-v "font-version"'
     Specify the target font version.  If omitted, the default version
     "1.0" is assigned.

`-c "font-copyright"'
     Specify the target font copyright information.  The default is the
     null string.

`-r <pixel-rows>'
     Specify how many pixel rows tall a glyph is.  The default is the
     traditional Unifont 16 rows of pixels.  This is an addition to
     support unihex2png(1) and unipng2hex(1), which allow designing
     glyphs that are 16, 24, or 32 pixel rows tall.


3.2.5 hex2bdf EXAMPLE
---------------------

Sample usage:

     hex2bdf -f "Unifont" -c "(C) 2013..." unifont.hex > unifont.bdf


3.2.6 hex2bdf FILES
-------------------

*.hex GNU Unifont font files

3.2.7 hex2bdf SEE ALSO
----------------------

bdfimplode(1), hex2sfd(1), hexbraille(1), hexdraw(1), hexmerge(1),
johab2ucs2(1), unibdf2hex(1), unibmp2hex(1), unicoverage(1), unidup(1),
unifont(5), unifontchojung(1), unifontksx(1), unifontpic(1),
unigencircles(1), unigenwidth(1), unihex2bmp(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.2.8 hex2bdf AUTHOR
--------------------

hex2bdf was written by Roman Czyborra.

3.2.9 hex2bdf LICENSE
---------------------

hex2bdf is Copyright (C) 1998 Roman Czyborra.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.2.10 hex2bdf BUGS
-------------------

No known bugs exist.  Support for glyph heights other than 16 pixels is
brand new and has not been extensively tested.

3.3 hex2sfd
===========

3.3.1 hex2sfd NAME
------------------

hex2sfd - Convert a GNU Unifont .hex file into a FontForge .sfd format

3.3.2 hex2sfd SYNOPSIS
----------------------

hex2sfd < input-font.hex > output-font.sfd

3.3.3 hex2sfd DESCRIPTION
-------------------------

hex2sfd reads a GNU Unifont .hex file from STDIN and writes an outline
font representation in FontForge Spline Font Database (.sfd) format.
The resulting .sfd file can then be converted by FontForge into a
TrueType .ttf font.

3.3.4 hex2sfd FILES
-------------------

GNU Unifont .hex font files for input, FontForge .sfd font files for
output

3.3.5 hex2sfd SEE ALSO
----------------------

bdfimplode(1), hex2bdf(1), hexbraille(1), hexdraw(1), hexmerge(1),
johab2ucs2(1), unibdf2hex(1), unibmp2hex(1), unicoverage(1), unidup(1),
unifont(5), unifontchojung(1), unifontksx(1), unifontpic(1),
unigencircles(1), unigenwidth(1), unihex2bmp(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.3.6 hex2sfd AUTHOR
--------------------

hex2sfd was written by Luis Alejandro Gonzalez Miranda in 2005, with
modifications by Paul Hardy in 2008.

3.3.7 hex2sfd LICENSE
---------------------

hex2sfd is Copyright (C) 2005 Luis Alejandro Gonzalez Miranda, (C) 2008
Paul Hardy.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.3.8 hex2sfd BUGS
------------------

No known bugs exist.

3.4 hexbraille
==============

3.4.1 hexbraille NAME
---------------------

hexbraille - Algorithmically generate the Unicode Braille range (U+28xx)

3.4.2 hexbraille SYNOPSIS
-------------------------

hexbraille > output-font.hex

3.4.3 hexbraille DESCRIPTION
----------------------------

hexbraille generates a GNU Unifont .hex format file (written on stdout)
containing the Braille dot patterns in the Unicode range U+2800..U+28FF.

3.4.4 hexbraille FILES
----------------------

braille.hex output font files

3.4.5 hexbraille SEE ALSO
-------------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexdraw(1), hexmerge(1),
johab2ucs2(1), unibdf2hex(1), unibmp2hex(1), unicoverage(1), unidup(1),
unifont(5), unifontchojung(1), unifontksx(1), unifontpic(1),
unigencircles(1), unigenwidth(1), unihex2bmp(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.4.6 hexbraille AUTHOR
-----------------------

hexbraille was written by Roman Czyborra, who named this script
"braille.pl".  In 2003, Roman incorporated a bug fix from Dominique at
unruh.de.

3.4.7 hexbraille LICENSE
------------------------

hexbraille is Copyright (C) 1998 Roman Czyborra.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.4.8 hexbraille BUGS
---------------------

No known bugs exist.

3.5 hexdraw
===========

3.5.1 hexdraw NAME
------------------

hexdraw - Convert a GNU Unifont .hex file to and from an ASCII text file

3.5.2 hexdraw SYNOPSIS
----------------------

hexdraw < input-font.hex > output-font.txt hexdraw < input-font.txt >
output-font.hex

3.5.3 hexdraw DESCRIPTION
-------------------------

hexdraw reads a sorted GNU Unifont .hex file from STDIN and writes a two
dimensional ASCII art rendering for each glyph to STDOUT.  The output
file can be edited with any text editor, then converted back into a
.hex file.

3.5.4 hexdraw FILES
-------------------

*.hex GNU Unifont font files

3.5.5 hexdraw SEE ALSO
----------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexmerge(1),
johab2ucs2(1), unibdf2hex(1), unibmp2hex(1), unicoverage(1), unidup(1),
unifont(5), unifontchojung(1), unifontksx(1), unifontpic(1),
unigencircles(1), unigenwidth(1), unihex2bmp(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.5.6 hexdraw AUTHOR
--------------------

hexdraw was written by Roman Czyborra.

3.5.7 hexdraw LICENSE
---------------------

hexdraw is Copyright (C) 1998 Roman Czyborra.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.5.8 hexdraw BUGS
------------------

No known bugs exist.

3.6 hexmerge
============

3.6.1 hexmerge NAME
-------------------

hexmerge - Merge two or more GNU Unifont .hex font files into one

3.6.2 hexmerge SYNOPSIS
-----------------------

hexmerge input-font1.hex input-font2.hex > output-font.hex

3.6.3 hexmerge DESCRIPTION
--------------------------

hexmerge reads two or more GNU Unifont .hex files, sorts them, and
writes the combined font to stdout.

3.6.4 hexmerge FILES
--------------------

*.hex GNU Unifont font files

3.6.5 hexmerge SEE ALSO
-----------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
johab2ucs2(1), unibdf2hex(1), unibmp2hex(1), unicoverage(1), unidup(1),
unifont(5), unifontchojung(1), unifontksx(1), unifontpic(1),
unigencircles(1), unigenwidth(1), unihex2bmp(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.6.6 hexmerge AUTHOR
---------------------

hexmerge was written by Roman Czyborra.

3.6.7 hexmerge LICENSE
----------------------

hexmerge is Copyright (C) 1998 Roman Czyborra.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.6.8 hexmerge BUGS
-------------------

No known bugs exist.

3.7 johab2ucs2
==============

3.7.1 johab2ucs2 NAME
---------------------

johab2ucs2 - Convert a Johab BDF font into GNU Unifont Hangul Syllables

3.7.2 johab2ucs2 SYNOPSIS
-------------------------

johab2ucs2 < input-font.bdf > output-font.hex

3.7.3 johab2ucs2 DESCRIPTION
----------------------------

johab2ucs2 reads a Johab encoded BDF font (as used in Hanterm) from
STDIN and writes a GNU Unifont .hex file containing the Unicode Hangul
Syllables to STDOUT.

3.7.4 johab2ucs2 FILES
----------------------

*.bdf font files

3.7.5 johab2ucs2 SEE ALSO
-------------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
hexmerge(1), unibdf2hex(1), unibmp2hex(1), unicoverage(1), unidup(1),
unifont(5), unifontchojung(1), unifontksx(1), unifontpic(1),
unigencircles(1), unigenwidth(1), unihex2bmp(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.7.6 johab2ucs2 AUTHOR
-----------------------

johab2ucs2 was written in 1998 by Jungshik Shin and given to Roman
Czyborra.  Paul Hardy made some modifications and bug fixes in 2008.

3.7.7 johab2ucs2 LICENSE
------------------------

johab2ucs2 is Copyright (C) 1998 Jungshik Shin and Roman Czyborra, (C)
2008 Paul Hardy.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.7.8 johab2ucs2 BUGS
---------------------

No known bugs exist.

3.8 unibdf2hex
==============

3.8.1 unibdf2hex NAME
---------------------

unibdf2hex - Convert BDF font glyphs into Unifont .hex glyphs

3.8.2 unibdf2hex SYNOPSIS
-------------------------

unibdf2hex < input-font.bdf > output-font.hex

3.8.3 unibdf2hex DESCRIPTION
----------------------------

unibdf2hex reads a BDF font file, extracting selected code points and
printing them on stdout in Unifont .hex format.  This program was used
to extract CJK ideographs from the 16x16 version of Wen Quan Yi's BDF
font.  Currently the program is hard-coded to only extract those code
points that comprise the "wqy.hex" source font file used to build
"unifont.hex" but this source code could easily be modified.

3.8.4 unibdf2hex FILES
----------------------

*.hex GNU Unifont font files

3.8.5 unibdf2hex SEE ALSO
-------------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
hexmerge(1), johab2ucs2(1), unibmp2hex(1), unicoverage(1), unidup(1),
unifont(5), unifontchojung(1), unifontksx(1), unifontpic(1),
unigencircles(1), unigenwidth(1), unihex2bmp(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.8.6 unibdf2hex AUTHOR
-----------------------

unibdf2hex was written by Paul Hardy.

3.8.7 unibdf2hex LICENSE
------------------------

unibdf2hex is Copyright (C) 2008 Paul Hardy.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.8.8 unibdf2hex BUGS
---------------------

No known bugs exist.

3.9 unibmp2hex
==============

3.9.1 unibmp2hex NAME
---------------------

unibmp2hex - Bitmap graphics file to GNU Unifont .hex file converter

3.9.2 unibmp2hex SYNOPSIS
-------------------------

unibmp2hex [-phexpage] [-iinput_file.bmp] [-ooutput_file.hex] [-w]

3.9.3 unibmp2hex DESCRIPTION
----------------------------

unibmp2hex reads a bitmap produced by unihex2bmp before or after
editing, and converts it back into a Unifont .hex format file.  The
graphics file contains a block of 256 Unicode code points arranged in a
16 by 16 grid.  Each code point appears in a 32 by 32 pixel grid.
Characters are either 16 rows high by 8 columns, or 16 rows by 16
columns.

3.9.4 unibmp2hex OPTIONS
------------------------

`-ppagenum'
     Specify that the code points will be assigned to the 256 block
     space pagenum in the .hex file.  If not specified, unibmp2hex will
     determine the appropriate block by reading the row and column
     headers.  Note that "page" is not a standard Unicode term.  It
     refers to an output bitmap graphics page of 16 by 16 code points.
     If pagenum is greater than FF, the block resides above the Unicode
     Basic Multilingual Plane. In that event, the .hex file will contain
     eight digit hexadecimal code points rather than the Unifont
     standard of four hexadecimal code points.

`-i'
     Specify the input file. The default is STDIN.

`-o'
     Specify the output file. The default is STDOUT.

`-w'
     Force all output .hex glyphs to be 16 pixels wide rather than dual
     width (8 or 16 pixels).

     Sample usage:

          unibmp2hex -imy_input_file.bmp -omy_output_file.hex



3.9.5 unibmp2hex FILES
----------------------

*.bmp or *.wbmp graphics files

3.9.6 unibmp2hex SEE ALSO
-------------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
hexmerge(1), johab2ucs2(1), unibdf2hex(1), unicoverage(1), unidup(1),
unifont(5), unifontchojung(1), unifontksx(1), unifontpic(1),
unigencircles(1), unigenwidth(1), unihex2bmp(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.9.7 unibmp2hex AUTHOR
-----------------------

unibmp2hex was written by Paul Hardy.

3.9.8 unibmp2hex LICENSE
------------------------

unibmp2hex is Copyright (C) 2007, 2008 Paul Hardy.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.9.9 unibmp2hex BUGS
---------------------

No known real bugs exist, except that this software does not perform
extensive error checking on its input files.  If they're not in the
format of the original bitmapped output from unihex2bmp, all bets are
off.

If the output file is for a "page" containing space code points and the
bitmap file squares for those code points are not empty, unibmp2hex
preserves the graphics as they are drawn.

3.10 unicoverage
================

3.10.1 unicoverage NAME
-----------------------

unicoverage - Print coverage of each Unicode BMP Script

3.10.2 unicoverage SYNOPSIS
---------------------------

unicoverage [-iinput-file] [-ooutput-file]

3.10.3 unicoverage DESCRIPTION
------------------------------

unicoverage reads a GNU Unifont .hex font and uses data in coverage.dat
(which must reside in the current directory).  The output is the
percent coverage of each script in the Unicode Basic Multilingual Plane.

3.10.4 unicoverage OPTIONS
--------------------------

`-i'
     Specify the input file. The default is STDIN.

`-o'
     Specify the output file. The default is STDOUT.  Sample usage:

          unicoverage < unifont.hex >coverage.txt



3.10.5 unicoverage FILES
------------------------

coverage.dat, *.hex GNU Unifont files.

3.10.6 unicoverage SEE ALSO
---------------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
hexmerge(1), johab2ucs2(1), unibdf2hex(1), unibmp2hex(1), unidup(1),
unifont(5), unifontchojung(1), unifontksx(1), unifontpic(1),
unigencircles(1), unigenwidth(1), unihex2bmp(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.10.7 unicoverage AUTHOR
-------------------------

unicoverage was written by Paul Hardy.

3.10.8 unicoverage LICENSE
--------------------------

unicoverage is Copyright (C) 2007, 2008 Paul Hardy.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.10.9 unicoverage BUGS
-----------------------

No known real bugs exist, except that this software does not perform
extensive error checking on its input files.

3.11 unidup
===========

3.11.1 unidup NAME
------------------

unidup - Scan through a sorted .hex file and report duplicate code
points

3.11.2 unidup SYNOPSIS
----------------------

unidup [ input-font.hex ]

3.11.3 unidup DESCRIPTION
-------------------------

unidup reads a sorted GNU Unifont .hex file (sorted with the Unix sort
utility) and prints notification of any duplicate code points on stdout.
The input file can be specified on the command line.  If no file is
specified, input will be read from STDIN until end of file.

3.11.4 unidup FILES
-------------------

*.hex GNU Unifont font files

3.11.5 unidup SEE ALSO
----------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
hexmerge(1), johab2ucs2(1), unibdf2hex(1), unibmp2hex(1),
unicoverage(1), unifont(5), unifontchojung(1), unifontksx(1),
unifontpic(1), unigencircles(1), unigenwidth(1), unihex2bmp(1),
unihex2png(1), unihexgen(1), unipagecount(1), unipng2hex(1)

3.11.6 unidup AUTHOR
--------------------

unidup was written by Paul Hardy.

3.11.7 unidup LICENSE
---------------------

unidup is Copyright (C) 2007, 2013 Paul Hardy.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.11.8 unidup BUGS
------------------

No known bugs exist.

3.12 unifontchojung
===================

3.12.1 unifontchojung NAME
--------------------------

unifontchojung - Extract Hangul syllables that have no final consonant

3.12.2 unifontchojung SYNOPSIS
------------------------------

unifontchojung < input-font.hex > output-font.hex

3.12.3 unifontchojung DESCRIPTION
---------------------------------

unifontchojung reads a Unifont-format .hex font file from STDIN and
writes a Unifont .hex file containing a subset to STDOUT.  The subset
that is output only contains syllables that contain an initial
consonant (chojung) plus middle vowel (jungseong), with no final
consonant (jongseong).  This lets a font designer focus on this subset
during font creation.

3.12.4 unifontchojung FILES
---------------------------

*.bdf font files

3.12.5 unifontchojung SEE ALSO
------------------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
hexmerge(1), johab2ucs2(1), unibdf2hex(1), unibmp2hex(1),
unicoverage(1), unidup(1), unifont(5), unifontksx(1), unifontpic(1),
unigencircles(1), unigenwidth(1), unihex2bmp(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.12.6 unifontchojung AUTHOR
----------------------------

unifontchojung was written by Paul Hardy.

3.12.7 unifontchojung LICENSE
-----------------------------

unifontchojung is Copyright (C) 2012 Paul Hardy.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.12.8 unifontchojung BUGS
--------------------------

No known bugs exist.

3.13 unifontksx
===============

3.13.1 unifontksx NAME
----------------------

unifontksx - Extract Hangul syllables that comprise KS X 1001:1992

3.13.2 unifontksx SYNOPSIS
--------------------------

unifontksx < input-font.hex > output-font.hex

3.13.3 unifontksx DESCRIPTION
-----------------------------

unifontksx reads a Unifont-format .hex font file from STDIN and writes
a Unifont .hex file containing a subset to STDOUT.  The subset that is
output only contains the 2,350 syllables that comprise Korean Standard
KS X 1001:1992.  These are extracted from the Unicode Hangul Syllables
block, U+AC00..U+D7A3.  This lets a font designer focus on those
syllables that are most common in modern Hangul usage during font
development.

3.13.4 unifontksx FILES
-----------------------

*.bdf font files

3.13.5 unifontksx SEE ALSO
--------------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
hexmerge(1), johab2ucs2(1), unibdf2hex(1), unibmp2hex(1),
unicoverage(1), unidup(1), unifont(5), unifontchojung(1), unifontpic(1),
unigencircles(1), unigenwidth(1), unihex2bmp(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.13.6 unifontksx AUTHOR
------------------------

unifontksx was written by Paul Hardy.

3.13.7 unifontksx LICENSE
-------------------------

unifontksx is Copyright (C) 2012 Paul Hardy.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.13.8 unifontksx BUGS
----------------------

No known bugs exist.

3.14 unifontpic
===============

3.14.1 unifontpic NAME
----------------------

unifontpic - Convert GNU Unifont .hex input to a bitmap image of the
whole font

3.14.2 unifontpic SYNOPSIS
--------------------------

unifontpic [-dnnn][-l][-t] < input-font.hex > output-font.bmp

3.14.3 unifontpic DESCRIPTION
-----------------------------

unifontpic reads a GNU Unifont .hex file from STDIN and writes a two
dimensional rendering for each glyph to STDOUT.  The output displays
the entire Unicode Basic Multilingual Plane (BMP) as one large graphic
image, showing a grid of 256 glyphs by 256 glyphs as the default, or
(at your option) 16 glyphs across by 4,096 glyphs down.

Input can be one or more files in Unifont .hex format.  They don't have
to be sorted, as unifontpic will populate the entire glyph array of
65,536 code points before writing its output.  The input glyph code
points should all be unique, as feeding in duplicate code points will
produce unpredictable results.  Use unidup (1) on a sorted input of
.hex files to guarantee no code point duplication.

3.14.4 unifontpic OPTIONS
-------------------------

`-dnnn'
     Specify a Dots per Inch (DPI) resolution of nnn.  For example,
     specifying -d120 will encode the bitmap graphics file output as
     having a resolution of 120 DPI.

`-l'
     Produce a long chart, 16 glyphs wide by 4,096 glyphs tall.  The
     default is a wide chart, 256 glyphs wide by 256 glyphs tall.

`-t'
     Use tiny numbers for the row and column code point labels.  Tiny
     numbers are on a 4 by 5 pixel grid.  Only tiny code point labels
     appear on the long chart variant; this option only has effect for
     wide charts (the default, of 256 by 256 glyphs).  If this option
     is not specified for the default 256-by-256 grid, row and column
     code point labels are taken from Unifont's glyphs for `0' to `9'
     and `A' to `F'.


3.14.5 unifontpic EXAMPLES
--------------------------

Sample usage:

     cat *.hex | unifontpic -d120 > unifontpic.bmp


To generate a bitmap that shows combining circles, from the font/
subdirectory:

     sort hexsrc/*.hex | unigencircles ttfsrc/combining.txt |
     unifontpic -d120 >unifontpic.bmp


3.14.6 unifontpic FILES
-----------------------

*.hex GNU Unifont font files

3.14.7 unifontpic SEE ALSO
--------------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
hexmerge(1), johab2ucs2(1), unibdf2hex(1), unibmp2hex(1),
unicoverage(1), unidup(1), unifont(5), unifontchojung(1), unifontksx(1),
unigencircles(1), unigenwidth(1), unihex2bmp(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.14.8 unifontpic AUTHOR
------------------------

unifontpic was written by Paul Hardy.

3.14.9 unifontpic LICENSE
-------------------------

unifontpic is Copyright (C) 2013 Paul Hardy.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.14.10 unifontpic BUGS
-----------------------

No known bugs exist.

3.15 unigencircles
==================

3.15.1 unigencircles NAME
-------------------------

unigencircles - Add dashed combining circles to a unifont.hex file

3.15.2 unigencircles SYNOPSIS
-----------------------------

unigencircles combining.txt nonprinting.hex < unifont.hex >
unifont-circles.hex

3.15.3 unigencircles DESCRIPTION
--------------------------------

unigencircles reads a unifont.hex file from STDIN, adds dashed combining
circles to the hex strings for code points listed in "combining.txt"
but not listed in "nonprinting.hex", and writes the revised set of
glyphs in unifont.hex format to STDOUT.  The resulting combining
character glyphs show the dashed combining circles that appear in The
Unicode Standard code charts.

For each code point listed in the "combining.txt" file but not listed
in the "nonprinting.hex" file, unigencircles will superimpose a
single-width dashed circle in glyphs that are single-width (i.e., their
hex glyph strings are 32 characters long) and will superimpose a
double-width dashed circle in glyphs that are double-width (i.e., their
hex glyph strings are 64 characters long).

3.15.4 unigencircles EXAMPLE
----------------------------

     unigencircles combining.txt nonprinting.hex < unifont.hex >
     unifont-circles.hex


3.15.5 unigencircles FILES
--------------------------

*.hex files for Unifont glyph data

font/ttfsrc/combining.txt for combining code points

font/hexsrc/nonprinting.hex for non-printing code points

3.15.6 unigencircles SEE ALSO
-----------------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
hexmerge(1), johab2ucs2(1), unibdf2hex(1), unibmp2hex(1),
unicoverage(1), unidup(1), unifont(5), unifontchojung(1), unifontksx(1),
unifontpic(1), unigenwidth(1), unihex2bmp(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.15.7 unigencircles AUTHOR
---------------------------

unigencircles was written by Paul Hardy.

3.15.8 unigencircles LICENSE
----------------------------

unigencircles is Copyright (C) 2013 Paul Hardy.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.15.9 unigencircles BUGS
-------------------------

No known real bugs exist, except that this software does not perform
extensive error checking on its input files.

3.16 unigenwidth
================

3.16.1 unigenwidth NAME
-----------------------

unigenwidth - Generate C code for POSIX wcwidth and wcswidth functions

3.16.2 unigenwidth SYNOPSIS
---------------------------

unigenwidth unifont.hex combining.txt

3.16.3 unigenwidth DESCRIPTION
------------------------------

unigenwidth reads a collection of glyphs in Unifont's .hex format, then
reads a list of combining characters as a hexadecimal list.  From these
two files, it produces C code to implement the POSIX wcwidth(3) and
wcswidth(3) functions.  The format of these definitions is based upon
POSIX 1003.1-2008 System Interfaces, pages 2251 and 2241, respectively.

3.16.4 unigenwidth EXAMPLE
--------------------------

Sample usage:

     unigenwidth unifont.hex combining.txt > wccode.c


3.16.5 unigenwidth FILES
------------------------

*.hex files for Unifont glyph data; combining.txt for combining code
points.

3.16.6 unigenwidth SEE ALSO
---------------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
hexmerge(1), johab2ucs2(1), unibdf2hex(1), unibmp2hex(1),
unicoverage(1), unidup(1), unifont(5), unifontchojung(1), unifontksx(1),
unifontpic(1), unigencircles(1), unihex2bmp(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.16.7 unigenwidth AUTHOR
-------------------------

unigenwidth was written by Paul Hardy.

3.16.8 unigenwidth LICENSE
--------------------------

unigenwidth is Copyright (C) 2013 Paul Hardy.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.16.9 unigenwidth BUGS
-----------------------

No known real bugs exist, except that this software does not perform
extensive error checking on its input files.

3.17 unihex2bmp
===============

3.17.1 unihex2bmp NAME
----------------------

unihex2bmp - GNU Unifont .hex file to bitmap graphics file converter

3.17.2 unihex2bmp SYNOPSIS
--------------------------

unihex2bmp [-phexpage] [-iinput_file.hex] [-ooutput_file.bmp] [-f] [-w]

3.17.3 unihex2bmp DESCRIPTION
-----------------------------

unihex2bmp reads a GNU Unifont .hex file Unicode page of 256 code points
and converts the page into a Microsoft Windows Bitmap (.bmp) or
Wireless Bitmap (.wbmp) file.  The bitmap file displays the glyphs of a
Unicode block of 256 code points in a 32 by 32 pixel grid.  The glyphs
themselves must be 16 rows high, and either 8 columns or 16 columns
wide. The default page is 0; that is, the range U+0000 through U+00FF.

The bitmap can be printed.  It can also be edited with a bitmap editor.
An edited bitmap can then be re-converted into a GNU Unifont .hex file
with the unibmp2hex command.

3.17.4 unihex2bmp OPTIONS
-------------------------

`-ppagenum'
     Extract page pagenum from the .hex file.  The default is Page 0
     (Unicode range U+0000 through U+00FF).  Note that "page" is not a
     standard Unicode term.  It refers to an output bitmap graphics
     page of 16 by 16 code points.

`-i'
     Specify the input file. The default is STDIN.

`-o'
     Specify the output file. The default is STDOUT.

`-f'
     "Flip" (transpose) the grid so it matches the Unicode standard
     order.

`-w'
     Produce a Wireless Bitmap format file instead of a Microsoft
     Windows Bitmap file.

     Sample usage:

          unihex2bmp -imy_input_file.hex -omy_output_file.bmp



3.17.5 unihex2bmp FILES
-----------------------

*.hex GNU Unifont font files

3.17.6 unihex2bmp SEE ALSO
--------------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
hexmerge(1), johab2ucs2(1), unibdf2hex(1), unibmp2hex(1),
unicoverage(1), unidup(1), unifont(5), unifontchojung(1), unifontksx(1),
unifontpic(1), unigencircles(1), unigenwidth(1), unihex2png(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.17.7 unihex2bmp AUTHOR
------------------------

unihex2bmp was written by Paul Hardy.

3.17.8 unihex2bmp LICENSE
-------------------------

unihex2bmp is Copyright (C) 2007 Paul Hardy.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.17.9 unihex2bmp BUGS
----------------------

No known real bugs exist, except that this software does not perform
extensive error checking on its input files.  If they're not in the
format of the original GNU Unifont .hex file, all bets are off.  Lines
can be terminated either with line feed, or carriage return plus line
feed.

3.18 unihex2png
===============

3.18.1 unihex2png NAME
----------------------

unihex2png - GNU Unifont .hex file to Portable Network Graphics
converter

3.18.2 unihex2png SYNOPSIS
--------------------------

unihex2png [-i input_file.hex ] -o output_file.png [-p pagenum ] [-r
rows ]

3.18.3 unihex2png DESCRIPTION
-----------------------------

unihex2png reads a page of 256 Unicode code points from a GNU Unifont
.hex file and converts the page into a Portable Network Graphics (PNG)
file.  The graphics file displays the glyphs of a Unicode block of 256
code points in a 32 by 32 pixel grid, or in a 40 by 40 pixel grid if
"-r 32" is specified.  The glyphs themselves can be either 16, 24, or
32 pixels tall depending on the "-r" parameter.  They can be 8, 16, 24,
or 32 pixels wide (widths of 32 are only supported if "-r 32" is
specified).  The default page is 0; that is, the range U+0000 through
U+00FF, inclusive.

The PNG file can be printed.  It can also be edited with a graphics
editor.  An edited PNG file can then be re-converted into a GNU Unifont
.hex file with the unipng2hex command.

3.18.4 unihex2png OPTIONS
-------------------------

`-i'
     Specify the input file.  If not omitted, a Unifont .hex file is
     read from STDIN.

`-o'
     Specify the output file.

`-p pagenum'
     Extract page pagenum from the .hex file.  The default is Page 0
     (Unicode range U+0000 through U+00FF).  Note that "page" is not a
     standard Unicode term.  It refers to an output bitmap graphics
     page of 16 by 16 code points.

`-r rows'
     Specify the rows of pixels in the output glyphs.  Valid values are
     16, 24, and 32.  The default is 16 pixel rows tall.

`-h'
     Print a help message of options and exit.


3.18.5 unihex2png EXAMPLE
-------------------------

Sample usage:

     unihex2png -i my_input_file.hex -o my_output_file.png


3.18.6 unihex2png FILES
-----------------------

*.hex GNU Unifont font files

3.18.7 unihex2png SEE ALSO
--------------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
hexmerge(1), johab2ucs2(1), unibdf2hex(1), unibmp2hex(1),
unicoverage(1), unidup(1), unifont(5), unifontchojung(1), unifontksx(1),
unifontpic(1), unigencircles(1), unigenwidth(1), unihex2bmp(1),
unihexgen(1), unipagecount(1), unipng2hex(1)

3.18.8 unihex2png AUTHOR
------------------------

unihex2png was written by Andrew Miller, starting by converting Paul
Hardy's unihex2bmp C program to Perl.

3.18.9 unihex2png LICENSE
-------------------------

unihex2png is Copyright (C) 2007 Paul Hardy, (C) 2013 Andrew Miller.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.18.10 unihex2png BUGS
-----------------------

No known real bugs exist, but the optional pixel rows parameter is not
yet supported by all other Unifont utilities.  Use of glyphs taller than
the default of 16 pixels is considered experimental.  Currently
unihex2png, unipng2hex, hexdraw, and hex2bdf tentatively support glyphs
that are 16, 24, and 32 pixels tall.

Also, there is no extensive error checking on input files.  If they're
not in the format of the original GNU Unifont .hex file, all bets are
off.  Lines can be terminated either with line feed, or carriage return
plus line feed.

3.19 unihexgen
==============

3.19.1 unihexgen NAME
---------------------

unihexgen - Generate Unifont 4- or 6-digit hexadecimal glyphs

3.19.2 unihexgen SYNOPSIS
-------------------------

unihexgen startpoint endpoint

3.19.3 unihexgen DESCRIPTION
----------------------------

unihexgen produces unifont.hex entries in the Unicode code point range
startpoint to endpoint (specified as the two command-line arguments).
Output is to STDOUT.  If a codepoint is less than or equal to "FFFF"
(i.e., 0xFFFF), a four-digit hexadecimal number is encoded within the
corresponding Unifont glyph as two digits on each of two rows.
Otherwise, a six-digit hexadecimal number is encoded as three digits on
each of two rows.

3.19.4 unihexgen OPTIONS
------------------------

There are no options.

3.19.5 unihexgen FILES
----------------------

*.hex as output.

3.19.6 unihexgen EXAMPLE
------------------------

To generate the Private Use Area glyphs in the Unicode range
U+E000..U+F8FF, invoke unihexgen with these arguments:

     unihexgen e000 f8ff


3.19.7 unihexgen SEE ALSO
-------------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
hexmerge(1), johab2ucs2(1), unibdf2hex(1), unibmp2hex(1),
unicoverage(1), unidup(1), unifont(5), unifontchojung(1), unifontksx(1),
unifontpic(1), unigencircles(1), unigenwidth(1), unihex2bmp(1),
unihex2png(1), unipagecount(1), unipng2hex(1)

3.19.8 unihexgen AUTHOR
-----------------------

unihexgen was written by Paul Hardy.

3.19.9 unihexgen LICENSE
------------------------

unihexgen is Copyright (C) 2013 Paul Hardy.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.19.10 unihexgen BUGS
----------------------

No known real bugs exist, except that this software does not perform
extensive error checking on its command-line arguments.  If they're not
in the format of the original bitmapped output from unihexgen, all bets
are off.

3.20 unipagecount
=================

3.20.1 unipagecount NAME
------------------------

unipagecount - Count the assigned code points in a GNU Unifont .hex file

3.20.2 unipagecount SYNOPSIS
----------------------------

unipagecount [-ppagenum] [-h|-l]

3.20.3 unipagecount DESCRIPTION
-------------------------------

unipagecount reads a GNU Unifont .hex file from STDIN and prints a 16
by 16 grid of the number of defined code points in each 256 character
block to STDOUT.  Code points proceed from left to right, then top to
bottom.

3.20.4 unipagecount OPTIONS
---------------------------

`-ppagenum'
     Just print information on one 256 code point "page" rather than
     the entire Basic Multilingual Plane.  This prints a 16 by 16 table
     with an asterisk in every code point that has an assigned glyph.

`-h'
     Print an HTML table with color-coded cell background colors
     instead of a plain text table.

`-l'
     [The letter "l"]: Print hyperlinks to font bitmaps in the HTML
     table.  To create the bitmaps themselves, use the unihex2bmp
     program.  The bitmaps are assumed to be in the directory "bmp/".


3.20.5 unipagecount FILES
-------------------------

*.hex GNU Unifont font files

3.20.6 unipagecount SEE ALSO
----------------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
hexmerge(1), johab2ucs2(1), unibdf2hex(1), unibmp2hex(1),
unicoverage(1), unidup(1), unifont(5), unifontchojung(1), unifontksx(1),
unifontpic(1), unigencircles(1), unigenwidth(1), unihex2bmp(1),
unihex2png(1), unihexgen(1), unipng2hex(1)

3.20.7 unipagecount AUTHOR
--------------------------

unipagecount was written by Paul Hardy.

3.20.8 unipagecount LICENSE
---------------------------

unipagecount is Copyright (C) 2007 Paul Hardy.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.20.9 unipagecount BUGS
------------------------

No known real bugs exist, except that this software does not perform
extensive error checking on its input files.  If they're not in the
format of the original GNU Unifont .hex file, all bets are off.

3.21 unipng2hex
===============

3.21.1 unipng2hex NAME
----------------------

unipng2hex - Portable Network Graphics to GNU Unifont .hex file
converter

3.21.2 unipng2hex SYNOPSIS
--------------------------

unipng2hex -i input_file.png [-o output_file.hex ] [-w width ]

3.21.3 unipng2hex DESCRIPTION
-----------------------------

unipng2hex reads a PNG file produced by unihex2png before or after
editing, and converts it back into a Unifont .hex format file.  The PNG
file contains a block of 256 Unicode code points arranged in a 16 by 16
grid.  Each code point appears in a 32 by 32 or a 40 by 40 pixel grid.
Characters are either 16, 24 or 32 pixel rows high, depending on the
"-r" parameter specified by unihex2png.  They can be 8, 16, 24, or 32
pixel columns wide (widths of 32 are only supported for 32 pixel row
tall characters).

3.21.4 unipng2hex OPTIONS
-------------------------

`-i'
     Specify the input file.

`-o'
     Specify the output file.  If omitted, a file in the Unifont .hex
     format is written to STDOUT.

`-w width'
     Specify the minimum width of the output glyphs.  Valid values are
     16, 24,  and 32.  The default is no minimum width.

`-h'
     Print a help message of options and exit.


3.21.5 unipng2hex EXAMPLE
-------------------------

Sample usage:

     unipng2hex -i my_input_file.png -o my_output_file.hex


3.21.6 unipng2hex FILES
-----------------------

*.png graphics files

3.21.7 unipng2hex SEE ALSO
--------------------------

bdfimplode(1), hex2bdf(1), hex2sfd(1), hexbraille(1), hexdraw(1),
hexmerge(1), johab2ucs2(1), unibdf2hex(1), unibmp2hex(1),
unicoverage(1), unidup(1), unifont(5), unifontchojung(1), unifontksx(1),
unifontpic(1), unigencircles(1), unigenwidth(1), unihex2bmp(1),
unihex2png(1), unihexgen(1), unipagecount(1)

3.21.8 unipng2hex AUTHOR
------------------------

unipng2hex was written by Andrew Miller, starting by converting Paul
Hardy's unibmp2hex C program to Perl.

3.21.9 unipng2hex LICENSE
-------------------------

unipng2hex is Copyright (C) 2007, 2008 Paul Hardy, (C) 2013 Andrew
Miller.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

3.21.10 unipng2hex BUGS
-----------------------

No known real bugs exist, but the optional pixel rows parameter is not
yet supported by all other Unifont utilities.  Use of glyphs taller than
the default of 16 pixels is considered experimental.  Currently
unihex2png, unipng2hex, hexdraw, and hex2bdf tentatively support glyphs
that are 16, 24, and 32 pixels tall.

Also, this software does not perform extensive error checking on its
input files.  If they're not in the format of the original PNG output
from unihex2png, all bets are off.

If the output file is for a "page" containing space code points and the
PNG file squares for those code points are not empty, unipng2hex
preserves the graphics as they are drawn.

unipng2hex is designed to work with black and white pixels; do not use
other colors.

