Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!ads.com!saturn!bhanafee
From: bhanafee@deimos.ads.com (Brian Hanafee)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Font usage in non-US Systems
Message-ID: <BHANAFEE.91Apr16172711@deimos.ads.com>
Date: 16 Apr 91 22:27:11 GMT
References: <1991Apr16.184125.17534@rodan.acs.syr.edu>
Sender: usenet@ads.com (USENET News)
Organization: Advanced Decision Systems, Mountain View, CA 94043, +1 (415)
	960-7300
Lines: 39
In-Reply-To: nicktrou@rodan.acs.syr.edu's message of 16 Apr 91 18:41:25 GMT

In article <1991Apr16.184125.17534@rodan.acs.syr.edu> nicktrou@rodan.acs.syr.edu (Nikos B. Troullinos) writes:

   Some Mac programs when run under a non-US operating system seem to insist that
   a required font is called the same name as in the US system (e.g. Chicago,
   Monaco) instead of just using the font with the same ID (and there is always
   one available for the basic fonts Chicago, Geneva, Monaco).

   Is there a way to patch an existing program so that this problem can be
   circumvented? What is the correct way for specifying usage of the basic fonts
   in programs that are to be used internationally? My specific experiences are
   with the Greek version of the System.

   -Nikos Troullinos
   nicktrou@cat.syr.edu

Possible solutions (listed from (IMHO) least to most difficult):

1.  If you use Suitcase or some such program, you may be able to
persuade it to make the substitution for you.

2.  Put copies of your versions of the basic fonts (with US names)
into the resource fork of the offending application.  This may cause
you problems when you print the documents, however.  You can do this
with the Font/DA mover.

3.  Put copies of the basics fonts in your system with the appropriate
US names but different font ids.  (You'll need ResEdit and you'll be
stuck with two copies of each of your basic fonts.)

4.  Patch the get named resource toolbox call (I forgot the name & my
IM is at home with my mac) to check for the special names and cast
those calls into get by id.  This would add much overhead and would
probably be incompatible with everything under the sun.  You'd also
need to write some code.  The advantage is you'd have a solution which
would solve the general problem (e.g. you wouldn't have to check every
application), could be easily distributed, and would probably work
for other international systems as well.

Brian Hanafee