J
Julian Turner
Hello
I use multi-level lists extensively in legal documents that I author,
and I am looking for some opinions as to whether, in the future, I
should be using List Styles or sticking with the older Multi-Level
Lists
The reason for my question is because I am not clear which is more
flexible and which is the future, or indeed how the two relate to each
other:-
(a) Microsoft's online web-site web site says that "list styles" are
not as flexible (because you cannot attach paragraph styles) and
should only be used with simple lists. But is this wrong? In
practice you can associate paragraph styles to list styles, using the
modify > numbering dialogue, which takes you back to a full multi-
level list dialogue. I.e. List Styles seems to be able to link to a
full-multi-level list template, but I am not clear how that link works
and if it is linking to the same thing as a normal multi-level list.
Also there is that odd fact that if you link a list style level to a
paragraph style, the list style seems to lose track of the linked
paragraph style if you later modify the numbering indents etc.
(b) Word 2007 help says that "list styles" are more flexible,
because you can modify them, whereas modifying a multi-level list
creates a new multi-level list (and chaos follows).
To give you an idea of my level of knowledge, I am quite familiar with
Visual Basic and the Word Object Model, and have historically micro-
managed my lists directly though Visual Basic.
My lists (as they appear in the style manager) tend to follow the
followng pattern
L1_BASE (base style for list, all others inherit from it)
1. L1_BODY (numbered, but not bold - this is the linked style for
Level 1 in the list)
1. L1_HEADING (bold, inherits from L1_BODY, and so inherits the
list)
L1_NONUM (no numbering, inherits from L2_BODY)
1.1 L2_BODY
1.1 L2_HEADING (bold, inherits from L2_BODY)
L2_NONUM (no numbering, inherits from L2_BODY)
1.1.1L3_BODY
1.1.1L3_HEADING (bold, inherits from L3_BODY)
L3_NONUM (no numbering, inherits from L3_BODY)
The reason for having a non-heading, heading and no-number for each
level is that sometimes in legal documents you want the convenience of
all three.
This all works fine, and I have successfully implemented it both
normal multi-level lists and recently through a List Style .
Interestingly, the Bold for the HEADING style works on the list number
because although the multi-level outline overrides paragraph styles,
if the Bold property for the number > font is not set with either True
or False (i.e. it is wdUndefined), the override does not happen.
Julian
I use multi-level lists extensively in legal documents that I author,
and I am looking for some opinions as to whether, in the future, I
should be using List Styles or sticking with the older Multi-Level
Lists
The reason for my question is because I am not clear which is more
flexible and which is the future, or indeed how the two relate to each
other:-
(a) Microsoft's online web-site web site says that "list styles" are
not as flexible (because you cannot attach paragraph styles) and
should only be used with simple lists. But is this wrong? In
practice you can associate paragraph styles to list styles, using the
modify > numbering dialogue, which takes you back to a full multi-
level list dialogue. I.e. List Styles seems to be able to link to a
full-multi-level list template, but I am not clear how that link works
and if it is linking to the same thing as a normal multi-level list.
Also there is that odd fact that if you link a list style level to a
paragraph style, the list style seems to lose track of the linked
paragraph style if you later modify the numbering indents etc.
(b) Word 2007 help says that "list styles" are more flexible,
because you can modify them, whereas modifying a multi-level list
creates a new multi-level list (and chaos follows).
To give you an idea of my level of knowledge, I am quite familiar with
Visual Basic and the Word Object Model, and have historically micro-
managed my lists directly though Visual Basic.
My lists (as they appear in the style manager) tend to follow the
followng pattern
L1_BASE (base style for list, all others inherit from it)
1. L1_BODY (numbered, but not bold - this is the linked style for
Level 1 in the list)
1. L1_HEADING (bold, inherits from L1_BODY, and so inherits the
list)
L1_NONUM (no numbering, inherits from L2_BODY)
1.1 L2_BODY
1.1 L2_HEADING (bold, inherits from L2_BODY)
L2_NONUM (no numbering, inherits from L2_BODY)
1.1.1L3_BODY
1.1.1L3_HEADING (bold, inherits from L3_BODY)
L3_NONUM (no numbering, inherits from L3_BODY)
The reason for having a non-heading, heading and no-number for each
level is that sometimes in legal documents you want the convenience of
all three.
This all works fine, and I have successfully implemented it both
normal multi-level lists and recently through a List Style .
Interestingly, the Bold for the HEADING style works on the list number
because although the multi-level outline overrides paragraph styles,
if the Bold property for the number > font is not set with either True
or False (i.e. it is wdUndefined), the override does not happen.
Julian