Electronics Repair (sci.electronics.repair) Discussion of repairing electronic equipment. Topics include requests for assistance, where to obtain servicing information and parts, techniques for diagnosis and repair, and annecdotes about success, failures and problems.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1   Report Post  
Posted to sci.electronics.repair
external usenet poster
 
Posts: 3,469
Default Word as a publishing program

Sorry for reviving an old, dead thread, but I ran across something I'd
like to respond to. In a thread entitled "Which Os is better among the
Windows Vista", William Sommerwerck wrote, regarding Microsoft Word:

Excuse while I roll on the floor laughing.

Microsoft might want us to _think_ Word is a DTP, but it's anything but.
It's an excellent word processor that has been tarted up with features that
give the illusion -- to the ignorant -- that it's suitable for DTP.

I cut my DTP teeth with the "original" Ventura Publisher, versions 2 and 3,
almost 20 years ago. Those "primitive" versions, which ran under GEM
(Graphics Environment Manager) utterly and totally blow away the current
versions of Word (and, I assume, WP and other word processors) for producing
long, complex documents. * And they're actually easier to use, because they
give you direct control over what you're doing, rather than automating it.

Word has major flaws that make it virtually useless for complex documents,
and even for a lot of simple ones. The worst of these is its unstable image
placement. You cannot insert an image, then expect it to either remain where
you put it, or move the way you want with the text flow. Last year I spent
several hours in a largely unsuccessful attempt to organize the graphics in
a co-worker's document. Once I got it "right", adding text or new images
caused the exisiting images to irrationally shift position, which then
required starting over.

Another problem is that, though Word can create TOCs pretty much by the user
saying "Put a TOC here", TOC formatting is unstable, and often requires
manual alterations to make the TOC look the way you want.

No one at Microsoft seems to care about these problems. And they're not
new -- I was complaining about some of them over a decade ago. For example,
there's a bug that causes Word to spontaneously switch to automatic
repagination for no obvious reason. This bug has persisted across the last
four or five versions.


I'd like to challenge that by saying that Microsoft Word *can be* a
quite usable desktop-publishing program, in fact a very powerful and
flexible one.

That is not to say that it's not without major problems. But let me tell
my story:

I worked for a company as a technical writer, producing user manuals
among other things. Full-blown, long manuals. I started out using
Ventura Publisher, the old GEM versions that you described above. It
worked OK, and at the time was really the only thing available (for the
PC, at any rate) that would even do the job I needed to do.

Then Ventura decided to Windows-ize the program. You probably remember
this. Without wasting too many words on the subject, they basically
broke it beyond recognition. I remember throwing my hands up in despair;
the new version sucked so badly that it was unusable.

I have a minor claim to fame, in that the owner of the company I worked
for was friends with Rick Altman, who you may remember as the Ventura
"guru"; Rick published several books and software add-ons for VP. I was
actually able to talk to the guy. I don't think he liked me very much,
because I basically vented upon him my utter frustration with the
abominable new version. He did agree with me on most of the complaints I
had, but of course he was pretty powerless to do anything about it.

Anyhow, to make a long story less long, this began my search for another
tool to write my manuals with. We briefly toyed with PageMaker: another
utter failure. Sure, you could coax a long document out of it, but it
was a pain in the ass. (Just one example: tables in PM are embedded
objects, not native, so anytime you want to change anything in a table,
you basically have to invoke a whole 'nother application, edit the
table, save it, then re-embed it in the document. No thanks!)

Because of my antipathy to all things Micro$oft, it hadn't even occurred
to me to try Word, and I had simply assumed that it wouldn't cut the
mustard. I don't remember how I ended up using it; probably total
frustration at every other available publishing program drove me to it.
In any case, after getting over my initial distaste for it, I discovered
that not only could it do everything I had done with Ventura, but it
could do many things better, and it could do a lot of things VP couldn't do.

The latter category includes such things as text references, like "for
more information, see _______ on page X". With VP, I had to do these by
hand; I put in the text, replacing the page number with a certain
string, then when I got ready to print the manual, I'd go through the
document with a seach and replace, find the referenced page number by
hand, and type it in.

Pain in the ass! With Word, I could insert a bookmark in the text. Then
when it came time to print, I simply did the "update fields" command,
and voila! instant page numbers.

Before I go too far, I should acknowledge that Word does indeed have
many, many flaws. You talked about "unstable image placement"; how about
images disappearing entirely? For an extreme example, imagine you have a
120-page document with hundreds of images in it, as mine did. Then
imagine opening your document to work on it and discovering that each
and every image had been replaced by a red frame with a big red "X"
through it!

This did happen to me, but it was with an older version of Word (pre-97,
forget which one exactly) that also had bad problems handling EPS
images, which I used extensively. But these problems were fixed in the
next release.

