Thank you for your kind replies.  As I said, this is my first EDD and
there's a lot I don't know so please bear with me.  I set up the
numbering in the EDD (I want to minimize the available elements, and
instead have the properties governed by where they appear):

If level is 1:
If context is: {first}
   Numbering properties
      Autonumber format: <n=1>.\t
   Numbering properties
      Autonumber format: <n+>.\t

Else, if level is: 2
   If context is: ul
      Numbering properties
         Autonumber format: \b\t
   If context is: {first}
      Numbering properties
         Autonumber format: <a=1>.\t
   Numbering properties
      Autonumber format: <a+>.\t

There's more to it, of course.  There is no opportunity in the EDD
won't let me put in a letter with a colon, n: or a:.  Hope this helps.

I'm doing it the EDD way so that no matter where a LI occurs, it will
be formatted correctly depending on where it is: numbered, bulleted,
first, middle, table (haven't figured that one out yet, had to create
a new element and para format), etc.

On 11/22/05, Etzel, Gary <Gary.Etzel at> wrote:
> I think you need to change the numbering properties for the paragraph
> format. I don't know if you are defining that through the paragraph designer
> or the EDD, but it's the same concept either way. In your first level OL,
> you probably have something like the following as the autonumber format:
> n:<n+>\t. In your second level OL, you need to change the n's to a different
> letter, like this: a:\t<a+>\t. That will distinguish the first-level "n"
> numbering scheme from the second level "a" numbering scheme.
> Regards,
> Gary
> -----Original Message-----
> From: at
> [ at] On
> Behalf Of Stacie Knas
> Sent: Tuesday, November 22, 2005 1:27 PM
> To: framers at
> Subject: Numbered list item picks up from preceding nested list item
> Dear Framers:
> Frame 7.1, Windows XP Pro
> I am tweaking my first EDD (using the Structured Application
> Developer's Guide) to get the levels and spacing right with list items
> (LI) in ordered lists (OL) and unordered lists (UL) and various nested
> combinations thereof, including depending on whether the list is
> compact or non-compact.  I am very pleased with what I have figured
> out so far, it's working well, except for one thing:  If I have an OL
> nested in a LI in an OL, the LI that follows the nested OL picks up
> that OL's numbering, thus:
> 6.  Item a
> 7.  Item b
>     a.  item A
>     b.  item B
>     c.  item C
> 4.  Item c
> 5.  ...
> It doesn't happen with unordered lists.  My level rules seem fine, and
> they work if they are not interrupted by a nested OL.  I don't know
> where else to look; can you point me to places I could investigate?
> Thanks so much.  This list is invaluable.  Sorry I can't provide
> answers yet, but I'm learning a lot.
> --Stacie
> foolofgrace at
> This e-mail, and any attachments are strictly confidential and intended for 
> the addressee(s) only.  The content may also contain legal, professional or 
> other privileged information.  If you are not the intended recipient, please 
> notify the sender immediately, by return of email, and then delete the e-mail 
> and any attachments.  You should not disclose, copy or take any action in 
> reliance on this transmission.
> Please ensure you have adequate virus protection before you open or detach 
> any documents from this transmission.
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit
> ______________________________________________________________________

Reply via email to