The use of Unicode is rightly commonplace as a character encoding for electronic documents. While the choice to use Unicode is beneficial, there are many contexts in which there are valid needs for characters and glyphs not represented in Unicode. The nature of medieval manuscripts and their descriptions entails a requirement for non-standard characters.
There are a number of clear recommendations that come out of the use of Unicode and nonstandard characters in the ENRICH project:
- Wherever possible projects should use a Unicode character encoding such as UTF-8.
- Projects needing to reference or record non-standard characters should in preference adopt a system such as the TEI Gaiji module recommendations for documenting their use of non-standard characters and/or the Unicode Private Use Area. ENRICH strongly recommends use of the TEI Guidelines in preference for such undertakings.
- Character normalization should be well-documented and consistently applied using standardized decomposed characters that have wide font support. Any mappings to such characters need to be clearly documented.
- All transformations, migrations, indexing and search routines should use the same table of equivalences in searching for normalized fonts.
- Although CSS3 web fonts provide a promising method to push fonts to users viewing a web page, this should not yet be recommended practice until consistently implemented across browsers.
This gBank application should serve to end-users interested in finding a particular non-standard character. The interface displays characters arranged in sets which can be further searched in order to find individual characters.
Please read also the documentation available below: