roger Symons

Q: Spreadsheet cell contents overflow when printed.

The contents of a "just full" cell in an AppleWorks 6.2.9 spreadsheet will frequently overflow when printed. It appears that the displayed font is not the same as the selected font; what you see is not what you get! 

However, if you Print…Preview then you do see the selected font, and any potential cell overflow.  Then you have to go back and increase the cell size and Preview again - a process of trial and error.

This is tedious.   Any ideas, anyone?

Posted on Jul 3, 2013 4:11 AM

Close

Q: Spreadsheet cell contents overflow when printed.

  • All replies
  • Helpful answers

  • by Roger Wilmut1,

    Roger Wilmut1 Roger Wilmut1 Jul 4, 2013 1:27 AM in response to roger Symons
    Level 9 (78,510 points)
    iTunes
    Jul 4, 2013 1:27 AM in response to roger Symons

    I can't reproduce this fault. I tried several different fonts and sizes, adjusting the column width to just accommodate the text, and Preview shows it correctly in each case. Have you got a printer which uses font substitution? This can cause oddities. Also, do you get this with different fonts or only the default Geneva?

  • by roger Symons,

    roger Symons roger Symons Jul 7, 2013 4:59 AM in response to Roger Wilmut1
    Level 2 (184 points)
    Desktops
    Jul 7, 2013 4:59 AM in response to Roger Wilmut1

    I agree that Preview correctly shows how the printout will appear.

    But this trial and error should not be necessary; what you see in your draft should be what you get!

    I am not using the default Geneva; again, this should not be necessary; nowhere does AppleWorks help say that you should draft your spreadsheet in Geneva font in order to guarantee an accurate printout!

  • by Roger Wilmut1,

    Roger Wilmut1 Roger Wilmut1 Jul 7, 2013 8:31 AM in response to roger Symons
    Level 9 (78,510 points)
    iTunes
    Jul 7, 2013 8:31 AM in response to roger Symons

    As I say, I tried with several fonts and had no problems.  I've seen this sort of thing in the past with a printer which supplied its own fonts, which it substituted when the printing was done - there could be tiny differences which could cause issues like this. I don't know whether any modern printers to this. Otherwise I can't see why this should be happening - it's certainly not normal.

  • by Barry,

    Barry Barry Jul 11, 2013 12:47 AM in response to roger Symons
    Level 7 (32,714 points)
    iWork
    Jul 11, 2013 12:47 AM in response to roger Symons

    Hi Roger,

     

    You wrote:

     

    "...should be what you get!

    ...should not be necessary;

    nowhere does AppleWorks help say..."

     

    Plese remember that AppleWorks Help (for vrsion 6.2.9) was last edited circa 2004. AppleWorks was declared EOL in 2007. The EOL designation meant the application would no longer be sold or supported by Apple (although actual deveopment had ended well before that.

     

    Print operations, handled by the operating system, have changed greatly since 2004, and it's not surprising that there are issues with presentation of type (both on the screen and on paper) when using legacy software on more current coputers. With each new version of OS X that was introduced, AppleWorks and the new OS became less compatible. With OS X v10.7 (Lion), AppleWorks (and all other PPC based applications) ceased working altogether.

     

    "should be" and "should not" as used in your post are outside the purview of this user-to-user forum. The people in the forum are users, not developers. They deal with the application as it exists, and have no control or influence over how it "should be."

     

    For current applications, the Feedback channel, fould in the application menu (the one between the Apple and File on the menu bar) is the one to use to send 'should be' suggestions to Apple and to the application's developers.

     

    AppleWorks 6.2.9 is the last version of AppleWorks. It has served well, but it is what it is, and it will not change from that. It will run on your current computer, provided your OS X version is Snow Leopard or earlier, but will not run on Lion, Mountain Lion, or any newer version of OS X. If you have valuable data in AppleWorks files, you should be saving copies of those files in formats that can be opened by other (current) applications, and you should be doing that NOW, not later.

     

    Regards,

    Barry

  • by MlchaelLAX,

    MlchaelLAX MlchaelLAX Jul 11, 2013 10:08 AM in response to Barry
    Level 4 (2,256 points)
    Jul 11, 2013 10:08 AM in response to Barry

    Barry:

     

    You do realize that Roger has written the definitive internet treatise on Abandoning Appleworks:

     

    http://www.wilmut.webspace.virginmedia.com/notes/aw/page1.html

  • by Roger Wilmut1,

    Roger Wilmut1 Roger Wilmut1 Jul 11, 2013 10:13 AM in response to MlchaelLAX
    Level 9 (78,510 points)
    iTunes
    Jul 11, 2013 10:13 AM in response to MlchaelLAX

    I didn't post that link because the OP wants to get it to work properly rather than abandon it. I suspect that it's something odd within his system, because I can't reproduce the fault with the same operating system.

     

    On the other hand, of course, AppleWorks is dead in the water as soon as you go beyond Snow Leopard. Roger: if you have only one computer with Snow Leopard and one day it goes phut, then when you replace it you will lose access to some of your AW documents, particularly databases. It's something to be thinking about in the long term.

  • by MlchaelLAX,

    MlchaelLAX MlchaelLAX Jul 11, 2013 10:16 AM in response to Roger Wilmut1
    Level 4 (2,256 points)
    Jul 11, 2013 10:16 AM in response to Roger Wilmut1

    [As you well know]: Appleworks on life support in Lion/Mt. Lion:

     

    Appleworks in SLS.png

    TOP SIX.jpg

                                  [click on images to enlarge]

     

    http://forums.macrumors.com/showthread.php?t=1365439

  • by Barry,

    Barry Barry Jul 11, 2013 9:37 PM in response to MlchaelLAX
    Level 7 (32,714 points)
    iWork
    Jul 11, 2013 9:37 PM in response to MlchaelLAX

    Hi Michael,

     

    I do, but I had forgotten I had that artice bookmarked. Thaks for posting the link.

     

    Regards,

    Barry