On Thu, Oct 17, 2002 at 09:18:24PM -0700, Swen Stsop wrote:
I believe I understand that using chunk.xsl with cocoon
doesn't work. This is because it designed to save the
output to files and now send it to standard out I'm on the
right track, right?. So is there some stylesheets out
there
How much modification do you suppose there would be to add navigation? If you could include it you could modify how links to other parts of the book are made. So instead of href="cho2.html" it could be href="doc.html?root.id=ch02#anchor". Something like that. Does that make sense?
Bob Stayton
On Fri, Oct 18, 2002 at 05:03:55AM -0700, Swen Stsop wrote:
How much modification do you suppose there would be to add navigation? If you could
include it you could modify how links to other parts of the book are made. So
instead of href=cho2.html it could be
Hey thanks. I think I'm on the right trackand may just have to write something myself. I'll post it if I get it working. It will be as generic as possible.
Any more ideas out there?
Thanks in advance.
Bob Stayton [EMAIL PROTECTED] wrote:
On Fri, Oct 18, 2002 at 05:03:55AM -0700, Swen Stsop
I believe I understand that using chunk.xsl with cocoon doesn't work. This is becauseit designed to save the output to files and now send it to standard out I'm on the right track, right?. So is there some stylesheets out there that can support chunking for cocoon? I'm guessing you pass the xslt
At 21:58 04/05/2002 +0200, Jirka Kosek wrote:
This is (was) bug in AElfred. Mike Kay said me that he fixed this bug in
6.5.2, but I didn't test it yet. Same bug caused troubles with catalog
files and AElfred when used within Saxon. You can try Saxon 6.5.2, and
if this doesn't help, you can still
you can still change default parser used by Saxon
to Xerces by setting system property
javax.xml.parsers.SAXParserFactory=
org.apache.xerces.jaxp.SAXParserFactoryImpl.
well... 8-(
I've tried swapping out to 1.49 version of the sheets, I've tried hardcoding
the file paths in the i18n.xml
Dave Pawson wrote:
At 21:58 04/05/2002 +0200, Jirka Kosek wrote:
This is (was) bug in AElfred. Mike Kay said me that he fixed this bug in
6.5.2, but I didn't test it yet. Same bug caused troubles with catalog
files and AElfred when used within Saxon. You can try Saxon 6.5.2, and
if this
Hi Jirka,
Jirka Kosek wrote:
Sven Kitschke wrote:
In the tomcat-dir\webapps\cocoon\WEB-INF\logs\core.log you
can find: java.net.MalformedURLException: no protocol: af.xml
(adding file: doesn't fix the problem)
Aha.
I know that's the wrong list, but: has anyone an idea
where
Hi Michael,
Michael Cortez wrote:
I've tried swapping out to 1.49 version of the sheets, I've tried hardcoding
the file paths in the i18n.xml .xsl files and I've tried configuring the
I'm sure you mean l10n.xml. But are you in the right file? At least you
should see an other error
I'm sure you mean l10n.xml. But are you in the right file?
Ya... sorry, right file, bad quote on my part.
At least you should see an other error message in the logs
(resource or file/path not found).
Maybe the uris are not right. For Windows worked for example
file:/e:/my-path/xsl/common/af.xml or
Hip, hip, hurray! It works 8-D
One problem down, on to the next Now I just got to figure out how to get
it to stop trying to cache the xml pipeline, since I'm using Xindice --
which from cocoon doesn't support caching -- but it keeps trying, so only
Michael Cortez wrote:
7.0 and 7.1 are experimental releases. In order to use
saxon:output the
stylesheet has to have a version number different than 1.0.
For compatibility's saxe I would stick to 6.5
Running with 6.5.1 I appear to be having Localization problems now 8-(
Lots
Hi,
Michael Cortez wrote:
[snip]
Lots of:
No localization exists for en or . Using default en.
No en localization of TableofContents exists.
No localization exists for en or . Using default en.
No en localization exists.
Sven Kitschke wrote:
In the tomcat-dir\webapps\cocoon\WEB-INF\logs\core.log you
can find: java.net.MalformedURLException: no protocol: af.xml
(adding file: doesn't fix the problem)
Aha.
I know that's the wrong list, but: has anyone an idea
where the bug resides? Is it a configuration
Has anyone been able to get Cocoon to process DocBook, books with the 1.50
Stylesheets? I've been fighting with this for the last couple of days, and
I can get Cocoon to process DocBook articles w/o any problems, but not
DocBook books...
I suspect this is probably a problem with Cocoon, so I've
Michael Cortez wrote:
Has anyone been able to get Cocoon to process DocBook, books with the 1.50
Stylesheets? I've been fighting with this for the last couple of days, and
I can get Cocoon to process DocBook articles w/o any problems, but not
DocBook books...
Problem might by in Xalan.
Problem might by in Xalan. This is processor which is used
by default in Cocoon and Xalan has some serious problems
with some of DocBook stylesheets.
That was one of my suspects -- does XT do any better? I've some
documentation on switching out from Xalan to XT. Normally I use Saxon but
Michael Cortez wrote:
Problem might by in Xalan. This is processor which is used
by default in Cocoon and Xalan has some serious problems
with some of DocBook stylesheets.
That was one of my suspects -- does XT do any better? I've some
documentation on switching out from Xalan to XT.
Michael:
7.0 and 7.1 are experimental releases. In order to use saxon:output the
stylesheet has to have a version number different than 1.0.
For compatibility's saxe I would stick to 6.5
Carlos
On 05/03/02 14:24, Michael Cortez [EMAIL PROTECTED] wrote:
I'm not entirely sure Tomcat Cocoon
7.0 and 7.1 are experimental releases. In order to use
saxon:output the
stylesheet has to have a version number different than 1.0.
For compatibility's saxe I would stick to 6.5
Running with 6.5.1 I appear to be having Localization problems now 8-(
Lots of:
21 matches
Mail list logo
