Need an opinion about extended character fonts

I am making a font where there will be a choice of several glyphs for each lower case character in the alphabet. Do you guys think it’s better to use extended characters, or make several fonts that work together? I can see pros and cons for both situations. I know some people don’t like extended characters because they can’t remember where to find the darn things, but if I make several fonts that work together, then the user will have to cut and paste when they want to replace a character. I’m trying to decide which one is the least problematic for the user. Also, I know making them as seperate fonts will make the kerning a bit more complicated but I’m willing to do that if it’s the best answer. Any opinions on this would be MOST helpful. Thanks!

Sue

Do you guys think it’s better to use extended characters, or make several fonts that work together?

My feeling is that it depends upon what you want to do. For example, if you are offering people the chance to use glyph variants for use in producing a pdf document using a desktop publishing package for, say, publishing poetry, then several fonts might be better.

However, if someone is to be sat at a PC in a library trying to key a transcript of, say, an old printed book, then maybe putting the alternative glyphs in the Private Use Area and providing a list of glyphs and code points would be better, with everything in one font. Such a usage could be tedious using, say, Microsoft WordPad, yet a program such as Microsoft Word has an Insert Symbol facility where one could look through the available glyphs and select without referring to the code points. However, the result would be a file with Private Use Area characters. That could be helpful or not depending whether you wish to preserve the keyed text in a plain text format or not.

Another issue is that some software packages only use 256 characters with fonts, so a font using the Private Use Area would not be suitable for use with them, so it depends which software package or packages you have in mind to use with the font. However, for such a software package you could perhaps go for a non-Unicode character set where, say, what is properly an o acute character has a glyph for a fancy lowercase g. That could be fine if, say, the font were being used with Microsoft Paint to produce graphics which have text in the graphic.

A rather fine example of using several fonts which work together is the Operina set of three fonts.

http://www.p22.com/ihof/operinaset.html

There is a a pdf document available from that page.

William Overington

Gosh, William, you are full of information and I really appreciate your taking so much time with your responses, it’s very generous of you. I do have a couple of questions, though.

You use the term “private use area”. What does this mean? Are there 256 glyph spaces available without using the private use area? I will have less than that (104 letters plus punctuation, etc.) even with the additional lower case characters I’m making but my understanding is that anything that is not on a standard keyboard (and I count 94 possible characters, if I’m not mistaken) has to be accessed by typing alt and a numbered code. Is this correct?

My other concern is with kerning. If I make several fonts that can be used together, I don’t see how kerning can work without making duplicates of lots of letters, as I assume kerning doesn’t work across fonts. And, like the Operina font, the kerning will be extremely important to the look of this font. I’m very curious as to how the author of Operina made the fonts work together with all the ascenders, descenders and swashes in different sizes and positioning. Any ideas on that?

Thanks!
Sue

You use the term “private use area”. What does this mean?

It is an area of the Unicode codespace where anyone may make his or her own codepoint allocations. This has the downside that they are not unique as everyone else can also make his or her own allocations too! Indeed, people can make more than one allocation each for use in different scenarios if they so choose. Used with care it can be very useful.

There is information about the Private Use Area in the following document.

http://www.unicode.org/versions/Unicode4.0.0/ch15.pdf

It is available from the following web page as Chapter 15.

http://www.unicode.org/versions/Unicode4.1.0/

Here is a transcript of what I wrote some time ago for the following web page at the http://decode.meso.net webspace.

http://decode.meso.net/w3.php?nodeId=70095&page=1&lang=2&zoom=&prop=

The Private Use Area consists of 6400 codepoints located from U+E000 to U+F8FF inclusive. Its formal title is the primary Private Use Area. It is often known simply as the Private Use Area.

The Unicode Standard presently also contains two other Private Use Areas. The other two Private Use Areas are located in planes fifteen and sixteen, where they each occupy all but two codepoints of a whole plane. They are known as Supplementary Private Use Area-A and Supplementary Private Use Area-B respectively.

The following text refers to the Private Use Area which is located in the Basic Multilingual Plane, that is, to the Private Use Area which is located in plane zero, from U+E000 to U+F8FF.

The Unicode Standard states the following.

quote

By convention, the primary Private Use Area is divided into a corporate use subarea for platform writers, starting at U+F8FF and extending downward in values, and an end user subarea, starting at U+E000 and extending upward. By following this convention, the likelihood of collision between private-use characters defined by platform writers with private-use characters defined by end users can be reduced. However, it should be noted that this is only a convention, not a normative specification. In principle, any user can define any interpretation of any private-use character.

end quote

In practice there are other factors not mentioned in the Unicode Standard which someone defining a character in the Private Use Area may choose to consider.

One factor is that the Microsoft Corporation has a particular use of many characters in the range U+F000 to U+F0FF in relation to symbol fonts on the Microsoft platform for PCs. It is perhaps best to avoid using that range for ordinary Private Use Area character definition, though I cannot state any specific reasons for doing so.

Another factor is that there are various published uses of various Private Use Area codepoints by a number of individuals and organizations. These should possibly be considered before deciding to make a new allocation of one’s own. In the basic theory of the Private Use Area there is no need whatsoever to do that, because each person is free to make Private Use Area allocations as he or she chooses. However, suppose that one is defining one or two characters which one would like to become added into an existing font, perhaps a font from an independent fontmaker. A request to add a Private Use Area character into the font in a place which does not clash with an existing Private Use Area codepoint within that font is more likely to be successful than asking the fontmaker to discard a character already in the font. Also, a fontmaker may have tacitly, in his or her own mind, decided to reserve some Private Use Area codepoints in the font for the possible later addition of some characters from an already published Private Use Area allocation. Thus, although each person is free to make his or her own Private Use Area allocations, it can be advantageous to consider the practicalities of making progress with the applying of such an allocation for the desired needs.


My Quest text font has lots of items within the Private Use Area.

http://www.users.globalnet.co.uk/~ngo/fonts.htm

One note though: as you are learning, please note that Quest text was not originally produced using Font Creator 5.0, so certainly it is fun for looking for Private Use Area items, yet it would be best to use some other font if you are looking as to how to produce a font as Quest text was my first published font.

… my understanding is that anything that is not on a standard keyboard (and I count 94 possible characters, if I’m not mistaken) has to be accessed by typing alt and a numbered code. Is this correct?

Not necessarily. If you are using WordPad on a Windows 98 PC, then it is, as far as I know. With Word 97 on a Windows 98 PC there is the Insert | Symbol facility and shortcuts involving one or more of CTRL, ALT and SHIFT together with a keyable character can be set up . It all depends which package is being used.

My other concern is with kerning.

I have never used kerning with Font Creator, I have only used it once, in a test, with the Softy program, so I am unable to help with this part of your question.

William