Regarding your experiences with image placement, it's true that images
can be a bitch to position correctly, and can move mysteriously. But it
turns out that this behavior is correctable. The problem is that most
people don't know how to correct it, and that the default,
out-of-the-box settings can cause this kind of behavior.

Out of the box, Word is *not* ready for handling long documents. But it
can be tamed. The first thing I do upon installing Word is to go through
the option settings and, for the most part, disable all the automatic
crap that causes so many problems. Things like autoformatting tables,
bullets, etc.; automatic text substitution (although I do like a few
things here, like turning "--" into real typographic em dashes,
formatting fractions, a few other things). I certainly don't want Word
turning things like "(O" into smiley faces, or inserting hyperlinks for
URLs or email addresses. All this is settable through the Options dialog.

But I have to say that I came to respect Word's functionality for
creating long documents, including tables of contents, indexes, tables
and cross-references. Its use of "styles" for global formatting is
extremely powerful and sensible, and helps immensely in long document
creation. (Pity 99% of Word users have no idea how to use styles: ever
tried to "fix" a document where people changed fonts, boldface, etc.,
every other word or so, inserted tabs to format text, used dashes to
create tables?)

A very useful skill in using Word is knowing what doesn't work and
either staying away from it or working around it. I never had the
problems with automatic pagination you described (maybe you were using
an earlier version that me: I used 97 for a long time, now use 2000),
but there are lots of things that don't work as well as they should or
just plain don't work at all. But for the most part, its features work
well enough to make it an appropriate tool for long documents.

One thing I wanted to do but never could make work was master documents
and subdocuments, which would have been nice, as my manuals were divided
into chapters. I never did determine if this facility even worked at
all, and just gave up. It made for very large (multi-megabyte)
documents, but they were still manageable.

I'd summarize Word by saying it's an extremely powerful program (you
might not realize just how powerful it is until you start playing with
VB and macros) with a very badly-designed user interface that is quite
suitable for documents of any length.


--
Made From Pears: Pretty good chance that the product is at least
mostly pears.
Made With Pears: Pretty good chance that pears will be detectable in
the product.
Contains Pears: One pear seed per multiple tons of product.

(with apologies to Dorothy L. Sayers)
  #2   Report Post  
Posted to sci.electronics.repair
external usenet poster
 
Posts: 3,833
Default Word as a publishing program

Then Ventura decided to Windows-ize the program. You probably
remember this. Without wasting too many words on the subject,
they basically broke it beyond recognition. I remember throwing
my hands up in despair; the new version sucked so badly that it
was unusable.


That's odd, because I never had problems with the 4.x versions.


Anyhow, to make a long story less long, this began my search
for another tool to write my manuals with. We briefly toyed with
PageMaker: another utter failure. Sure, you could coax a long
document out of it, but it was a pain in the ass.


PageMaker is ideal for producing highly irregular (unstructured) documents,
of any length. It is not a good choice for "structured" documents that need
TOCs, cross-references, etc. For that purpose, it's pretty much without
equal and very easy to learn and use. It's a shame it's no longer in print.
I consider it a classic piece of software -- like the House of Peers, it
doesn't do very much, but it does it very well.


Because of my antipathy to all things Micro$oft, it hadn't even occurred
to me to try Word, and I had simply assumed that it wouldn't cut the
mustard. I don't remember how I ended up using it; probably total
frustration at every other available publishing program drove me to it.
In any case, after getting over my initial distaste for it, I discovered
that not only could it do everything I had done with Ventura, but it
could do many things better, and it could do a lot of things VP couldn't

do.

I don't know which version of Word you're talking about, but it's not any
I've ever seen. I know of nothing that Word can that VP cannot. At least,
not in earlier versions.

If I had to choose between the current version of Word (2007), which is an
excellent word processor (I especially like the ribbon), and v3 of Ventura,
running under GEM, to produce a complex document, I wouldn't have to think
for a microsecond as to which I'd use.


The latter category includes such things as text references, like "for
more information, see _______ on page X". With VP, I had to do these
by hand; I put in the text, replacing the page number with a certain
string, then when I got ready to print the manual, I'd go through the
document with a seach and replace, find the referenced page number
by hand, and type it in.


I don't know which version of VP you were using, but once you've entered the
page-number tag, Ventura completely automates computing and inserting the
cross references. IT ALWAYS HAS.


Before I go too far, I should acknowledge that Word does indeed have
many, many flaws. You talked about "unstable image placement"; how
about images disappearing entirely? For an extreme example, imagine
you have a 120-page document with hundreds of images in it, as mine
did. Then imagine opening your document to work on it and discovering
that each and every image had been replaced by a red frame with a big
red "X" through it!


