home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!ANDREW.CMU.EDU!rr2b+
- From: rr2b+@ANDREW.CMU.EDU (Robert Andrew Ryan)
- Newsgroups: comp.soft-sys.andrew
- Subject: Re: Is there any reason *not* to install OW fonts in "X11fonts"?
- Message-ID: <IePLzcW00Vs=0=YeJY@andrew.cmu.edu>
- Date: 22 Jul 92 15:34:00 GMT
- References: <AePKxDS0ts4j43LqUA@alw.nih.gov>
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: world
- Organization: The Internet
- Lines: 20
-
- In a recent pass over xim.c I changed it to accept a preference and an
- environment variable to determine what font path to add. (This still
- isn't quite right, really the "right" way is for the normal X, or OW,
- startup sequence to add the appropriate paths I think...) You can also
- use the preference or environment variable to disable xim's attempt to
- set the fontpath.
-
- There are a couple reasons not to put different types of fonts in one dir...
-
- 1. If both formats require a fonts.dir, which one do you use? Will it
- be compatible with the other?
-
- 2. Some mkfontdir implementations get confused by extraneous files.
-
- 3. Sometimes different formats have the same extensions. (For example
- as near as I can tell MIT R5 pcf fonts work with DEC R4 servers, but not
- vice-versa. Both use a .pcf extension)
-
- -Rob Ryan
- Andrew Consortium
-