Hi Aaron:
Well, I won't be quite as hard on you as Elliott. Then again, I don't know
as much about typography as Elliott
I, like yourself, publish books directly from Word. Good typography and
page design is as possible in Word as it is in any other program. And I
agree with you: long documents are probably better handled in Word than they
are in a page-layout program. Word will deal efficiently with text in much
higher volumes than many page layout programs are designed for.
However, I would suggest that you are under-valuing your audience. An
audience that wants to learn typography in Word would, I believe, be looking
for more information at greater depth and with more explanation.
There are some statements you make in chapter 2 that I would quibble with: I
believe you are making some errors of fact there. For example:
* I would specifically recommend PC Word 2000 and Word 2003. Word 97 and
Word 2002 are too bug-ridden and unstable for serious production work
* I believe your whole Optimising for Speed section needs to be re-written.
The real speed-hogs are embedded pictures, Live Word Count, and Page Layout
View. The other items you mention have a negligible effect on speed,
although misuse of them can corrupt the document and make the whole thing
slow.
* In Chapter 2, you frequently make statements with no qualification or
explanation. This lack of detail detracts from what would otherwise be an
important piece of information. For example, you say Word needs plenty of
memory, but you don't say how much (512 MB for long document work).
* You mention reducing graphics resolution, but you don't explain what this
is, how to do it, or how to determine what the resolution should be. Anyone
can say "Make it better", our job is to tell the user HOW
* Goodness knows why you are telling your users to turn off background
saves? You should say why if you really want them to turn it off. I don't
see what effect that would have on stability. But it will certainly slow
the user down, and you don't mention that.
* If you are going to mention AutoRecover, you should explain to the user
what it actually does, how it operates, and why they should not rely on it
for backup.
* I wouldn't be quite so over-confident about Mac viruses
I would
agree that you could characterise the threat from viruses on the Mac as
lower than it is on the PC. However, in the interests of delivering
responsible advice to people who don't know that, you should probably also
mention that if they get one, they may indeed loose every file on their
system, and quite possibly, their backup as well. And that if they operate
without a regularly-updated antivirus, at some point in the life of their
system, they almost certainly will get one. I think it is fine to tell
people they can cut corners, but I consider it irresponsible not to advise
them of the risks so they are fully informed
* I happen to agree with you about Master Documents
However, I believe
that you should mention that they will be fine in Office 12 if the user
users the .docx file format.
* On the other hand, any document large enough to be looking for a
typography solution is likely to also require tracked changes, nested
tables, and list numbering and bullets. Again, I believe that what you say
in that section is so brief I would actually consider it to be technically
inaccurate.
* Similarly "Customising your Workspace". Either tell them what to do and
how to do it, or take that section out.
* I suggest that you revisit "Choosing your Views". Your text makes it
appear that you do not actually understand the subject. Choosing between
the views may be "mostly" a matter of preference -- tell us when it isn't,
and why. You have a typo when you say Page Preview, either Print Preview or
Page Layout View.
* You say Print Preview is not always perfect: in a book on typography, you
need to specify at which times it is not!! And how!!
* If you're going to mention Document Map, mention that it doesn't exist on
the Mac, and say HOW it changes your formatting and why.
* Showing Invisibles should be "Showing non-Printing Characters" -- use the
term Word uses.
* Controlling Automatic Changes is a big-ticket hot-seller in books on
using Word for complex document production. Your current section is a
reasonable "outline" of what should be there. You need to tell this
audience in explicit detail specifically what to enable or disable, and HOW.
I would disagree with your advice to turn off Smart Selection. When editing
text as opposed to code, it's easier to work with it on. Similarly, turning
off "Automatically include paragraph mark" is safer ON than off for users
who habitually run with the paragraph marks hidden.
* I disagree with your advice to turn off "Use printer metrics". Word will
repaginate every time the printer changes anyway, but if you don't use
printer metrics, the user won't be able to see the precise effect. Word
will use the printer metrics at print time, and what they get won't be the
same as what they saw on screen.
I guess I also agree with Elliott that Chapter 1 needs a re-angle. Rather
than "Why Not Word?" how about "Why Use Word?" There are good reasons why I
use Word for typography: the cost of Adobe CS2 is not one of them
Rather than be curmudgeonly like I usually am, allow me to suggest that the
book you are proposing to write is a good idea. It is needed. Users do ask
for such a book. But you're not writing the book they're asking for. Not
yet. Currently your book is shaping up to be simplistic and trite. It will
annoy its target reader, and cause a wave of vocal negative publicity that
will destroy your sales.
I think you're onto a good idea. Now you need to put the work in. You need
to put the Information in.
Hope this helps
I'm at work on the second edition of "Books, Typography, and Microsoft
Word" -- a full-size paperback this time, not an ebook -- and I could
use the expertise of this newsgroup.
As available, I'm posting preliminary, unformatted drafts of the
chapters on my Web site as PDF files. I welcome your downloading and
reading the chapters and sending me comments, criticisms, and
corrections. Here's the address:
http://www.aaronshep.com/publishing/books/WordType.html
The chapters will be
1. Why Not Word?
2. Optimizing Word
3. Using Styles and Templates
4. Laying Out Your Pages
5. Typesetting Your Text
6. Handling Graphics
7. Dealing with Details
8. Preparing for Print
9. Creating a Cover
I've just posted the first two chapters, and they're ready for
download. I'll post the remaining ones over the next week or so, and
tell the newsgroup as I do. Since I'm trying to get out the book in
January, the sooner I receive your comments the better.
Thanks!
Aaron
--
Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.
John McGhie <
[email protected]>
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 (0) 4 1209 1410