On Wednesday, Sept 29 1999, Scott Raney 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?
The only delimiter I've seen recently in font names other than a-z 0-9 is
".". Are there any restrictions on what is allowed in a font name? But
there are thousands of fonts out there. If in doubt, perhaps you could make
it a double delimiter - i.e. two of the same characters right after each
other? E.g. ::.
Regards,
Kevin
> If you want to bone up on the issues involved here, I recommend:
> http://www.unicode.org/
> Regards,
> Scott
>
> ********************************************************
> Scott Raney [EMAIL PROTECTED] http://www.metacard.com
> MetaCard: You know, there's an easier way to do that...
Kevin Miller <[EMAIL PROTECTED]> <http://www.xworlds.com/>
Cross Worlds Computing, MetaCard Distributors, Custom Development.
Tel: +44 (0)131 672 2909. Fax: +44 (0)1639 830 707.
