
11-Mar-88 19:15:50-PST,55167;000000000000
Return-Path: <dow@wjh12.harvard.edu>
Date: Fri, 11 Mar 88 21:59:28 EST
From: dow@wjh12.harvard.edu (Dominik Wujastyk)

                               TEXFONT.MEMO

     [An index at the end of this document lists the fonts discussed.]


                 Introduction, History and Revision notes


This memorandum  seeks to  give a  reasonably complete  survey of the fonts
that are available for use with  the TeX typesetting software.  I  would be
grateful for any relevant information that you may have that is not already
mentioned.    While  keeping  the  memo  concise,  I  have  given  all  the
information that I currently have.  In  other words, this is it:  there  is
probably  nothing  more  to  be  learned  by contacting me directly than is
already in the memo.  I have also given everything I know about how to  get
more  information  about  each  font,  so  follow  those  leads rather than
contacting me.

I first started compiling this Memorandum late in 1987, as a note to myself
and my immediate Indological colleagues.   But it seemed little  extra work
to include more information  in it about other  fonts I have heard  of, and
doing this has greatly widened its usefulness to TeX users in general.   As
this  memo  has  grown  beyond  its  original  purpose, and more people are
requesting it, I think it is now worth adding the following notes giving  a
date for the current revision.  I shall post these revision notes to TeXhax
from  time  to  time,  and  send   the  latest  version  of  the  memo   to
score.stanford.edu.  This way people will know whether there is enough  new
stuff in it to be worth downloading it (again).

                              Revision Notes

March 10, 1988:
   Added information  on Listserve  access to  Goldberg's Arabic;   Knuth's
   Devanagari  la;  Billawala's  Pandora;  new  person  may  work on Tamil;
   Icelandic;  Times  Roman in Metafont;   two people  may work on  Telugu;
   IPA  now  available  from  Washington;    Bitstream font family for TeX;
   HP2TeX conversion of HP soft fonts to TeX fonts.

   Since the tail has started to  wag the dog, I have reformatted  the memo
   slightly, removing some of the bias towards Indic matters, to make it  a
   more general note about  TeX fonts.  Index  added.  General tidy  up and
   removal of infelicities.

February 3, 1988:
   added information on Austin  Code Works, Hebrew, OCR,  Elvish, Ramanujan
   Tamil.

---------------------------------------------------------------------

                               INTRODUCTION


   Here is a compilation of what I know of fonts and METAfonts for use with
   TeX.    Although  I  am  primarily  interested  in  fonts  designed with
   METAFONT, I would also like to include information about any other Indic
   fonts that have been successfully  used with TeX, i.e., fonts  with Font
   Metric  files,  and  a  mechanism  for  the  creation of the appropriate
   ligatures, be it within the .TFM file, or by means of a preprocessor.

   I have added  an appendix giving  some information about  additional TeX
   fonts known to me.

1. DEVANAGARI

1a As far as I know,  Donald Knuth coded the first Devanagari  character to
   be  created  with  Metafont.    This  was  the single syllable la, which
   Matthew  Carter  gave  to  Knuth  in  1980  as  a  challenge to test the
   capabilities  of  the  then  nascent  Metafont.   The smoke proof of the
   character, and  several interesting  remarks about  the experience, were
   published as "My First  Experience with Indian Scripts",  in _CALTIS-84:
   Special Issue on Calligraphy, Lettering & Typography of Indian Scripts_,
   (Proceedings of a Delhi 1984 conference).

1b An early Devanagari font was designed with old METAFONT (MF-in-SAIL)  by
   P. K. Ghosh during a visit  to Stanford in 1982--83.  Ghosh  published a
   report on what he had done as Stanford Computer Science Report 965:  _An
   Approach  to  Type  Design  and  Text  Compostion  in  Indian   Scripts_
   (Stanford, 1984).   One of the  valuable aspects of  this work was  that
   Ghosh worked from  Devanagari characters designed  and drawn for  him by
   the famous Bombay  calligrapher R. K.  Joshi.  Drawings  of these, on  a
   grid,  are  published  in  the  abovementioned  Report.   Unfortunately,
   Ghosh's work was done in a  now superseded version of METAFONT, and  was
   not fully worked out at the keyboard level.  It also lacked a number  of
   the conjunct  consonant clusters  necesary for  fine Indian  typography.
   The report, however,  remains of interest  for general background.   The
   source code is available at  U. Washington, throught Pierre MacKay  (net
   address below), and presumably at Stanford (try Emma Pease).  Ghosh  has
   said explicitly that he has no objection to others doing further work on
   it.  MacKay has said that one problem with the Ghosh font is that it was
   arbitrarily  developed  in  a  framework  that  bears no relation to the
   monotype-based character grid used for Computer Modern, and that this is
   unfortunate,  since  it  makes   it  almost  unusable  in   a  bilingual
   environment.

   If you wish to contact Ghosh he can be reached at the following address:
            Pijush Ghosh,
            National Centre for Software Technology,
            Gulmohar Cross Road 9,
            Juhu, Bombay 400 049,
            INDIA
1c The only fully worked  out version of Devanagari presently  available is
   that of Frans Velthuis:

Date of information: 25 December 1987

The font:
   In November 1987, Frans Velthuis  completed version 1.0 of a  Devanagari
   METAfont for TeX.   He has  written METAFONT code  for all the  aksharas
   necessary for Hindi, and most of those for Sanskrit too, although in the
   latter case some viramas are used.   Frans intends to produce a  special
   Sanskrit version  of his  font in  the future.   Also  included are  the
   Devanagari  numerals,  anusvara,  virama,  danda,  candrabindu, visarga,
   avagraha, full stop and superscript abbreviation circle.

Usage:
   You  prepare  your  TeX  or  LaTeX  file  normally,  and  mark any Hindi
   portions, typed  a simple  Roman transliteration,  with the  font marker
   {\dn ... }.  At the top of the TeX file you \input a file called DNMACS;
   in LaTeX, a DEV.STY file is provided which inputs the necessary  macros,
   and automatically makes necessary font  size changes.  Frans provides  a
   preprocessor, DEVNAG,  written in  Pascal (source  not available), which
   reads  your  file  and  converts  the  Hindi  transliteration  into  the
   appropriate  codes  for  Frans's  font.    The  converted  file  is then
   processed by TeX or LaTeX in the normal way, and the resulting .DVI file
   can be printed on using a standard DVI output program.  The portions  of
   Hindi  text  originally  in  Roman  transliteration  will  be printed in
   Devanagari, with full use of conjunct consonants (sandhyaksharas), etc.

