Outline numbering - need more levels

J

J. Nelson

At work we use the built-in Heading styles for outline
numbering in all our documents in this format:

1. This is Heading 1
1.1. This is Heading 2
1.1.1. This is Heading 3
etc.

But it only goes up to Heading 7. Heading 8 becomes
an "a,b,c" list and Heading 9 becomes a numbered sublevel
of Heading 8.

Example:

1.1.1.1.1.1. This is Heading 6
1.1.1.1.1.1.1. This is Heading 7
a. This is Heading 8
1. This is Heading 9

We need outline numbering to go at least 10 levels
(horrid I know, but not my idea!).

Example:

1.1.1.1.1.1.1. Heading 7
1.1.1.1.1.1.1.1. Heading 8
1.1.1.1.1.1.1.1.1. Heading 9
1.1.1.1.1.1.1.1.1.1. Heading 10

We've tried modifying the style for Heading 8 and 9 with
no luck. Haven't even begun to try figuring out how to
create a Heading 10.

If anyone can help me customize this, I'd greatly
appreciate it. Thanks!
 
B

Bruce Brown

JN - Posted this a while back. Legal numbering beyond 9 levels is
actually a piece of cake; keeping track of it is the nasty part.
==========================================================================
At least two posters within the past year have asked how to create 18
levels of numbering. Working with the STYLEREF field the other day, an
answer occurred to me that's laughably easy.

Set up the built-in Heading styles in the legal number format 1.1.,
1.1.1., etc. and use them for levels 1 through 9. Beyond level 9, use
the STYLEREF and LISTNUM fields side by side -- the first to capture
the 9 numeric values at the point of insertion, and the second to
number levels 10 to 18.

( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 1 \S 1 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 2 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 3 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 4 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 5 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 6 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 7 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 8 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 9 )

.. . . gives you . . .

3.5.7.2.8.9.4.6.3.1.
3.5.7.2.8.9.4.6.3.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.1.1.1.

.. . . etc.

You have to be careful about adding the start switch \S 1 to the first
level 10 field that follows a Heading 9 number, which re-starts all
levels 10 and above. But that's only the one immediately after a
Heading 9; otherwise you don't want any \S switch at all, just the
level switch \L.

Other than that, it's a pretty straightforward method: Heading styles
up to level 9, compound fields after that.

If someone absolutely insists that there be no period after the last
number, you're out of luck. The period is part of the LISTNUM
LegalDefault style and cannot be removed.

Should your format call for a hodge-podge of numbering styles other
than straight legal numbering, you could handle that too -- by setting
up a named list template with outline-numbered styles defined by you,
then using that name within the LISTNUM field in place of
LegalDefault. In that case, you'd never actually use the styles you
create; you'd use the LISTNUM field as a substitute for them.

How about SEQ fields? Wouldn't they be better for this purpose? I
don't think so. SEQ fields do single level lists only, not outlines,
so you'd need nine differently named SEQ fields to do the same
numbering as one LISTNUM field at level 9, and each of the nine SEQ
fields would have to be re-started manually throughout the document.

Setting up the 18 levels is the easy part. After that, how could
anyone possibly read them?

JN - for your purposes, you'd need only { LISTNUM \L 1 }like so:

( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 1 \S 1 ) - start level 10
at 1
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 1 ) - continue level 10

Good luck, Bruce. P.S. Hey Greg, it's good to see your
Archie/Jughead logo again, or whatever your official name for him is.
Just out of curiosity, I gave him some extra hair, a moustache,
centered his right-leaning head and gave him a pair of headphones to
listen to. Please don't sue me. P.P.S. No more Hawaii?