In fairness, the 2007 version of Word no longer has unstable image
placement. But the ability to exactly position an image, and more
importantly, to control its spacing from the text, is one of VP's strong
points.

The problem with Word is that it was never intended to produce long, complex
documents, whereas VP was. Word's "enhancements" in this regard only make it
clunkier. As Word has made certain operations -- such as heading
numbering -- more and more automated, they have become increasingly
difficult to use. Worse, formatting can become corrupted in startling and
unbelievable ways that make it impossible to change the formatting without
moving the text to an empty document. This simply does not occur in VP.

The beauty of VP is that it /doesn't/ automate things that are easy to do by
hand -- such as specifying how you want a heading numbered.

If the PM for Word were someone who was actually a professional writer, Word
would quickly and drastically improve. I have no idea who the current PM is,
but whoever it is is an utter idiot.

One of the startling problems with Word, which has existed from at least the
first Windows version, and has never been corrected, is that the default
paragraph spacing is 0 points. This leads to ignorant users (ie, 99% of
users) putting double carriage returns between lines. The resulting
documents are usually a mess.


But I have to say that I came to respect Word's functionality for
creating long documents, including tables of contents, indexes, tables
and cross-references. Its use of "styles" for global formatting is
extremely powerful and sensible, and helps immensely in long document
creation. (Pity 99% of Word users have no idea how to use styles: ever
tried to "fix" a document where people changed fonts, boldface, etc.,
every other word or so, inserted tabs to format text, used dashes to
create tables?)


VP uses styles, too. Indeed, they are weirdly similar to XML tagging.

If I were teaching a class in Word, the first thing I'd teach (after showing
the students how to create, save, and open files) is Styles. If you don't
understand Styles, you have no idea how to use Word efficiently and
productively, nor will you be able to create good-looking, easily maintained
documents.

The one apparent advantage of Word in this regard is that one style can be
derived from another. So, for example, if Heading 2, 3, etc, are all derived
from Heading 1, then changing Heading 1's font will automatically change the
font of all the sub headings. As far as I know, VP doesn't work that way.


A very useful skill in using Word is knowing what doesn't work and
either staying away from it or working around it. I never had the
problems with automatic pagination you described (maybe you were using
an earlier version that me: I used 97 for a long time, now use 2000),
but there are lots of things that don't work as well as they should or
just plain don't work at all. But for the most part, its features work
well enough to make it an appropriate tool for long documents.


Unwanted background repagination/pagebreak has occurred in every version of
WinWord I've used, regardless of the computer or operating system, even when
I turn it off.


One thing I wanted to do but never could make work was master
documents and subdocuments, which would have been nice, as
my manuals were divided into chapters. I never did determine if this
facility even worked at all, and just gave up. It made for very large
(multi-megabyte) documents, but they were still manageable.


I've seen other people try to use it and wind up with a mess. Whether this
was their fault, of Word's fault (I suspect the latter), I don't know.


I'd summarize Word by saying it's an extremely powerful program
(you might not realize just how powerful it is until you start playing
with VB and macros) with a very badly-designed user interface that
is quite suitable for documents of any length.


For Word processing, I wouldn't use anything /but/ Word. But I would never,
ever use it for long documents. It's clumsy and frustrating beyond belief.
VP is simple.


  #3   Report Post  
Posted to sci.electronics.repair
external usenet poster
 
Posts: 19
Default Word as a publishing program

On Sat, 24 Jan 2009 13:43:58 -0800, David Nebenzahl wrote:
Sorry for reviving an old, dead thread, but I ran across something I'd
like to respond to. In a thread entitled "Which Os is better among the
Windows Vista",


And, you posted this *as a new thread* in
sci.electronics.repair - - - why????

That post was OT and/or a troll from a google groper 14 months ago.

Yours may be a World Record for the delay in rising to a troll.

  #4   Report Post  
Posted to sci.electronics.repair
external usenet poster
 
Posts: 555
Default Word as a publishing program


"Spamm Trappe" wrote in message
...
On Sat, 24 Jan 2009 13:43:58 -0800, David Nebenzahl wrote:
Sorry for reviving an old, dead thread, but I ran across something I'd
like to respond to. In a thread entitled "Which Os is better among the
Windows Vista",


And, you posted this *as a new thread* in
sci.electronics.repair - - - why????

That post was OT and/or a troll from a google groper 14 months ago.

Yours may be a World Record for the delay in rising to a troll.


So far off topic, that it is perhaps in one of those 11 dimensions (and
alternate universes) predicted by string theory.


  #5   Report Post  
Posted to sci.electronics.repair
external usenet poster
 
Posts: 5
Default Word as a publishing program


"William Sommerwerck" wrote in message
...

One thing I wanted to do but never could make work was master
documents and subdocuments, which would have been nice,


