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?
P.S. Apologies if someone else has already posted this solution; I
missed it.
========================================================================
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 418 |
Nodes: | 16 (0 / 16) |
Uptime: | 35:28:39 |
Calls: | 8,781 |
Calls today: | 8 |
Files: | 13,291 |
Messages: | 5,963,929 |