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] Why do formalparas only allow one para?



Here is an example where we would really like the second para to be part of the formalpara.

<formalpara>
    <title>Simple encryption</title>
    <para>This level of encryption is equivalent to obfuscation and makes it more difficult for someone using a disk utility to look at the file to decipher the data in your database. Simple encryption does not require a key to encrypt the database.</para>
   </formalpara>
   <para>Simple encryption technology is supported in previous versions of &sa_full;.</para>


The problem is that it is easy to grab the formalpara to move it somewhere else and not realize that the sentence following the formalpara belongs with it.

We don't want to use a section or a simplesect -- those tags are too big for our purposes.





Scott Hudson <scott.hudson@flatironssolutions.com>

07/23/2009 03:50 PM

To
"Kate.Wringe@sybase.com" <Kate.Wringe@sybase.com>
cc
Jirka Kosek <jirka@kosek.cz>, "docbook@lists.oasis-open.org" <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]