Conversion table not converting

[larry.kollar@xxxxxxxxxx]

I can't seem to get Frame to wrap up my steps the way I
want them. I assume I'm missing something fundamental
here, but I can't figure out what.

Searching the archives didn't turn up any known bugs,
and the Dev Guide suggest that I should be able to do this.

As a little background, I'm trying to structure a large
set of manuals. The tasks/procedures should look
something like this (in SGML):

<task>
<step><action><p>...txt...</p>
        <step><action><p>... substeps...</p></action></step>
</action></step>
(more steps)
</task>

(The <p> tag is a wrapper for text & various character-
level elements.) There's more to my <step> tag than this,
namely action, commentary, and a couple of other valid
subelements, but if I can't even get the simplest case to
work....

In the current unstructured documentation, the step_1
paragraph style resets the step counter; step_2 continues
it. The step_a and step_b styles do the same for substeps.

The conversion table tries to wrap it up nicely (spacing
added to improve readability):

Wrap                    Element         Qualifier
-------------------------------------------------
P:step_1                p               act
P:step_2                p               act
P:step_a                p               actsub
P:step_b                p               actsub

E:p[actsub]             action          sub
E:action[sub]           step            sub

E:p[act], E:step[sub]*  action          toplev
E:action[toplev]        step            toplev

E:step[toplev]+         task 

The problem is, the conversion only gets through the
first part -- it converts the step_* styles to p elements,
but the subsequent entries don't get recognized for some
reason. I've tried removing the E:step[sub]* from the
<action> wrapper but that didn't help either.

I have a very similar two-level structure for
bulleted lists (in the same table) and it works. I don't
understand what's happening here. I've tried using
different qualifier names, retyping element names,
checking for duplicate entries (none). The printed
manuals fill a 3.5-inch binder, so I'd hate to have to
fix all of that by hand. :-P

Can anyone see what's going on here?

--
Larry Kollar, Senior Technical Writer, ARRIS
"Content creators are the engine that drives
value in the information life cycle."
    -- Barry Schaeffer, on XML-Doc

** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **