|
Updates for |
This page is designed to support the
second edition of Document Preparation for Classical Languages by
providing corrections and new information. A summary of changes appears first;
if you are coming back to this page to check for updates, you will be able to
see easily if there are any since your last visit. Then the errata are listed, followed up
various updates.
Summary
June 12, 2011 added
correction to page xiii
April 10, 2011 added
updates to pages 64, 77, and 83
February 5, 2011 added
updates to page 23 and 47
January 16, 2011 added
update to page 35
January 2, 2011 added
correction to page 155 and update to page 172
November 7, 2010 Updated for second printing; added bibliographic reference to Gaultney (page 192)
Errata (second printing)
Except for the errors listed on pages xiii, 11 and 155 in
the chart below, all errata of which I am aware have been fixed in the second
printing with corrections (files uploaded in the second week of November
2010). If you wish to check which
printing you have, look on the copyright page.
Errata (first printing)
LOCATION |
CURRENT TEXT |
CORRECTION |
|
|||
page xiii |
address for updates |
http://scholarsfonts.net/docproc |
http://scholarsfonts.net/docproc.html |
|
||
page 11 |
end of first paragraph |
See page ?? for some additional information about this
issue. |
Delete this sentence (refers to a topic
I planned to include but dropped late in the editing process). |
|
||
page 99 |
second paragraph from bottom |
A package called CET (Classical Text Editor) |
A package called CET (Critical Edition Typesetter) |
|
||
page 105 |
fourth bullet |
interest webfonts |
interest in webfonts |
|
||
page 135 |
sidebar |
MatchLowerCase |
MatchLowercase (note small ‘c’) |
|
||
page 155 |
§8.2, first paragraph |
in §5.1, page 91 |
in §5.1, pages 92–93 |
|
||
page 161 |
fourth paragraph |
font leaves at the meteg after |
font leaves the meteg after |
|
||
The first printing contained a few other typos (reversed
letters and so forth) not listed here, but in all such cases the correct
reading is obvious.
Updates
PAGE |
NEW INFORMATION |
23 |
See also http://zvon.org/comp/s/unicode_reference/index.html,
another site to check out Unicode characters.
You can type in a hexadecimal number, decimal number, or HTML entity
name and see information about the character and others similar to it. |
35 |
[after “Publisher does both.)”] Note that Word 2010 will actually apply OT
features only if a font is digitally signed—you can turn the features on the Fonts
dialog but nothing happens without the signature, even though the features
are present in the font. Publisher
2010 does not care about this. (See
page 25 and Figure 2.1 for explanation of the digital signature issue.) |
47 (top) |
The version of Uniscribe (see page 19 for background on
this Windows component) that shipped with Windows 7 was not programmed to
recognize any of the characters in the supplementary planes that were added
in Unicode 5.2, including Egyptian hieroglyphics, Imperial Aramaic, and
several others. If you attempt to use
any of these characters on a system with this version of Uniscribe, you will
see two empty rectangles instead of the character. At some point Microsoft will undoubtedly
issue an updated Uniscribe, but until then Windows 7 users who need any of
the 5.2 supplementary characters have a problem. |
64 |
The free font editor C R8Type has been updated and renamed
TypeLight; see http://www.cr8.netfirms.com/typelight.html. If you wish (and are allowed by the license) to modify a
font that contains OpenType, AAT, or Graphite features, you need to proceed
with caution to avoid rendering the features inoperative or buggy. FontLab Studio 5.02 has an option to
preserve binary tables (tables are where the feature information is stored)
when it opens a font, and another option to make use of these tables when it
exports a new version of the font. If
you enable these options and make no changes to any characters that are
included in the existing features (e.g., adding a missing character), you
should be all right. If you change or
delete a character that is part of a feature, the font may not export or may
not work right. FontLab Studio also
tries to convert the binary tables to a human-readable form that you can
edit, but don’t try this unless you really know what you are doing. I have read that Font Forge preserves
existing features, but have not experimented for myself in this area with it
or with any font editors except FontLab Studio. |
77 |
Another Windows character utility is Character Map (Java),
available from http://download.cnet.com/Character-Map-Java/3000-2316_4-10861904.html. |
83, 157 |
Logos Bible Software, well known for its commercial Bible
study products that include texts in the original languages, also offers a
free utility called Shibboleth (Windows XP or more recent only). This utility enables one to enter text in a
variety of ancient languages: Greek, Coptic, Hebrew, Arabic, Syriac,
Ugaritic, and others. One can then
copy and paste the results into a Unicode-based word processor or page layout
program. Shibboleth is designed
particularly for use with languages in which the user is not an expert or
which he/she does not type frequently; it provides both keyboard entry and
character palettes, the latter of which are intended to help users find characters
or distinguish similarly shaped glyphs.
A transliteration mode provides access to many Unicode combining
diacritics not usually found on keyboards.
Downloads and a brief manual are available from http://www.logos.com/shibboleth. It is interesting to note that Shibboleth
requires accents to be typed after the base character, rather than using the
more common deadkey setup described on page 79. Also from Logos come four Windows keyboards for Biblical Greek, Biblical Hebrew, Coptic, Syriac, and Latin transliteration (with diacritics used in the transliteration of biblical languages). These are free and well documented, including an installation video; see http://www.logos.com/support/downloads/keyboards. |
172 |
§9.5: Andrew West
(author of BabelMap and BabelPad) has created some excellent Unicode Runic
and Ogham fonts that take advantage of OpenType features and include mirrored
glyphs for the runes; highly recommended.
His blog also contains interesting articles about issues with Runic
and Ogham as well as information about his fonts. All this is available from his website, http://www.babelstone.co.uk/ |
192 |
Gaultney, J. Victor (2002). Problems of diacritic design for Latin
script text faces. Available
online at http://www.sil.org/~gaultney/ProbsOfDiacDesignLowRes.pdf. This is a very useful article (actually, a
master’s thesis) for those who are interested in the various issues involved
in creating diacritical marks that are both attractive and, most importantly,
legible. |
Click here to return to the homepage of Document Preparation for Classical Languages.
Click here to return to the main Fonts for Scholars page.
Last update June 12, 2011.