[
http://issues.apache.org/jira/browse/FOR-592?page=comments#action_12317757 ]
David Crossley commented on FOR-592:
Re: FOR-592 - pelt and i18n clarifications
http://marc.theaimsgroup.com/?t=11231601642
> Pelt skin not HTML 4.01 compliant
>
[
http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12317756 ]
David Crossley commented on FOR-506:
Some html validation issues ...
Re: FOR-592 - pelt and i18n clarifications
http://marc.theaimsgroup.com/?t=11231601642
> Do not hard
Thank you for tackling issues like this.
Exactly what we need, people tidying up the current
state of things rather than rushing on to new abilities.
Both are needed of course.
Interesting your FOR-592 comment:
"I would like to help if I can with various
parts of Forrest , starting with the little
On Thursday 04 August 2005 3:04 pm, Ross Gardler wrote:
> How do you avoid name conflicts given that Forrest does not have a
> monopoly on plugin publication?
>
> That is what if I call a plugin foo and Joe calls his plugin foo and
> then Forrest creates one called foo?
Hmm, I guess that does crea
Anil Ramnanan wrote:
> Ross Gardler wrote:
>
> > The wizard will then use this method to get the URL for each of the
> > plugin descriptors and processes them as you intended above.
> >
> > When we change the forrest configuration system we would just need to
> > change the way the forrest.propert
Ross Gardler wrote:
> David Crossley wrote:
> >
> >Are you just talking about the stylesheet or the DTDs too?
> >The trouble with the DTDs is that they will make this
> >plugin, and our SVN trunk, very cumbersome. How many
> >versions of Full DocBook and Simplified DocBook will
> >we support?
>
>
Ross Gardler wrote:
> The wizard will then use this method to get the URL for each of the
> plugin descriptors and processes them as you intended above.
>
> When we change the forrest configuration system we would just need to
> change the way the forrest.properties are read into the above class.
Rasik Pandey wrote:
> > At first glance, this looks like a Cocoon related error to me.
Hopefully
> > someone more familiar with Cocoon will be able to help you out.
>
>
> In addition we are now using a different version of Cocoon. If this is a
> cocoon error (and it seems to be) it may be
Addi wrote:
Diwaker Gupta wrote:
The naming convention for the plugins is fine, but I think it would be
nice if users are able to declare required plugins using simpler names
like "pdf", "text", "docbook" and so on.
We can figure out what simple names exactly to use later. I just
wanted to
David Crossley wrote:
Do we actually need to use XConfToolTask?
Cocoon recently [1] gained the ability to include
*.xconf files without needing to rewrite the main
xconf file.
Actually this had been sitting on my hard drive for a long time (around
six months ago I was trying to make Cocoon Blo
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
Phillip Evans wrote:
I suppose it is possible to modify input.xmap so that will accept
sdocbook-v1.1 as well?
Where should that be done?
You could alter the input.xmap in the
FORREST_HOME/build/plugins/org.apache.forrest.pl
Diwaker Gupta wrote:
The naming convention for the plugins is fine, but I think it would be nice if
users are able to declare required plugins using simpler names like "pdf",
"text", "docbook" and so on.
We can figure out what simple names exactly to use later. I just wanted to see
what peop
[ http://issues.apache.org/jira/browse/FOR-597?page=all ]
Rasik Pandey updated FOR-597:
-
Attachment: org.apache.forrest.plugin.internal.GoogleSitemap.zip
Cleaned up some useless files
> Internal Plugin which allows generation of a Google Sitemap conformant
[ http://issues.apache.org/jira/browse/FOR-597?page=all ]
Rasik Pandey updated FOR-597:
-
Attachment: org.apache.forrest.plugin.internal.GoogleSitemap.zip
enjoy
> Internal Plugin which allows generation of a Google Sitemap conformant list
> of pages for a F
Internal Plugin which allows generation of a Google Sitemap conformant list of
pages for a Forrest site
---
Key: FOR-597
URL: http://issues.apache.org/jira/browse/FOR-597
Pro
Just put the first version, 0.1-dev, which works with Forrest 0.7 into JIRA. Ignore the first attachment.
See:
http://issues.apache.org/jira/browse/FOR-597-- Regards,Ruswww.discountdracula
.com"Your Bargain BloodSucka:Suckin' the Best Deals Outta the Web"
> > At first glance, this looks like a Cocoon related error to me. Hopefully> > someone more familiar with Cocoon will be able to help you out.> > > In addition we are now using a different version of Cocoon. If this is a
> cocoon error (and it seems to be) it may be solved in 0.7 and/or head.I
hav
Hi All,
With regard to the above issue , which involves the pelt skin not validating
if project.i18n is not set to true I would like to clarify and then ask a
few things.
1. Setting project.i18n in any forrest.properties config file did not seem
to me to make any difference, the static site pr
On Thu, 2005-08-04 at 10:31 +0200, Cyriaque Dupoirieux wrote:
> Diwaker Gupta a écrit :
>
> >I'm trying to make a contract for google maps. Here's the problem I'm facing:
> >
> >Something like this in the contract works:
> >http://maps.google.com/maps?file=api
> >
> >But this fails:
> >http://maps
On 8/4/05 04:16, Diwaker Gupta wrote:
> I'm trying to make a contract for google maps. Here's the problem I'm facing:
>
> Something like this in the contract works:
> http://maps.google.com/maps?file=api
>
> But this fails:
> http://maps.google.com/maps?file=api&v=1
>
Diwaker Gupta a écrit :
I'm trying to make a contract for google maps. Here's the problem I'm facing:
Something like this in the contract works:
http://maps.google.com/maps?file=api
But this fails:
http://maps.google.com/maps?file=api&v=1
^^^
After plenty of t
I'm trying to make a contract for google maps. Here's the problem I'm facing:
Something like this in the contract works:
http://maps.google.com/maps?file=api
But this fails:
http://maps.google.com/maps?file=api&v=1
^^^
After plenty of trial and error, I think I'
The naming convention for the plugins is fine, but I think it would be nice if
users are able to declare required plugins using simpler names like "pdf",
"text", "docbook" and so on.
We can figure out what simple names exactly to use later. I just wanted to see
what people feel about this? It s
23 matches
Mail list logo
