[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: docbook-apps-digest Digest #445
Re: DOCBOOK-APPS: <beginpage /> fails with fop xsl 1.60.1 Re: DOCBOOK-APPS: XIncludes DOCBOOK-APPS: Re: XIncludes [Fwd: Re: DOCBOOK-APPS: <beginpage /> fails with fop xsl 1.60.1] DOCBOOK-APPS: Re: NW-DBK2FO-XSLTs 1.60.1: titlepage doesn't work anymore DOCBOOK-APPS: xsltproc: fox:outline element missing for TOC bookmark in PDF DOCBOOK-APPS: Problems with saxon, XML Catalogs, and dbnotnx.mod DOCBOOK-APPS: Help with customizing headers Re: DOCBOOK-APPS: Re: XIncludes Re: DOCBOOK-APPS: Re: XIncludes DOCBOOK-APPS: Re: Context dependent styling of footnotes DOCBOOK-APPS: Re: Chunked HTML file names too long for ISO9660 DOCBOOK-APPS: Re: Top border lacking on repeated table headers with xep RE: DOCBOOK-APPS: Re: Top border lacking on repeated table headers with xep DOCBOOK-APPS: Re: Chunked HTML file names too long for ISO9660 Re: DOCBOOK-APPS: FOP: "No ImageReader" when using PDF as vector format Re: DOCBOOK-APPS: Table breaking over pages Re: DOCBOOK-APPS: image sizes Re: DOCBOOK-APPS: underline chars in tex using dsssl Re: DOCBOOK-APPS: dsl + jadetex font tweaking ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
- From: Jirka Kosek <jirka@kosek.cz>
- To: Jens Skripczynski <skripi@mail2003.skripczynski.de>
- Date: Wed, 12 Mar 2003 09:35:55 +0100
Jens Skripczynski wrote: > The docbook lists the <beginpage /> option, but it seems, that > the xsl stylesheet does not know about this. (I have a red > <beginpage></beginpage> in the pdf output file). Beginpage is here for legacy purposes -- e.g. you want to mark where page break was in printed version of document. But processing tools are not suppoused to create pagebreaks in places where <beginpage/> occur. You can put some PI in place where you want pagebreak: <?page-break?> and add something like <xsl:template match="processing-instruction('page-break')"> <fo:blok break-after="page"/> </xsl:template> Maybe we can reconsider adding support of common PIs for page and line breaks into standard XSL stylesheets. Generally it is not good idea to specify breaks manually, but sometimes it's reasonable solution. > P.S.: I think it would be good to add to the index section on > "http://docbook.org/tdg/en/html/index.html", > that a simple <index /> tells processor where to put the > index. I searched for this hint some time. > thx to Jirka. This is true for XSL stylesheets, but other processing tools may behave differently. TDG describes DocBook as general document type. Details of processing should be specified in documentation of particular processing tools. Jirka -- ----------------------------------------------------------------- Jirka Kosek e-mail: jirka@kosek.cz http://www.kosek.cz
- From: Markus Spath <mspath@arcor.de>
- To: docbook-apps@lists.oasis-open.org
- Date: Wed, 12 Mar 2003 10:24:43 +0100
Damian Kohlfeld wrote: > I use xerces/xalan/fop and I believe Xerces doesn't handle XIncludes at this > time. What would you recommend for handling XIncludes? > > I looked at http://xincluder.sourceforge.net, would this be the way to go? > > XIncluder does a pretty good job, it has some limitations though (does not support fragment identifiers,...), but there is an ant-task available and it should fit nicely into your setup. markus
- From: Stefan Bylund <steby@enea.se>
- To: docbook-apps@lists.oasis-open.org, damian@kohlfeld.com
- Date: Wed, 12 Mar 2003 10:45:14 +0100
Hi Damian, I first tried xincluder but I soon found out that xmllint is more fully featured. I use the following command to resolve all xincludes before invoking the XSLT processor (Saxon): xmllint --xinclude --catalogs document.xml > resolved.xml Note that xmllint uses the SGML_CATALOG_FILES environment variable to find the catalog(s). The xmllint tool is part of libxml2 which is located at http://xmlsoft.org/. It is also a very good validating XML parser; I use it the following way: xmllint --xinclude --postvalid --noout --catalogs document.xml /Stefan Damian Kohlfeld wrote: I use xerces/xalan/fop and I believe Xerces doesn't handle XIncludes at this time. What would you recommend for handling XIncludes? I looked at http://xincluder.sourceforge.net, would this be the way to go?begin:vcard n:Bylund;Stefan tel;cell:+46 709 714 325 tel;work:+46 8 507 143 25 x-mozilla-html:FALSE url:http://www.ose.com org:OSE Systems adr:;;Nytorpsvägen 5;Täby;;183 23;Sweden version:2.1 email;internet:steby@enea.se title:Software Engineer fn:Stefan Bylund end:vcard
- From: Jirka Kosek <jirka@kosek.cz>
- To: "docbook-apps@lists.oasis-open.org" <docbook-apps@lists.oasis-open.org>
- Date: Wed, 12 Mar 2003 13:31:44 +0100
-------- Original Message -------- From: Jens Skripczynski <skripi@mail2003.skripczynski.de> Subject: Re: DOCBOOK-APPS: <beginpage /> fails with fop xsl 1.60.1 To: Jirka Kosek <jirka@kosek.cz> CC: Jens Skripczynski <skripi@mail2003.skripczynski.de> Hi, as I said, I'm new to doc-book and don't know much about the structure. So i have a lot of questions, I hope you can help me with some of them. (like forward me to some web-ressources). ########### # Docbook I'm used to latex, but xsl docbook behaves quiet different. One thing is, I belief, that Formatting objects is new and has not all features included. I was anouyed, that there was not pagebreak after the sect1 sections. Well i found out, that I was looking for chapter, so I have to switch to book. For my first week if find it very had to find information about docbook. The online documentation about docbook, is just something like getting started. (exspecially for xsl). - What are your docbook sources ? - How would you list a web ressource in bibliography ? -------------------------------- <biblioentry id="gurps-athas"> <author><surname>wrathchild@hippie.dk</surname></author> <title id="gurps-athas.title"> <ulink url="http://www.secretmasters.net/wrathchild/darksun/">GURPS Athas (GURPS Dark Sun)</ulink></title> </biblioentry> <biblioentry> <title id="athas-org"> <ulink url="http://www.athas.org">The Burnt world of Athas</ulink></title> </biblioentry> -------------------------------- I'm not too satisfied with that. But it is hard (like at those two ressources) to get author, copyright, pubdate... This does not really relate to docbook itsself, where can i get information about things like that ? ########### # xsl - using entities. Can i use entities (that are defined) like , ü and they do appear in the output ? Currently i mainly use &uuml; or &nbsp; ############### # Styling output - What does <sidebar> mean? I understand the documentation that the processor can render it in two ways: ----------- sidebar ------ text test ----------- sidebar ----- or | text | text Am I right ? Would it be hard to achieve the second part with xsl stylesheets and FOP ? i have a book style that i would like to use. :) - outputing text in rows HEADING (like sect1.title) text text | .. text test continue... | .. .... I there a switch, command in docbook or does this belong to xsl stylesheets ? I think there must be a switch in the docbook source, that tells xsl how to render the next chapter. (e.g. one_row_text-with_sidebar, two_row_text,...) - Fop, pdf and <index> e.g. for <sect3 id="elf-run"> <title>Elf Run [5 CP]</title> <indexterm><primary>Advantage</primary><secondary>race</secondary></indexterm> I the html page i have in the index section sth. like A advantages, races, elf-run #page in the pdf output: A advantage, 10, 11, 11, Index is not listed in the toc, and all the title disapeard. Am i doing something wrong ? The thing i really want is (in html and pdf) <title> elf-run</title> <cost> 5 CP </cost> <prerequisite>something</something> rendered: <text-align=left><b><title/></b></textalign> <text-align=right><cost/><prerequisite/></text-align> in one line and later a table like: Advantage Cost page <title/>..........<cost>...<page> (with the dots spanning and 4 continuing rows). - html and pdf output: Table column graying like row1 row2 row3 row1******row2*****row3 (second line grayed) row1 row2 row3 row1******row2*****row3 I would love to switch this on and off, as for some table it improves reading, for others not. ----- Is this an overkill for a (bloody) beginner ? ----- Jirka Kosek: > Beginpage is here for legacy purposes -- e.g. you want to mark where > page break was in printed version of document. But processing tools are > not suppoused to create pagebreaks in places where <beginpage/> occur. > > You can put some PI in place where you want pagebreak: > > <?page-break?> > > and add something like > > <xsl:template match="processing-instruction('page-break')"> > <fo:blok break-after="page"/> > </xsl:template> *thx a lot* > Maybe we can reconsider adding support of common PIs for page and line > breaks into standard XSL stylesheets. Generally it is not good idea to > specify breaks manually, but sometimes it's reasonable solution. Maybe even an option (for pagebreak), with a number of emty lines. (in latex \\[x] ) > > P.S.: I think it would be good to add to the index section on > > "http://docbook.org/tdg/en/html/index.html", > > that a simple <index /> tells processor where to put the > > index. I searched for this hint some time. > > thx to Jirka. > This is true for XSL stylesheets, but other processing tools may behave > differently. TDG describes DocBook as general document type. Details of > processing should be specified in documentation of particular processing > tools. ok, then to the xsl docu. I think it would be good, to link to a compatability page, that lists, what processor supports which option, rather than saying, this option is not supported by all processors (Because, how am I to find out ?). Like for index, I used google with ('docbook', 'xsl', 'index', 'use|make|create|...') and because the mailinglist page has a link called 'index', nothing usefull appeared. Well this was alot, mainly because i do not know how to look it up and where to search. For <index> i was trying for 2 days. Ciao Jens Skripczynski -- E-Mail: skripczynski(at)mail2003(dot)skripczynski(dot)de If Microsoft is innovative in any area, it is in creating new forms of intimidation. -- Ralph Nader
- From: Norman Walsh <ndw@nwalsh.com>
- To: Tobias Reif <tobiasreif@pinkjuice.com>
- Date: Wed, 12 Mar 2003 08:05:41 -0500
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 / Tobias Reif <tobiasreif@pinkjuice.com> was heard to say: |> The RELEASE-NOTES.html file emphasize that this release |> included significant changes to the titlepage mechanism. | | I see; sorry for not having read it. But I'm not sure how that helps me. | | In the past you strongly encouraged users (people who customize the | styles) to use the titlepage mechanism. (actually Norm told me to) Yes. And it's almost always the case that upgrading the stylesheets requires no changes to the titlepage mechanism. But in the 1.60 release I reworked the titlepage stuff. I called it out specifically in the release notes (which I'm trying to keep accurate and up-to-date) so that you'd know what was coming. | Now I'm not sure if I can use it at all. The file is over 1000 lines | of code. To customize styles, I need to edit lines which can be | anywhere in that file. Now if I upgrade the XSLT package, how am I | supposed to deal with fundamental changes in the format of | titlepage.templates.xml? They don't happen very often, and I'm pretty sure everything you could do in the old format you can do in the new format. | Making a new copy from the new package and then manually checking what | my style customizations were would take a lot of time, and I could | miss styles. I'll try not to do it very often :-) Be seeing you, norm - -- Norman Walsh <ndw@nwalsh.com> | Mountains appear more lofty the http://www.oasis-open.org/docbook/ | nearer they are approached, but Chair, DocBook Technical Committee | great men resemble them not in | this particular.--Lady Blessington -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/> iD8DBQE+bzClOyltUcwYWjsRAkrlAKCY4cJZC0rI9r3JBv3NBrPZzFAERwCfbXNS Vjc+GpwO2s9Ndb7Bt7pK66s= =eA7r -----END PGP SIGNATURE-----
- From: Tilly Bayard-Richard <Tilly.Bayard-Richard@Jaluna.COM>
- To: docbook-apps@lists.oasis-open.org
- Date: Wed, 12 Mar 2003 14:54:19 +0100 (MET)
Bonjour, I am using docbook-xsl-1.60.1, xsltproc, and FOP 0.20.5rc2. I was happy with Jens's postprocessing fix for PDF bookmarks in: http://lists.oasis-open.org/archives/docbook-apps/200301/msg00251.html until I noticed that there was no bookmark created for the "Table of Contents". When I manually insert: <fox:outline xmlns:fox="http://xml.apache.org/fop/extensions" internal-destination="toc...mybook"> <fox:label>Table of Contents</fox:label> </fox:outline> in the fo file, I get the bookmark. Strangely enough, as I was developing the glossary collection system between books, I noticed that I did not reproduce the above problem for more complex documents with a glossary. Please do not tell me to build dummy glossaries for all my books ;) I have a collection of books, some have a glossary, other do not. It is not very satisfying to have blank page at the end of the latest, with just the title "Glossary" on it! I think there are other limitations... Even in cases where I can get the TOC bookmark all right, I never succeed in generating the LOF bookmark while having formal figures in my book. Merci d'avance pour votre aide, Tilly
- From: Steinar Bang <sb@dod.no>
- To: docbook-apps@lists.oasis-open.org
- Date: Wed, 12 Mar 2003 15:18:14 +0100
Platform: RedHat 8.0, IBM Java2 1.3.1 saxon 6.5 apache (Sun?) resolver 1.0 DocBook XML 4.1.2 (native to RedHat 8) DocBook XSL 1.60.1 (from an RPM created by myself) When I try building my documents, I get error messages about the dbnotnx.mod file not being found in the document directory. This seems to be the same problem discussed in this email thread: http://www.biglist.com/lists/xsl-list/archives/200301/threads.html#00011 However, the fix suggested by Dave Pawson in this thread doesn't work for me. Is there anything else I could try? The fix was to include the docbook.cat file with the construct <group prefer="public" xml:base="/usr/share/sgml/docbook/xml-dtd-4.1.2-1.0-14/" > <nextCatalog catalog="docbook.cat"/> </group> instead of <nextCatalog catalog="/usr/share/sgml/docbook/xml-dtd-4.1.2-1.0-14/docbook.cat"/> FWIW using saxon with XML Catalogs works for me on RedHat 7.2 and debian testing/unstable, albeit with different XML Catalog files. The current RedHat 8.0 catalog file started out as the RedHat 7.2 catalog file. I've included the error messages I get when I try to build HTML and FO from a simple document, and I've attached the catalog file I use on RedHat 7.2, the catalog file I use on RedHat 8.0, and the CatalogManager.properties file I use on RedHat. Thanx! - Steinar cd ~/cvs/projects/tps/doc/xml/simplebook/ make -k time java -cp ..:/usr/share/java/classes/saxon/saxon.jar:/usr/share/sgml/docbook/xsl-stylesheets/extensions/saxon65.jar:/usr/share/sgml/docbook/xsl-stylesheets/extensions/resolver-1.0.jar com.icl.saxon.StyleSheet -x org.apache.xml.resolver.tools.ResolvingXMLReader -y org.apache.xml.resolver.tools.ResolvingXMLReader -r org.apache.xml.resolver.tools.CatalogResolver -o simplebook.html simplebook.xml ../local-html.xsl Error on line 66 column 1 of file:/home/sba/cvs/projects/tps/doc/xml/simplebook/simplebook.xml: Error reported by XML parser: Cannot read from file:/home/sba/cvs/projects/tps/doc/xml/simplebook/dbnotnx.mod (/home/sba/cvs/projects/tps/doc/xml/simplebook/dbnotnx.mod (No such file or directory)) Transformation failed: Run-time errors were reported Command exited with non-zero status 2 12.60user 0.48system 0:19.30elapsed 67%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (2894major+14374minor)pagefaults 0swaps make: *** [simplebook.html] Error 2 time java -cp ..:/usr/share/java/classes/saxon/saxon.jar:/usr/share/sgml/docbook/xsl-stylesheets/extensions/saxon65.jar:/usr/share/sgml/docbook/xsl-stylesheets/extensions/resolver-1.0.jar com.icl.saxon.StyleSheet -x org.apache.xml.resolver.tools.ResolvingXMLReader -y org.apache.xml.resolver.tools.ResolvingXMLReader -r org.apache.xml.resolver.tools.CatalogResolver -o simplebook.fo simplebook.xml ../local-fo.xsl Error on line 66 column 1 of file:/home/sba/cvs/projects/tps/doc/xml/simplebook/simplebook.xml: Error reported by XML parser: Cannot read from file:/home/sba/cvs/projects/tps/doc/xml/simplebook/dbnotnx.mod (/home/sba/cvs/projects/tps/doc/xml/simplebook/dbnotnx.mod (No such file or directory)) Transformation failed: Run-time errors were reported Command exited with non-zero status 2 12.66user 0.41system 0:19.46elapsed 67%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (2894major+13683minor)pagefaults 0swaps make: *** [simplebook.fo] Error 2 make: Target `all' not remade because of errors. Compilation exited abnormally with code 2 at Wed Mar 12 15:03:21<?xml version="1.0"?> <!DOCTYPE catalog PUBLIC "-//OASIS/DTD Entity Resolution XML Catalog V1.0//EN" "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"> <catalog> <!-- Translate DocBook XML 4.1.2 system ids to local file names --> <rewriteSystem systemIdStartString="http://www.oasis-open.org/docbook/xml/4.1.2/" rewritePrefix="/usr/share/sgml/docbook/xml-dtd-4.1.2/"/> <!-- Translate DocBook XML 4.1.2 public ids to local file names --> <nextCatalog catalog="/usr/share/sgml/docbook/xml-dtd-4.1.2/docbook.cat"/> <!-- Translate DocBook XML 4.2 system ids to local file names --> <rewriteSystem systemIdStartString="http://www.oasis-open.org/docbook/xml/4.2/" rewritePrefix="/usr/share/sgml/docbook/xml-dtd-4.2/"/> <!-- Translate DocBook XML 4.2 public ids to local file names --> <nextCatalog catalog="/usr/share/sgml/docbook/xml-dtd-4.2/catalog.xml"/> <!-- Translate URIs referring to the most current DocBook XSL release, into paths in the local file system. Note that the value of the rewritePrefix is a symlink pointing to the currently installed version of the style sheets --> <rewriteURI uriStartString="http://docbook.sourceforge.net/release/xsl/current/" rewritePrefix="/usr/share/sgml/docbook/xsl-stylesheets/"/> <!-- Translate URIs referring to the most current DocBook to LaTeX XSL style sheets, into paths in the local file system. Currently the local files are a CVS checkout. --> <rewriteURI uriStartString="http://db2latex.sourceforge.net/xsl/current/" rewritePrefix="../../db2latex/"/> </catalog><?xml version="1.0"?> <!DOCTYPE catalog PUBLIC "-//OASIS/DTD Entity Resolution XML Catalog V1.0//EN" "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"> <catalog> <rewriteSystem systemIdStartString="http://localhost/xml/dtds/docbook4.1.2/" rewritePrefix="/usr/share/sgml/docbook/xml-dtd-4.1.2-1.0-14/"/> <!-- Translate DocBook XML 4.1.2 system ids to local file names --> <rewriteSystem systemIdStartString="http://www.oasis-open.org/docbook/xml/4.1.2/" rewritePrefix="/usr/share/sgml/docbook/xml-dtd-4.1.2-1.0-14/"/> <!-- Translate DocBook XML 4.1.2 public ids to local file names --> <group prefer="public" xml:base="/usr/share/sgml/docbook/xml-dtd-4.1.2-1.0-14/" > <nextCatalog catalog="docbook.cat"/> </group> <!-- Translate DocBook XML 4.2 system ids to local file names --> <rewriteSystem systemIdStartString="http://www.oasis-open.org/docbook/xml/4.2/" rewritePrefix="/usr/share/sgml/docbook/xml-dtd-4.2-1.0-14/"/> <!-- Translate DocBook XML 4.2 public ids to local file names --> <nextCatalog catalog="/usr/share/sgml/docbook/xml-dtd-4.2-1.0-14/catalog.xml"/> <!-- Translate URIs referring to the most current DocBook XSL release, into paths in the local file system. Note that the value of the rewritePrefix is a symlink pointing to the currently installed version of the style sheets --> <rewriteURI uriStartString="http://docbook.sourceforge.net/release/xsl/current/" rewritePrefix="/usr/share/sgml/docbook/xsl-stylesheets/"/> <!-- Translate URIs referring to the most current DocBook to LaTeX XSL style sheets, into paths in the local file system. Currently the local files are a CVS checkout. --> <rewriteURI uriStartString="http://db2latex.sourceforge.net/xsl/current/" rewritePrefix="../../db2latex/"/> </catalog>catalogs=../../../../docbook/catalog-redhat.xml verbosity=1 prefer=public static-catalog=yes allow-oasis-xml-catalog-pi=yes catalog-class-name=org.apache.xml.resolver.Resolver
- From: Brian Burridge <brian@burridge.net>
- To: DocBookApps <docbook-apps@lists.oasis-open.org>
- Date: Wed, 12 Mar 2003 11:37:29 -0500
I've been working all morning on trying to customize my headers. (I can't believe the default is to put the name of the current section). I am using double sided, so I want the Book Title to be left justified on the even pages, and the chapter name to be right justified on the odd pages. I have the justification and page sequence working, but I can't figure out how to get the chapter number and name in there, and the book title. I see that "title.markup" gives the current chapter name, but don't know how to add the chapter number, and don't know how to get the book title. I tried "book.title.markup" but that didn't work. Brian
- From: Jens Skripczynski <skripi@mail2003.skripczynski.de>
- To: Stefan Bylund <steby@enea.se>
- Date: Wed, 12 Mar 2003 16:57:17 +0100
Stefan Bylund: > Hi Damian, > > I first tried xincluder but I soon found out that xmllint is more fully > featured. I use the following command to resolve all xincludes before invoking > the XSLT processor (Saxon): > > xmllint --xinclude --catalogs document.xml > resolved.xml > > Note that xmllint uses the SGML_CATALOG_FILES environment variable to find the > catalog(s). > > The xmllint tool is part of libxml2 which is located at http://xmlsoft.org/. It > is also a very good validating XML parser; I use it the following way: > > xmllint --xinclude --postvalid --noout --catalogs document.xml Thx for this hint !!! Now Error searching became so much easier. *happy* Ciao Jens Skripczynski -- E-Mail: skripczynski(at)mail2003(dot)skripczynski(dot)de We would like to inform you that, due to the introduction of the EURO, from January 2nd 2002 the Kamasutra position usually known as 69 will now be known as 35.28
- From: Damian Kohlfeld <damian@kohlfeld.com>
- To: Stefan Bylund <steby@enea.se>, docbook-apps@lists.oasis-open.org
- Date: Wed, 12 Mar 2003 13:00:30 -0600
Thank you. I'm trying both Xincludes and xmllint with much success. -Damian ----- Original Message ----- From: "Stefan Bylund" <steby@enea.se> To: <docbook-apps@lists.oasis-open.org>; <damian@kohlfeld.com> Sent: Wednesday, March 12, 2003 3:45 AM Subject: DOCBOOK-APPS: Re: XIncludes > Hi Damian, > > I first tried xincluder but I soon found out that xmllint is more fully > featured. I use the following command to resolve all xincludes before invoking > the XSLT processor (Saxon): > > xmllint --xinclude --catalogs document.xml > resolved.xml > > Note that xmllint uses the SGML_CATALOG_FILES environment variable to find the > catalog(s). > > The xmllint tool is part of libxml2 which is located at http://xmlsoft.org/. It > is also a very good validating XML parser; I use it the following way: > > xmllint --xinclude --postvalid --noout --catalogs document.xml > > /Stefan > > > Damian Kohlfeld wrote: > I use xerces/xalan/fop and I believe Xerces doesn't handle XIncludes at this > time. What would you recommend for handling XIncludes? > > I looked at http://xincluder.sourceforge.net, would this be the way to go? > >
- From: Norman Walsh <ndw@nwalsh.com>
- To: docbook-apps@lists.oasis-open.org
- Date: Wed, 12 Mar 2003 15:16:37 -0500
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 / totschnig.michael@uqam.ca was heard to say: | I wanted to ask if Fop is really to blame for this, since by reading | Dave Pawson's book on XSL-FO on page 27 he sais that footnotes do | inherit properties from the content in which they occur. If this is | the case, is it possible to correct this problem in the distribution? Seems reasonable to me. Done in CVS. Be seeing you, norm - -- Norman Walsh <ndw@nwalsh.com> | A man's dying is more the survivors' http://nwalsh.com/ | affair than his own.--Thomas Mann -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/> iD8DBQE+b5WlOyltUcwYWjsRAjXtAKCw0AWO6dXo/iqmY3/WXSXAdq9NVgCfYxsE myXmgneORl/EoVi6uuvbQos= =+c5l -----END PGP SIGNATURE-----
- From: Norman Walsh <ndw@nwalsh.com>
- To: Steinar Bang <sb@dod.no>
- Date: Wed, 12 Mar 2003 19:44:25 -0500
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 / Steinar Bang <sb@dod.no> was heard to say: | Yesterday I discovered that when I inserted a CDROM containing a | chunked HTML document on a Win2k machine, I found some of the pages | missing. The reason was that the file names were too long. I have | use.id.as.filename, and some of my IDs were too long. | | I'm changing the troublesome IDs now, but is there some way to fix | this automatically? Either shorten the filenames and links to the | files when generating the chunked HTML, or generate warnings/errors? Do you need the ID-based filenames? Would the automatically generated names not be ok? Be seeing you, norm - -- Norman Walsh <ndw@nwalsh.com> | The wonder is, not that the field http://www.oasis-open.org/docbook/ | of stars is so vast, but that man Chair, DocBook Technical Committee | has measured it.--Anatole France -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/> iD8DBQE+b9RpOyltUcwYWjsRAvK+AJ0R3k/fPqZuo39F0ogNMROrHA8NxACgj14Q s+F6QtkO8y1h2M1ovY9HDsg= =Gv/9 -----END PGP SIGNATURE-----
- From: Norman Walsh <ndw@nwalsh.com>
- To: David Cramer <dcramer@broadjump.com>
- Date: Wed, 12 Mar 2003 19:42:51 -0500
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's been a month or so, has there been any follow-up on this? Do I need to add some more properties to the stylesheets? / David Cramer <dcramer@broadjump.com> was heard to say: | Ok, that make sense, but when I add border-top-width.conditionality="retain" or border-before-width.conditionality="retain" to the fo:table, nothing changes (the top border of the running headers are still not there in the pdf): | | <fo:table margin-left="0pt" margin-right="0pt" border-collapse="collapse" border-top-width.conditionality="retain" border-left-style="solid" border-right-style="solid" border-top-style="solid" border-bottom-style="solid" border-left-width="0.5pt" border-right-width="0.5pt" border-top-width="0.5pt" border-bottom-width="0.5pt" border-left-color="black" border-right-color="black" border-top-color="black" border-bottom-color="black" width="100%"> | | David | |> -----Original Message----- |> From: David Tolpin [mailto:dvd@renderx.com] |> Sent: Thursday, February 06, 2003 2:17 AM |> To: docbook-apps@lists.oasis-open.org |> Subject: Re: DOCBOOK-APPS: Top border lacking on repeated |> table headers |> with xep |> |> |> > |> > XEP (2.x at least) for some reason doesn't put a border |> declared in fo:table |> > on running headers. So even tho you have frame="all" on |> your docbook table |> > and rowseps="1" elsewhere, you still end up with this in |> your output: |> |> David, |> |> I'll post your messages sent to xep-support (they have been |> bounced since sent not from a subscribed |> address), but the problem is not with XEP but with the |> stylesheets, and XEP's behaviour is |> compliant. |> |> border-*.conditionality is discard by default. That's why |> table borders are not drawn |> at the top and bottom of the intermediate chunks. If one |> want's the top border to be |> drawn always, border-before.conditionality="retain" must be specified. |> |> David |> |> |> Be seeing you, norm - -- Norman Walsh <ndw@nwalsh.com> | Endurance is frequently a form of http://www.oasis-open.org/docbook/ | indecision.--Elizabeth Bibesco Chair, DocBook Technical Committee | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/> iD8DBQE+b9QLOyltUcwYWjsRAha5AJ94ILLPh2iHkrsW5r5u2AtEtTwEcACfXcau HFjKvPrI232VGSh1d3NdiMI= =MLjS -----END PGP SIGNATURE-----
- From: David Cramer <dcramer@motive.com>
- To: docbook-apps@lists.oasis-open.org
- Date: Wed, 12 Mar 2003 22:27:19 -0600
I didn't see any effect when I changed the conditionality to retain on fo:table, so I added a top and bottom border to the row as a short-term fix (see below). There's a barely visible problem with this workaround though: the side borders of the table extend a tiny bit above the top border on the second and following pages. I haven't ever gotten back to it to test the conditionality thing further and see if it was me or xep doing something wrong. Perhaps I misunderstood what David T. was suggesting? David =================================================================== RCS file: /export/CVS/src/docmodules/doctools/1.0/DocShared/xsl/docbook/motive-pdf /table.xsl,v retrieving revision 1.2 retrieving revision 1.1 diff -w -r1.2 -r1.1 12c12 < <!-- <xsl:include href="../common/table.xsl"/> --> --- > <xsl:include href="../common/table.xsl"/> 15c15 < $Id: table.xsl,v 1.2 2003/02/06 07:38:59 dcramer Exp $ --- > $Id: table.xsl,v 1.1 2003/02/06 07:37:03 dcramer Exp $ 27c27 < $Id: table.xsl,v 1.2 2003/02/06 07:38:59 dcramer Exp $ --- > $Id: table.xsl,v 1.1 2003/02/06 07:37:03 dcramer Exp $ 254,261d253 < <xsl:if test="@rowsep > 0 and parent::thead"> < <xsl:call-template name="border"> < <xsl:with-param name="side" select="'bottom'"/> < </xsl:call-template> < <xsl:call-template name="border"> < <xsl:with-param name="side" select="'top'"/> < </xsl:call-template> < </xsl:if> -----Original Message----- From: Norman Walsh [mailto:ndw@nwalsh.com] Sent: Wednesday, March 12, 2003 6:43 PM To: David Cramer Cc: David Tolpin; docbook-apps@lists.oasis-open.org Subject: DOCBOOK-APPS: Re: Top border lacking on repeated table headers with xep -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's been a month or so, has there been any follow-up on this? Do I need to add some more properties to the stylesheets? / David Cramer <dcramer@broadjump.com> was heard to say: | Ok, that make sense, but when I add border-top-width.conditionality="retain" or border-before-width.conditionality="retain" to the fo:table, nothing changes (the top border of the running headers are still not there in the pdf): | | <fo:table margin-left="0pt" margin-right="0pt" border-collapse="collapse" border-top-width.conditionality="retain" border-left-style="solid" border-right-style="solid" border-top-style="solid" border-bottom-style="solid" border-left-width="0.5pt" border-right-width="0.5pt" border-top-width="0.5pt" border-bottom-width="0.5pt" border-left-color="black" border-right-color="black" border-top-color="black" border-bottom-color="black" width="100%"> | | David | |> -----Original Message----- |> From: David Tolpin [mailto:dvd@renderx.com] |> Sent: Thursday, February 06, 2003 2:17 AM |> To: docbook-apps@lists.oasis-open.org |> Subject: Re: DOCBOOK-APPS: Top border lacking on repeated |> table headers |> with xep |> |> |> > |> > XEP (2.x at least) for some reason doesn't put a border |> declared in fo:table |> > on running headers. So even tho you have frame="all" on |> your docbook table |> > and rowseps="1" elsewhere, you still end up with this in |> your output: |> |> David, |> |> I'll post your messages sent to xep-support (they have been |> bounced since sent not from a subscribed |> address), but the problem is not with XEP but with the |> stylesheets, and XEP's behaviour is |> compliant. |> |> border-*.conditionality is discard by default. That's why |> table borders are not drawn |> at the top and bottom of the intermediate chunks. If one |> want's the top border to be |> drawn always, border-before.conditionality="retain" must be specified. |> |> David |>
- From: Steinar Bang <sb@dod.no>
- To: docbook-apps@lists.oasis-open.org
- Date: Thu, 13 Mar 2003 08:11:54 +0100
>>>>> Norman Walsh <ndw@nwalsh.com>: > Do you need the ID-based filenames? Need, no. Prefer, yes. > Would the automatically generated names not be ok? Are these names persistent, if sections change order in the XML source?
- From: Shawn <javajunkie@koyuru.com>
- To: Joachim Ziegler <ziegler@mpi-sb.mpg.de>
- Date: Thu, 13 Mar 2003 17:34:32 +0900
Hi, I had the same problem and ended up adding image support for FOP. The Jimi image library, which is by default used for processing images in PNG and other formats, was removed from the distribution for licensing reasons. So...: Either a) obtain Jimi from http://java.sun.com/products/jimi/ and Extract the file "JimiProClasses.zip" from the archive you've downloaded, rename it to "jimi-1.0.jar" and move it to FOP's lib directory. OR b) obtain JAI from http://java.sun.com/products/java-media/jai/downloads/download.html and follow the installation instructions there. (much faster, but not available for all platforms) On Wed, 2003-03-12 at 00:28, Joachim Ziegler wrote: > Hello, > > Bob Stayton writes in "Using the XSLT Sheets" that > FOP can handle PDF as a vector format: > > Table 16.6. FO processor supported graphics formats > FO Processor Bitmap formats Vector formats > FOP PNG JPEG SVG PDF > > > But I get the following error from FOP 0.20.5rc2 > > [ERROR] Error while creating area : No ImageReader for this type of > image (file:/KM/usr/ziegler/LEDA/Tutorial/pdf/Pictures/ArrayOfChar.pdf) > > > My DocBook source is the following: > > <mediaobject> > <imageobject role="html"> > <imagedata align="center" format="PNG" > fileref="Pictures/ArrayOfChar.png"/> > </imageobject> > > <imageobject role="fo"> > <imagedata align="center" format="PDF" > fileref="Pictures/ArrayOfChar.pdf"/> > </imageobject> > </mediaobject> > > > Can someone please help me? I've already browsed through the mailinglist > archive and the bug reports of FOP, but I haven't found anything. > > > I'm using java version "1.3.1", DocBook Stylesheets 1.60.1 > > > Greetings, > Joachim > > -- Shawn <javajunkie@koyuru.com>
- From: Adam DiCarlo <adam@onshored.com>
- To: Mark Earlam <mearlam@orctel.co.uk>
- Date: Thu, 13 Mar 2003 02:49:38 -0600
Mark Earlam <mearlam@orctel.co.uk> writes: > How can i modify the style sheet to do this? Find a convenient display-group construction rule which can be easily overridden, and add the attribute pair: "keep: 'page". This will keep the whole thing on one page. Obviously this can't be the default behavior for the stylesheets.... -- ...Adam Di Carlo...<adam@onshored.com>.......<URL:http://www.onshored.com/>
- From: Adam DiCarlo <adam@onshored.com>
- To: ddb@R3401.msl.titech.ac.jp
- Date: Thu, 13 Mar 2003 02:54:13 -0600
Doug du Boulay <ddb@R3401.msl.titech.ac.jp> writes: > Actually I discovered that the stock dsssl1.77 stylesheets respond perfectly > well to: > > <imagedata fileref="images/image.jpg" format="JPG" width="80%" scale="80"> > > The width attribute is only used by HTML and the scale attribute > (which is a percent without the % sign) is only used in the tex > output. Herm, that seems really buggy on the part of the stylesheets, but I'd have to look at the table processing expectations again. I believe width is for fixed width and scale is for scaling. Not sure how it would be meaningful to set them both. > All other image scaling attribute controls permitted by the DTD seem to be > ignored by the dsssl stylesheets (obvious really, !). Sarcasm I hope. Doesn't seem very right to me. > What I dont know is what the widths and scales are percentages of. The > original figures widths? the page width? the text-column width? > I have no idea what magic goes on within web-browsers or tex to impose this > spec. Well, read the HTML spec, but it's width of their containing block element. Generally this is the width of the visible page but it could also be smaller (e.g., inside blockquote or whatever). -- ...Adam Di Carlo...<adam@onshored.com>.......<URL:http://www.onshored.com/>
- From: Adam DiCarlo <adam@onshored.com>
- To: ddb@R3401.msl.titech.ac.jp
- Date: Thu, 13 Mar 2003 02:58:41 -0600
Doug du Boulay <ddb@R3401.msl.titech.ac.jp> writes: > Seems to be no mention of underline in the dsssl spec. See the score flow object. I think in dsssl the accel element uses this. -- ...Adam Di Carlo...<adam@onshored.com>.......<URL:http://www.onshored.com/>
- From: Adam DiCarlo <adam@onshored.com>
- To: kdunn@hsc.edu
- Date: Thu, 13 Mar 2003 03:11:05 -0600
Kevin Dunn <kdunn@hsc.edu> writes: > I have an almost insignificant problem that I have had little > success in understanding--the degree symbol in my generated pdf has > extra whitespace at the end. I have looked in the .tex output from > openjade and jadetex and there is no extra whitespace there. I can > only suspect that tex itself thinks that the symbol is wider than it > acutally is. Woah, no idea. Submit as a bug against jadetex, though it might be a TeX issue... -- ...Adam Di Carlo...<adam@onshored.com>.......<URL:http://www.onshored.com/>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Powered by ezmlm-idx