DOCBOOK-APPS: indexing an entire set

2001-08-16 Thread Claus Rasmussen

Hi all,

I've successfully made indexes for my books. Now I want to combine some books 
in a set - is there no way of making an index for the entire set? The spec 
says that index can't be a child of set.

I know there is setindex, but that doesn't let me benefit from the 
automated indexing provided by Norm's XSL style sheets?

I'm using xml-books (4.1.2) with Saxon and Norms style sheets.

/claus



To subscribe or unsubscribe from this elist use the subscription
manager: http://lists.oasis-open.org/ob/adm.pl



DOCBOOK-APPS: Can anything handle tables when creating PDFs?

2001-05-30 Thread Claus Rasmussen

Hi all,

Is there _any_ product, free or commercial, that will handle tables correctly
when producing PDFs - without me supplying the column-widths? I'm sort of sick
of trying all kinds of tricks.

My setup:
DocBook XML 4.1.2
XSL 1.34 (not moving on for now since I've based a lot of custom stuff on the
'old model')
Saxon 6.2.2

Thanks,
Claus



--
To unsubscribe from this elist send a message with the single word
unsubscribe in the body to: [EMAIL PROTECTED]



Re: DOCBOOK-APPS: Xalan is stealing my sleep

2001-03-01 Thread Claus Rasmussen

 XSLT Error (javax.xml.transform.TransformerException): -9
 
 Very helpful message, eh?  8^)
 
 I think Norm will have to fix chunk.xsl to work
 with XalanJ2, beyond my simple adjustment above.

If it's of any assistance to Norm or others, the problem comes when Xalan is 
about to finalize the chunking. All pages are created, but when finalizing and 
writing the index.html (or whatever) it explodes.

For instance, this simple file throws the error - produces all the sections as 
files, but not the final "cover page":


  chapter id="some-id"
titleFor Everyone/title

section
titleOverview/title
paraBrief introduction/para
/section

section
titleMore stuff/title
paraSome content/para
/section
   /chapter


I simply haven't been able to figure out where the style sheets could be 
wrong, and since I'm no Java man, I can't tell if it's a problem with the 
Xalan extension for chunking.

Anyone?

/claus


--
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: [EMAIL PROTECTED]

--
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: [EMAIL PROTECTED]



DOCBOOK-APPS: Xalan is stealing my sleep

2001-02-27 Thread Claus Rasmussen

First of all - this posting contains a lot of error-messages. Sorry for
that, but it's the only way I can sketch out my problem.

For a while I've been thinking that it had to be our customizations that
broke Xalan 2, but now I give up:

I install a pure, untouched version of

 - Xalan 2 java
 - Norms XSL style sheets v1.29
 - The DocBook XML DTD v4.1.2

The Xalan tests all run without problems.

When I try the tests that come with Norms style sheets the trouble begins.

(I should mention that chunking is the problem - producing one big document
goes smoothly).

First error is:

DOM ERROR! class: org.apache.xalan.templates.ElemExtensionCall
file:///home/claus/docbook/xsl/1.29-untouched/docbook/html/chunk.xsl; Line
17; Column 58;
XSLT Error (javax.xml.transform.TransformerConfigurationException): Failed
calling setPrefix method!

Closer inspection of chunk.xsl shows a workaround for Xalan 1. I comment
this out and try again:

file:///home/claus/docbook/xsl/1.29-untouched/docbook/html/chunk-common.xsl;
Line 657; Column 16; Writing ch01s02.html f
or sect1
javax.xml.transform.TransformerException
at
org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j
ava:1212)
at
org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:2894)
at java.lang.Thread.run(Thread.java:484)
-
java.lang.ArrayIndexOutOfBoundsException
at org.apache.xml.utils.BoolStack.pop(BoolStack.java:134)
at
org.apache.xalan.serialize.SerializerToHTML.endElement(SerializerToHTML.java
:631)
at
org.apache.xalan.transformer.ResultTreeHandler.endElement(ResultTreeHandler.
java:284)
at
org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:
749)
at
org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform
erImpl.java:2154)
at
org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform
erImpl.java:2097)
at
org.apache.xalan.templates.ElemTemplate.execute(ElemTemplate.java:380)
at
org.apache.xalan.templates.ElemCallTemplate.execute(ElemCallTemplate.java:20
2)

...and some 20-30 lines more of java errors.

Now this is exactly what happens with my customized style sheet also - I
just wanted to test it with ...the tests.

Am I insane? Is my Java insane? What am I doing wrong ?

Anyone helping out will go to bed tonight knowing that he/she pulled a
desperate guy back from the edge...

Thanks,
Claus


--
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: [EMAIL PROTECTED]



DOCBOOK-APPS: Still want id to turn into filename

2001-01-18 Thread Claus Rasmussen

Hi folks,

I asked a question a few days ago regarding having my id-tags turn into 
filenames when parsing to HTML.

My setup: 
- DocBook 4.1.2 XML DTD
- XSL StyleSheets 1.24 (went back to the stable one - tried 1.28)
- XT (and yes, I'm using xtchunk.xsl)

I still can't make the magic happen, which is crucial for us to move on from 
the ol' DSSSL stuff (don't want our URLs to change and hold no meaning).

So let me ask in another way: What will _prevent_ id-tags from turning into 
filenames when parsing?

/claus