Hmmm... Intellectually, I agree with John. A global add-inn (or even, a
series of attached templates) is the "proper" way to do this.
However, this is somewhat a case of "Do what I say, not what I do..." I
have had all my customisations in Normal template for some years. The
Normal template I use is a variation of one I began at the ASX in Year 2000.
My reason for this is purely laziness. With everything in one bucket, I
only have to carry one file with me from site to site. And with everything
in Normal, I don't have to pick my way through a maze of macro warnings,
security considerations and permission issues. The problem is worse on the
Mac because the design of its template mechanism is utterly broken for
corporate use.
The PC template is still going strong after all of these years of aggressive
updates. The Mac template does go bang every few months: Mac Word 2004
seems to have a problem with Normal template corruption. However, it is
more likely that the corruption I experience is due to the fact that I am
constantly fiddling with it to try out things for the newsgroup posting I do
here.
That said, *when* it goes bang, I simply re-name it. I then allow Word to
create a new Normal template, and use Organiser to bring the styles,
toolbars and macros back from the old one.
What I am saying is that I have come to the belief that expecting or
advising users to do it the "right" way is too difficult. Unless the user
is in a professional documentation workgroup, the learning curve is just too
steep. There's layer after layer of "considerations" and "practices"
involved in getting this working properly.
In a professional documentation workgroup, there will be policies,
processes, procedures and infrastructure in place. Everyone is
appropriately trained, and network resources are correctly permission to
make this work method straightforward.
But I believe many of our users are on their own: often at home. They don't
have skilled system administrators with an understanding of documentation
workflows, verified and reliable backup regimes, documented workflows or
even a disaster recovery plan. Sometimes our users are "The only one in the
company who cares about documentation" or "the only one in the company using
a Mac".
I think we need to keep it simple. Offer advice that makes it "just work".
And flame the hell out of Microsoft until it "just works reliably"
I have high hopes for the next version of Office. The new XML-based file
formats in Office 12 are not only practically immune to corruption, they
have vary substantial self-healing ability.
Just my thoughts
Ah, full agreement. Creating a Global Template is certainly a better idea
than customizing Normal, even if you back it up daily.
JE's instructions for creating such a global template are here:
http://word.mvps.org/mac/GlobalTemplate.html
Daiya
--
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