TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: MSWord problem From:"harold (h.o.n.) floysvik" <hal -at- BNR -dot- CA> Date:Fri, 9 Dec 1994 11:03:00 -0500
Time for a new term. A few years ago, one of our guys coined the expression
WYGINS -- What You Get Is No Surprise. I tried using it for a while but
nobody seemed to want to acknowledge there is no such things as WYSIWYG
when trying to use a low resolution medium (the screen) to represent a
high resolution medium (300 dpi plus on paper).
On second thought, WYGINS probably won't cut it either because we still get
surprises. How about WYGINBS (Big Surprise) or WYGICE (Is Close Enough).
In message "MSWord problem", Arlen -dot- P -dot- Walker -at- JCI -dot- com writes:
> Re: Margaret, I have experienced these problems before. I finally
realized
> Re: that this is sometimes what I'd like to call a WYSIWYG problem. I'll
> Re: explain further:
> Re:
> Re:Remember the definition of WYSIWYG: What You So Intensely Wish You'd
Gotten.
> Re:
> Re:I haven't seen this in a lot of packages (just Word and Aldus Persuasion)
but
> Re:I've wondered about it. Have you noticed that Print/Preview typically takes
> Re:significantly longer to draw the screen than the Page View does? That seems
to
> Re:indicate to me that they're cutting corners in the display code for Page
View
> Re:for the sake of speed. Before you criticize this decision, think of how
you'd
> Re:feel if every page in your WP took as long to display as it does in P/P.
> Re:
> Re:I've taken to using P/P as "*real* Page View" and only using Page View as a
> Re:rough guess on how the doc will look.
> Re:
> Re:
> Re:Have fun,
> Re:Arlen
> Re:Chief Managing Director In Charge, Department of Redundancy Department
> Re:DNRC 24
> Re:
> Re:Arlen -dot- P -dot- Walker -at- JCI -dot- Com
> Re:----------------------------------------------
> Re:In God we trust; all others must provide data.
> Re:----------------------------------------------
> Re:
> Re:What you see on the screen is never (really) what you actually see in
print.
> Re:I have found that it SEEMS like you have more room (or, in your case, it's
> Re:getting cut off at the bottom--and that seems to be peculiar), but you
really
> Re:don't. Sometimes, if I go to the "Print Preview" display option, I will
see
> Re:that I really don't have that room left that I thought was there.
> Re:
> Re:
> Re:Has anyone else on techwr-l experienced such problems with displays that
> Re:aren't WYSIWYG? I've also found that that (most) word processors that I've
> Re:used are NOT WYSIWYG, which I'm beginning to think is a BIG problem within
the
> Re:industry.
> Re:
> Re:Just sign me:
> Re:Troubled with WYSIWYG
> Re:
> Re:Bill Hartzer (william -dot- hartzer -at- emc2-tao -dot- fisc -dot- com)
> Re:Technical Writer, Fischer International Systems Corporation
> Re:Naples, Florida USA
> Re:
> Re:P.S. It's 69 degrees here this morning!!!!
> Re:
