Re: DOCBOOK-APPS: Solution to funky TOCs in HTML Help...

/ Bradford, Denis [EMAIL PROTECTED] was heard to say: | You should always have in mind that XML (and thus XML version of | DocBook) is much more sensitive to spaces and newlines than most typical | SGML appliacations. For example: | | According to my XSLT book, XSLT has lots of ways to control

Re: DOCBOOK-APPS: caution and sect2 problem

/ Joel Boonstra [EMAIL PROTECTED] was heard to say: | Yep, that did it. Syntactically, though, it seems that the caution now | applies only to my last sect2, rather than to the parent sect1, which | seems wrong. This method seems like a hack to get things to display | properly. Visually, your

Re: DOCBOOK-APPS: Sun Resolver classes released

If you're using Saxon with these classes, beware of the following problem: AElfred, Saxon's default XML parser, has a serious bug in recent Saxon releases; it calculates the base URI of external entities incorrectly. To avoid this problem, I suggest that you use Xerces or any other JAXP

Re: DOCBOOK-APPS: Suppressing page breaks

norm, Sorry, DSSSL (print), Docbook 4.1, dsssl-1.71, jadetex 3.11. Rick / Rick Bronson [EMAIL PROTECTED] was heard to say: | I'm thinking of becoming more ecological in the publishing of my | book by eliminating page breaks after every chapter and thereby saving | tons of trees.

Re: DOCBOOK-APPS: Suppressing page breaks

/ Rick Bronson [EMAIL PROTECTED] was heard to say: | norm, | | Sorry, DSSSL (print), Docbook 4.1, dsssl-1.71, jadetex 3.11. I thought it was going to be easy, then I realized it's going to be quite tricky. In order to get proper page-break functionality (odd pages, new headers and footers,

Re: DOCBOOK-APPS: Sun Resolver classes released

Norman Walsh wrote: I'm pleased to announce that the set of Java classes that I wrote to implement the OASIS XML Catalogs Committee Specification[1] for SAX entityResolver() and JAXP URIResolver()s have been released[2]. How does this relate to the Arbortext catalog resolver code? What's

DOCBOOK-APPS: RE: HTML XSL

| 1. Create an Index. Can I just simply place IndexTerms in my document and | have the xsl sheets automatically create a hyperlinked index for me? Yes, if you use the autoidx.xsl stylesheet. Is there a complete listing of all the different XSL sheets and what they do. I had thought that

DOCBOOK-APPS: chunks and TOC's

Hi, Can anybody confirm that it is possible to have a TOC with the chunk.xsl stylesheet. (if someone else seen, i should be able also ;-) ) Downloading the last version 1.44 i believe, i still have not been able to generate them for chapters. It is a mistery to me, since the non chunked

DOCBOOK-APPS: RE: RE: HTML XSL

| 1. Create an Index. Can I just simply place IndexTerms in my document and | have the xsl sheets automatically create a hyperlinked index for me? Yes, if you use the autoidx.xsl stylesheet. I just tried using this, and I get back: file:/C:/Projects/ORPS/xsl/html/autoidx.xsl:85:

Re: DOCBOOK-APPS: Does measurement-to-length works bad?

Norman Walsh wrote: / Juan R. Migoya [EMAIL PROTECTED] was heard to say: | The measurement-to-length function in the lib/dblib.dsl file of | the Docbook DSSSL distribution works with an associative list. | It seems that the program always look for unit in uppercase (CM, MM | and so on), but

Re: DOCBOOK-APPS: Suppressing page breaks

norm, So much for ecology ;-) Ok, I guess I'm willing to take a stab at this one... but do me just one favor please, point me to the line/file that actually DOES the page break. For the life of me, I just can't locate it. I commented EVERY line in $component$ and still got page-breaks.