[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [docbook] Why do formalparas only allow one para?
Right, but you still can't put anything after the section (also the formatting of the section's title is different...the heading size depends on how deep you are in nested sections and it's not a runin head). I had the very same request about formal paras from our users. I modified our DTD to allow multiple paras in a formalpara and then added a preprocessing xslt step that pulls the extra paras out of the formalpara just to be sure I'm feeding straight docbook to the docbook xslts. I think the docbook xslts would handle it, but I also have targets that generate straight docbook for interchange purposes. I think what she'd _really_ like to have is a <div>. Then she could wrap arbitrary collections of elements, assign them an id, and xinclude them into other docs. I can see where a <div> is not very semantic. Aside from semantic purity, are there other problems with having something <div>-like in DocBook to facilitate content sharing? David > -----Original Message----- > From: Scott Hudson [mailto:scott.hudson@flatironssolutions.com] > Sent: Thursday, July 23, 2009 2:50 PM > To: Kate.Wringe@sybase.com > Cc: Jirka Kosek; docbook@lists.oasis-open.org > Subject: Re: [docbook] Why do formalparas only allow one para? > > Sorry, but what makes this different than a <section> then? > > Section has a title and allows multiple para elements? > > Best regards, > > --Scott > > > Kate.Wringe@sybase.com wrote: > > > > One problem with simplesect is that it is not allowed to float in a > > component. That is, you cannot place anything after it. > > This restriction is a deal breaker for us. > > > > > > > > > > *Jirka Kosek <jirka@kosek.cz>* > > > > 07/23/2009 01:25 PM > > > > > > To > > Kate.Wringe@sybase.com > > cc > > docbook@lists.oasis-open.org > > Subject > > Re: [docbook] Why do formalparas only allow one para? > > > > > > > > > > > > > > > > > > Kate.Wringe@sybase.com wrote: > > > It would be nice if you could include multiple paras > within a > > > <formalpara>. Is there a reason why you can only have one > <para> in a > > > <formalpara> tag? > > > We have a lot of cases where we would like to use > <formalpara> but > > can't > because of the one para restriction. > > > We like the format of a formalpara because you can put > an (inline) > > title > on the content, you can embed indexterms within it, and > > because it is > container tag, you can move it easily. > > > > Doesn't simplesect fits your needs? > > > > -- > > ------------------------------------------------------------------ > > Jirka Kosek e-mail: jirka@kosek.cz http://xmlguru.cz > > ------------------------------------------------------------------ > > Professional XML consulting and training services DocBook > > customization, custom XSLT/XSL-FO document processing > > ------------------------------------------------------------------ > > OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member > > ------------------------------------------------------------------ > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: docbook-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: docbook-help@lists.oasis-open.org > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]