Thursday 29 September 2016

Some remarks about Unicode Hieroglyphic fonts

Some topics are so well known that often they are not even mentioned. This post is about one such topic namely that there are many modern fonts on computers and other digital devices so a writer or publisher needs to choose one or more that work for a specific purpose. Choose the wrong font for your content and the result will be be missing or unsatisfactory characters. This is true for hieroglyphic like every other writing system,

Currently all Unicode Egyptian Hieroglyphic font releases I know of implement the whole Unicode Standard (2009) basic repertoire of 1071 hieroglyphs. There are no subset fonts for specific purposes such as early school education where two hundred signs would be more than adequate. So right now we don't see missing characters or need to take a variety of fonts into account to a great extent.

With ongoing work to extend the Unicode repertoire and include quadrat shaping to make an actual writing system, this situation will likely change considerably. A font designer concerned with the classical phase of the writing system will not want to spend months or years dealing with thousands of specialist hieroglyphs attested only from the Ptolemaic period. A font designed to work well for Ramesside hieratic transcription into hieroglyphic cannot be expected to optimise quadrat arrangements irrelevant to hieratic. A font optimised for small print (e.g. 12pt - 18pt) may make different design choices for glyphs and quadrat shaping than one optimised for 24pt plus).

Furthermore decorative colour fonts are now possible using OpenType but such fonts may be limited in scope to specific purposes.

In short, over time we can expect a wide range of hieroglyphic fonts will evolve. As with modern writing systems. Some aspiring to beauty, others providing specialist functionality. Their scope of use will often be different.

First generation digital hieroglyphic systems (typically using one or another form of Manuel de Codage aka MdC coding), mask these issues. Specialist hieroglyphic software to date typically uses a single 'one size fits all' font such as a Gardiner or Hierogyphica derivation with a single fixed method of arranging hieroglyphs in quadrats. New thinking is needed to embrace a rich world of multiple fonts and take advantage of the Unicode principle of separating plain text encoding data from the fonts used to render the text.

Some of the difficulties in gaining consensus on next steps for Unicode appear to be grounded in the mistaken notion that Unicode should be used in exactly the same way as MdC practice as if the goal were a single Unicode hieroglyphic font that does everything an Egyptologist could ever ask for. There is room for a general purpose font or two - a fallback font - but it should be understood its a small part of the story for many purposes,

One practical consequence of font diversity is Unicode hieroglyphic in plain text can expect to show an 'unsupported character' glyph when displayed using a font that does not support the writers intent. Likewise a quadrat control character sequence will have visible control characters for quadrats the font does not support and might look like:

(actually all quadrats in this specific illustration will likely be fine in most fonts but it illustrates the principle).

This is no different to the situation with Unicode in many disciplines. Mathematical typesetting is a good complex example but even simple examples are commonplace in everyday life if you read beyond a-z. The solution is to understand what you are doing and use appropriate fonts, formats, and software tools for the task in hand. If specific fonts don't do the job you simply don't use them.

Like many concepts this topic will be trivial to understand once hieroglyphic is available for use as a writing system and multiple fonts are released. For now it needs a little imagination.

Historical note

As far as I know (and someone correct me if I am wrong!) the first hieroglyphic typeface was that used in the hieroglyphic dictionary and grammar of Samuel Birch, published in 1867. Next year, we can celebrate 150 years of hieroglyphs in print.

Facsimiles of typeface used in Samuel Birch's' Grammar and Dictionary from 1867. 

The Gardiner/Oxford metal typeface was cut around 60 years after Birch/Bonomi/Longman and several other fonts made and used during the intervening years. Lepsius/Theinhardt is probably the best known of these. The usual MdC situation with a single all-purpose font has a long tradition in print.

It is only recently that we are starting to see richer use of multiple fonts. A good example is Middle Egyptian Literature (James Allen, 2015) which makes effective use of a distinctive bold face.

Distinctive bold font in Middle Egyptian Literature (2015)

I expect we'll see many more innovations once the additions to Unicode are available and supported. We are approaching the beginning of a new era.


Bob Richmond

Monday 26 September 2016

Unicode Hieroglyphs in web browsers: Web Fonts

I outlined the situation with hieroglyphic for general purpose web pages in an earlier post Unicode Hieroglyphs in web browsers: generic web pages. This note outlines another way of presenting Unicode hieroglyphs on a web page designed for Egyptian.

Web fonts are fonts that are requested by web pages for download (if necessary) for use on the web page. WOFF (the Web Open Font Format [Wikipedia]) is the international standard for packaging web fonts. All popular browsers have supported WOFF since 2010. Browsers may still support older schemes for 'font embedding' for compatibility issues with old web pages but for the vast majority of web sites WOFF should be used and the older schemes avoided.

Web fonts are especially useful for web pages that want to make use of specialist writing systems without having to rely on the writing system being fully supported on your device in order to read the page. They are therefore potentially useful for Egyptian Hieroglyphic in Unicode.

Some useful points to be aware of.

  • Web fonts are compressed and usually 'cached' on the local device so they need not be downloaded each time they are used. This is especially useful and efficient for mobile devices.
  • Browser software usually needs to be enhanced every time the Unicode standard is updated as relates to a specific writing system. This will affect progress during introduction of the hieroglyphic writing system.
  • Services such as Google Fonts can supply identical fonts to a wide range of web sites. Google Fonts is easy for web site developers to use, and only a single copy of the font needs to be downloaded for sharing among sites that use it. For Egyptian Hieroglyphs the recent delays in Unicode standardisation and the cost of creation and release of suitable Google Fonts means this route will probably be impractical for some time unless there is adequate support for the process.
  • Fonts can be provided on an individual site basis. This is the short term approach to be adopted for the Hieroglyphs Everywhere Project web site which also hopes to provide the tools to enable other sites to do the same once the Unicode standard is updated. The same approach could be adopted for a large web site such as Wikipedia.
  • If you copy hieroglyphic from a web page that uses a web font to another application (or web page), that application (or web page) will need to have access to the same (or similar) font in order to gain a satisfactory result. This is no different to any writing system but less obvious in the well-supported systems such as the Latin-based scripts used for English and other popular languages . 

Much can be said on technical aspects of web fonts so I'll likely return to the topic when there is more use of Egyptian Hieroglyphic in Unicode on the web.

In order to set the ball rolling on hieroglyphic web fonts I've created a Browser Test Page for Hieroglyphic in Unicode development. This page uses a web font with a feature to get around the fact that the hieroglyphic writing system is not yet available in Unicode (we have 1071 hieroglyphs but control characters for quadrat arrangements are still being delayed). You can use the page to confirm your web-browser is working correctly. (If there are problems on specific devices I'd like to hear about them so this can be resolved or documented to inform others in a similar situation. Thanks.)

Bob Richmond