Dear M. Shafie, Thank you for the explanations; indeed, we know how to use the profiling stylesheets (because that what we do) and how to use XHTML rather than HTML from our customization.
What we don't know is how to let the user choose, as you do in the stock DocBook documentation... but I am not sure this is 100% useful in our case, since all Web browsers deployed nowadays in our company fully support XHTML. Many thanks, philippe. PS: Starting hints on how to implement this support in our customization would be appreciated, just for the record. > When custom XSLT stylesheets have been specified by a consultant like > you, we simply do *not* know how to implement: > > * Generate XHTML rather than HTML > * Use the profiling stylesheets > > We know how to implement the above features only for the *stock* DocBook > XSLT stylesheets. > > You, as a consultant (i.e. as opposed to a normal user), are expected to > specify: > > <property name="docb.toHTML1.transform" url="true"> > xsl/html1/default_custom.xsl > </property> > > where "xsl/html1/default_custom.xsl" > > * readily generates XHTML rather than HTML, if this is what you prefer. > * readily imports the profiling XSLT stylesheets rather the normal one, > if this is what you prefer. > > > >
<<attachment: philippe_nobili.vcf>>
-- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
