[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] Imageobject choices for ROLE.
Hi Dean,
Out of the box, the role values that work are established by the
global param named 'stylesheet.result.type', which is set in each
stylesheet. It is not set in the param.xsl file because it is an internal
param that is not to be set by the user.
- In fo/docbook.xsl, $stylehsheet.result.type is set to 'fo', so an
imageobject with role="fo" is matched there.
- In html/docbook.xsl, the param is set to 'html'. Since chunk.xsl imports
that file, it gets that value too.
- In xhtml/docbook.xsl and xhtml_1-1/docbook.xsl, it is set to 'xhtml', but
the selection process will fall back to an imageobject with role="html" if there
isn't an imageobject with role='xhtml'.
- All the other stylesheets inherit the param value that they import.
Since htmlhelp imports html/docbook.xsl, it selects for 'html' too. Same
with eclipse and javahelp. The epub stylesheet imports xhtml_1.1, it
selects for 'xhtml' (with fallback to 'html').
You mentioned role values of 'HTML', 'XHTML', 'fo-xep', and 'fo-fop'.
None of those would be recognized (it is case sensitive), and the selection
process falls back to looking at image filename extensions to find one that is
acceptable for the given output.
But you can override any of these by setting the param
'preferred.mediaobject.role' in your customization layer to some value other
than blank. That param is checked first. My example with 'fo-xep'
set that param as an example of customizing the selection process.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]