I've seen other people try to use it and wind up with a mess. Whether this
was their fault, of Word's fault (I suspect the latter), I don't know.


It's possible to make it work, but it's a royal pain. Fussy, fussy, fussy.

I'd summarize Word by saying it's an extremely powerful program
(you might not realize just how powerful it is until you start playing
with VB and macros) with a very badly-designed user interface that
is quite suitable for documents of any length.


For Word processing, I wouldn't use anything /but/ Word. But I would
never,
ever use it for long documents. It's clumsy and frustrating beyond belief.
VP is simple.


Here, I respectfully agree. Word, at least Word 2000, doesn't handle large
documents well (where large is over a few hundred pages or so). For that,
the only game in town seems to be FrameMaker (I used to work at Nortel,
where document suites often ran to the tens of thousands of pages, with
complex indices, TOCs, internal references, ad nauseam). FrameMaker also
handles graphics properly, does tables well, has styles, etc..

And no, I don't know what this is doing in this newsgroup either, but at
least it's something I can comment on intelligently.

Dave O'H



  #6   Report Post  
Posted to sci.electronics.repair
external usenet poster
 
Posts: 157
Default Word as a publishing program

On Jan 29, 10:42*pm, "D O'Heare" wrote:
"William Sommerwerck" wrote in message

...

One thing I wanted to do but never could make work was master
documents and subdocuments, which would have been nice,


I've seen other people try to use it and wind up with a mess. Whether this
was their fault, of Word's fault (I suspect the latter), I don't know.


It's possible to make it work, but it's a royal pain. Fussy, fussy, fussy..


If you have ever googled word+subdocs, the one comment that you will
see over and over is:
"Word master documents exist in 2 states : either corrupt, or about to
become corrupt."

Here at work, I have seen some success in emulating master documents
by using document properties in the "master" document to specify a
subdirectory where the subdocs live, then using the INCLUDETEXT
directive in an inserted Field to include the subdocument. You do all
your editing in the subdoc, then you go to the master doc, Select All,
and Update Fields. Seems to work pretty well.

Jerry
  #7   Report Post  
Posted to sci.electronics.repair
external usenet poster
 
Posts: 679
Default Word as a publishing program

D O'Heare wrote:
"William Sommerwerck" wrote in message
...

One thing I wanted to do but never could make work was master
documents and subdocuments, which would have been nice,


I've seen other people try to use it and wind up with a mess.
Whether this was their fault, of Word's fault (I suspect the
latter), I don't know.


It's possible to make it work, but it's a royal pain. Fussy, fussy,
fussy.
I'd summarize Word by saying it's an extremely powerful program
(you might not realize just how powerful it is until you start
playing with VB and macros) with a very badly-designed user
interface that is quite suitable for documents of any length.


For Word processing, I wouldn't use anything /but/ Word. But I would
never,
ever use it for long documents. It's clumsy and frustrating beyond
belief. VP is simple.


Here, I respectfully agree. Word, at least Word 2000, doesn't handle
large documents well (where large is over a few hundred pages or so).
For that, the only game in town seems to be FrameMaker (I used to
work at Nortel, where document suites often ran to the tens of
thousands of pages, with complex indices, TOCs, internal references,
ad nauseam). FrameMaker also handles graphics properly, does tables
well, has styles, etc..
And no, I don't know what this is doing in this newsgroup either, but
at least it's something I can comment on intelligently.

Dave O'H


Master Document never has and never will work reliably in Office. MS
has no intentions of fixing it. It will eventually disappear as we know
it now.

Do a search and you will find some articles and a white paper or two
describing how to use it reliably but it's a hassle and a half, believe
me.

Personally, I have switched to Open Office, the free open source
alternative to MS Office and with the exception of their refusing to
make it do envelopes properly, it's great and does even more than MSO
does without the bloat and useless data content. The latest version
will read/save all MS files and many others plus its own native, more
functional Open File Format, someting windoes refuses to do. It's under
the GPL license and can be used by anyone anywhere. BTW, Master
Document, using a different methodology, works great in Open Office but
you have to unlearn some bad habits from MS.

Twayne


Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules

Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
CMS for publishing FAQ articles Grunff UK diy 51 December 19th 06 11:57 AM
Sams Technical Publishing E:Fact Doug Electronics Repair 2 November 26th 06 06:04 PM
Kids Eye View Publishing - Childrens Book On Sale Now!!! jmgconsultants Home Ownership 0 October 18th 06 03:16 AM
I need a spy program ( non harmful) program... fixpc Electronics Repair 8 February 7th 06 06:20 AM
integrated publishing mhyk Electronics 0 July 7th 05 06:20 AM


All times are GMT +1. The time now is 10:51 AM.

Powered by vBulletin® Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 DIYbanter.
The comments are property of their posters.
 

About Us

"It's about DIY & home improvement"