J
John McGhie
Hi Norm:
Yes. Again, you cannot make "rules" that always hold true at this level, or
you will end up with a rulebook twice the size of the London phone book.
And nobody puts their number in the phone book anymore because nobody can
find their number in it: it's too big
1) When I am showing you how to create a style, I will start from scratch
so you know how to create one.
2) When I am showing you how to create a List Style, I have to start from
scratch, because there are no existing List Styles.
3) If I were to show you how to create a Table Style, I could do either,
but I would probably start from scratch because the Microsoft ones are so
horrid and so useless that life is to short to correct the detritus
contained in them.
I don't change the names of any built-in styles: that's correct. That's
because I want to leave the document with the standard style names, so other
users can find their way around.
But I set the formatting of the ones I intend to use, appropriately for each
document or template.
I also do not want to deal with the complexities around which ones you can
rename and which ones won't let you. Word actually has THREE classes of
style in the style table, not two. But it never describes or reveals the
difference in the user interface. In fact, it is difficult to find it when
you are programming also, and if you get it wrong, your code blows up.
There are "Custom Styles" and "Built-in Styles". Within the built-in
styles, there is a subset that doesn't seem to have an official name:
sometimes referred to as "Default" styles. You cannot delete a default
style, Word won't let you. And if you try to re-name it, Word will add the
name you create to the default name. If you try to create a style with the
same name, it will refuse. It's annoying and complex, and you won't see it
until you get into VBA.
Again: Come back to the 50,000-foot-view. What are you trying to DO? You
are trying to save effort. Most importantly, save effort for YOU. Saving
effort for other users is a "nice to have", but you are the one who matters
You will do a lot less work if you customise the built-in styles, because
their definitions will usually be close to what you will want to specify in
any case.
If you send documents for editing to anyone else, I suggest that you leave
the style names unchanged, otherwise they will probably start doing strange
things in your document, which you will have to fix when you get it back!
Although Clive is quite right: many users out there have yet to find out how
much work they save by using styles, and for them, it will make no
difference. But it's extra work for you to rename things; and try to
remember what you renamed them to!
I have a different constraint: as m'learned colleague from Canberra has
alluded, the possibility of getting engineers and senior business executives
to "do" this stuff is inversely and directly proportional to how difficult
you make it. So I will often do things that involve a lot of work for me,
in order to get the documents being returned closer to what the company
specifies. Because *I* will have to fix them if they are not...
And working backwards and forwards between platforms, trying to learn the
various different keystrokes of each is just too much work, so I don't
bother
Cheers
--
The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or unless you intend to pay!
John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410
+61 4 1209 1410, mailto:[email protected]
So when "we" were doing the list style exercise of creating a list
paragraph style and a list style, we used some made up names. I gather
changing names was just for practice. When you do the real thing you
keep MS's name convention for styles as much as possible. But you may
define that style differently for a specialized purpose and retain that
in a separate template. Correct?
Yes. Again, you cannot make "rules" that always hold true at this level, or
you will end up with a rulebook twice the size of the London phone book.
And nobody puts their number in the phone book anymore because nobody can
find their number in it: it's too big
1) When I am showing you how to create a style, I will start from scratch
so you know how to create one.
2) When I am showing you how to create a List Style, I have to start from
scratch, because there are no existing List Styles.
3) If I were to show you how to create a Table Style, I could do either,
but I would probably start from scratch because the Microsoft ones are so
horrid and so useless that life is to short to correct the detritus
contained in them.
And you don't change the names like Clive does. It seems like you both
start the first step in any linked style from scratch, not linked to
Normal style but Clive changes the names and you don't. Correct?
I don't change the names of any built-in styles: that's correct. That's
because I want to leave the document with the standard style names, so other
users can find their way around.
But I set the formatting of the ones I intend to use, appropriately for each
document or template.
I also do not want to deal with the complexities around which ones you can
rename and which ones won't let you. Word actually has THREE classes of
style in the style table, not two. But it never describes or reveals the
difference in the user interface. In fact, it is difficult to find it when
you are programming also, and if you get it wrong, your code blows up.
There are "Custom Styles" and "Built-in Styles". Within the built-in
styles, there is a subset that doesn't seem to have an official name:
sometimes referred to as "Default" styles. You cannot delete a default
style, Word won't let you. And if you try to re-name it, Word will add the
name you create to the default name. If you try to create a style with the
same name, it will refuse. It's annoying and complex, and you won't see it
until you get into VBA.
Again: Come back to the 50,000-foot-view. What are you trying to DO? You
are trying to save effort. Most importantly, save effort for YOU. Saving
effort for other users is a "nice to have", but you are the one who matters
You will do a lot less work if you customise the built-in styles, because
their definitions will usually be close to what you will want to specify in
any case.
If you send documents for editing to anyone else, I suggest that you leave
the style names unchanged, otherwise they will probably start doing strange
things in your document, which you will have to fix when you get it back!
Although Clive is quite right: many users out there have yet to find out how
much work they save by using styles, and for them, it will make no
difference. But it's extra work for you to rename things; and try to
remember what you renamed them to!
I have a different constraint: as m'learned colleague from Canberra has
alluded, the possibility of getting engineers and senior business executives
to "do" this stuff is inversely and directly proportional to how difficult
you make it. So I will often do things that involve a lot of work for me,
in order to get the documents being returned closer to what the company
specifies. Because *I* will have to fix them if they are not...
And working backwards and forwards between platforms, trying to learn the
various different keystrokes of each is just too much work, so I don't
bother
Cheers
--
The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or unless you intend to pay!
John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410
+61 4 1209 1410, mailto:[email protected]