Gav wrote:
>
> What would be the consequences of moving header/abstract into ?
>
> I am trying to re-organise header/abstract + MOTD + ToC into a container
> div, but is a little difficult when some of the content/structure comes from
> site-to-xhtml.xsl and some come from document-to-html.x
Gav... wrote:
> who="David Crossley"
> > Ross Gardler wrote:
> >> David Crossley wrote:
> >> >Gav wrote:
> >> >>
> >> >> In site-to-xhtml.xsl we have tests which to me say :-
> >> >>
> >> >> when:
> >> >> if test = x then do z
> >> >> otherwise:
> >> >> if test = y then do z
> >> >>
> >> >> In
[
https://issues.apache.org/jira/browse/FOR-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SinDoc updated FOR-1018:
Attachment: sourcetypeaction-rdf.patch
As a workaround, I'd suggest to add handle RDF files a bit differently, that i
[
https://issues.apache.org/jira/browse/FOR-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510794
]
SinDoc commented on FOR-1018:
-
I forgot to make a patch from $FORREST_HOME, so just in case, here [1] is
another one.
[1]
Making sourcetypeaction work for RDF files
--
Key: FOR-1018
URL: https://issues.apache.org/jira/browse/FOR-1018
Project: Forrest
Issue Type: Sub-task
Components: Plugin: input.doap, Plugin: i
[
https://issues.apache.org/jira/browse/FOR-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510629
]
David Crossley commented on FOR-655:
Need to update our example file, after updating our RELAX NG to be
http://www.
[
https://issues.apache.org/jira/browse/FOR-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510628
]
David Crossley commented on FOR-654:
Need to update our copy to the current Working Draft 26 July 2006
(http://www.
Ross Gardler wrote:
> Oshani Seneviratne wrote:
> >
> >In the FOAF plugin, I was trying to make the FOAF data get
> >auto-discovered by a tool like Semantic Radar [1]. To do that, I
> >believe there should be a link tag, such as the following, inside the
> >head element of the page.
> >
> >
> >
> >