\\\\\\\\\\///////////
[( @ @ )]
----oo00---(_)---00oo----
`````
GM
 
G

Greg Maxey

Bruce,

Thanks for the touch-up. He looks fine when I send but must get all mixed
up in the transmission. Perhaps I will abandon. I had to leave Hawaii in
June for Florida. Military orders. Orders I really would have loved to
pass on. Least it is in sultry central Florida and not a desert.



--
\\\\///////////
( @ @ )
----oo00---(_)---00oo----
Greg Maxey
A peer in "peer to peer" support
Rockledge, FL

Bruce said:
JN - Posted this a while back. Legal numbering beyond 9 levels is
actually a piece of cake; keeping track of it is the nasty part.
==========================================================================
At least two posters within the past year have asked how to create 18
levels of numbering. Working with the STYLEREF field the other day, an
answer occurred to me that's laughably easy.

Set up the built-in Heading styles in the legal number format 1.1.,
1.1.1., etc. and use them for levels 1 through 9. Beyond level 9, use
the STYLEREF and LISTNUM fields side by side -- the first to capture
the 9 numeric values at the point of insertion, and the second to
number levels 10 to 18.

( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 1 \S 1 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 2 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 3 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 4 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 5 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 6 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 7 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 8 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 9 )

. . . gives you . . .

3.5.7.2.8.9.4.6.3.1.
3.5.7.2.8.9.4.6.3.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.1.1.1.

. . . etc.

You have to be careful about adding the start switch \S 1 to the first
level 10 field that follows a Heading 9 number, which re-starts all
levels 10 and above. But that's only the one immediately after a
Heading 9; otherwise you don't want any \S switch at all, just the
level switch \L.

Other than that, it's a pretty straightforward method: Heading styles
up to level 9, compound fields after that.

If someone absolutely insists that there be no period after the last
number, you're out of luck. The period is part of the LISTNUM
LegalDefault style and cannot be removed.

Should your format call for a hodge-podge of numbering styles other
than straight legal numbering, you could handle that too -- by setting
up a named list template with outline-numbered styles defined by you,
then using that name within the LISTNUM field in place of
LegalDefault. In that case, you'd never actually use the styles you
create; you'd use the LISTNUM field as a substitute for them.

How about SEQ fields? Wouldn't they be better for this purpose? I
don't think so. SEQ fields do single level lists only, not outlines,
so you'd need nine differently named SEQ fields to do the same
numbering as one LISTNUM field at level 9, and each of the nine SEQ
fields would have to be re-started manually throughout the document.

Setting up the 18 levels is the easy part. After that, how could
anyone possibly read them?

JN - for your purposes, you'd need only { LISTNUM \L 1 }like so:

( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 1 \S 1 ) - start level 10
at 1
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 1 ) - continue level 10

Good luck, Bruce. P.S. Hey Greg, it's good to see your
Archie/Jughead logo again, or whatever your official name for him is.
Just out of curiosity, I gave him some extra hair, a moustache,
centered his right-leaning head and gave him a pair of headphones to
listen to. Please don't sue me. P.P.S. No more Hawaii?

\\\\\\\\\\///////////
[( @ @ )]
----oo00---(_)---00oo----
`````
GM


Greg Maxey said:
J.

This is as good an explanation as it gets:

http://www.shaunakelly.com/word/numbering/OutlineNumbering.html
--
\\\\///////////
( @ @ )
----oo00---(_)---00oo----
Greg Maxey
A peer in "peer to peer" support
Rockledge, FL
 
B

Bruce Brown

No, please don't abandon! It's the most charming thing on the threads,
just as you send it out without changing a thing.

- Bruce


Greg Maxey said:
Bruce,

Thanks for the touch-up. He looks fine when I send but must get all mixed
up in the transmission. Perhaps I will abandon. I had to leave Hawaii in
June for Florida. Military orders. Orders I really would have loved to
pass on. Least it is in sultry central Florida and not a desert.



--
\\\\///////////
( @ @ )
----oo00---(_)---00oo----
Greg Maxey
A peer in "peer to peer" support
Rockledge, FL

Bruce said:
JN - Posted this a while back. Legal numbering beyond 9 levels is
actually a piece of cake; keeping track of it is the nasty part.
==========================================================================
At least two posters within the past year have asked how to create 18
levels of numbering. Working with the STYLEREF field the other day, an
answer occurred to me that's laughably easy.

Set up the built-in Heading styles in the legal number format 1.1.,
1.1.1., etc. and use them for levels 1 through 9. Beyond level 9, use
the STYLEREF and LISTNUM fields side by side -- the first to capture
the 9 numeric values at the point of insertion, and the second to
number levels 10 to 18.

( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 1 \S 1 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 2 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 3 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 4 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 5 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 6 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 7 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 8 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 9 )

