TrueType font for Egyptian hieroglyphs from
Unicode proposal N3349
This font contains the 1071 glyphs from 0x13000 to 0x1342E,
forming the section from
that deals with Egyptian Hieroglyphs.
(There is further information about the glyphs.)
The name indicates that the font does not have
the pretence to offer much more than the shapes of the font used by
Gardiner in his grammar and in supplementary documents,
while it is 'new' in the sense of being somewhat more streamlined
The font was explicitly designed for use on a computer screen, and
consequently the lines are thicker than in some other hieroglyphic fonts.
It is also suitable for hieroglyphic text on paper however.
A detailed list of justifications for the design of
individual glyphs, including the choices of their dimensions,
The font is available in two versions. In the first, the code points
are as prescribed in Unicode, from 0x13000 to 0x1342E (in the SMP).
In the second, the code points were transposed to 0xE000 to 0xE42E
(in the Private Use Area of BMP).
This was in order to accommodate for legacy software that cannot
handle character codes of more than 2 bytes.
The zip file (approx. 1.0 MB) includes:
- NewGardiner.pdf: PDF file with printed glyphs
- NewGardinerSMP.ttf: TrueType font (SMP)
- NewGardinerBMP.ttf: TrueType font (BMP)
- NewGardiner.txt: Plain-text mapping from Gardiner names to code points in BMP
- OFL.txt: OFL 1.1 license
- OFL-FAQ.txt: OFL FAQ
- FONTLOG.txt: Basic information about font
Version 2.06 (2021-01-07):
- Redrew B005A.
- Improved G053.
Version 2.05 (2020-11-09):
Version 2.04 (2020-07-09):
- Improved A042A to show scepter more clearly.
Version 2.03 (2014-05-25):
- Improved R027, R028.
- As work-around for another bug in TextLayout.getBounds()
introduced with Java 1.7, some lines were redrawn in B001, B002, B005 and E003.
Version 2.02 (2012-08-08):
- Improved A021, C011, P008, P009.
Version 2.01 (2012-05-10):
- As work-around for a bug in TextLayout.getBounds()
in Java on (some versions of) Mac OS X,
which sometimes gives the wrong x-value,
all glyphs are moved to x=0.
Version 2.00 (2009-12-30):
- Categories A, B, C completely redesigned to be more uniform.
Version 1.01 (2009-01-08):
- Adobe Reader complained about bad widths in font. Now corrected.
Version 1.00 (2009-01-07):
Can I use this font, and if so how?
See the enclosed OFL 1.1 license.
How do you feel about extending the font with new signs?
If there is a systematic way to do it, fine, otherwise I don't
see the point. What is needed is that the Egyptological community
gets organised and assigns responsible people to maintain
a list of candidate signs to be added to the list from the Unicode proposal,
by clear and well-founded principles,
avoiding proliferation of trivial variant signs, combined signs
and such lunacy. The emphasis should be on keeping
the number of code points down.
The motto 'the more the better' leads to unavoidable disaster.
How did you create this font?
I load the font in Word and nothing happens. Why?
What did you expect? That English text is magically translated
into Ancient Egyptian? Some additional tool is needed to format
hieroglyphic encoding into an image. See for example
RES in Latex and
Use of NewGardiner with Unicode control characters
Comprehensive and elegant font.
It includes a section compatible with the Unicode proposal.
For convenience, I have rescaled the glyphs of that section, and moved the code points
to match the NewGardiner font in the Private Use Area of BMP:
- JSeshFont: Unicode font in JSesh