El mié, 08-03-2006 a las 13:09 +0930, Paul Bolger escribió:
As mentioned I'm developing a site with Dispatcher.
I don't use Internet Explorer, but unfortunately most of my clients
do. Checking my site in IE revealed a problem: Although Firefox
correctly sets the character encoding to UTF8, as
Paul Bolger wrote:
Information loss is not very accurate, I should have said something
like unpredictable behaviour. Here's just one example of such
unpredictable behaviour:
...
I can live with that. The problem here is with the people writing the
docs. I might have to see if I can work out
David Crossley wrote:
Ross, while i was fixing a bug, i encountered something
that looks like an accidental commit by you.
http://svn.apache.org/viewcvs.cgi/forrest/trunk/main/webapp/resources/schema/catalog.forrest.xcat
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project forrest-whiteboard-forrestdoc has an issue affecting its community
integration.
Thorsten Scherler wrote:
El mar, 07-03-2006 a las 21:06 +, Ross Gardler escribió:
Thorsten Scherler wrote:
El mar, 07-03-2006 a las 09:18 +, Ross Gardler escribió:
Thorsten Scherler wrote:
El lun, 06-03-2006 a las 10:13 +, Ross Gardler escribió:
Thorsten Scherler wrote:
New Doc - Migrating existing site to Forrest
Key: FOR-825
URL: http://issues.apache.org/jira/browse/FOR-825
Project: Forrest
Type: Improvement
Components: Documentation and website
Reporter: Tim Williams
[
http://issues.apache.org/jira/browse/FOR-825?page=comments#action_12369439 ]
Ross Gardler commented on FOR-825:
--
One such doc, which deals with the stripping of existing navigation and
decoration from a site so it can be rendered in Forrest is
Have we sorted out who is going to run the channel yet.?
I will be there at various stages and hope to get some more stuff done.
Hoping I can get forrest working on new computer by then!
Gav...
- Original Message -
From: Tim Williams [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
I was wondering if this would be the best way to fix this. The
alternative would be to turn off the XML declaration and add an html
type character encoding metadata statement.
If you think adding the namespace is the best way to go I'm happy to
do a patch, but it'd save me time if you could tell
Forrest Developers,
My apologies for starting a JIRA issue before writing to this list; I
didn't read Procedure for reporting bugs and issues and enhancement
suggestions on the site carefully enough before pulling the trigger...
David Crossley asked two questions in his comment to FOR-824 of
El mié, 08-03-2006 a las 14:59 +1100, David Crossley escribió:
Ross Gardler wrote:
Thorsten Scherler wrote:
Ross Gardler escribi??:
With respect to reusing the search definition code.
- What license is the definition schema released as?
Not found any information on it but it
Steve Masover wrote:
Forrest Developers,
My apologies for starting a JIRA issue before writing to this list; I
didn't read Procedure for reporting bugs and issues and enhancement
suggestions on the site carefully enough before pulling the trigger...
No problem. I could see that it would
Thorsten Scherler wrote:
David Crossley wrote:
New Revision: 384121
URL: http://svn.apache.org/viewcvs?rev=384121view=rev
Log:
She did this, he did that, none of it would be possible without the rest of
us.
Lets not start claiming ownership. Where would we stop?
Modified:
I'm probably a unique case in that I don't particular want credit for
anything I've done here. I'm usually dissatisfied with most code I've
written within a couple weeks of having written it so long-lasting
credit for it is the last thing I want. I do, however, like to be
associated with this
David Crossley asked:
Anyway, am i correct in saying that the issue was fixed
in Forrest-0.7 and your explanation (b) is to help explain (a)?
The short answer: yes, the DTD problem was fixed. I described it to
help explain why the a class=fork (et al.) problem didn't get
picked up when
It would be great if you could provide a patch or this. The advantage is
that you will not have to keep your OOo plugin in synch with the one we
release and, of course, we all get the benefit of your work.
I've made a patch, but can't see the option appearing in
forrest.properties in a new
Forrest has a lack. Only one set of menu items will
be displayed,
In my view this is a feature and not a 'lack'. Or - to put it
differently - one of two ways of handling menus. Keeping everything
open that the user opens is an alternative way of handling menus that
will soon become a pain
17 matches
Mail list logo
