DOCBOOK-APPS: table visible in html, not in pdf
I'm using docbook v4.12 and the v1.48 docbook xsl stylesheets. I'm processing the fo output through Fop-0.20.3rc and I don't seem to need the extra step of fo-patch-for-fop.xsl. Most everything seems to work. However the table I made shows up in html but not in the pdf. The table does show up in the "List of Tables" however at the end of the line of "" there is no page number. You can see the the html and pdf here (pdf ~600k): http://concord.org/ccprobeware/ccprobe/ccprobe-documentation.html The table in question displays just after here: http://concord.org/ccprobeware/ccprobe/ccprobe-ref.html#NB2B Here's the actual table, seems pretty simple: --- Available Packages of CCProbe Operating System archive type link PalmOS exe for Windows http://concord.org/ccprobeware/ccprobe/download/ccprobe-palmos/CCProbe.exe";>CCProbe.exe PalmOS tarred and gzipped for Unix http://concord.org/ccprobeware/ccprobe/download/ccprobe-palmos/CCProbe.tgz";>CCProbe.tgz PalmOS binhex self-extracting archive for MacOS http://concord.org/ccprobeware/ccprobe/download/ccprobe-palmos/CCProbe.sea.hqx";>CCProbe.sea.hqx PocketPC (for MIPS and StrongArm) exe for Windows http://concord.org/ccprobeware/ccprobe/download/ccprobe-pocketpc/CCProbe.exe";>CCProbe.exe MacOS Classic binhex self-extracting archive for MacOS http://concord.org/ccprobeware/ccprobe/download/ccprobe-macos-classic/CCProbe.sea.hqx";>CCProbe.sea.hqx MacOS X binhex self-extracting archive for MacOS http://concord.org/ccprobeware/ccprobe/download/ccprobe-macosx/CCProbe.sea.hqx";>CCProbe.sea.hqx Windows exe for Windows http://concord.org/ccprobeware/ccprobe/download/ccprobe-windows/CCProbe.exe";>CCProbe.exe Linux/Unix tarred and gzipped for Unix http://concord.org/ccprobeware/ccprobe/download/ccprobe-unix/CCProbe.tgz";>CCProbe.tgz -- -- Stephen Bannasch Director of Technology, Concord Consortium http://www.concord.org mailto:[EMAIL PROTECTED]
DOCBOOK-APPS: Re: DOCBOOK: I want to have content of element inevery chunk
On Fri, Feb 15, 2002 at 09:17:48PM +0100, [EMAIL PROTECTED] wrote: > Hello, > > I use DocBook + Norman Walsh's XSL stylesheets v1.48 to produce e- > learning HTML courses. Currently I use stylesheet CHUNK.XSL, > because I need small HTML pages with header and footer. My > problem is: How can I put into every chunk (into footer) date, > which I have already defined in of document? > Header/footer of chunks are realized by table, so I put here new > row with code: > > > > But its only put date into first chunk - titlepage. > > Date is defined in style TITLEPAGE.XSL: > > > > > > > > > I think problem is that there is text 'mode="titlepage.mode"'. > > So I'll probably need to create new template which provide > generating of date in every chunk. > I tried to create it directly in CHUNK.XSL, but my experiences > with programming XSL are insufficient, so it does not work. > > If somebody know how put into footer of chunks content of element > defined in (or content of other elements), > please help me. You can do this using a stylesheet customization file. See this DocBook FAQ to learn how to customize DocBook XSL: http://www.dpawson.co.uk/docbook/styling/custom.html#d61e77 For the specifics on customizing the footer, see: http://www.dpawson.co.uk/docbook/styling/html.html#d64e60 If you follow that FAQ, you'll create a template named 'user.footer.content', which would look something like this: You can add other HTML tags if you like. Bob Stayton 400 Encinal Street Publications Architect Santa Cruz, CA 95060 Technical Publications voice: (831) 427-7796 Caldera International, Inc. fax: (831) 429-1887 email: [EMAIL PROTECTED]
DOCBOOK-APPS: Re: DOCBOOK: Quick newbie question
[Follow ups should go to docbook-apps] Ben, > Right now I am making articles, and each 1st level section in the > article is put onto a different html page. > > How do I make it so that I can break out the 2nd (or more) level > sections out into different pages too? Funny! I just had to use this feature earlier this week...small world :) The short answer: http://lists.oasis-open.org/archives/docbook-apps/200107/msg00175.html The "I want an answer now!" anser: There's this item in the modular stylesheets called chunk-element-list that sets the level at which HTML documents are split up (or "chunked"). Copy that section from the modular stylesheet and put it in ldp.dsl then add or remove the items to/from that list and, voila!, the chunking works as you expect it. Meg -- Megan Golding ([EMAIL PROTECTED]) SecureWorks, Inc. Women who seek to be equal with men lack ambition. -- Timothy Leary
DOCBOOK-APPS: I want to have content of element in every chunk
Hello, I use DocBook + Norman Walsh's XSL stylesheets v1.48 to produce e- learning HTML courses. Currently I use stylesheet CHUNK.XSL, because I need small HTML pages with header and footer. My problem is: How can I put into every chunk (into footer) date, which I have already defined in of document? Header/footer of chunks are realized by table, so I put here new row with code: But its only put date into first chunk - titlepage. Date is defined in style TITLEPAGE.XSL: I think problem is that there is text 'mode="titlepage.mode"'. So I'll probably need to create new template which provide generating of date in every chunk. I tried to create it directly in CHUNK.XSL, but my experiences with programming XSL are insufficient, so it does not work. If somebody know how put into footer of chunks content of element defined in (or content of other elements), please help me. Sorry for my english, Thanks. = www.centrum.cz doporučuje = Nový vyhledávač pro český internet www.WebFast.cz - prostě najde ...
Re: DOCBOOK-APPS: No callout numbers in the code with programlistingco
Bob Stayton wrote: > On Thu, Feb 14, 2002 at 04:21:02PM -0600, Patrick Hartling wrote: > >>Patrick Hartling wrote: >> >>>Bob Stayton wrote: >>> >>> >>[snip] >> >> Can you generate your .fo file with Xalan and see if the callouts are getting in there? If so, then it is a FOP problem on the back end. >>> >>>I tried Xalan 2.2, and I saw nothing in the .fo file that showed the >>>callouts with the code. I am trying to get 2.3.D1 to work, but I am >>>having some problems with finding DocBook files such as dbnotnx.mod and >>>many .ent files. If I copy the files it cannot find into my working >>>directory, it catches an array out of bounds exception: >>> >>>(Location of error unknown)XSLT Error >>>(javax.xml.transform.TransformerException): >>>java.lang.ArrayIndexOutOfBoundsException: 6 >= 1 >>> >>>I realize that that is probably not very helpful output, but it is all I >>>have to work with so far. Are there command line options I need besides >>>-IN, -XSL, and -OUT? I've tried running org.apache.xalan.xslt.Process >>>with JDK 1.3.1 and 1.4.0, and both give me the same (frustrating) results. >>> >>I apologize for responding to my own message, but I misspoke in the above >>paragraph. If I use JDK 1.4.0 and the latest Xalan snapshot (20020214), >>I do not get any of the errors about missing files or array access >>exceptions. (I had a path set incorrectly when I was testing things.) >>However, even with the latest snapshot, the callout numbers still do not >>appear in the .fo file. >> > > Check a couple more things before you give up. > To use any extension functions the parameter > 'use.extensions' needs to be non-zero (the default is zero). > To use the callouts, the 'callouts.extension' parameter > needs to be non-zero (that's 1 by default). > And the parameter 'callout.graphics.path' needs to > be set to the directory containing the callout image files. > > Then you need to make sure the correct extensions jar file > is in your CLASSPATH when you run Xalan. You need > docbook-xsl-1.48/extensions/xalan2.jar in your case. > > Those steps should at least get the callouts code into > the fo file. Whether FOP will handle it properly > is another question Okay, all of this did the trick for the .fo file. Neither FOP nor XEP are handling the span elements properly, however. Is there something else I am missing? HTML generation using Xalan works like a charm, though, and I am happy with that. Thanks for the help. What is a good value for callout.graphics.path? Right now, I just have a subdirectory named images that contains PNGs. -Patrick -- Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED]| 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/
RE: DOCBOOK-APPS: Re: condition attribute + XSL + doctype declara tion
If you're using saxon and don't mind using extensions, he's got saxon:doctype and dtd:entity elements that could help: http://saxon.sourceforge.net/saxon6.5.1/extensions.html#saxon:doctype David > -Original Message- > From: Jirka Kosek [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 15, 2002 4:12 AM > To: Bradford, Denis > Cc: [EMAIL PROTECTED] > Subject: Re: DOCBOOK-APPS: Re: condition attribute + XSL + > doctype declara tion > > > "Bradford, Denis" wrote: > > > That takes care of the DTD declaration, but I'm losing > everything else in > > the subset, too! Here's before and after running profile.xsl: > > > > source.xml > > -- > > > > > "docbookx.dtd" [ > > > > > > > > > > ]> > > > > ... > > > > profiled.xml > > > > > > > PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" "docbookx.dtd"> > > > > ... > > This is not problem for text entities as they are correctly substitued > during profiling transformation. But binary entity (NDATA) is problem, > as XSLT doesn't have access to such declaration. Probably easiest > workaround will be using fileref instead entityref for images. > > Jirka > > -- > - > Jirka Kosek > e-mail: [EMAIL PROTECTED] > http://www.kosek.cz >
DOCBOOK-APPS: Re: extreme newbie - dsssl customization ...
[ Follow-ups to docbook-apps, please ]
/ Douglas du Boulay <[EMAIL PROTECTED]> was heard to say:
| Sorry, me again. I'm getting closer to a final rendering now -
| thanks Norm, thanks Bob.
|
| Now I need to customize the dsssl behaviour for and because,
| well basically, I abused them.
|
| I found "The Modular DocBook Stylesheets" manual by Norm
| But the relevent chapter(3) concerning the actual customization doesn't
| seem go into "how to override the behaviour of existing stylesheet elements".
|
| I also found a dsssl customization FAQ somewhere but it seemed to deal only
| with flipping the dsssl option switches from #t to #f for different
| rendering results rather than actually hacking the dsssl.
|
| Not sure where the guide to dsssl itself is, which is probably what I should
| be reading.
|
| anyway, basically what I want is for
| not to to get treated as a paragraph with breaks above and
| below, and, for any contained s not to get wrapped in [arg] square
| brackets but to be rendered in a bold font, and if their so happens to be
| an then render it as bold and red font.
| Nothing too fancy.
So you want something like this in your customization layer:
(element cmdsynopsis
(process-children))
(element (cmdsynopsis arg)
(make element gi: "B"
(if (equal? (attribute-string (normalize "role")) "default")
(make element gi: "FONT"
attributes: '(("COLOR" "RED"))
(process-children))
(process-children
| Also I used a number of standard isogreek etc. entities which get mapped to
| some obscure #xxx; HTML entities and I wonder where that mapping table
| exists and is accessed by the dsssl? (So I can methodically search and
| replace with dinky greek symbol icons)
Those entities have been expanded by the time DSSSL sees the file. You can
search for individual characters but it makes Jade *really slow*.
Be seeing you,
norm
--
Norman Walsh <[EMAIL PROTECTED]> | You look wise. Pray correct that
http://www.oasis-open.org/docbook/ | error.--Charles Lamb
Chair, DocBook Technical Committee |
Re: DOCBOOK-APPS: Re: condition attribute + XSL + doctype declara tion
"Bradford, Denis" wrote: > That takes care of the DTD declaration, but I'm losing everything else in > the subset, too! Here's before and after running profile.xsl: > > source.xml > -- > > "docbookx.dtd" [ > > > > > ]> > > ... > > profiled.xml > > >PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" "docbookx.dtd"> > > ... This is not problem for text entities as they are correctly substitued during profiling transformation. But binary entity (NDATA) is problem, as XSLT doesn't have access to such declaration. Probably easiest workaround will be using fileref instead entityref for images. Jirka -- - Jirka Kosek e-mail: [EMAIL PROTECTED] http://www.kosek.cz
Re: DOCBOOK-APPS: No callout numbers in the code with programlistingco
Patrick Hartling wrote: > I apologize for responding to my own message, but I misspoke in the above > paragraph. If I use JDK 1.4.0 and the latest Xalan snapshot (20020214), > I do not get any of the errors about missing files or array access > exceptions. (I had a path set incorrectly when I was testing things.) > However, even with the latest snapshot, the callout numbers still do not > appear in the .fo file. Did you specify use.extensions=1 parameter to Xalan when invoking transformation? You must explicitly turn on extensions use by this way. -- - Jirka Kosek e-mail: [EMAIL PROTECTED] http://www.kosek.cz
Re: DOCBOOK-APPS: No callout numbers in the code with programlistingco
On Thu, Feb 14, 2002 at 04:21:02PM -0600, Patrick Hartling wrote: > Patrick Hartling wrote: > > Bob Stayton wrote: > > > > [snip] > > > > >> Can you generate your .fo file with Xalan and see if > >> the callouts are getting in there? If so, then it > >> is a FOP problem on the back end. > > > > > > I tried Xalan 2.2, and I saw nothing in the .fo file that showed the > > callouts with the code. I am trying to get 2.3.D1 to work, but I am > > having some problems with finding DocBook files such as dbnotnx.mod and > > many .ent files. If I copy the files it cannot find into my working > > directory, it catches an array out of bounds exception: > > > > (Location of error unknown)XSLT Error > > (javax.xml.transform.TransformerException): > > java.lang.ArrayIndexOutOfBoundsException: 6 >= 1 > > > > I realize that that is probably not very helpful output, but it is all I > > have to work with so far. Are there command line options I need besides > > -IN, -XSL, and -OUT? I've tried running org.apache.xalan.xslt.Process > > with JDK 1.3.1 and 1.4.0, and both give me the same (frustrating) results. > > I apologize for responding to my own message, but I misspoke in the above > paragraph. If I use JDK 1.4.0 and the latest Xalan snapshot (20020214), > I do not get any of the errors about missing files or array access > exceptions. (I had a path set incorrectly when I was testing things.) > However, even with the latest snapshot, the callout numbers still do not > appear in the .fo file. Check a couple more things before you give up. To use any extension functions the parameter 'use.extensions' needs to be non-zero (the default is zero). To use the callouts, the 'callouts.extension' parameter needs to be non-zero (that's 1 by default). And the parameter 'callout.graphics.path' needs to be set to the directory containing the callout image files. Then you need to make sure the correct extensions jar file is in your CLASSPATH when you run Xalan. You need docbook-xsl-1.48/extensions/xalan2.jar in your case. Those steps should at least get the callouts code into the fo file. Whether FOP will handle it properly is another question. -- Bob Stayton 400 Encinal Street Publications Architect Santa Cruz, CA 95060 Technical Publications voice: (831) 427-7796 Caldera International, Inc. fax: (831) 429-1887 email: [EMAIL PROTECTED]
Re: DOCBOOK-APPS: Mozilla and DocBook processing
camille wrote: > Hi all, > > Latest Mozillas are able to succesfully load, process and display XML > little samples as well as big ones > (http://www.w3.org/2001/05/xslt-example/REC-xml-20001006.xml). > > Though when trying to process any minimal DocBook XML sample, Mozilla > freezes. > > Has anyone else eperimented this? Is this known and why? > > Camille. > > > Yeah, I have the same experiences (sp?) I have no idea why Mozilla freezes. Rune Enggaard
DOCBOOK-APPS: Mozilla and DocBook processing
Hi all, Latest Mozillas are able to succesfully load, process and display XML little samples as well as big ones (http://www.w3.org/2001/05/xslt-example/REC-xml-20001006.xml). Though when trying to process any minimal DocBook XML sample, Mozilla freezes. Has anyone else eperimented this? Is this known and why? Camille.
Re: DOCBOOK-APPS: Re: condition attribute + XSL + doctype declara tion
Bob Stayton wrote: > > The XSLT spec doesn't support it [internal subsets], so unless > someone has a creative solution, it looks like an extension would be > required to pass through an internal subset. Saxon has an extension element () made for exactly this. I haven't tried it, but given the overall quality of Saxon, I would be surprised if it doesn't work like a charm :-) Best regards Rune Enggaard
DOCBOOK-APPS: Re: "XXXX is not a function name" errors - again
>From: Nick Hunt <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: DOCBOOK-APPS: " is not a function name" errors - again >Date: Wed, 13 Feb 2002 22:38:57 + > >Hi All, > >I hesitate to bring this issue up again on the list, but... I recently ran into this, too, and was surprised at the difficulty of mining the answer out of the list archives. Hopefully, this will give you enough information (your problem is with the character entity definitions, actually): http://lists.oasis-open.org/archives/docbook-apps/200201/msg00287.html BTW, another thing to keep in mind is that the ORDER in which you specify catalog files (i.e. in SGML_CATALOG_FILES) DOES MATTER!! I have them listed in this order: * docbook.cat (from the XML docbook DTD) * catalog, from the DSSSL distribution * catalog, from the OpenJade distribution, in the dsssl dir * my own catalog that maps the PUBLIC and SYSTEM identifiers for the XML DocBook DTD to the location where I installed it Good luck! Matt Gruenke _ Chat with friends online, try MSN Messenger: http://messenger.msn.com
