LINGUIST List 4.734

Tue 21 Sep 1993

FYI: Computer Resources

Editor for this issue: <>


Directory

  1. "Charles A. Bigelow", phonetic fonts
  2. debbie mandelbaum, Mac Fonts
  3. John Cowan, Re: FYI: Printing Postscript Files

Message 1: phonetic fonts

Date: Sat, 18 Sep 93 12:46:28 PDphonetic fonts
From: "Charles A. Bigelow" <bigelowCS.Stanford.EDU>
Subject: phonetic fonts

Over a year ago, I announced that I would make free copies of Lucida Sans
phonetic fonts available tolinguists. I have received many requests, but
unfortunately have only sent fonts to about half of them. To those who have not
yet received fonts, I apologize. The reason for the delay is fairly simple -
I have too much other work and more pressing (for me) obligations, and the task
of organizing the font distribution has fallen through the cracks.

However, I would still like to see our phonetic fonts be distributed. So, if
there is anyone who would volunteer to take over the task of distributing the
fonts, whether by e-mail, anonymous ftp, mail, or whatever, I would be happy to
send diskettes of the various fonts to such custodians.

Currently available are two fonts in two formats:

IPA - layout similar to that used by SIL

Lucida Sans Phonetic Alternate - various additional characters, including
 Americanist symbols, discontinued IPA symbols etc

The formats are: unhinted Type1, unhinted TrueType

Users can use programs like Fontographer or Font Monger to remap the character
layouts.

 -- Chuck Bigelow
Mail to author|Respond to list|Read more issues|LINGUIST home page|Top of issue

Message 2: Mac Fonts

Date: Fri, 17 Sep 93 17:11:26 EDMac Fonts
From: debbie mandelbaum <IDMGCCUNYVM.CUNY.EDU>
Subject: Mac Fonts

I am writing in response to Bill Bennett's question about Mac fonts,
since he needs to be able to create his own IPA/nonIPA symbols. There
is software available for this purpose, such as Fontographer 4.0;
there are others besides Fontographer available for the Mac as well.
Mail to author|Respond to list|Read more issues|LINGUIST home page|Top of issue

Message 3: Re: FYI: Printing Postscript Files

Date: Tue, 31 Aug 1993 13:38:21 Re: FYI: Printing Postscript Files
From: John Cowan <cowangvls1.VFL.Paramax.COM>
Subject: Re: FYI: Printing Postscript Files

***************************************************************************
The following program, written in C, will strip out most of the gibberish
from a Postscript file, for those of us who do not have Postscript printers.
Not all Postscript files work, but those generated by TeX and its variants
usually work pretty well. The main limitation is that erratic spaces are
put into the text, mak ing it loo k li ke t his , w hic h is anno ying.
Compile the program with any decent C compiler (ANSI or K&R) and then
it serves as a filter, reading Postscript from the standard input and
writing "AS CII" to the standard output. If a command line argument is given,
it is used instead of the standard input. This program works fine on Unix and
MS-DOS systems, and probably would work fine on Amigas, Macs, and VMS as well.
****************************************************************************

include <stdio.h>

main(argc,argv)
int argc;
char **argv;
 {
 int ch;
 int string = 0;
 int nlLast = 1;

 if (argc == 2) freopen(argv[1], "r", stdin);
 while ((ch = getchar()) != EOF)
 switch (ch) {
 case '\\':
 ch = getchar();
 if (ch != '0') {putchar(ch); continue;}
 ch = getchar();
 if (ch != '1') {putchar('0'); putchar(ch); continue;}
 ch = getchar();
 switch (ch) {
 case '3': printf("ff"); break;
 case '4': printf("fi"); break;
 case '5': printf("fl"); break;
 case '6': printf("ffi"); break;
 case '7': printf("ffl"); break;
 default: putchar('0'); putchar('1'); putchar(ch);
 }
 break;
 case '\n':
 if (!nlLast) putchar(ch);
 nlLast = 1;
 break;
 case '(':
 string = 1;
 break;
 case ')':
 string = 0;
 putchar(' ');
 nlLast = 0;
 break;
 default:
 if (string) {
 putchar(ch);
 nlLast = 0;
 }
 break;
 }
 }

 --
John Cowan cowansnark.thyrsus.com
 ...!uunet!lock60!snark!cowan
 e'osai ko sarji la lojban.
Mail to author|Respond to list|Read more issues|LINGUIST home page|Top of issue