This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
Re: [docbook] Re: How to mark up inline program listings?
- From: Tobias Reif <tobiasreif at pinkjuice dot com>
- To: docbook at lists dot oasis-open dot org
- Cc: Norman Walsh <ndw at nwalsh dot com>
- Date: Fri, 18 Jul 2003 10:30:37 +0200
- Subject: Re: [docbook] Re: How to mark up inline program listings?
- References: <200306201655.h5KGtSZI016646@village.sfbay.sun.com> <3EF34617.8080109@pinkjuice.com> <87oezspy28.fsf@nwalsh.com>
Norman Walsh wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> / Tobias Reif <tobiasreif@pinkjuice.com> was heard to say:
> |> We would use <literal> for that case.
> |
> | ... which doesn't say that the contained text is a program.
>
> <literal role="code">
This tells humans that the contents are code, but it doesn't do so in a
standardized way, thus I can't expect software to understand or handle
that information.
> But a <code> element is clearly in scope for DocBook.
Might be a good idea, but I don't know what exactly you're proposing.
Would it be inline, block, or both (eg via an attribute)?
What does it mark up; How is it (and it's content) different from
programlisting?
Tobi
--
http://www.pinkjuice.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-help@lists.oasis-open.org