2009/2/26 EMMEL Thomas <thomas.em...@3ds.com>: > Ross Gardler schrieb: > > 2009/2/26 EMMEL Thomas <thomas.em...@3ds.com>: >> Hi, >> >> there is a line in >> >> plugins/org.apache.forrest.plugin.output.pdf/resources/stylesheets/helper-commonElements.xsl >> which I changed locally for me: >> >> >> @@ -368,7 +368,7 @@ >> <xsl:apply-templates/> >> </fo:block> >> </xsl:template> >> - <xsl:template match="link|fork|jump"> >> + <xsl:template match="link|fork|jump|a"> >> <xsl:variable name="color" >> select="$config/colors/col...@name = 'body']/@link"/> >> <xsl:choose> >> >> Is it a bug or feature that <a></a> is not supported here? >> >> If I add it, the links will be activated, however they might be not useful >> in all cases yet when generating the wholesite.pdf, where >> external links need to be changed to internal links... > > In theory it is "feature". > > Internally Forrest does not have the <a> element. Under what > circumstances do you find a document containing an <a> gets processed > by this stylesheet?
... > Confusion !!!! > > <a> is the first element documented in the document-v20.dtd and is therefore > very valid element in forrest I think. > > http://forrest.apache.org/dtdx/document-v20.dtdx.html#a > > I use it everywhere I need a link since <link> and <fork> and <jump> are not > in the DTD... > > Do I miss something????? Forrest does not use the V2 DTD *internally*, it uses the V1.3 DTD [1]. This is because of history rather than design. Ultimately the intention is to move to a sbset of XHTML2 on the internals. XDoc V2 is pretty much this subset already (give or take a few bits and pieces). However, this has been the plan for a very long time and doesn't look like being implemented any time soon - it's a major rewrite of both input and output stylesheets. It is likely that there is no harm in adding the match that you identify. However, until we understand the circumstances in which you are managing to get that element to the output plugin it is hard to say. I'm worried that you might be doing something that bypasses the internal processing (which is bad) or that we have a "hole" in one of the internal processes. Such a hole would not show up when converting to HTML as the <a> element is legal there and would be passed through unmodified by the internal processing. However, given that Forrest is in use in a great many places and this hasn't raised it's head before I want to check everything is in order. To that end we need an answer to my earlier question "Under what circumstances do you find a document containing an <a> gets processed by this stylesheet?" Ross [1] http://forrest.apache.org/dtdx/document-v13.dtdx.html -- -- Ross Gardler OSS Watch - awareness and understanding of open source software development and use in education http://www.oss-watch.ac.uk
