jetzer@studsys.mu.edu (Mike Jetzer) (11/19/89)
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? 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. 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. On one other page, there was *no* bottom or top margin (I use the default 0" top, 2" bottom margin). The text just went on, there was a line with the page number, and the rest of the page. On a different document, this one done in proportional-1, I had the same problem of having extra words in the first line of what should have been the bottom margin. On another different document, this one with a number of superscript begins and ends, and a few underlined words, the pagination on the screen was *totally* different from what showed up on paper. The paper was supposedly 16 pages long, when in reality it was 16 1/2. The last line on the first page (on the screen) was actually the first line on the second page. Just about every page on the screen was one line longer than it should have been. Therefore, the last two lines on the second page were actually the first two on the third page, the last three on the 3rd were the 1st 3 on the fourth, etc. 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 am using the standard ImageWriter // print driver (although the same problems occur using the normal ImageWriter driver). 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. On another note (ie., not just complaining), how would I best go reporting these bugs to Claris? Send them a disk full of paginated files with which I have problems and a cover letter explaining what's wrong with each? (Will this even matter? I doubt that they even have all the upgrades sent out for 3.0, much less having them come out with 3.1 any time soon.) -- Mike Jetzer "Hack first, ask questions later."
saa33413@uxa.cso.uiuc.edu (11/20/89)
I've found some bugs in 3.0 also. I started out by making a "custom" Image- writer. I added more CPI codes (semicondensed, ultracondensed, 18 and 20 CPI for use with downloadable fonts, etc.), switches between the German and Amer- ican character sets (I do some homework for German on my IIe), and a graphic Open-Apple character (I don't have an Imagewriter II). I wrote a letter one day and set it in full justification--as I normally do. AW 3.0 chose to disregard the platen width setting (8.0) and the right margin setting (0.7) and spit out text for a full 8 inches. This meant that the printer spit out most of a line and tacked on the rest of it before the begin- ning of the line. Either I can (1) use full justification or (2) get 20 CPI, German, and Open-Apple. I can't get both. ------------------------------------------------------------------------------- ! Scott Alfter ! Go ! McCoy: ...they don't exactly like you. ! ! alftersoft@uiuc.edu ! Illini ! Kirk: I know, Bones. The feeling's mutual. ! -------------------------------------------------------------------------------
jazzman@claris.com (Sydney R. Polk) (11/21/89)
From article <687@studsys.mu.edu>, by jetzer@studsys.mu.edu (Mike Jetzer): ( ... lots of AppleWorks 3.0 bugs deleted ...) > On another note (ie., not just complaining), how would I best go reporting > these bugs to Claris? Send them a disk full of paginated files with > which I have problems and a cover letter explaining what's wrong with > each? (Will this even matter? I doubt that they even have all the > upgrades sent out for 3.0, much less having them come out with 3.1 > any time soon.) > > -- > Mike Jetzer > "Hack first, ask questions later." I will pass these on to the correct people here. -- Syd Polk | Wherever you go, there you are. jazzman@claris.com | Let the music be your light. GO 'STROS! | These opinions are mine. Any resemblence to other GO RICE! | opinions, real or fictitious, is purely coincidence.
KMILES@CC.USU.EDU ("Kurt Miles, VAX Consultant") (11/21/89)
>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" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^