Quality:
   The quality of the fonts  is excellent, with full calligraphic  moulding
   of the curves and loops, like some of the best handwriting of manuscript
   scribes using a broad nib.

Terms of Availability:
   Frans will sell a set of four or five sizes of the Devanagari fonts,  at
   the printer  resolution you  specify (Epson  type 9-pin  matrix, 24  pin
   matrix (180*180,  360*360, 180*360),  write-white laser,  or write-black
   laser), together with  the compiled code  (specify VAX/VMS, SUN,  Cyber,
   IBM/PC,  Atari  ST)  of  DEVNAG,  his  text  preprocessor, for $119. The
   METAFONT  source  programs  are  not  at  present  being  made generally
   available.

Contact:
   Frans J. Velthuis
   Postal address: Nyensteinheerd 267,
                   9736 TV Groningen,
                   The Netherlands
   Bitnet:         Velthuis@HGRRUG5.Bitnet

Other comments:
   A note about Velthuis's Devanagari font appeared in TeXhax, 1987,  issue
   93.


2. TAMIL

2a Arthanari

Date of information: December 26, 1987

Contact:
   According to  Emma Pease  (network response  on 10  November 1987  to my
   query in TeXhax 1987, issue 93) a basic set of Tamil characters for  TeX
   was designed  at Stanford  by T.  S. Arthanari  created when  he was  at
   Stanford (May-July 1985).  Emma has the source code but does not want to
   distribute it further without his knowledge.  His present address is

           Quality Informatics Labs, Ltd.
           312, P. M. G. Complex
           57, South Usman Rd.
           Madras, 600 017
           INDIA

   (Address gotten by Emma from the Stanford Computer Science Dept.)

   There are approximately  160 characters in  several styles written  in a
   pre-release  version  of  the  current  Metafont.  Emma  has  only tried
   producing characters for one style but had little difficulty in doing so
   (a few commands had changed).  They are rough but look fairly good.

   I  (Dominik)  am  writing  to  Mr.  Arthanari  today  to  ascertain  his
   intentions concerning his  work, and especially  to learn whether  he is
   willing  and  able  to  allow  the  source  code of his Tamil font to be
   distributed  as  public  domain  software.    (March  10, 1988: still no
   answer.)

2b Ramanujan

Date of information: Fri Jan 22 1988 (mail from Pierre MacKay)

The font:
   Ramanujan, a graduate  student who worked  at Washington two  years ago,
   designed a  Tamil font  in METAFONT84  (I think).   According  to Pierre
   MacKay, the problem  with this, as  with Ghosh's Devanagari,  is that it
   was arbitrarily developed in a  framework that bears no relation  to the
   monotype-based  character  grid  used  for  Computer  Modern;    this is
   unfortunate,  since  it  makes   it  almost  unusable  in   a  bilingual
   environment.    Moreover,  it  does  not  make  much  use  of  the macro
   capabilities of  METAFONT, and  although reasonably  well designed,  the   programming could perhaps be improved.   MacKay says that the  people at
   Washington are continuing to work on it.

Contact:
   Pierre MacKay,
   Phone: 206-543-6259; 545-2386.
   Net: MacKay@june.cs.washington.edu


2c Rengarajan

Date of information: March 11, 1988
   T. K. Rengarajan, a software engineer (Database Systems, Digital  Equip.
   Corp.)  mailed  me  on  Fri,  5  Feb  88  and mentioned that he may do a
   METAFONT Tamil.

Contact:
   ranga%debit.DEC@decwrl.dec.com


3. MARATHI
   No known  font, but  the addition  of a  few extra  characters, such  as
   retroflex la, to Velthuis's  Devanagari (which he is  considering doing)
   will make his font perfectly suitable for Marathi.


4. ARABIC

4a Goldberg

Date of information: February 3, 1988, February 11, 1988,

   On Mon, 18 Jan 88, and again on 15 Feb 88, Jacques J. Goldberg wrote  to
   TeXhax (1988, issues #07 and #15),   giving details of a package  giving
   the  capability  of  printing  Hebrew.      He  said  that an article is
   currently  being  written  for  submission  to  TUGboat (see below under
   HEBREW).  He also included a brief note referring to a nearly  completed
   Arabic font.

The font:
   Goldberg said, "An Arabic font is three characters away from completion,
   but the MetaFounders are near mid  year exams and unpaid, so the  Arabic
   font MIGHT show up around mid March [1988].  (to be precise, their  font
   is Parsi, and some limited work is needed to extend it to full Arabic)".
   "This  needs  NO  change  either  in  TeX  or  in  DVI drivers: a simple
   preprocessing of the TeX input file and a small additional macro package
   do it.



Terms of Availability:
   Regarding the Hebrew  package of fonts  and macros Goldberg  says, "I do
   not  expect  any  fee  from  individuals,  but  I  would  be  happy   if
   INSTITUTIONS  that  may  use   this  package  would  later   voluntarily
   contribute $25 to  $50 [payable to  the Treasurer of  the University] to
   help my Department ... pay  students employed on font development."   It
   is likely that the Arabic may be distributed on similar terms.

   He later added, "All  that project is stored  and freely available on  a
   Bitnet server.   To get the  whole package, send  an interactive message
   GET  IVRITEX  PACKAGE  to  LISTSERV@TAUNIVM.  Arpanet  or other nets not
   interactively  connected  to  Bitnet,  just  send  a  MAIL  file to that
   address, with the request  GET IVRITEX PACKAGE in  the first line (  NOT
   Subject) of the message.  Other useful commands to that server are:  GET
   IVRITEX FILELIST to get  a directory of the  project INFO FILES   to get
   instructions how to sign up for automatic updates."


Contact:
   Jacques J. Goldberg, phr00jg@technion.bitnet  (the id has two  zeroes in
   it).  If you are not on Bitnet, try:
   <PHR00JG%TECHNION.BITNET@forsythe.stanford.edu>,
   or write to:
           Prof. Jacques J. Goldberg,
           Dept of Physics,
           Technion-City,
           32000 HAIFA, Israel.

4b MacKay

   Pierre A. MacKay  (TUG Site Coordinator  for Unix-flavored TeX)  and the
   Washington team have been working on an Arabic implementation of TeX for
   some  years.    Their  plans  are  ambitious,  and  include  building  a
   customised version of  TeX, to be  called TeX-XeT, which  has a built-in
   capability of handling  bidirectional text.   Details of this  change to
   TeX were published by Don Knuth and Pierre MacKay in TUGboat vol.8,  #1.
   This is an active project, but MacKay says wistfully that Arabic remains
   a long-term dream.  On Tue, 9 Feb 88, MacKay noted that "I got a working
   compilation of TeX-XeT,  and have been  using it for  a while (just  for
   ordinary  text)  on  another  (un-networked)  machine.   I would like to
   incorporate the changes into a change file for Tim Morgan's TeX-to-C  (I
   hope that nothing falls outside  the general syntax rules of  tex-to-c).
   When I do, I will make it available for ftp."

