Ross Gardler wrote:
But then, why not use an ID-Attribute to achieve this?
RG Perhaps this is because we can't use an ID attribute in the site:
RG protocol (I'm guessing, I do not know this to be the case).
Can anybody else tell me why?
--
Ferdinand Soethe
Hi,
just my 2 cents.
Ross Gardler [EMAIL PROTECTED] writes:
Apache Forrest is a standards-based documentation framework based
on Apache Cocoon. Forrest emphasizes separation of presentation
and content through a plugin architecture for transforming and
aggregating a variety of input sources into
Ferdinand Soethe wrote:
I know this has come up before, but I'm not sure which of the info in
old threads is still relevant today so I'll ask again:
If you remind us what came up before, then we might be able
to tell you if still relevant.
Why does Forrest expect unique element names in
David Crossley wrote:
Ferdinand Soethe wrote:
I know this has come up before, but I'm not sure which of the info in
old threads is still relevant today so I'll ask again:
If you remind us what came up before, then we might be able
to tell you if still relevant.
Why does Forrest expect unique
David Crossley wrote:
Taking the comments into account, we now have this ...
Apache Forrest is a standards-based documentation framework
which uses Apache Cocoon. Forrest emphasises separation of
presentation and content, using a plugin architecture to
transform and aggregate various
On Thu, 2005-04-21 at 13:02 +0100, Ross Gardler wrote:
Thorsten Scherler wrote:
Ok, I am not the expert on that but have a look on:
http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/components/modules/input/package-summary.html
Ross Gardler wrote:
RG I think what Ferdinand is saying is that he wants to use a schema to
RG drive an Editor for the site.xml and tabs.xml files.
Yes and Actually, while I'm at it, I'd write one schema for both files to
reduce complexity even further.
RG Without a defined
RG schema he can't
Ferdinand Soethe wrote:
Ross Gardler wrote:
...
RG I believe it will break the site: and ext: protocols as I don't think we
RG can use attributes to identify nodes in those protocols (I may be
RG wrong). Certainly the IMSManifest plugin breaks these protocols.
So is this definite? Will it break
The following comment has been added to this issue:
Author: Ross Gardler
Created: Thu, 21 Apr 2005 12:05 PM
Body:
The problem is that you have to use a template that defines which formats you
can use and then only use those when editing your dosucments. You can get the
template
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-486
Here is an overview of the issue:
-
I'm no expert when it comes to catalogs and it's late so I am not going
to try and fix this now. Perhaps someone can point me at the right docs
somewhere on the web to tell me how to do this when I return to it
tomorrow afternoon (GMT).
My question is simple how do I extend the catalog files
Ross Gardler wrote:
I'm no expert when it comes to catalogs and it's late so I am not going
to try and fix this now. Perhaps someone can point me at the right docs
somewhere on the web to tell me how to do this when I return to it
tomorrow afternoon (GMT).
My question is simple how do I
The following issue has been updated:
Updater: David Crossley (mailto:[EMAIL PROTECTED])
Date: Thu, 21 Apr 2005 6:35 PM
Changes:
summary changed from Extract DTD specific DTD's to Enable plugins
to supply their own packaged DTDs
Component changed to XML
The following comment has been added to this issue:
Author: David Crossley
Created: Thu, 21 Apr 2005 6:36 PM
Body:
See discussion in http://marc.theaimsgroup.com/?t=11141208422
-
View this comment:
Ross Gardler wrote:
From my blog
(http://www.jroller.com/page/rgardler/20050421#commercial_appreciation_of_open_source
)
Matthew Langham often posts on the relationships between Open Source
projects and commercial organisations profiting from those projects.
Usually I find myself
Ross Gardler wrote:
David Crossley wrote:
Ferdinand Soethe wrote:
I know this has come up before, but I'm not sure which of the info in
old threads is still relevant today so I'll ask again:
If you remind us what came up before, then we might be able
to tell you if still relevant.
Any
I don't understand what you mean Ross. It already works for me,
the catalog entity resolver finds the local status DTD.
That can be proved that by changing the publicIdentifier
in status.xml to be deliberately broken, then it fails
as it should,
e.g. ... PUBLIC -//APACHE//DTD Status Foo-Bust
17 matches
Mail list logo
