Re: Are these characters encoded?

From: John Hudson (tiro@tiro.com)
Date: Sat Dec 01 2001 - 15:01:05 EST


At 05:52 12/1/2001, Stefan Persson wrote:

>1.) Swedish ampersand (see "&.bmp"). It's an "o" (for "och", i.e. "and")
>with a line below. In handwritten text it is almost always used instead of
>&, in machine-written text I don't think I've ever seen it.

This is, as your analysis suggests, a glyph variant, not a distinct
character. If the same text would have this Swedish form in manuscript, but
the regular ampersand form in print, this is something that needs to be
handled, if at all, at the font level. The logical implementation would be
to substitute the Swedish manuscript ampersand form in Swedish text set in
handwriting and calligraphic fonts.

>2.) Fractions with any number, see "bråk.bmp."

This is a layout issue, not an encoding issue. Arbitrary fraction forming
can be handled in selected runs with contextual lookups (I devised the
system now used in most OpenType fonts and can send you a more detailed
explanation if you would like).

>3.) Roman numerals. I know â… -â…« are encoded, but what if you want to use
>higher numbers? Typing "XX," you might suggest. This is not always
>sufficient; in Sweden we often put a line under and one above the numbers,
>see "Roma.bmp." And what about ten thousands? Neither "XÌ…" nor "XÌ„" are
>displayed properly!

The lines above and below are stylistic variant roman numerals and, like
the Swedish ampersand, they can be handled at the font level.

John Hudson

Tiro Typeworks www.tiro.com
Vancouver, BC tiro@tiro.com

... es ist ein unwiederbringliches Bild der Vergangenheit,
das mit jeder Gegenwart zu verschwinden droht, die sich
nicht in ihm gemeint erkannte.

... every image of the past that is not recognized by the
present as one of its own concerns threatens to disappear
irretrievably.
                                               Walter Benjamin



This archive was generated by hypermail 2.1.2 : Sat Dec 01 2001 - 15:59:47 EST