Re: docbook conversion issue: nesting of formatting

[arnold]

Hi Eli.

> > The first issue has to do with nesting.  Texinfo, like TeX, is quite
> > general about letting you nest one thing inside another. Docbook,
> > on the other hand, is quite picky and context sensitive.  For example,
> > something like
> > 
> >     The term @address@hidden program} refers ...
> > 
> > produce this:
> > 
> >     The term <firstterm><command>awk</command> program</firstterm> refers 
> > ...
> > 
> > The problem is that <command>...</command> is not allowed to appear
> > inside <firstterm>...</firsterm>.
>
> Is this a real-life example?  Because if it is, I don't understand how
> "@command{awk} program" ended up in @dfn, since the latter is supposed
> to be used for introducing new terminology, which this phrase isn't.

Yes, it's a real example. Here is the full paragraph:

        The term @command{awk} refers to a particular program as well as
        to the language you use to tell this program what to do.  When we
        need to be careful, we call the language ``the @command{awk}
        language,'' and the program ``the @command{awk} utility.''
        This @value{DOCUMENT} explains both how to write programs in the
        @command{awk} language and how to run the @command{awk} utility.
        The term @address@hidden program} refers to a program written
        by you in the @command{awk} programming language.

I can, and probably will, work around this by changing it to say

        ... The term address@hidden program'' referss to ...

But the general issue of context sensitivity in Docbook remains.
I can find other examples, I'm pretty sure.

Thanks,

Arnold