On 08/11/11 10:44, Lex Trotman wrote:
[...]
Thanks for the explanatin Lex, the fog is starting to clear :-)
Would something as simple as a {blockname} attribute set to the name of
the
current block ('quote', 'paragraph', 'example', 'sidebar' etc) work?
You could then do:

<text:p text:style-name="{blockname}block">para 1</text:p>

Cheers, Stuart


Setting {blockname} to the CSS class names currently used in xhtml11 and
html5
would be more consistent, the {blockname} could then replace the hardwired
class
names in xhtml11 and html5 conf files.


This will allow a single nesting block only, but thats similar to the
limitations of docbook.  I'd say it is ok for version one.

Would my previous {blockpath} suggestion help here?

http://groups.google.com/group/asciidoc/browse_thread/thread/843d7d3d671006fb/5f3b864bc3a36286?lnk=gst&q=blockpath#5f3b864bc3a36286


Thinking about the configuration file entry for paragraph, the logic
of the style part needs to be:

if user specified a [style] then
     text:style-name={style}
else if {blockname}  then
     text:style-name={blockname}
else nothing

the first part is clearly {style? text:style-name="{style}"}  but how
do I do the elseif part, ie test one attribute not defined and one is
defined?  IIUC you can't nest conditional attributes.

Do you mean the 'role' (1st positional) block attribute?
e.g. this listing:

[source,c]
--------------------------------------
#include <stdio.h>
--------------------------------------

Has a blockname of 'listingblock' and the role is 'source'

So would it make sense to set 3 global attributes?

{blockclass} = 'listingblock'
{blockrole} = 'source'
{blockname} = 'source-listingblock'

Similarly for other roled blocks/paragraphs: verse, quote, literal


Cheers, Stuart


Cheers
Lex


Cheers
Lex



Cheers, Stuart


Cheers
Lex

PS Dag is also worried about outlawing some nesting, but I don't see
that as a problem.

j>>

Cheers, Stuart

--
You received this message because you are subscribed to the Google
Groups
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/asciidoc?hl=en.




--
You received this message because you are subscribed to the Google
Groups
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/asciidoc?hl=en.




--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/asciidoc?hl=en.




--
You received this message because you are subscribed to the Google Groups 
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/asciidoc?hl=en.

Reply via email to