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

Second sentence should read ‘… for specific elements’ not attributes.


From: Miller, Ray (Centech)
Sent: Monday, November 06, 2006 9:30 AM
To: docbook-apps@lists.oasis-open.org
Subject: RE: [docbook-apps] Assigning Default Role Values to Elements


>>One can write CSS selectors to match on these default class values.  It looks like you are looking to override the default class values with other values using the role attribute.  Is that because you want the authors to be able to assign different styles to different chapter titles?  Your example only showed one style, so I wasn't sure if that's what you intended.<<


CSS class selectors are pre-defined by the enterprise. So yes, wish to override class selectors for specific attributes. Currently do so with phrase, emphasis and para elements; wish to accomplish this transparently though a stylesheet customization. As for the chapter and section titles, they must too conform to the enterprise CSS which does not rely on <h1> <h2> <h3> … for chapter and section title formatting in user content areas, instead utilizing custom CSS class selector names. What I wish to accomplish is a stylesheet customization that conforms to the enterprise’s CSS without having to apply role=  in elements or wrapping Chapter and Section titles with phrase elements. In short, transparent enterprise CSS conformance. This is a MAJOR issue that must be resolved for DocBook enterprise Internet and Intranet acceptance; authors need to focus on artifact content and structure only; presentation must be pre-defined and transparently conformant.



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