. . . gives you . . .

3.5.7.2.8.9.4.6.3.1.
3.5.7.2.8.9.4.6.3.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.1.1.1.

. . . etc.

You have to be careful about adding the start switch \S 1 to the first
level 10 field that follows a Heading 9 number, which re-starts all
levels 10 and above. But that's only the one immediately after a
Heading 9; otherwise you don't want any \S switch at all, just the
level switch \L.

Other than that, it's a pretty straightforward method: Heading styles
up to level 9, compound fields after that.

If someone absolutely insists that there be no period after the last
number, you're out of luck. The period is part of the LISTNUM
LegalDefault style and cannot be removed.

Should your format call for a hodge-podge of numbering styles other
than straight legal numbering, you could handle that too -- by setting
up a named list template with outline-numbered styles defined by you,
then using that name within the LISTNUM field in place of
LegalDefault. In that case, you'd never actually use the styles you
create; you'd use the LISTNUM field as a substitute for them.

How about SEQ fields? Wouldn't they be better for this purpose? I
don't think so. SEQ fields do single level lists only, not outlines,
so you'd need nine differently named SEQ fields to do the same
numbering as one LISTNUM field at level 9, and each of the nine SEQ
fields would have to be re-started manually throughout the document.

Setting up the 18 levels is the easy part. After that, how could
anyone possibly read them?

JN - for your purposes, you'd need only { LISTNUM \L 1 }like so:

( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 1 \S 1 ) - start level 10
at 1
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 1 ) - continue level 10

Good luck, Bruce. P.S. Hey Greg, it's good to see your
Archie/Jughead logo again, or whatever your official name for him is.
Just out of curiosity, I gave him some extra hair, a moustache,
centered his right-leaning head and gave him a pair of headphones to
listen to. Please don't sue me. P.P.S. No more Hawaii?

