Abel Braaksma wrote:
Yves Forkl wrote:
My idea was to define an XML language that would describe the
desired transformation for each p style, and to retrieve the
transformation rules specified as XML from inside the
application-specific style sheet that just imports the module with
the unmodified "p" template.
try XSLT, it is an XML language that can be used to describe any
desired transformation.
Good point. :-) I will follow your advice and try developing a
meta-stylesheet to generate the template rules I need. (There will be a
lot of repeated code, that's why I looked to generate it by configuring
a more general process, while hoping to escape the need of actually
generating XSLT style sheets by means of XSLT.) Thank you also for your
hints about other techniques like customization by reading external
documents and about "tuning" import of modules.
Meanwhile, I am doing as David suggested, writing conventional templates
that match "p" elements depending on their style attribute.
The grouping problem still trips me up... I will give details on it in
my reply to Michael's posting. Thank you all so far for helping me that
much.
Yves
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--