OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook] Re: How to mark up inline program listings?

Norman Walsh wrote:
 > 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 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]