[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: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > / Tobias Reif <tobiasreif@pinkjuice.com> was heard to say: > | Michael Smith wrote: > | > | > Myself, I would use Literal. If that doesn't meet your need, file an > | > RFE. But I'd suggest proposing Code and not Inlineprogram. > | > | Perhaps > | <programlisting type="inline">p 6</programlisting> > | (as with simplelist) ... > > No, programlisting is always a block. I know that the DB element named programlisting always is a block, and I suggested to allow for a choice, for very short inline code snippets or extremely short programs, since some program listings are one the inline level. eg http://www.w3.org/TR/xhtml2/mod-inline-text.html#edef_inline-text_code "9.3. The code element The code element contains a fragment of computer code. [...] Example: The Pascal statement <code>i := 1;</code> assigns the literal value one to the variable <var>i</var>." Perhaps it would make sense to have element programlisting for blocks of code (parallel to XHTML 2 blockcode [bc]) and add element code for inline programs and inline code (program fragments) (parallel to XHTML code [c]). That would be great AFAICS. Is that what you proposed in the other post? > The fact that simplelist is sometimes > a block and sometimes an inline is probably not a good feature :-) Why not? I use this feature, and so far I think it's great. Tobi [bc] http://www.w3.org/TR/xhtml2/mod-block-text.html#sec_8.2. [c] http://www.w3.org/TR/xhtml2/mod-inline-text.html#edef_inline-text_code -- http://www.pinkjuice.com/
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]