Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!usc!ucsd!ucbvax!CC.USU.EDU!KMILES
From: KMILES@CC.USU.EDU ("Kurt Miles, VAX Consultant")
Newsgroups: comp.sys.apple
Subject: RE: AppleWorks 3.0 bugs
Message-ID: <8911211645.AA00306@apple.com>
Date: 21 Nov 89 15:43:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 80


>Has anyone else noticed the bugs in AppleWorks 3.0's word processing
>module?  Not the small ones, like usualy going to the beginning of the
>file whenever you insert a "new page" using ctrl-p, but the serious
>pagination problems?
> 

Yes.  


>For example, I typed an outline earlier this week.  Each number or letter
>in the outline was 3-5 lines long.  Each one started with the appropriate
>number of tabs, and was indented so that the second line of text wrapped
>around and lined up after the period and space of the header.  Each
>page after the first had a header of "right justify, print page number,
>unjustified".  I used 10 chars. per inch.
>

I didn't start each page with printing instructions, but I had the problem of
an indented line having a return put in at a page break, and then the first
line (should have been indented) was not indented on the next page, although
following lines were.  Apparently, AW3.0 sees the inserted return as a signal
not ot indent the next line.  if you make an edit anywhere so that the
pagination dissapears, the indent reappears.
 
> 
>Well, when it came time to paginate the document, various things happened
>on various pages (it was 14 pages long).  On most pages, the line
>ended in the middle.  That is, rather than having the last line on the
>bottom of the page end at the right margin, there was an extra word
>or three on the next line.  These extra lines were indented to the proper
>place, but the extra part of the line didn't belong on the page (the
>last full line was about 1" from the bottom of the page).  The first
>line of the next page started properly indented.
> 
My problem was carrying two or three words into the footer area, missing the
bottom margin command, and then putting in a return and new page.  The first
lin of the next page was shorter than it should be, by those two or three
words, and then the following lines were ok, till the bottom of the page,
again.

 
>	[paras deleted]

 
>This is really getting to annoy me.  I have to inspect each page as
>it comes off the printer so that it has the correct margins, etc.
>If not, I have to insert RETURNS or new page codes so that it comes
>out right.  This really gets to be annoying and wasteful even with
>moderately sized papers (10-15 pages), as I might wind up printing
>20-30 pages.
> 

I agree.  I have having to print a paper two or three times to get it right.


>I am using the standard ImageWriter // print driver (although the
>same problems occur using the normal ImageWriter driver).
> 

I am using the EPsom driver from the original disks for both the Applewoorks
and systems disks.


>I am not a novice at AppleWorks, having started out at 1.3 and upgraded
>each step of the way.  I have typed several thousands of pages of
>papers using AppleWorks in the past few years (I type papers on
>campus to help pay for college).  These appear to be bugs in 3.0.
> 

Me also, only I started with 2.0.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Kurt Miles                   |      GreyMan ------>    and the    <----- DRAGON 
KMILES@USU (Bitnet)          |      ...... remember, sometimes the DRAGON wins!
KMILES@CC.USU.EDU (Internet) |                                     ------
-------------------------------------------------------------------------------
Doctoral Student in Instructional Technology at Utah State University
"Dissertation?   Doesn't that come after dinner?  I like strawberry shortcake"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^