Muke Tever wrote:

>
> Peter T. Daniels <grammatim@...> wrote:
> > Peter Constable wrote:
> >>
> >> > From: Andrew Dunbar [mailto:hippietrail@...]
> >>
> >> > No. He's just misusing the terminology again. He means
> >> > the standard Windows encoding doesn't provide the
> >> > Hungarian double acute accent letters. Again, there
> >> > are many standard Windows encodings but obviously he
> >> > means the 8-bit Western European encoding. (Also known
> >> > as code page 1252, but that's technical enough that not
> >> > knowing it isn't ignorance).
> >>
> >> But making declarations about fonts having "223 slots" and not knowing
> >> that the platforms in question are not so limited and have not been for
> >> years (in the case of Windows, not since Windows 3.1) is speaking in
> >> ignorance.
> >
> > I am not talking about platforms, I am talking about fonts.
> >
> > Does Adobe now sell, say, the Stone family with more than 223 characters
> > in each variety?
>
> ITC Stone Serif Std Medium
> http://store.adobe.com/type/browser/F/STEQ/F_STEQ-10005000.html
>
> If I count right, the repertoire PDF shows 248 glyphs, plus one more to
> count the space, minus about four or five symbols displayed twice...

The 248 may include the tiny handful of glyphs that are used in the
Windows standard but not the Mac standard, such as edh and thorn.
PopChar sometimes reveals that there are unusable characters parked in
the lower 32 slots -- perhaps they intend that if you need them, you can
substitute them with Fontographer vel sim. for usable characters that
you don't need.

> It is true, however, that in fonts with _non-standard_ encodings only the
> space and 223 characters will be accessible, according to the TrueType
> specification, chapter 3:
>
> << Under both OS/2 and Windows, only the first 224 characters of non-standard
> fonts will be accessible: a space and up to 223 printing characters. >>
>
> http://www.microsoft.com/typography/tt/ttf_spec/ttch03.doc
>
> Ideally then you'd tell Fontographer to use a standard character set (such as the
> Unicode Glyph List) and encode your glyphs by their proper unicode values (or in
> the private use area, for characters not in Unicode), though this would also require
> a separate IME as your characters are outside the range of the common QWERTY keyboard.

That's why we have the Option key. And using ResEdit you could make
keyboards that do wonderful things (cf. Ecological Linguistics).
--
Peter T. Daniels grammatim@...