forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: svn commit: r392105 - /forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.input.glossary/src/documentation/content/xdocs/glossary.xml
Date Fri, 07 Apr 2006 08:05:25 GMT
David Crossley wrote:
> Ross Gardler wrote:
>>>Author: crossley
>>>Date: Thu Apr  6 15:47:46 2006
>>>New Revision: 392105
>>>Remove examples of acronym and definition/@cite until we know how to use 
>>See inline...
Thu Apr  6 15:47:46 2006
>>>@@ -23,10 +23,11 @@
>>>    <title>C</title>
>>>    <item id="CSS">
>>>      <term>Cascading Style Sheets</term>
>>>-      <acronym>CSS</acronym>
>>>-      <definition cite="">Cascading Style 
>>>Sheets (CSS)
>>>+      <definition>Cascading Style Sheets (CSS)
>>>      is a simple mechanism for adding style (e.g. fonts, colors, 
>>>      spacing) to Web
>>>-      documents.</definition>
>>Cite is used to link to an original source for the definition. Each 
>>glossary term can have multiple definitions, some of which may not be 
>>our copyright, therefore we need to cite the source.
> Yes definitely. That is why i was careful to add this
> workaround.
>>>+      documents.
>>>+      Source: <a href="">W3C</a>.
> That was my workaround because i could not get the @cite
> to work. The generated html had links that went nowhere.
> Now that i look more carefully at your example site,
> i understand more. It seems that it is somehow magically
> linked to a citations document. Great, however we don't
> yet have the Citations plugin at Forrest. FOR-756

Ahhhh... I completely forgot about that. When I get time I'll dig out 
the citations "plugin" too. It's in the same state as the original 
glossary donation (i.e. against Forest 0.5).

All these "plugins" are the reason I created the plugin framework in the 
first place. Its ironic that I have never found the time to migrate the 
original motivations to real plugins. I suppose that is what happens 
with a change in job.

> Also i was getting xml validation errors, e.g.
> "An element with the identifier "W3C-CSS" must appear in the document."

Not sure about that I'm afraid.


View raw message