Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!pasteur!cory.Berkeley.EDU!fadden
From: fadden@cory.Berkeley.EDU (Andy McFadden)
Newsgroups: comp.sys.apple
Subject: Re: Writing a Custom FST
Summary: Yeah, right
Message-ID: <17037@pasteur.Berkeley.EDU>
Date: 10 Sep 89 22:19:11 GMT
References: <8909092140.AA18977@trout.nosc.mil>
Sender: news@pasteur.Berkeley.EDU
Reply-To: fadden@cory.Berkeley.EDU.UUCP (Andy McFadden)
Organization: University of California, Berkeley
Lines: 35

In article <8909092140.AA18977@trout.nosc.mil> lhaider@pro-sol.cts.com (Lawrence Haider) writes:
>Network Comment: to #10844 by dlyons@apple.com
>
>>the policy on FSTs is that Apple writes them all.  (Dave Lyons)
>
>If Apple must write all of the FSTs, why are they so slow in providing a
>decent collection of FSTs that would be useful for their end users.  Just the
>basics for MS-DOS and Mac file system translation would be more than useful
>for anyone (like me) who must use more than just the //gs in their day to day
>business and personal lives.

The Apple //gs is very low in priority for most of Apple, and FSTs are low
priority among Apple developers.  We should either have FSTs or something
like that File Exchange program for the Mac, but this continues the MPW
tradition of requiring a Macintosh to do an serious development work for the
Apple //gs.

>Let's either get Apple to provide some decent FSTs to the users or let the
>users make it themselves.

Somebody wanted to do this, but was told in no uncertain terms that not only
would he not be able to get information, but that it was not advisable to do
so.  I'm beginning to care very little about what Apple considers advisable.
If somebody out there can figure out how to write a DOS 3.3 or Mac HFS FST,
DO IT.  I'm tired of empty promises.

If there's some problem with compatibility later on, we can probably deal
with it.  Distribute them with the disclaimer that use of these may cause
problems later on, but *distribute them*!!!

>                                        Laer

-- 
fadden@cory.berkeley.edu (Andy McFadden)
...!ucbvax!cory!fadden