\\\\\\\\\\///////////
[( @ @ )]
----oo00---(_)---00oo----
`````
GM


Greg Maxey said:
J.

This is as good an explanation as it gets:

http://www.shaunakelly.com/word/numbering/OutlineNumbering.html
--
\\\\///////////
( @ @ )
----oo00---(_)---00oo----
Greg Maxey
A peer in "peer to peer" support
Rockledge, FL

J. Nelson wrote:
At work we use the built-in Heading styles for outline
numbering in all our documents in this format:

1. This is Heading 1
1.1. This is Heading 2
1.1.1. This is Heading 3
etc.

But it only goes up to Heading 7. Heading 8 becomes
an "a,b,c" list and Heading 9 becomes a numbered sublevel
of Heading 8.

Example:

1.1.1.1.1.1. This is Heading 6
1.1.1.1.1.1.1. This is Heading 7
a. This is Heading 8
1. This is Heading 9

We need outline numbering to go at least 10 levels
(horrid I know, but not my idea!).

Example:

1.1.1.1.1.1.1. Heading 7
1.1.1.1.1.1.1.1. Heading 8
1.1.1.1.1.1.1.1.1. Heading 9
1.1.1.1.1.1.1.1.1.1. Heading 10

We've tried modifying the style for Heading 8 and 9 with
no luck. Haven't even begun to try figuring out how to
create a Heading 10.

If anyone can help me customize this, I'd greatly
appreciate it. Thanks!
 
S

Suzanne S. Barnhill

FWIW, in Arial, he is skewed sideways. Using the Fixed setting for text just
aggravates the problem. And, BTW, his name is Chad. Graham Mayor used to use
him but gave it up along with other sigs that didn't pass muster (including
one that included the apparently banned term V*I*A*G*R*A).

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://www.mvps.org/word
Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.

Bruce Brown said:
No, please don't abandon! It's the most charming thing on the threads,
just as you send it out without changing a thing.

- Bruce


"Greg Maxey" <[email protected]> wrote in message
Bruce,

Thanks for the touch-up. He looks fine when I send but must get all mixed
up in the transmission. Perhaps I will abandon. I had to leave Hawaii in
June for Florida. Military orders. Orders I really would have loved to
pass on. Least it is in sultry central Florida and not a desert.



--
\\\\///////////
( @ @ )
----oo00---(_)---00oo----
Greg Maxey
A peer in "peer to peer" support
Rockledge, FL

Bruce said:
JN - Posted this a while back. Legal numbering beyond 9 levels is
actually a piece of cake; keeping track of it is the nasty part.
==========================================================================
At least two posters within the past year have asked how to create 18
levels of numbering. Working with the STYLEREF field the other day, an
answer occurred to me that's laughably easy.

Set up the built-in Heading styles in the legal number format 1.1.,
1.1.1., etc. and use them for levels 1 through 9. Beyond level 9, use
the STYLEREF and LISTNUM fields side by side -- the first to capture
the 9 numeric values at the point of insertion, and the second to
number levels 10 to 18.

( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 1 \S 1 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 2 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 3 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 4 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 5 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 6 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 7 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 8 )
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 9 )

. . . gives you . . .

3.5.7.2.8.9.4.6.3.1.
3.5.7.2.8.9.4.6.3.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.1.1.
3.5.7.2.8.9.4.6.3.1.1.1.1.1.1.1.1.1.

. . . etc.

You have to be careful about adding the start switch \S 1 to the first
level 10 field that follows a Heading 9 number, which re-starts all
levels 10 and above. But that's only the one immediately after a
Heading 9; otherwise you don't want any \S switch at all, just the
level switch \L.

Other than that, it's a pretty straightforward method: Heading styles
up to level 9, compound fields after that.

If someone absolutely insists that there be no period after the last
number, you're out of luck. The period is part of the LISTNUM
LegalDefault style and cannot be removed.

Should your format call for a hodge-podge of numbering styles other
than straight legal numbering, you could handle that too -- by setting
up a named list template with outline-numbered styles defined by you,
then using that name within the LISTNUM field in place of
LegalDefault. In that case, you'd never actually use the styles you
create; you'd use the LISTNUM field as a substitute for them.

How about SEQ fields? Wouldn't they be better for this purpose? I
don't think so. SEQ fields do single level lists only, not outlines,
so you'd need nine differently named SEQ fields to do the same
numbering as one LISTNUM field at level 9, and each of the nine SEQ
fields would have to be re-started manually throughout the document.

Setting up the 18 levels is the easy part. After that, how could
anyone possibly read them?

JN - for your purposes, you'd need only { LISTNUM \L 1 }like so:

( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 1 \S 1 ) - start level 10
at 1
( STYLEREF 9 \S }.{ LISTNUM LegalDefault \L 1 ) - continue level 10

Good luck, Bruce. P.S. Hey Greg, it's good to see your
Archie/Jughead logo again, or whatever your official name for him is.
Just out of curiosity, I gave him some extra hair, a moustache,
centered his right-leaning head and gave him a pair of headphones to
listen to. Please don't sue me. P.P.S. No more Hawaii?

\\\\\\\\\\///////////
[( @ @ )]
----oo00---(_)---00oo----
`````
GM


J.

This is as good an explanation as it gets:

http://www.shaunakelly.com/word/numbering/OutlineNumbering.html
--
\\\\///////////
( @ @ )
----oo00---(_)---00oo----
Greg Maxey
A peer in "peer to peer" support
Rockledge, FL

J. Nelson wrote:
At work we use the built-in Heading styles for outline
numbering in all our documents in this format:

1. This is Heading 1
1.1. This is Heading 2
1.1.1. This is Heading 3
etc.

But it only goes up to Heading 7. Heading 8 becomes
an "a,b,c" list and Heading 9 becomes a numbered sublevel
of Heading 8.

Example:

1.1.1.1.1.1. This is Heading 6
1.1.1.1.1.1.1. This is Heading 7
a. This is Heading 8
1. This is Heading 9

We need outline numbering to go at least 10 levels
(horrid I know, but not my idea!).

Example:

1.1.1.1.1.1.1. Heading 7
1.1.1.1.1.1.1.1. Heading 8
1.1.1.1.1.1.1.1.1. Heading 9
1.1.1.1.1.1.1.1.1.1. Heading 10

We've tried modifying the style for Heading 8 and 9 with
no luck. Haven't even begun to try figuring out how to
create a Heading 10.

If anyone can help me customize this, I'd greatly
appreciate it. Thanks!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top