On fredag 15. oktober 2004, 03:42, Joachim Breitner wrote: > Since probably each level needs (at least partly) different styling, > would you > * make the stylesheet find out what to do by looking at the root > element > * have the provider have a (hardcoded or somehow configurable) > mapping of levels to stylesheet and somehow tell AxKit what > stylesheet to use * have the provider povide different MIME-codes for > each level and use these to configure AxKit the regular way to use > the right stylesheet
That would depend heavily on to what extent they would be different. If they are very different, sure, different pipelines might be the way to go. However, I suspect they wouldn't be really *that* different, and so, I think that I would take the road of modularizing the transforms. That is, write certain templates for different parts of the document, which is then imported when you need them to perform a specific task. The final transforming stylesheet can be kept relatively simple that way, even if it has to perform many different tasks. As for transforming to different mime-types, which is indeed an important task, I haven't found The Solution yet, but I think the way to go would be to have a stylechooser plugin or something find out what kind of MIME type the client wants, and at the end of the pipeline, have different stylesheets to transform to different MIME types. As if this did bring any clarity.... :-) Cheers, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