Availability:
   MacKay notes that  the babel directory  in the UnixTeX  distribution now
   contains a directory  for Semitic languages  with TeX-Xet.web and  other
   program fragments, which will be added to.

   On Tue, 9 Feb 88, MacKay posted  a note to TeXhax (1988, #15) about  the   availability of TeX-XeT:  "I have  put the rough workings of TeX-XeT  on
   the ./babel directory  in the UnixTeX  distribution, but it  is a clumsy
   and cumbersome first pass, and I  can't recommend it at all.   XET.CH (I
   think that is the name) is on the SCORE archives, probably in TEX.WEB."

Contact:
   Phone: 206-543-6259; 545-2386.
   Net: MacKay@june.cs.washington.edu


5. OCR-A

Information given in TeXhax 1987, issue #106.
   Coded in METAFONT84 by Tor Lillqvist, VTT/ATK (Technical Research Centre
   of Finland, Computing Services).  Based on ISO Recommendation R1073, 1st
   ed., May 1969 (probably obsolete by now).

Contact:
   Tor    Lillqvist    at    tml@fingate.BITNET,    tml@santra.UUCP,     or
   mcvax!santra!tml.

   On  1  Jun  87,  Brandon  S.  Allbery  (allbery@ncoast.UUCP) and Michael
   Lichter  (cwruecmp!sun!seismo!harvard!csvax.caltech.EDU!netsrc)   posted
   the  METAFONT  sources  for  the  OCR-A  on  USENET  as  article  53  of
   comp.sources.misc (Message-ID: <7632@brl-adm.ARPA>)


6. CLASSICAL AND MODERN GREEK

Date of information: January 21, 1988.

   Regular, bold, and typewriter versions  of the Greek alphabet have  been
   coded in METAFONT84 by Silvio Levy of Princeton, starting from the Greek
   character set created by  Don Knuth as part  of the CM family,  but with
   all  accents,  breathings,  correct  spacing,  and macros to implement a
   convenient Roman transliteration for input.

   The initial release  of the METAFONT  source at the  end of December  87
   proved to  contain difficulties,  at least  when attempts  were made  to
   compile the fonts using the  PC implementation of METAFONT version  1.3.
   These difficulties seem to center on  the levels of nested files that  a
   particular METAFONT implementation allows.  Levy says the following:
      If possible, you should create a version of METAFONT with max_in_open
      >= 8.   The  default value  of this  variable [5,  I think] is really
      unreasonably small, and barely enough for making the CM fonts.  In my
      case it would be possible but  much less orderly to use fewer  levels
      of nesting.

      Don't worry about a bad path in drawing the lowercase omega, it comes
      out all right.  I'll  fix it when I have  the time.  I think  there's
      also a bad pen_pos somewhere.
   Doug Henderson  is working  on a  version of  these Greek  fonts for the
   American Mathematical Society's APS phototypesetter, to be published  in
   TUGboat, and in the process he is  revising the code.  Levy is aware  of
   the difficulties and  will be producing  a revised release  of the fonts
   early in 1988.

Contact:
   Silvio Levy: levy@Princeton.EDU


7. JAPANESE

Date of information: March 11, 1988
   I  recently  received  a  comprehensive  message  from  Edgar  M.  Cooke
   (Assistant  Manager  Software  Tools  &  Technology  Division) about the
   current state of TeX in Japan.  I reproduce most of it below.  He begins
   with the following:

   At present, two publicly-available versions of TeX are being distributed
   that  support  Japanese, and one  further version is  supposed to become
   available shortly. These are not entirely mutually compatible, and  each
   has its strong and weak  points.

7a Japanese TeX developed by ASCII,  Inc.  (This is a mainly  microcomputer
   oriented  magazine/book  publisher  and  software  house  that has taken
   strong interest  in TeX  for their  own publishing  work and  whose UNIX
   support section has  produced and distributes  the Japanized version  of
   TeX.) ASCII's version was implemented without concern for 100%  internal
   compatibility with Knuth's TeX, and cannot pass the trip test (NB: it is
   closer to passing as of ver. 1.0).  However, the output of an  identical
   English .TEX input file is, to the best of my knowledge, identical  with
   that of standard TeX.  They have added a few primitives (concerned  with
   spacing between  the ideographs  and letters,  etc.) useful  in handling
   Japanese  or  Japanese  with  romanized  languages,  and  have created a
   variant  of  TFM  which  they  call  JFM  (but  which still has the .TFM
   extension, although is internally identifiable  by a coded ID byte)  the
   purpose  of  which  is  to  allow  1  font  to  hold  the more than 6000
   characters of a typical Japanese font.   It also differs in other  ways,
   notably  that  the  ligature  table  (unnecessary  in Japanese) has been
   replaced  by  a  "glue  table",  which  handles  much of the information
   necessary  concerning  spacing  between  the  characters  (which usually
   appear  without  distinction  between  inter-character  and   inter-word
   spaces,  unlike  in  modern  Western  languages).   At present, ASCII is
   freely distributing this in the  form of sources including change  files
   for INITeX, VIRTeX, and BiBTeX, and Japanized macro files for plain TeX,
   LaTeX, and SliTeX\  (with the LaTeX  style files), and  they include the
   source for  a (just  adequate) printer  driver for  the Canon LBP-8 that
   uses its internal Japanese character set, and JFM files for point  sizes
   5 through 10 of a standard ("Mincho" = Ming Dynasty style) font and of a   emboldened ("Gothic") font which can  probably be used with a  number of
   different pixel  font sets,  e.g., the  internal Canon  LBP-8 set,  (but
   which in ver. 1.0 is based on the Dai Nippon Printing Co. [DNP]  fonts).
   (A printer driver and X-windows previewer handling the DNP fonts are now
   available.)

