Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!ut-emx!ccwf.cc.utexas.edu
From: clouds@ccwf.cc.utexas.edu (Kathy Strong)
Newsgroups: comp.fonts
Subject: Re: Changing Fonts in Microsoft Word
Message-ID: <40285@ut-emx.uucp>
Date: 28 Nov 90 04:27:21 GMT
References: <90328.221839SXS144@psuvm.psu.edu> <40137@ut-emx.uucp> <40214@ut-emx.uucp> <6176@mace.cc.purdue.edu>
Sender: news@ut-emx.uucp
Reply-To: clouds@ccwf.cc.utexas.edu (Kathy Strong)
Lines: 30

In article <6176@mace.cc.purdue.edu> nvi@mace.cc.purdue.edu (Charles C. Allen) 
writes:
>> The tab character takes you to the next tab stop...
>
>I'd just like to point out that this behavior (shared by, at least,
>MacWrite II and FullWrite) is incorrect by typesetting standards.  The
>first tab should take you to the first tab stop, the second to the
>second tab stop, etc., not the "next" one if the insertion point is
>already beyond that.  In that case, the insertion point should not be
>advanced at all.  FrameMaker handles this correctly.
                                           ---------

Well, Charles, I'd just like to remind you of how many of us use word
processing packages, versus how many of us are typesetters.  :-)  In fact,
the "tab key takes you to the next stop" convention dates from the days
of manual typewriters, and every word processing package that I know of
does it that way.

I make no claims one way or the other about the validity of this convention--
just want to point out that about 95% of us would find your convention
non-standard.  :-)

--K

-- 
...........................................................................
:   Kathy Strong               :  "Try our Hubble-Rita: just one shot,     :
:  (Clouds moving slowly)      :   and everything's blurry"                :
:   clouds@ccwf.cc.utexas.edu  :                           --El Arroyo     :
:..........................................................................: