docbook-tc message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: Re: [docbook-tc] parent elements of <arg>
- From: "Nancy (Paisner) Harrison" <nancyh@rational.com>
- To: Norman Walsh <ndw@nwalsh.com>
- Date: Fri, 28 Dec 2001 10:53:09 -0500
Thanks, this gives me food for thought. We were
planning on using cmdsynopsis only in reference pages, but we may want to
revisit that.
Nancy
At 03:55 PM 12/27/01 , Norman Walsh wrote:
>/ "Nancy (Paisner) Harrison" <nancyh@rational.com>
was heard to say:
>| This may be a really stupid question, but I'm trying to figure out
why an
>| <option> element can be put into <userinput>, but not
an <arg> element.
>| Since user input is often the specific rendition of a command, I
would
>| think the basic elements of a cmdsynopsis could be used
there.
>
>I don't think we imagined that userinput would be the rendition of
a
>command (rendering commands is what cmdsynopsis is for).
>
>I think the expectation was that userinput would be used to
markup
>user responses to questions (like configuration script prompts and
the
>like).
>
>| reason for doing this. But I can't figure it out now, and not
having it
>| available is problematical for me.
>
>Would parameter do? Can you provide some more context?
>
>
Be seeing you,
>
norm
>
>--
>Norman Walsh <ndw@nwalsh.com> |
The world is a vast temple
>http://www.oasis-open.org/docbook/
| dedicated to Discord.--Voltaire
>Chair, DocBook Technical Committee |
>
>----------------------------------------------------------------
>To subscribe or unsubscribe from this elist use the
subscription
>manager:
<http://lists.oasis-open.org/ob/adm.pl>
________________________
Nancy (Paisner) Harrison
Rational Software
Lexington MA
nancyh@rational.com
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC