On Thu, 30 Sep 1999, M. Uli Kusterer wrote:
> >> One quick-and-dirty solution that's been proposed is to just add some
> >> sort of tag to the fontName property to indicate that all text in this
> >> font should be rendered in double-byte chunks. For example, the
> >> fontName might be set to "Helvetica,W" or "Helvetica/U" (i.e., "wide"
> >> or "unicode" tags). It would be relatively straightforward to hide
> >> this hack in the UI (so the user would not have to see these names),
> >> but it would maybe cause some problems for automated tools. We'd also
> >> have to be very careful to choose a delimiter that would never be
> >> found in any font name. Suggestions?
>
> Scott,
>
> please don't do it. Metacharacters and "tags" are bad.
Agreed, but sometimes a hack is better than no solution at all...
> I'd prefer a
> unicodeFonts property that contains a list of all fonts that are to be
> rendered as unicode.
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 ;-)
Regards,
Scott
> 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
>
>
********************************************************
Scott Raney [EMAIL PROTECTED] http://www.metacard.com
MetaCard: You know, there's an easier way to do that...
