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


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

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

Subject: Re: [docbook-apps] Is verbatim something that can be inherited by inline elements?


I tried this example using the sourceforge stylesheets (1.76.1), both in print and html, and the line breaks were preserved, even inside the inline markup. So, these stylesheets work as you (and I) think they should.

The specification says that "Line-specific environments," which include the verbatim elements, preserve whitespace and line breaks in the source text. The general description of inline elements says that inlines "do not cause line or paragraph breaks." I take that to mean that unlike a block element, the processor should not insert a line break before or after an inline element. I don't take it to mean that inlines change the mode of operation inherited from the enclosing block.

I suppose the specification could explicitly say that white space and line breaks inside an inline are to be treated in accordance with the style of the enclosing block. However, I think it's pretty clear, esp. since any other interpretation would force you to do some pretty gruesome things (like closing an inline at the end of a line, then reopening it at the beginning of the next), just to preserve the verbatim environment.

So I think the problem is a real bug, but not one in the sourceforge stylesheets. Rather it looks like a bug either in Publican or in a customization (are you using a customization?)

I hope that helps,
Richard Hamilton
XML Press
XML for Technical Communicators

On Nov 11, 2011, at 12:17 AM, Raphael Hertzog wrote:

> (Please cc-me your answers)
> Hello,
> I argued in a publican bugreport that <computeroutput> within <screen>
> should be treated like a verbatim environment:
> https://bugzilla.redhat.com/show_bug.cgi?id=752881
> It got closed because the spec clearly say it's not a verbatim environment
> in itself:
> http://docbook.org/tdg/en/html/computeroutput.html
> Is this really correct? If yes, I wonder what's the point of allowing
> computeroutput within a <screen>...
> Cheers,
> -- 
> Raphaël Hertzog ◈ Writer/Consultant ◈ Debian Developer
> Pre-order a copy of The Debian Administrator's Handbook and
> help liberate it: http://debian-handbook.info/go/ulule-rh/
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org

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