>Can't work: the same font could be used in different ways in different
>contexts. Actually this is just about guaranteed to happen. For
>example, if you add "Courier" to the "unicodeFonts" property to make
>your stacks work right, all the examples in the MetaCard on-line would
>turn to gibberish. Only thing worse than a "tag" hack is a global
>property that seriously breaks backward compatibility ;-)
Scott,
this complicates things, of course. Maybe you could give fields a property
"renderAsUnicode" of some sorts?
Or you could support syntax like
set the textFont of fld 4 to unicodeFont "Courier"
Using tags here is bad, since there's always bound to be a platform where a
font exists that uses this tag in its name. Especially on the Mac, where
all characters may be in a font name. If this is only needed under NT, you
could of course resolve this to a tag there, but unicodeFont should simply
be ignored on another platform. That is, for Linux
set the textFont of fld 4 to unicodeFont "Courier"
and
set the textFont of fld 4 to "Courier"
are the same, but under NT these might resolve to
set the textFont of fld 4 to "Courier/u"
and
set the textFont of fld 4 to "Courier"
instead. At least this would keep scripts compatible without endangering
different platforms. Of course, if we need a way to determine a field's
font including whether it uses Unicode we could only go by compares to
unicodeFont "Courier" in this case.
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
--- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
