maymudes@husc4.HARVARD.EDU (David M. Maymudes) (03/07/89)
What exactly needs to be done to make the system realize that a given FONT and
KCHR are linked together? In essence, if you have, suppose, a Russian font,
and a KCHR defined for use with that font, it should be possible (I think/
hope) to set the ID of the FONT, together with the ID of the KCHR, to tell
Script Manager-compatible applications to use the correct keyboard mapping when
the user types in the font. Is this correct? Is this _all_ that needs to be
done, or is it necessary to initialize the Script Manager in some way before it
will expect anything except plain, roman, text?
On a slightly higher level of complexity, suppose you have a language (in my
case, Ancient Greek) with accented characters that you would like to require
more than two keystrokes to type. You can't use a simple KCHR, so there must
be some other method of installing the code that is to be used.
I've read the "APDA Script Manager Development Package," and all related IM
stuff. As far as I know, the only script systems available (at least in the
United States) are the Kanji and Arabic systems, which are much more complex
than what I'm talking about. Is there documentation available for creating
script systems on this level of complexity? Do scripts for more languages
exist somewhere? (Hebrew, Classical Greek...)
Any information would be appreciated, either via e-mail or, if you'd like,
to the net. Thanks,
--David Maymudes
maymudes%husc4@harvard.ARPA maymudes@husc4.harvard.edu
maymudes@husc4.UUCP maymudes@HARVUNXU.BITNET
..{sesimo, harpo, ihnp4, linus, allegra, ut-sally}!harvard!husc4!maymudes
davidm@harvarda.BITNETsas1@tank.uchicago.edu (stuart austin schmukler) (03/13/89)
David: This may sound like a commerial, but I helped get an Anient Greek Script Interface System running. I think that SMK, Inc. sells the product. You may want to contact Richard Crane (of Harvard's Classials Department) for more information. SaS