Re: DOCBOOK-APPS: chunks and TOC's
klaas holwerda wrote: 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 stylesheet produces TOC just fine. Maybe there is another parameter i do not know of yet? Which XSLT processor did you use. Older version of Saxon had bug - one of side-effect was complete empty ToC. - Jirka Kosek e-mail: [EMAIL PROTECTED] http://www.kosek.cz To subscribe or unsubscribe from this elist use the subscription manager: http://lists.oasis-open.org/ob/adm.pl
Re: DOCBOOK-APPS: RE: RE: HTML XSL
Michael Cortez wrote:
I just tried using this, and I get back:
file:/C:/Projects/ORPS/xsl/html/autoidx.xsl:85: no such function: key
That line in the XSL Sheet is:
xsl:variable name="terms" select="//indexterm[count(.|key('letter',
translate(substring(primary;, 1,
1),lowercase;,uppercase;))[1]) = 1]"/
I am using XT for my XSL Transformation, should I be using another?
Yep. XT doesn't support key() function which is fundamental base of
autoindexing stylesheet. I'm quite satisfied by Saxon processor, be sure
that you are using latest version, older had some bugs.
-
Jirka Kosek
e-mail: [EMAIL PROTECTED]
http://www.kosek.cz
To subscribe or unsubscribe from this elist use the subscription
manager: http://lists.oasis-open.org/ob/adm.pl
Re: DOCBOOK-APPS: Suppressing page breaks
Rick Bronson wrote: 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. Thanks for your help. Rick Just by making a simple-page-sequence you are defining a new flow object, wich will began in a new page: (define ($component$) (make simple-page-sequence ;; Here's the start of Flow Object page-n-columns: %page-n-columns% page-number-restart?: (or %page-number-restart% (book-start?) (first-chapter?)) etc... Regards, Juan R. Migoya SPAIN To subscribe or unsubscribe from this elist use the subscription manager: http://lists.oasis-open.org/ob/adm.pl
DOCBOOK-APPS: indexing an entire set
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: Parameters 'default.encoding' and'saxon.character.representation'
Hi, there are parameters 'default.encoding' and 'saxon.character.representation' in chuker.xsl file to specify encoding and entity translations of chunked .html files. I use these features for generating UTF-8 encoded .html files. But I cannot find this parameter in non-chunking stylesheets. Is this a bug or is there some other way how to specify output encoding for .html files? I use Saxon 6.4.3, Crimson 1.1.1, XSL Stylesheets 1.43. Martin Perina ATACO, spol. s r. o. email: [EMAIL PROTECTED] Lesetinska 676 www: http://www.ataco.cz/ Ostrava - Kuncice phone: +420 (69) 568 28 62 707 02 fax: +420 (69) 568 27 56 Czech Republic To subscribe or unsubscribe from this elist use the subscription manager: http://lists.oasis-open.org/ob/adm.pl
Re: DOCBOOK-APPS: Suppressing page breaks
/ Rick Bronson [EMAIL PROTECTED] was heard to say: | 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. There's no particular line, it's the fact that the components use (make simple-page-sequence ...) Each simple-page-sequence has to start on, uh, a new page :-) What you have to do is change those to: (make display-group ;; or something appropriate But then you'll have to make sure that some higher-level element generates a (simple-page-sequence) because you have to have one of them. And there are probably some properties on the simple-page-sequences that aren't appropriate for display-groups; you'll have to remove those. Be seeing you, norm -- Norman Walsh [EMAIL PROTECTED] | One may be driven to commit murder http://www.oasis-open.org/docbook/ | by love or hatred, but one can Chair, DocBook Technical Committee | only advocate murder out of sheer | wickedness.--Italo Svevo To subscribe or unsubscribe from this elist use the subscription manager: http://lists.oasis-open.org/ob/adm.pl
Re: DOCBOOK-APPS: RE: RE: HTML XSL
/ Michael Cortez [EMAIL PROTECTED] was heard to say: | I am using XT for my XSL Transformation, should I be using another? Yes, XT does not support keys and cannot generate indexes. Almost any other processor will do. Be seeing you, norm -- Norman Walsh [EMAIL PROTECTED] | He that overvalues himself will http://www.oasis-open.org/docbook/ | undervalue others, and he that Chair, DocBook Technical Committee | undervalues others will oppress | them.--Dr. Johnson To subscribe or unsubscribe from this elist use the subscription manager: http://lists.oasis-open.org/ob/adm.pl
Re: DOCBOOK-APPS: Parameters 'default.encoding' and'saxon.character.representation'
/ Martin Perina [EMAIL PROTECTED] was heard to say: | cannot find this parameter in non-chunking stylesheets. Is this | a bug or is there some other way how to specify output encoding | for .html files? Uh, that's a bug. Or at least an oversight. Request it at sf.net/projects/docbook/ please. Be seeing you, norm -- Norman Walsh [EMAIL PROTECTED] | Criticism talks a good deal of http://www.oasis-open.org/docbook/ | nonsense, but even its nonsense is Chair, DocBook Technical Committee | a useful force. It keeps the | question of art before the world, | insists upon its importance, and | makes it always in order.--Henry | James To subscribe or unsubscribe from this elist use the subscription manager: http://lists.oasis-open.org/ob/adm.pl
Re: DOCBOOK-APPS: Sun Resolver classes released
Thanks Norm, That's great on the future license - hope that happens soon. Eric Norman Walsh wrote: / Eric Richardson [EMAIL PROTECTED] was heard to say: | 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? This code is a complete replacement for the Arbortext code. (And is actually a radical extension of that code base.) | What's the open source status on this new code as Sun makes us log in | etc.? I forget what the binary license agreement says. I'm this close to a source code release with a BSD-like license. There's one more legal hurdle to do a backflip through. | p.s. Figures that I just got the Arbortext catalog stuff working last | week. Well, the Resolver classes should be pretty easy to swap in. Be seeing you, norm -- Norman Walsh [EMAIL PROTECTED] | The best people usually owe their http://www.oasis-open.org/docbook/ | excellence to a combination of Chair, DocBook Technical Committee | qualities which might have been | supposed incompatible.--Bertrand | Russell To subscribe or unsubscribe from this elist use the subscription manager: http://lists.oasis-open.org/ob/adm.pl To subscribe or unsubscribe from this elist use the subscription manager: http://lists.oasis-open.org/ob/adm.pl
Re: DOCBOOK-APPS: indexing an entire set
Hi Claus, We faced the challenge of indexing a set of books last year, particularly how to incorporate some kind of functionality with the local, global, and all scope attributes on indexterms. We modified Norm's collateindex.pl to do this, and posted a diff file to this newsgroup at that time (before the days of sourceforge), but I don't think our customizations were incorporated into collateindex.pl. At any rate, we also wrote a perl script that used our modified collateindex.pl to let us generate a number of different kinds of indices for books and sets. We also had to modify our DSSSL stylesheet to produce the correct output. I know you are working with the XML stylesheets, but you can view these at the links below, and are welcome to take what you need and use it as you see fit. http://24.112.178.91/cogent/prepdoc/pd-collateindexpl.html http://24.112.178.91/cogent/prepdoc/pd-collateall.html http://24.112.178.91/cogent/prepdoc/pd-customizingthedssslstylesheets.html#PD-COGENTBOTHDSLFILE (towards the bottom) Claus Rasmussen wrote: 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? Cheerio! Bob --- Robert McIlvride ([EMAIL PROTECTED]) Cogent Real-Time Systems (www.cogent.ca) To subscribe or unsubscribe from this elist use the subscription manager: http://lists.oasis-open.org/ob/adm.pl
Re: DOCBOOK-APPS: Sun Resolver classes released
On Thu, Aug 16, 2001 at 08:42:18AM -0700, Eric Richardson wrote: Thanks Norm, That's great on the future license - hope that happens soon. Hum, that reminds me I never finished my own implementation ... Hello BTW, I just joined the docbook lists. Daniel -- Daniel Veillard | Red Hat Network http://redhat.com/products/network/ [EMAIL PROTECTED] | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ To subscribe or unsubscribe from this elist use the subscription manager: http://lists.oasis-open.org/ob/adm.pl
DOCBOOK-APPS: jadetex suit characters
I am using dsssl 1.71 and jadetex 3.10. I have hearts; spades; etc
in my sgml source. Jade transforms these into \Character{9825}, etc in the .tex file.
Spades and clubs look great, diamonds is a square rather than a rhombus, and hearts
does not print at all. The .log file contains Warning: Unknown character 9825, at
15826. If I replace \Character{9825} with $\heartsuit$ in the tex, I get a nice
heart. Any hints about where my toolchain is breaking down?
On the HTML front, the suits appear as ? with the ISO-8859-1 character set under
netscape. With UTF-8 or UTF-7, the suits get printed, but mdash; appears as ?. All
suggestions are welcome.
--
Kevin M. Dunn
Professor of Chemistry
Hampden-Sydney College
--
To subscribe or unsubscribe from this elist use the subscription
manager: http://lists.oasis-open.org/ob/adm.pl
Re: DOCBOOK-APPS: Suppressing page breaks
norm Juan, After digging for way too long, I think I'm giving up on this one... It looks too complex for me :( I'm not familiar enough with this whole thing to know what happens with footers, headers, chapter titles, etc when you have potentially multiple chapters on a single page. Thanks for your help. Rick To subscribe or unsubscribe from this elist use the subscription manager: http://lists.oasis-open.org/ob/adm.pl
DOCBOOK-APPS: fo stylesheets
Feature request please. 1. sect1/title is totally overshadowed by the 'title' in any following example or figure. Request that it be given a greater space-before and at leat a 1.2* size increase+bold. 2. xref/ presentation of xref linkend=ex1201/, and xref linkend=fig1201/, shows this in use. /para example id=ex1201 titleA basic link./title the xref produces as output the content of the title. I find it hard to distinguish the title (in line) from continuation text. If I use a period at the end of the title, it often makes little sense when read in line, I would prefer just 'example 12.3' rather than example 12.3 A basic link. I'd be guided by others experience of this, though I didn't expect the title contents unless I expanded the xref attribute set. Regards DaveP To subscribe or unsubscribe from this elist use the subscription manager: http://lists.oasis-open.org/ob/adm.pl
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].
Hi Norm,
In my docbook system, I use ant to call the parsers etc. to do the work.
My system needs to know where the root of the system is so I pass this
via a -D param to ant from a script. Other than this and one -D property
if you move the root of where the documents are stored, there is no
hardcoded paths etc. in the system.
If you don't provide a CatalogManager.properties then the following
occurs and it just hangs.
html:
[echo] Transforming: example.xml
[echo] Into:
/home/maxwell/pws/jdocbook/jdocbook_02/docroot/docs/example/example.html
[java] Cannot find CatalogManager.properties
[java] Cannot find CatalogManager.properties
[java] Cannot find CatalogManager.properties
[java] Cannot find CatalogManager.properties
[java] Cannot find CatalogManager.properties
[java] Cannot find CatalogManager.properties
The example properties file uses a full path, not a relative path for
the catalog. I put the following file in the classpath.
#CatalogManager.properties
verbosity=1
# Always use semicolons in this list
catalogs=docbook-dtd/docbook.cat
prefer=public
static-catalog=yes
allow-oasis-xml-catalog-pi=yes
catalog-class-name=com.sun.resolver.Resolver
I was hoping the system would use relative path from the classpath point
where it found the CatalogManager.properties file and it doesn't work.
I also tried a full path which works but is sub-optimal for me as this
path is hardcoded in the property file. Here is the output which either
way has the Cannot parse message. With no network it just hangs. It
can't find the catalog so it tries to fall back and use the URL?
html:
[echo] Transforming: example.xml
[echo] Into:
/home/maxwell/pws/jdocbook/jdocbook_02/docroot/docs/example/example.html
[java] Cannot parse verbosity: 1
I'm using xalan-j_2_2_D6 and here is how I am calling Xalan from ant.
java fork=true
classname=${xslt.processor}
classpathref=xalan.classpath
arg line=-IN ${input.file}
-XSL file://${xhtml.driver}
-OUT ${output.file}
-URIRESOLVER com.sun.resolver.tools.CatalogResolver
-ENTITYRESOLVER com.sun.resolver.tools.CatalogResolver/
/java
Don't really know how to proceed but the wrapper provided by Marc-Aurèle
for the old code worked great and I could pass the catalog as a system
property which I think is perhaps an alternate way to pass the minimal
property needed(the catalog) to the Resolver code.
java fork=true
classname=${xslt.processor}
classpathref=xalan.classpath
sysproperty key=xml.catalog.debug value=0/
sysproperty key=xml.catalog.override value=yes/
sysproperty key=xml.catalog.files value=${catalog.file}/
arg line=-IN ${input.file}
-XSL file://${xhtml.driver}
-OUT ${output.file}
-ENTITYRESOLVER ConfCatEntityResolver/
/java
Anyway, hope this feedback is useful.
Eric
To subscribe or unsubscribe from this elist use the subscription
manager: http://lists.oasis-open.org/ob/adm.pl
DOCBOOK-APPS: Abbrevs Auto Index PDFs
Ok, I've dumped XT and now am running with the latest Xalan, and FOP from Apache. Q1. I've still got problems with my Abbreviations just not showing up in the rendered HTML... Anyone have any suggestions? Here is a snippet of my XML: glosslist glossentry glosstermStrength/glossterm abbrevSTR/abbrev indexterm primaryStrength/primary secondaryAbility Score/secondary /indexterm glossdef para![CDATA[Strength measures a character's muscle and physical power. ]]/para /glossdef /glossentry ... /glosslist Q2. Does anybody have a short example document that works with the auto-indexer? I feed it mine, and nothing comes out... I don't even get an output file, AND I don't get any errors 8-( Q3. Also trying to product PDF files, and I get these interesting messages in the output: Warning: property - last-line-end-indent is not implemented yet. WARNING: Page subsequences exhausted. Using previous subsequence. ERROR: list-item must have exactly two children The resulting PDF missing most of my content. Any ideas here? The document validates OK in my xelen editor... Thanks, -- Michael Cortez http://www.OGExchange.com Promoting the Exchange of 100% Open Gaming Material To subscribe or unsubscribe from this elist use the subscription manager: http://lists.oasis-open.org/ob/adm.pl
Re: DOCBOOK-APPS: chunks and TOC's
Jirka, Thank you very much for your answer, i downloaded the new version of saxon, and everything is allright now, also with xt it is oke. I am very supprized that their was now warning are nothing. Anyway happy now, Thanks, JKlaas Jirka Kosek wrote: klaas holwerda wrote: To subscribe or unsubscribe from this elist use the subscription manager: http://lists.oasis-open.org/ob/adm.pl
Re: DOCBOOK-APPS: jadetex suit characters
Kevin Dunn wrote:
I am using dsssl 1.71 and jadetex 3.10. I have hearts; spades; etc
in my sgml source. Jade transforms these into \Character{9825}, etc in
the .tex file. Spades and clubs look great, diamonds is a square rather
than a rhombus, and hearts does not print at all. The .log file
contains Warning: Unknown character 9825, at 15826. If I replace
\Character{9825} with $\heartsuit$ in the tex, I get a nice heart.
Any hints about where my toolchain is breaking down?
On the HTML front, the suits appear as ? with the ISO-8859-1
character set under netscape. With UTF-8 or UTF-7, the suits get
printed, but mdash; appears as ?. All suggestions are welcome.
I don't think Norm approves of gambling. I once told him that I won
AU$20 after playing 8 hours of Mahjong, and he was mortified :-)
--
Richard Sharpe, [EMAIL PROTECTED], LPIC-1
www.samba.org, www.ethereal.com, SAMS Teach Yourself Samba
in 24 Hours, Special Edition, Using Samba
To subscribe or unsubscribe from this elist use the subscription
manager: http://lists.oasis-open.org/ob/adm.pl
