P

DeanNelson <[email protected]> schrieb:

>All,
>Wouldn't this be a real useful option in the var'lists? I know that in my own 
>conversions I needed to list in this manner but the only structure that would 
>look right is bold/underline the first term in the paragraph -which is wrong 
>on many levels. So if you go with a structure that is more sensible 
>(var'lists) then you have to "settle" for a significant space waste.
>
>Wouldn't this option be a great addition to stock DocBook variable lists? If 
>so, can file a bug report. If there is a better way to do it - I'd like to 
>know!
>
>Dean Nelson
>
>
>
>In a message dated 02/10/10 06:40:09 Pacific Standard Time, [email protected] 
>writes:
>
> 
> 
>Ok, in that case you could adapt the formalpara/title template and use it in 
>processing your variablelists :-) It's certainly possible to do that in your 
>customization layer. The fact that the structure of a varlistentry and a 
>formalpara is slightly different won't stop you and it would be a reasonble 
>customization to use for learning a little xslt (i.e. neither impossibly hard 
>nor so simple that you wouldn't learn anything). 
>
>David
>
>
>
>
>From: Laurie Burley [mailto:[email protected]] 
>Sent: Wednesday, February 10, 2010 8:14 AM
>To: David Cramer; [email protected]
>Subject: RE: [docbook-apps] variablelist styles
>
>
>Thanks David..
> 
> I’ve already looked at that.. I was just hoping that the variablelist could 
> be modified as the formalpara option would require us to change all our 
> variablelists to formal paragraphs.
> 
>I suppose we’ll need to revisit our use of variablelists... L
> 
>Regards,
> 
>Laurie.
> 
>From: David Cramer [mailto:[email protected]] 
>Sent: 10 February 2010 14:08
>To: Laurie Burley; [email protected]
>Subject: RE: [docbook-apps] variablelist styles
> 
>I think you really want a list of formalparas but without bullets.
> 
><itemizedlist mark="none">
><listitem><formalpara><title>Term</title><para>Definition of term 
>here.</para></formalpara></listitem>
></itemizedlist>
> 
>Note that you don't need to add a period in the title. The xsls add it for 
>you. However, if you add a .!? or : the xsls don't add a period. This behavior 
>is controlled by the xsl params:
> 
><xsl:param name="runinhead.default.title.end.punct" select="'.'"/>
><xsl:param name="runinhead.title.end.punct" select="'.!?:'"/>
> 
>David
>
>
>
>From: Laurie Burley [mailto:[email protected]] 
>Sent: Wednesday, February 10, 2010 5:31 AM
>To: [email protected]
>Subject: [docbook-apps] variablelist styles
>Hi,
> 
>I’ve been playing around with the variablelist styles to try and figure out if 
>there is a way to make the variablelist term and listitem definition appear on 
>the same line, but as if they run together.
> 
>I don’t like the default vl.as.list style because we have several long terms 
>and I don’t like the wrap behaviour of the list-item-label which is 
>independent to the list-item-body wrap behaviour.
> 
>Currently I have the following behaviour using the list style:
> 
>Term.                    Definition for the term here.
>Next Term.         Definition for next term here.
>Third Term          Definition for third term here.
>with a really 
>long title.
> 
>What I would like is:
> 
>Term.  Definition for the term here.
>Next Term.  Definition for next term here.
>Third Term with a really long title.  Definition for the third term here.
> 
>I am relatively new to XSL, so there is a lot about the way things nest that I 
>don’t understand yet. What I want may not be possible because of the listitem 
>element, but I thought it wouldn’t hurt to ask. Has anyone managed to create 
>the behaviour I would like above?
> 
>Any suggestions or advice would be really appreciated.
> 
>Kind Regards,
> 
>Laurie.
>Laurie Burley
>Sr. Tech Comm Spc.
>Kofax U.K., Ltd.
>201 Cambridge Science Park
>Milton Road, Cambridge
>CB4 0GZ
>United Kingdom
>Tel: +44 (0) 1223 226021
>[email protected]
> 
>
>
>
>This communication is only for the use of the intended recipient. It may 
>contain confidential or proprietary information. If you are not the intended 
>recipient or have received this communication in error, please notify the 
>sender via phone and destroy this communication immediately. 
> 
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to