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] Assigning Default Role Values to Elements


Hi Ray,
I understand that you want to propagate role values to class attributes in the HTML, but I'm not clear on what you mean by assigning default role values to elements.  That is usually a function of the DTD.  Can you give an example of what you mean?
 
Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net
 
 
----- Original Message -----
Sent: Tuesday, October 31, 2006 2:06 PM
Subject: [docbook-apps] Assigning Default Role Values to Elements

docbook-rng 5.0b9 xsl-1.71.1 saxon-6.5.5 oxygen-7.2 (eclipse-3.2.1 plugin)

 

First, located a code fragment from Bob Staytonís excellent book to generate bare HTML content (remove the <html>, <head>, and <body> tags, as well as the template calls that fill the <head> element and generate the header and footer). In the enterprise this is a major issue. Output will be Internet-specific. Enterprise Intranet Portal HTML and FO (PDF) will continue to utilize out-of-the-box DocBook XSL with just a few customizations.

 

I must now assign default role values to numerous elements to match the enterpriseís HTML CSS class selectors. Can someone post a stylesheet customization example; elements include emphasis, emphasis role=strong, chapter, sect1-5, entry (thead), entry (tbody), entry (entrytbl tbody), etc. *.propagates.style stringparms will all be set to 1.

 

Combined with bare HTML content generation, this customization will result in the organizationís default DocBook stylesheet for Internet publication.

 

Assistance would be greatly appreciated.

 

Ray



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