Overly ordered lists. We're #1! All of us!

Thread View: adobe.framemaker.sgml

7 messages

[T] Back to Threads [V] Tree View [G] Group Articles

7 total messages Started by David_Blyth_San_Diego Thu, 23 Oct 2008 21:38

#625

Author: David_Blyth_San_Diego
Date: Thu, 23 Oct 2008 21:38

50 lines
1854 bytes

Hi all;

This is a simple problem (I think) but I can't figure it out. I'm trying to do a simple numbered list in Structured Frame XML, to the tune of ....



 
   
   
* Put your hands into the protective gloves 
   
* Grab the chip 
   
* Dip the chip into sulferic acid to clean it 
   




But Frame 8 keeps formatting this with "1". Like...

1. Put your hands into the protective gloves
    1. Grab the chip
    1. Dip the chip into sulferic acid to clean it

Despite the fact that my EDD separates "format rules for first paragraph in element" from the normal "Text format rules", it looks like items #2 onwards always get trapped as the "first item" in the list.

Here's the relevant part of my EDD.

Element (Container): li

Format rules for first paragraph in element

If context is ol
                 count ancestors named: ol,ul

If level is:1
                              Use paragraph format: ListNumFirst
                          If level is:2
                              ....

Text format rules

If context is ol
                count ancestors name: ol,ul

If level is:1
                              Use paragraph format: ListNumNext
                          If level is:2
                              ....

Re: Overly ordered lists. We're #1! All of us!

#626

Author: Jon_White
Date: Thu, 23 Oct 2008 22:05

22 lines
1207 bytes

David,

First paragraph rules apply to the first paragraph in the element, not the first paragraph in the parent of the element.

What you need is something like:



 
Format rules for first paragraph in element 
If context is: {first} 
Use paragraph format: ListNumFirst

Else 
Use paragraph format: ListNumNext 




The {first} sibling indicator means "first element in the parent", i.e. first dlie in the dole

Jon

Re: Overly ordered lists. We're #1! All of us!

#627

Author: David_Blyth_San_Diego
Date: Thu, 23 Oct 2008 22:57

8 lines
1071 bytes

Duuhhhh. Thanks Jon! And it's obvious, too. Maybe my brain melted after I turned 51 a week ago...

David Blyth (the UNIX and vi dinosaur)
Staff Technical Writer
QUALCOMM - Standard Disclaimers Apply

Only 149,999,949 more years of Ruling The Earth to go
----------------------------------------------------------

Re: Overly ordered lists. We're #1! All of us!

#628

Author: Jon_White
Date: Thu, 23 Oct 2008 23:05

3 lines
653 bytes

Happy Birthday,

Jon

Re: Overly ordered lists. We're #1! All of us!

#319

Author: janice_swanson
Date: Fri, 09 Jan 2009 22:21

12 lines
1182 bytes

I too have an issue with numbers. I am trying to number Tables within a structured document so I can generate a list of tables for the book containing the document later. I have set the following text format rules in my EDD for TableTitle:

Text format rules
    1. If context is: {first}
            Numbering properties
                Autonumber format: Table <n=1>:
       Else
           Numbering properties
                Autonumber format: Table <n+>:

For some reason, all my tables are labelled "Table 1: xxx".
I've obviously missed something, but I'm not sure what.

Re: Overly ordered lists. We're #1! All of us!

#321

Author: Ian_Proudfoot
Date: Sun, 11 Jan 2009 11:25

23 lines
1541 bytes

Hi Janice,

The problem is almost certainly due to the location of the TableTitle. The {first} rule is checking that <TableTitle> is the first child element in <Table>. This may always be true, so all tables are #1.

The way to solve this problem is quite simple. In most cases the autonumbering does not need to be told when to start at 1. You will either have one continuous numbering stream through an entire book, or restart the numbering at each chapter.

I would use a rule for TableTitle such as

Text format rules
    1. In all contexts.
            Numbering properties
                Autonumber format: T:Table <n+>:

You can then use the numbering properties dialog to control whether the numbering sequence restarts at each chapter, or not.

Please note the T: prefix on the autonumber this keeps the table numbering separate from any other sequence.

I hope this helps

Ian

Ian Proudfoot
Adobe Community Expert

Re: Overly ordered lists. We're #1! All of us!

#327

Author: janice_swanson
Date: Mon, 12 Jan 2009 15:24

1 lines
690 bytes

That was exactly the problem. Thanks for the clarification, Ian.

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads