Re: Re: modified XSL problems...
| From: | Thomas Schöfbeck | Date: | Tue, 22 Apr 2003 19:26:35 +0000 |
| Subject: | Re: Re: modified XSL problems... | ||
| References: | 1 2 3 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969352815@lists.php.net to get a copy of this message | ||
Gabor Hojtsy wrote:
For the HTML Help stuff, the rule was: leave all CSS possible, and let skin designers use them if they want. I already have one skin on my hdd, but have not released it, cause I am delaying it till the next content update. There are quite a few CSS classes used in the HTMLHelp CSS files (see the htmlhelp/suippfiles/html dir in phpdoc CVS), though I have not cheked if those you disabled were used or not...We'll see when I work on it
Since it's already there and work, I'll leave it as is (BTW, I don't know if there is a absolutely right customization method, at least at this stage of docbook-xsl). ThomasJust short to the tech-question: The above template is called by e.g. <xsl:apply-templates select="." mode="phpdoc.object.title"/> and the above template itself calls another template (substitute-markup), which calls <xsl:apply-templates select="." mode="title.markup"/>. So why don't we call immediately the second one, saving 2 steps?This is a subroutine ;) It jumps to the substitute-markup template with parameters. substitute-markup's default params are not those used here to call it. BTW substitute-markup may call title.markup at the end, but it was not clear to me that this is always the case, and I considered it a wrong customization method to dig down into the templates when the sheets provide abstraction. This method may be slower a bit, but more compatible with future sheets... At least these are my reasons. If this clearly does the same, then feel free to modify the phpweb sheet accordingly.