7b J-TeX developed by Yasuaki Saito of Nippon Telephone & Telegraph  (NTT).
   The author's  article on  J-TeX appeared  in TUGboat,  Vol.8 No.2,  so I
   won't dwell on it other than to say that his policy has been to  attempt
   to avoid radical changes to standard  TeX as much as possible, but  this
   increased compatibility has led to problems: since a font can have  only
   256 characters, the number of fonts  one needs even to support a  single
   real Japanese font  set (33) tends  to be quite  large even if  one only
   declares the fonts corresponding to the various sections of the original
   font that  include characters  that have  actually been  input into  the
   document.  This  is available in  the US on  SCORE for Tops-20,  and the
   UNIX version  is being  distributed in  a less-than-enthusiastic fashion
   for the  time being  ("beta testing  period") by  the author with source
   files for pretty much what ASCII has, but with an Imagen printer  driver
   that handles external Japanese font data and an X-windows previewer  for
   J-TeX,  as  well  as  a  version  of  DVI2PS supporting Japanese, but no
   support for BiBTeX or SliTeX is  offered.  A standard (but ugly)  set of
   Japanese  characters  that  is  in  the  public domain (known as the JIS
   fonts,  for  the  Japanese  Industrial  Standards  Institute,  which  is
   responsible  for  the  abjectly  arbitrary  standard  coding of Japanese
   characters and for making the  font set available) is included  with the
   distribution.    This  originally  consisted  of  only  1  size,  namely
   characters  described  in  a  24-dot  square  matrix,  but  the   author
   mechanically generated 36-, 48-, and 72-dot fonts to imitate other point
   sizes or \magsteps.  This set is not very high quality by any  standard,
   but it is the only public domain font known to me.  The author has  also
   collaborated  with  Dai  Nippon  Printing  Co.  to  make  their industry
   standard fonts  available---but for  a price  (95,000 Japanese  yen last
   time I checked; ASCII and SONY  are also negotiating with Dai Nippon  to
   allow similar font sets to become available for different resolutions of
   printers, and, if  we are lucky,  a vector stroke  font of high  quality
   that is applicable to various sizes and resolutions may become available
   next year).  This J-TeX has  240, 300, 400, and 480 dpi  fonts available
   currently.    Please  note  that  6000+  characters  makes for a largish
   distribution tape---the rudimentary  set of JIS  fonts in an  adapted GF
   format with TFMs takes up about 10  M of disk space, while the PXL,  GF,
   and TFM files for  the DNP Mincho and  Gothic fonts very nearly  fill an
   entire 2400 ft  magtape at 6250  bpi! (I had  a chance to  measure these
   more  carefully:  DNP  fonts,  GF  format:  Mincho:  49,312,713, Gothic:
   43,401,652,  TFMs:  559,152,  total:  93,273,517  bytes;  JIS fonts, PXL
   format: 11,321,384, GF format: 7,729,124, TFMs: 137,417 bytes; in  other
   words, non-trivial.)

Further information from myself:
   Date of information: Fri  25 Dec 87, given  in TeXhax 1987, issue  #106.
   (An article  on JTeX  and the  fonts appeared  in TUGboat  volume 8, #2,
   103--116.)

Contact:
   Hideki ISOZAKI, NTT Software Laboratories, Japan.
   JUNET isozaki@ntt-20.ntt.junet
   CSNET isozaki@ntt-20.ntt.jp
   ARPA  isozaki%ntt-20@sumex-aim.stanford.edu

   or
   Yasuki  Saito,  NTT  Electrical  Communications Laboratories, NTT Corp.,
   3-9-11 Midori-cho Musashina-shi, Tokyo 180, Japan.
   Phone: +81 (422) 59-2537
   Net: yaski%ntt-20@sumex-aim.stanford.edu

7c There is a version that  is likely to become available from  Canon which
   resembles that of NTT, but it may take a LONG time for the management at
   Canon to make anything available to the public domain, so I don't  think
   it  will  be  until  sometime  next  year  that  this becomes available.
   Similarly, IBM Japan has a Japanese version based on the Canon algorithm
   (which was also the stimulus for the NTT version).

Conclusion (Edgar M. Cooke)
   There has been a meeting of the leaders and interested parties of  J-TUG
   about whether it is possible to merge these three versions, and a number
   of suggestions and guidelines have been set forth, but lacking a central
   authority figure along the lines of a Donald Knuth has limited this from
   going  beyond  recommendations.    All  three  parties  are  working  on
   improving their inherent quality and mutual compatibility, and I  expect
   that they will  be working on  this throughout the  next year (all  this
   being more or less volunteer work). Except for the fact that just  about
   none of the other utilities (DVITYPE, etc.) seem to work with the  ASCII
   version (except TFTOPL and PLTOTF to preen JFMs), I suspect that it is a
   leading contender, because (1) they are promoting it through prompt  and
   widespread  distribution  of  the  sources  advertised  in their own and
   others' publications,  and (2)  because they  have obviously  lavished a
   good deal of care in attending to details of Japanese printing  practice
   that make it at least as good as either of the others---in addition,  of
   course, to  removing the  burden of  having to  deal with  a plethora of
   fonts each comprising a tiny fragment of a whole Japanese font set.

Contact:
   Edgar M. Cooke is prepared to act as a clearing house for TeX going into
   and coming out of Japan.  His e-mail address is:

   cooke\%srava.sra.junet@uunet.uu.NET

   (It is possible to reply to any mail he will send you by "R" or "r" from
   the  Unix  mail(1)  program,  but  then  it  will come via CS-NET, which
   (although  days  faster)  is  prohibited  to  non-member,   non-academic   institutions such as his.)

   He is in close  touch with Pierre MacKay,  and has sent Pierre  both the
   above mentioned versions of TeX.


8. CHINESE

   Work  done  on  a  Chinese  METAfont  by  Gu  Guoan and John D. Hobby is
   available by anonymous FTP from june.cs.washington.edu, in the directory
   /pub,  as  the  (large)  file  chinese.tar.Z.    This  was written up in
   TUGboat, issue #5.2 (November 1984), pp.119--136.  (This is a reprint of
   the Stanford Computer Science Report 974 by Gu Guoan and J. D. Hobby: _A
   Chinese Meta-font_ (Stanford, 1983).)


9. TURKISH

Date of information: Fri Jan 22 1988 (mail from Pierre MacKay)

The font
   Work on  properly accented  roman-letter Turkish  fonts in  METAFONT has
   been undertaken at the University of Washington by Pierre A. MacKay  and
   Walter Andrews.  See the note  in TUGboat volume 8, #3, p.260b.   Pierre
   MacKay reports that the fonts lack only a reworking of the italics for a
   first working release.

   MacKay notes that the next Tugboat (the first 1988 issue) will  describe
   a Turkish hyphenation file.

Contact:
   Phone: 206-543-6259; 545-2386.
   Net: MacKay@june.cs.washington.edu
   Address:
           Prof. Pierre A. MacKay,
           Northwest Computer Support Group,
           Univ. of Washington,
           Mail Stop DW-10, Seattle, WA 98195.

