Re: XSLT call to arms! (was Re: [PHP-DOC] revcheck.html)

> > I'll check this out as soon as I have sufficient time. I am > > currently working on a quite ugly regular expression based > > implementation to generate newchm output. I am quite ready > > with it, only some errors are left... > > With respect, generating HTML Help by XSLT stylesheets works like a > charm, no need for REs, everything is taken directly from XML sources. Well for the first time, it seemed that producing HTML Help output from DSSSL generated output filtered through some formatting regepxs are better then a) Writing a new DSSSL customization or b) Writing a new XSL customization because a) Starting always from XML sources seems too much pain to me, as we have many HTML formats out here. To generate every format from XML, we need to pay with our time for too much repetitive work b) XSL is currently not supported enough in phpdoc c) It takes much more time to generate output from XML than output from HTML using my custom regexps (related to prev point). As we already have DSSSL generated HTML, why not reuse it? d) I have no profession to do the customizations for the cute things we decided to include in the HTML Help Edition. e) Some of these customizations are even not possible with DSSSL/XSL, for example the color coding of examples. Some of the customizations would be a pain to implement, like "path to this page", as it is more easier to implement in PHP... Well, I know, that using some heavily customized XSL style sheets would be the best method for interoperability, wide range of tools available, and general point of view. But after considering the points above, I decided to use regexps in PHP to filter DSSSL generated HTML code. With each and every new "filter" I add to my regexps, I see that this is not the best way in the long run, but it's still fast, and it works. I have just sent a sample to php-doc-chm@lists.php.net with the current filtered DSSSL HTML files. They look quite professional (with some CSS related exceptions). There are some points where my concept fails: a) in the future, DSSSL will go out, and it would mean a need for a complete overhaul of my filter code (it is based heavily on DSSSL created HTML constructs) b) while the code is well commented, it is still hard to modify to reflect filtering needs, as complex pregs are not that easy to understand, and pregs to filter complex structures are not that easy to implement I would not like to ask anybody to help me figure out how to implement XSL code producing equivalent output to our filters output, as a) we have no final desired output b) the thing to do are quite complex, and time consuming I attached a sample created by our interface designer, Holger Eggert, presenting how manual page structures look like (this is not a correct date manual page, as it contains all the stuff we considered to be formatted, like tables, warnings, and so on). I cannot feel enough power in myself to make any XSL customizations to produce HTML code as seen in date_lo.html currently. The official mailing list for discussion about designs, programs, CSS, JS and other related issues is php-doc-chm@lists.php.net BTW. Goba

Attachment: [text/css] stylesheet_lo.css
Attachment: [text/html] date_lo.html