This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
Re: [docbook] how to represent userinput with a command option?
- From: "Robert P. J. Day" <rpjday at mindspring dot com>
- To: Yann Dirson <ydirson at fr dot alcove dot com>
- Cc: docbook mailing list <docbook at lists dot oasis-open dot org>
- Date: Tue, 13 May 2003 12:37:12 -0400 (EDT)
- Subject: Re: [docbook] how to represent userinput with a command option?
On Tue, 13 May 2003, Yann Dirson wrote:
> On Tue, May 13, 2003 at 12:19:28PM -0400, Robert P. J. Day wrote:
> > nice idea, but wrapping the above in a <userinput> causes everything
> > to be bolded, which is what i'm trying to avoid.
> >
> > also, i'm not sure that, semantically, i should be using a
> > <cmdsynopsis>. i'm not trying to supply a command synopsis,
> > just trying to show a sample *usage* of that command, which
> > i'm convinced shouldn't represent the same thing.
>
> In that case, probably you should just not try to specify optional
> stuff in this place ?
well, as i think about it, it is kind of a special case, as it's
early in a manual, and i'm demonstrating to the class what it means
to see a command where part of it is optional.
in this case, i think it's OK to just cheat for now.
rday
---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-help@lists.oasis-open.org