10. INTERNATIONAL PHONETIC ALPHABET

   Dean Gunther informs me (Mon Feb 29 1988) that:
   "Washington State University has an  IPA font available. It contains  90
   popular  IPA  characters  and  diacritics  as specified in the "Phonetic
   Symbol Guide" by Geoffery Pullum and William Ladusaw. Janene Winter  has
   done the work on this font. Presently Janene is reworking the  character
   positions in the table with input from Helmut Feldweg at the Mac-Planck-
   Institute f\"ur Psycholinguistick  in the Netherlands,  Christina Thiele
   at Carlton University and Brian MacWhinney at Carnegie Mellon."

Terms of availability:
   It is available  for $100 for  GF, PXL or  PK fonts in  10 and 12  point
   (together) in the roman face. The MF source is not included.


   Send a note to Janene at WINTER@WSUVM1 on BITNET, or write to:
        TEXT1 Distribution
        Computing Service Center
        Washington State University
        Pullman, WA  99164-1220


11. SPRITE.STY

   If you  use LaTeX,  and you  only need  one or  two extra characters, an
   ingenious and very easy way to generate them has been devised by  Martin
   Costabel (XBR1DA29@DDATHD21.BITNET).  It is a LaTeX style called SPRITE,
   and the  code and  documentation were  published on  14 November 1987 in
   issue  1.8  of  TeXMag,  an  online  TeX  magazine  put out by Don Hosek
   (DHOSEK@HMCVAX.BITNET).  Here is an extract from Martin's documentation:
      SPRITE.STY is a LaTeX macro that allows you to define in a quick  and
      dirty way your own symbols. You just have to define the character  as
      a dot pattern on your screen and enclose it by \sprite and \endsprite
      commands. Of  course, I  know, TeX  is awfully  professional and this
      primitive technique will not provide  results as good as a  MetaFont-
      designed character or even one drawn using device-dependent  \special
      commands, but  if you  just need  one special  character or some cute
      little symbol and you don't have the time/brains/MacIntosh/superuser-
      privilege/money-for-AmS-fonts/or    whatever-is-necessary    for    a
      professional solution, this might produce acceptable results.
   Using SPRITE one  "draws" the character  to be defined  as a pattern  of
   characters on a grid.  The following example shows how schwa is done:

\def\schwa{\FormOfSchwa\kern 1 pt} % Only necessary if \kern... is wanted
\sprite{\FormOfSchwa}(16,24)[0.4 em, 1 ex] % Resolution ca. 200x340 dpi.
:.......BBBBBBBBBB....... |
:....BBBB........BBBB.... |
:..BBB.............BBBB.. |
:.BB.................BBB. |
:.B...................BBB |
:.....................BBB |
:.....................BBB |
:.....................BBB |
:BBBBBBBBBBBBBBBBBBBBBBBB |
:BBB..................BBB |
:BBB..................BBB |
:BBB.................BBB. |
:.BBB...............BBB.. |
:..BBBB...........BBBB... |
:....BBBBB.....BBBBB..... |:.......BBBBBBBB......... |
\endsprite
   To use this character in your LaTeX document, all you have to do is  use
   the command \schwa.  This method uses a lot of TeX's memory, and is only
   suitable for  characters which  are used  rarely, say  a few  times on a
   page.


12. ELVISH

Date of information: February 3, 1988

   On 4 Dec 1986 (sic)  Mike Urban (urban@spp2.UUCP) released the  Metafont
   code  for  Tolkien's  Tengwar  through  USENET (article 66 of comp.text,
   Message-ID: <1191@spp2.UUCP>)

   Mike said the following:
   "This shell archive contains METAFONT sources for a digitized version of
   the Tengwar (Elvish script) created  by J.R.R. Tolkien.  They  have only
   been tested on a 300dpi laser  printer.  No guarantee of the  quality of
   either  the  code  or  the  output  is  offered.    I'm not particularly
   satisfied with the quality of the code (my first non-trivial attempt  to
   use METAFONT), but the results look OK to me."

Contact:
          Michael Urban,
           TRW Inc.,
           R2/2009
           One Space Park,
           Redondo Beach, CA 90278


13. HEBREW

Date of information: February 3, 1988

   On Mon, 18 Jan 88 Jacques J. Goldberg wrote to TeXhax (1988, issue  #07)
   giving details of  a package giving  the capability of  printing Hebrew.
   He said  that an  article is  currently being  written for submission to
   TUGboat.

The fonts:
   Goldberg says that the package comprises:
   --  a set of fonts at 8, 9, 10, 12, 17 points in regular type, 10 points
   slanted and bold, and any magnification on request (1000 off the shelf).
   --  a 100%  portable preprocessor written in  C (MSDOS users who  do not
   have a compiler can get the .COM file)
   --  a small set of TeX macros.
   --  a sample file.

Usage:
   Hebrew words in  English transliteration are  inserted either by  typing
   first-typed-last-read  with  the  font  invoked,  which  is  a  pain but
   "displays" in natural reading order, or by typing first typed first read
   as argument of the \reflect macro given by D.Knuth and P.MacKay, TugBoat
   vol.8, no.1,  p.14.   Long Hebrew  sequences are  typed, in first-typed-
   first-read order, within delimiters.  The preprocessor copies non Hebrew
   sequences to an auxiliary file. Hebrew sequences are parsed into  words,
   written to the  auxiliary file one  word at a  time after each  word has
   been reflected.  TeX is then  invoked, inputting the file which has  the
   extra  macro  package,  never  the  user's  input.  This macro reads the
   auxiliary files, feeding TeX with either English TeX as is or \lines{  }
   adjusted by the macro to the optimal number of Hebrew words.

Quality
   Goldberg is -- I suspect unnecessarily -- diffident about the quality of
   the fonts.  He  calls them "ugly fonts  not good for anything  else than
   Office documents (drafts,reports,...)".

Future development:
   Goldberg is looking  for a convenient  table representing the  22 Hebrew
   letters by  Latin letters.   Then  the preprocessor  could translate  to
   standard ASCII  the character  codes used  in Israel  with their special
   Hebrew terminals, so  that anybody with  an English-only terminal  could
   write in Hebrew.

Terms of Availability:
   Goldberg says, "I do not expect any fee from individuals, but I would be
   happy if INSTITUTIONS that may use this package would later  voluntarily
   contribute $25 to  $50 [payable to  the Treasurer of  the University] to
   help my Department ... pay students employed on font development."


Contact:
   Jacques J. Goldberg, phr00jg@technion.bitnet  (the id has two  zeroes in
   it).  If you are not on Bitnet, try:
   <PHR00JG%TECHNION.BITNET@forsythe.stanford.edu>,
   or write to:
           Prof. Jacques J. Goldberg,
           Dept of Physics,
           Technion-City,
           32000 HAIFA, Israel.


14. MISCELLANEOUS FONT COLLECTIONS

14a ACW
   The Austin Code Works has a  large collection of bitmap fonts that  work
   with TeX, and which were originally created at SAIL (Stanford Artificial
   Intelligence Lab) in the late 60s or early 70s (I think).  Because these   fonts are not  coded in up-to-date  Metafont, what you  get is what  you
   get, i.e., you  cannot change the  size or resolution  of the fonts.   I
   believe they are all (or most) 200dpi fonts.  Bear in mind that although
   you might get, say, a Hebrew  font, there are no accompanying macros  to
   implement it at the keyboard level.

The fonts:
   The "KST Fonts by Les Earnest" are described thus in the ACW handout:
   "Originally  developed  for  the  Xerox  XGP  printer, the 137 KST fonts
   include  Hebrew,  Greek,  Old  English,  Old German, Cyrillic, hand[sign
   alphabet], and Tengwar alphabets in addition to the Roman alphabet in  a
   large number of eclectic  styles.  Specify TeX  or bitmap format.   Both
   come with an extraction and display program."

   The fonts  include such  essentials as  single character  fonts for  the
   Stanford and MIT logos (separate  fonts for each, naturally), two  views
   of  Snoopy,  two  views  of  Starship  Enterprise,  three fonts of chess
   pieces, several sans  serif fonts, and  what looks as  if it might  be a
   very tiny Arabic font.

Terms of availablity:
   $30.

Contact:
   The Austin Code Works,
   11100 Leafwood Lane,
   Austin Texas 78750-3409 USA.
   Tel.: (512) 258-0785
   BBS:  (512) 258-8831
   FidoNet: 1:382/12
   Net: acw!info@uunet.uu.net


14b Metafoundry
   The Metafoundry offers several complete families of TeX fonts.  The main
   one on offer is  a sans serif which  is "lighter and more  compact" than
   the Computer Modern sans serif (CMSS) designed by Richard Southwell  and
   included in all TeX distributions.  It also includes math symbols,  math
   italic and extensible characters.

   Also offered are a decorative package, outline fonts, black letter fonts
   and a copperplate script font.

   The  fonts  are  supported  for  300dpi positive imaging machines (i.e.,
   Canon, HP, Apple and certain other laser printers.)

Terms of availablity:
   The fonts are distributed as bitmaps (not Metafont code) on a commercial
   basis.

Contact:
   For product catalogues send a cheque for $6 ($15 outside USA or  Canada)
   to:
   The Metafoundry,
   6565 Frantz Road,
   Dublin,
   Ohio 43017.


15. CYRILLIC

15a AMS
   The  American  Mathematical  Society  has  developed  a  post revolution
   Cyrillic font, in old  METAFONT78, and a set  of macros to implement  it
   comfortably.  Details of the font,  with examples of its use, and  grids
   of the character set were  published in TUGboat (somewhere about  issues
   #5--#7).  [Details to be filled in.]

Contact:
   Barbara Beeton,
   The American Mathematical Society,
   P. O. Box 6248,
   Providence, RI, 02940.
   Tel: (401) 272-9500
   Arpanet: bnb@xx.lcx.MIT.edu


15b MacKay

Date of information: Fri Jan 22 1988 (mail from Pierre MacKay)

   Pierre MacKay reports that the Washington team is working on Old Russian
   (more or  less Old  Church Slavonic,  but specifically  designed for the
   Slovo).

Contact:
   Phone: 206-543-6259; 545-2386.
   Net: MacKay@june.cs.washington.edu
   Address:
           Prof. Pierre A. MacKay,
           Northwest Computer Support Group,
           Univ. of Washington,
           Mail Stop DW-10, Seattle, WA 98195.

15c Metafoundry
   The  Metafoundry  offers  "a  Slavic  package  of  Cyrillic  and  slavic
   characters in Roman  and sans serif  styles compatible with  our English
   fonts."  The  fonts are supported  for 300dpi positive  imaging machines
   (i.e., Canon, HP, Apple and certain other laser printers.)
Terms of availablity:
   These fonts are  available on a  commercial basis, but  I don't remember
   the prices.  In the order of $100, I think.

Contact:
   The Metafoundry,
   6565 Frantz Road,
   Dublin,
   Ohio 43017.


16. CUSTOM FONTS

   If you are desparate  for a TeX font  which does not yet  exist, why not
   commission a Metafont programmer to create it?

   Neenie N. Billawala advertises her services as a METAFONT consultant  in
   TUGboat.  She is responsible for creating the fine calligraphic capitals
   that  are  part  of  the  Computer  Modern  typeface family (in the cmsy
   fonts).

   Billawala is also creating a new  typeface.  She has written a  Stanford
   Computer Science  Report (which  was still  "to appear"  in 1986) called
   _Meta-Marks: Preliminary Studies for a Pandora's Box of shapes_.   Knuth
   describes  this  study  as  "lavishly  illustrated  studies in parameter
   variation,  leading  to  the  design  of  a new typeface called Pandora"
   (_Computer Modern Typefaces_ (Reading etc., 1986), xiii).

Contact:
   Neenie Billawala,
   2014 Colony #8,
   Mt. View, CA 94043
   Tel: (415) 965-0643


18. BITSTREAM FONT FAMILY

Date of information: March 10, 1988

   In my view, one of the  most exciting developments in the area  of Latin
   script font  availability for  TeX has  been the  recent announcement by
   Personal TeX Inc., of the PTI Font Interface Package (FIP).  This is  an
   MS DOS  program that  converts the  outline fonts  of the Bitstream font
   library into .PXL (and then .PK) fonts, with associated .TFM files,  for
   use with TeX in a manner exactly analogous to the use of the CMR  fonts.
   The method of producing  the fonts is exactly  the same in principle  to
   using Metafont,  except one  has no  access to  the underlying character
   descriptions.  The FIP creates fonts at any desired point size between 6
   and 72 points and  above, and at any  resolution, from below 100dpi  for
   IBM PC  screens, to  over 1000dpi  for typesetters.   Optional  switches
   permit the adjustment of accents and letter spacing.  Furthermore, since
   the Bitstream font  outline files for  any given font  contain more than
   the 128 characters usual in  a TeX font, the extra  Bitstream characters
   can be generated in a complement font.  The Bitstream fonts generated by
   the FIP contain the same  characters as CMR10.  However,  equivalents of
   the math italic, math symbol and  extensible fonts of the CM family  are
   not  provided,  so  the  Bitstream  fonts  are  for  use  in typesetting
   predominantly textual  matter.   (One could,  of course,  mix the fonts,
   using Bitstream for the text and CM for the mathematics.)

   The  Bitstream  font  library  advertised  by  Personal  TeX  at present
   includes the following fonts, each consisting of a regular, an italic, a
   bold and a bold italic face:
   Bitstream Charter,
   Century Schoolbook,
   Courier,
   Dutch (i.e., Times Roman),
   Futura Book,
   Futura Light,
   Futura Medium,
   ITC Avant Garde Gothic,
   ITC Galliard,
   ITC Garamond,
   ITC Korinna,
   ITC Souvenir Light,
   Letter Gothic,
   Prestige,
   Swiss (i.e., Helvetica),
   Swiss Condensed,
   Swiss Light,
   Zapf Calligraphic, (i.e., Palatino)
   Zapf Humanist, (i.e., Optima)

   and a selection of Headline faces including
   Bitstream Cloister Black,
   Broadway,
   Cooper Black,
   University Roman.

   Bitstream's own publicity advertises several additional fonts, including
   Baskerville,
   Bitstream Cooper Light
   Goudy Old Style
   ITC Bookman Light
   ITC Garamond Condensed,
   News Gothic,
   Serifa.

   I assume that these fonts too  can be bought and installed for  use with
   TeX.
   Users  of  operating  systems  other  that  DOS  can  presumably use the
   Bitstream .PXL or .PK fonts (with .TFMs) once generated on a PC/AT, just
   by uploading them with, say, Kermit.


Quality
   A recent  discussion of  fonts in  _PC Magazine_  (March 15, 1988, issue
   #7.5, p.238) noted that  "Bitstream fonts are the  same ones you get  in
   already-generated form from H[ewlett] P[ackard], are widely (though  not
   exclusively) used in the printing  industry, and are used in  our Tengra
   galley-generating machine."  A useful article comparing Bitstream  fonts
   with Adobe  PS fonts  was published  in the  magazine _Publish!_  (March
   1988, issue #3.3, pp.46ff.).  It includes valuable illustrations of both
   manufacturers' fonts at several different resolutions.

   I myself have only experimented with the Dutch and Swiss fonts at  10pt,
   and then only on a 640x400 pixel screen, and at 240dpi on a 9-pin matrix
   printer.    On  both  these  devices  the  Bitstream fonts appear *much*
   superior to the  CM eqivalents (CMR10  and CMSS10).   The characters are
   somewhat broader, with relatively  rounder bowls and shorter  ascenders,
   and give a more even, regular appearance across the page.  They make the
   CM fonts look  very uneven by  comparison (I am  a great fan  of CM).  I
   suspect  that  the  CM  fonts  would  compare  more favourably at higher
   resolutions, since they  were not really  designed for such  poor output
   devices, and I suspect the Bitstream fonts were designed to be optimised
   for 300dpi and below.  (The Bitstream fonts are said to be excellent  on
   phototypesetters too.)

   The Bitstream  Font Interface  Package offers  TeX users  access for the
   first time to a proper font catalogue, and a highly professional one  at
   that.

Terms of availability
   The Installation Kit costs $195, and normally comes with the Swiss  font
   family  (one  can  make  a  special  request  to  have  the Dutch family
   instead).

Contacts:
   Personal TeX Inc.,                   Bitstream,
   12 Madrona Avenue,                    Athenaeum House,
   Mill Valley, CA 94941.                215 First Street,
   Phone: 415 388-8853                   Cambridge, MA 02142.
   Telex: 51060 10672 PCTEX              Phone: 617 497-6222
   Fax: 415 388-8865                     Telex: 467237
                                         Fax: 617 868-4632

20. HP2TEX (HP Font Conversion)

Date of information: March 11, 1988
   In February 1988 the uuencoded  .ARC file HP2TEX appeared on  USENET, in
   comp.text.  It included the Turbo Pascal 3.0 source code and a  compiled
   DOS version of HP2TEX,  a program to read  an HP soft font  and generate
   two files useful to TeX users, a PL and a PXL file.

   Since the  HP soft  fonts are  apparently generated  from the  Bitstream
   outline fonts  (see above),  this is  another way  to produce the latter
   family of  fonts.   However, the  TFM file  produced by  HP2TeX does not
   contain the information required to make ligatures, etc. (see below), so
   in practice, if real  quality is sought, it  would be better to  buy the
   FIP from PCTeX.

Usage:
   The HP2TEX program prompts the user for the names of the font files  for
   input and output, and also for the original design size of the HP  font,
   and its magnification (so that a 12pt HP font can make a 12pt PXL  font,
   or a 10pt PXL font magnified  \magstep1).  Names can be supplied  on the
   command line,  and will  be given  appropriate extensions  if necessary.
   The output is a  PXL font with its  associated property list (PL)  file.
   The PL file can be converted to a TFM file (with or without editing: see
   below) by the TeXware program PLtoTF (compiled DOS version available  on
   the PCTeX Bulletin board: 415 388-1708).  The PXL file can be left as it
   is, or converted to a smaller .PK file by PXtoPK (also on the same BBS).

   The PL file generated by  this program contains several parameters  that
   determine the appearance  of the TeX  output.  These  parameters control
   the interword glue, the space after a period, the size of a quad and  em
   space, and the parameters  determining accent placement.   The "correct"
   values for  these parameters  are NOT  contained in  the HP  soft fonts.
   They are estimated by HP2TEX, and might not be very good estimates.   If
   your output  is visually  bad, read  about font  dimen parameters in the
   back of the TeX book (or  Metafont book) and adjust their values  in the
   PL file.  Then  generate a new TFM  file.  The authors  not attempted to
   deal with kerns, although  you could add those  to the PL file  as well.
   Ligatures require the same action, assuming the ligature glyph is in the
   font at all.

   The authors note that certain fonts generated by GLYPHIX appear to
   convert with a bad underscore character that is far too low.  This is in
   fact how the underscore is encoded  in the font, not an artifact  of the
   conversion.

Terms of availability:
   HP2TEX was  written by  David Strip,  Albquerque NM,  with generous help
   from Dimitri L. Vulis of NYC. The program is copyrighted, and in keeping
   with the spirit of the TeX community, you are granted permission to copy
   and redistribute  it so  long as  you provide  the source  along and the
   README file along with any  executable. In addition, you may  not charge
   any fee in excess of the  actual cost of the media and  reasonable labor
   charges.  This charge may not exceed $3.00 per disk plus shipping costs.
Contact:
   David Strip
   arpanet: drstrip@sandia-2.arpa
   uucp: ....(ucbvax, cmu!rice, ihnp4!lanl, gatech)!unmvax!intvax!drstrip)
   Snail mail: 431 Camino de la Sierra NE
               Albuquerque, NM 87123

   Dimitri L. Vulis
   bitnet: dlv@cunyvms1.bitnet
   arpanet: dlv%cunyvms1.bitnet@cunyvm.cuny.edu)
   Snail mail: 529 W. 111 St. #61
               New York, New York 10025-1943

21. TELUGU

21a Lakshmi
Date of information:  March 11, 1988
   Recent  mail  from  Mukkavilli  Subbalakshmi  indicates her intention to
   implement a Telugu font in METAFONT.

Contact:
   CSNET:  lakshmi@iowa-state
   UUCP:    isucs1!lakshmi
   Snail mail: Ms. Mukkavilli V S Lakshmi,
               226 Computer Science,
               Iowa State University,
               Ames IA 50011.


21a Rao

Date of information:  March 11, 1988
   Recent  mail  from  K.  Sankara  Rao  indicates his similar intention to
   implement a Telugu font in METAFONT.

Contact:
   K. Sankara Rao
   Department of Electrical Engineering
   North Dakota State University
   Fargo, ND 58105
   BITNET:  nu043109@ndsuvm1


22. TIMES ROMAN in METAFONT

Date of information: March 10, 1988.

Source of information: TeXhax 1988, issue #22.

The font
   The author, Ian Kemmish, writes:
   I have a Times  font in Metafont which  I have been tinkering  with over
   the past  six or  seven months.   It  is modelled  on Monotype Times New
   Roman (visually - no callipers in sight!)  The standard of rasterisation
   is about comparable to a LaserWriter, but the typography is of necessity
   a lot more amateurish.  The regular font is largely OK, the italic is  a
   few weeks behind and  probably needs some tweaking.   There is a  rather
   lumpy semibold which needs parameter tweaking.  I suspect a genuine bold
   needs a new set of minusucule  routines.  I also have a  typewriter font
   generated from  it, and  am working  on a  Nebiolo Eurostyle  sans-serif
   font.  (I needed something easy after the Times!  I want to do Helvetica
   sometime soon.)

Terms of availability:
   Ian Kemmish writes:
   I'd be happy to  distribute what I have,  though I suspect my  employers
   would want to charge  something for it.   Ideally, I'd like to  send out
   some GF files  first to people  who are interested  in test-driving them
   and  can  make  constructive  comments  about  how to improve them.  The
   Metafont code is still  in a state of  flux.  I'd hate  to distribute it
   and have a lot of unco-iordinated changes being made to it all!


Contact:
   Ian Kemmish
   Whitechapel Workstations        UUCP:   ian@wcw.co.uk
   75 Whitechapel Road             OLDUUCP: ..!mcvax!ukc!wcwvax!ian
   London                          PHONE:  (+44) 01 377 8680
   E1 1DU                          FAX:    (+44) 01 247 4589
   England                         TELEX:  (UK) 885300 WCW G



23. ICELANDIC

Date of information: March 10, 1988

Source of information:
   TeXhax 1988, issue #22

The font:
   Jorgen Pind reports that he is running an unmodified TeX with new  fonts
   and formats (including hyphenation) which cater for Icelandic.

Contact:
   Jorgen Pind                 Internet: jorgen@lexis.hi.is
   Institute of Lexicography    uucp:  ...mcvax!hafro!rhi!lexis!jorgen
   University of Iceland
   Reykjavik 101   Iceland


------------------------------------------------------------------
Further information on several of the items mentioned above can be obtained
from the following publication:
   _Proceedings of the Eighth TeX Users Group Annual Meeting, Univesity  of
   Washington,  Seattle,  August  24--26,  1987_,  edited  by  Dean Gunther
   (Providence: TUG, 1988).

                 LIST OF PARTIES INTERESTED IN INDIC FONTS


   This memo started out as a collection of information specifically  about
   Indic fonts.   By the term  "Indic fonts" I  mean to include  Devanagari
   (with variants for Hindi, Marathi and Sanskrit), and fonts for  Bengali,
   Gujarati, Tamil,  Telugu, Kannada,  Malayalam, Sinhalese,  Urdu, Arabic,
   Persian, Kashmiri (Sharada) and Tibetan.

   The following  people would  be glad  to be  kept informed  of any  news
   concerning the development of Indic  METAfonts or any other Indic  fonts
   usable with TeX.

Dominik Wujastyk  DOW@Harvunxw.Bitnet or DOW@WJH12.Harvard.Edu (all)
Emma Pease        Emma@CSLI.Stanford.Edu (all)
Ajit Ranade       SO405000%BROWNVM.Bitnet@forsythe.Stanford.Edu (Devanag.)
Frans Velthuis    Velthuis@HGRRUG5.Bitnet (Devanagari)
Pierre MacKay     MacKay@june.cs.Washington.Edu (Arabic, all)
Michael Inman     minman@csli.stanford.edu (all)
Steven Osborne    osborne@unb.bitnet (Greek)
T. K. Rengarajan  ranga%debit.DEC@decwrl.dec.com  (Tamil)
M. V. S. Lakshmi  CSNET: lakshmi@iowa-state UUCP: isucs1!lakshmi (Telugu)
K. Sankara Rao    nu043109@ndsuvm1.BITNET (Telugu)


   These individuals are already in  touch with each other through  TeXhax,
   and/or person-to-person.   If you wish  to add your  name to this  list,
   which is maintained  by Dominik Wujastyk,  please send him  your network
   (or other) address.

Dominik Wujastyk
Until July 1988:
   Quincy House #101,
   Cambridge, MA, 02138, USA,

Thereafter:
   Wellcome Institute,
   183 Euston Road,
   London NW1 2BP, England.

---------------------------------------------------------------------

                                   INDEX



1. DEVANAGARI
2. TAMIL
3. MARATHI
4. ARABIC
5. OCR-A
6. CLASSICAL AND MODERN GREEK
7. JAPANESE
8. CHINESE
9. TURKISH
10. INTERNATIONAL PHONETIC ALPHABET
11. SPRITE.STY
12. ELVISH
13. HEBREW
14. MISCELLANEOUS FONT COLLECTIONS
15. CYRILLIC
16. CUSTOM FONTS
18. BITSTREAM FONT FAMILY
20. HP2TEX (HP Font Conversion)
21. TELUGU
22. TIMES ROMAN in METAFONT
23. ICELANDIC
                 LIST OF PARTIES INTERESTED IN INDIC FONTS


---------------------------------------------------------------------
             "I am food, I am the eater of food" -- Upanishad
                                  eat me
                                  eat me
                                  eat me
                                  eat me
                                  eat me
                                  eat me
                                  eat me
                                  eat me
                                  eat me
                                  eat me
                                  eat me
