DOCBOOK: XSLT stylesheet documentation
Hi, we are currently running the experiment of authoring a scientific article with docbook. Target is a pdf document. While everything worked almost smoothly from the very beginning, we are now wondering how to customize a few things. Having to write a customization wrapper stylesheet is clear from your documentation of docbook.sf.net, but is there any documentation on the switches that can be used for customization? Say, to switch the line separation to 1.5 lines in the output document? Cheers, Chris -- Dr. Christoph Steinbeck (http://www.ice.mpg.de/departments/ChemInf) MPI of Chemical Ecology, Winzerlaer Str. 10, Beutenberg Campus, 07745 Jena, Germany Tel: +49(0)3641 571263 - Fax: +49(0)3641 571202 What is man but that lofty spirit - that sense of enterprise. ... Kirk, I, Mudd, stardate 4513.3..
Re: DOCBOOK: XSLT stylesheet documentation
Christoph Steinbeck wrote: Having to write a customization wrapper stylesheet is clear from your documentation of docbook.sf.net, but is there any documentation on the switches that can be used for customization? Say, to switch the line separation to 1.5 lines in the output document? http://docbook.sourceforge.net/projects/xsl/doc/reference.html -- - Jirka Kosek e-mail: [EMAIL PROTECTED] http://www.kosek.cz
DOCBOOK: Re: Environment Variables in File/Directory Names
Norman Walsh [EMAIL PROTECTED] writes: Oh, I probably use envar for both. That distinction isn't often important. Really? If it was, I'd just use a role attribute. Or maybe literal role=envar. Or something. For environment variables there is envar or literal role=envar (if you're sure your stylesheets will support the role attribute); for values use literal. Gregory Leblanc [EMAIL PROTECTED] writes: This leads me to another question: What markup is appropriate for distinguishing between an environment variable and its value? (I'm simply talking about the difference between TOMCAT_HOME and $TOMCAT_HOME). I normally use varname... Really? And when your publischer decides, all environment variables should be prefixed with $ or printed with italics you've lost; better distinguish now: For envarDISPLAY/envar use literallocalhost:0.0/literal. varname is for such things like: varnamei/variable will increment from literal0/literal to literal9/literal. And finally we have: Check files in filename/usr/lib/pythonreplacableVERSION/replacable/filename -- [EMAIL PROTECTED] (work) / [EMAIL PROTECTED] (home): | http://www.suse.de/~ke/ | ,__o Free Translation Project:|_-\_, http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
DOCBOOK: Re: listitem
/ Matt G. [EMAIL PROTECTED] was heard to say: | I think I've just run into exactly the problem: I have a | variablelist, but I want to be able to nest more structure inside | the listitem, for each entry! Here's an sample of the information | I'd like to be able to provide about each variable: | * descriptive name | * type | * units [...] Try nested variablelists. | It seems like fieldsynopsis gets closer to what I want, but it seems | awkward to use as a child of a variablelist, since the variable name | would need to be specified twice. Furthermore, fieldsynopsis | doesn't allow me to describe many of the above aspects. What you're describing doesn't appear to bear any relation to a field in a programming language object, which is what fieldsynopsis was designed to document. | I believe listitem needs to allow structural hierarchy underneath | it. I don't understand why it was decided not to allow section as a | child, for example, but I also want a finer-grained structural element | (described below). Because sections provide hierarchical document structure, not random titled chunks. | Finally, is there any markup (I'm thinking along the lines of a block | element) that will allow me to specify a named property? For example, | I'm imagining something along the lines of: | | par | blah blah blah | /par | namedproperty | propnameVariable Type/propname | propvalunsigned int/propval | /namedproperty | par | foo bar baz | /par DocBook doesn't really have anything quite like that. It's almost a segmented list, but the seglist markup would be overkill for single pairs, I think. I suppose I'd resort to something like this, in a pinch: para role=namedproperty phrase role=nameVariable Type/phrase: phrase role=valueunsigned int/phrase/para | preceded and followed by at least one newline. I think a formalpara | might almost do the trick, if it had an option to treat title as a | heading, instead of the first sentence. You could tweak the stylesheets to do that, but I think it would be a bit of tag abuse. Be seeing you, norm -- Norman Walsh [EMAIL PROTECTED] | People say law but they mean http://www.oasis-open.org/docbook/ | wealth.--Emerson Chair, DocBook Technical Committee |
DOCBOOK: Re: listitem
/ Matt G. [EMAIL PROTECTED] was heard to say: [...] | You might try using nested variablelists. | Inside each of your main listitems, use a variable | list for this structured information. | | Well, I have a couple of problems with this approach. First of all, | it gets even further from the proper semantics to describe what I'm | actually trying to do (though I could deal with that, though hopefully | it'd only be a stop-gap measure). What are the semantics of your data? | More importantly (in the | short-term) it doesn't even appear to be nested, at all, in the DSSSL | print style-sheets (version 1.74b - the latest). Using what backend? | First of all, I feel one needs to be able to nest structural elements | in listitem. I'd certainly like to hear other points of view, on | the matter, but I just think it's imperative to be able to partition a | listitem into a finer-grained structure. There's a great long list of structural elements than you can put inside a list item. Section isn't one of them because it would make a complete mockery of the document hierarchy. | Secondly, I'm surprised there's no sort of an element with a title on | the same line (see my namedproperty block element example, in my | previous message). Title on the same line is a presentational, not a semantic or structural issue. | I mean, I can't believe you wouldn't want to be | able to generate something like the following: | | name: Foobius Baricus I use variablelists for this and a stylesheet that presents them the way I want. I recently added some PI support to the XSL HTML stylesheets to do this, I'll probably put those in the FO stylesheets eventually as well. I suppose you could use a table as well, if you wanted to. | sort of output, and there you go! HOWEVER, if DocBook is ever to | scale to meet the basic needs of a substantial portion of the various | technical and scientific documentation sub-domains, it must provide DocBook is an XML/SGML vocabulary particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications). The target domain of DocBook is computer software and hardware documentation. It happens to be suitable for a very wide range of other sorts of documentation, but the technical committee has historically been reluctant to add new markup specifically for features outside the scope of its present domain (DocBook is quite large enough :-). | vastly preferable to the outright ABUSE of existing problem-domain | oriented semantics, on the basis of their structural and | presentational qualities (which is how I regard the use of | variablelist to provide structure within a listitem element). If your data is nested lists, then nested lists is a perfectly reasonable way to mark them up. If you think your data is something other than nested lists, you haven't made it clear what you think it is. | In fact, my opinion is that there should be a layer *between* | problem-domain specific semantics and XSL-FO, which would be comprised | exclusively of constructs relating to document structure. Then, an Given my experience with the way authors write, it's generally impractical to separate document structure entirely from lower-level semantics. Yes, authors can be *trained* to write this way, but it's not the natural way that we're all taught to write from about the second grade. | pursue. If they are fairly unambitious, they can seek to augment the | structural vocabulary with some of their own extensions. If they want | to promote or enforce more rigid semantics that deal exclusively with | their problem-domain, and/or if they want close control over the | structure and content of their output documents, they can add a layer | on top of the document structure semantics (using XSLT, to do the | translation into XML DocBook, for example). Furthermore, there would | be a fairly smooth transition path from the former to the latter. Uh huh. Been there, done that. Do it often, in fact. Although I think I tend to do it from the other end so to speak. Usually, I have some very specific set of data that doesn't fit nicely into my documentation markup, but I want to use it in my documentation. So I write an XSLT stylesheet to convert it into the documentation markup I want. Then with makefiles, I can edit the data and rebuild the documentation entirely painlessly. | As it happens, I'm in the process of doing the former, however I'm | generating external parsed XML DocBook entities. So, it's a little | like the latter, in that it's partially layered on top of DocBook. | I'd hoped to take advantage of DocBook stylesheets to do most of the | formatting work, for me. I also wanted to be able to use the core | DocBook semantics in portions of the documents that are written by | hand (these parts contain the actual references to the external | entities, giving the author the ability to change their order and use, |
DOCBOOK: Re: Markup for Ant/Makefile Targets
/ Holger Rauch [EMAIL PROTECTED] was heard to say: | What tag should be used for marking up Ant (a Java-based build tool | similar to make) or Makefile targets? (Simply using literal seems a bit | too general to me.) literal role=target? Be seeing you, norm -- Norman Walsh [EMAIL PROTECTED] | There is no glory so bright but http://www.oasis-open.org/docbook/ | the veil of business can hide it Chair, DocBook Technical Committee | effectually. With most men life is | postponed to some trivial business | and so therefore is heaven. Men | think foolishly they may abuse and | misspend life as they please and | when they get to heaven turn over | a new leaf.--Thoreau
Re: DOCBOOK: XSLT stylesheet documentation
Jirka Kosek wrote: Christoph Steinbeck wrote: Having to write a customization wrapper stylesheet is clear from your documentation of docbook.sf.net, but is there any documentation on the switches that can be used for customization? Say, to switch the line separation to 1.5 lines in the output document? http://docbook.sourceforge.net/projects/xsl/doc/reference.html That helped a lot, thanks :-) I could, however, not find the parameter for setting the line separation in normal text. Can anyone instruct me on that topic. BTW, normal.para.spacing does not seem to do the job. Cheers, Chris -- Dr. Christoph Steinbeck (http://www.ice.mpg.de/departments/ChemInf) MPI of Chemical Ecology, Winzerlaer Str. 10, Beutenberg Campus, 07745 Jena, Germany Tel: +49(0)3641 571263 - Fax: +49(0)3641 571202 What is man but that lofty spirit - that sense of enterprise. ... Kirk, I, Mudd, stardate 4513.3..
Re: DOCBOOK: Re: Markup for Ant/Makefile Targets
Hi! Thanks for your reply! On Mon, 3 Dec 2001, Norman Walsh wrote: literal role=target? Okidoki, I *am* convinced now ;-) Yann Dirson suggested the same. To what extent is the role attribute handled by the style sheets? Greetings, Holger
DOCBOOK: Replaceable Parameter Values
Hi! What is the preferred way to mark up parameter values parameterreplaceablevalue/replaceable/parameter or simply replaceable class=parametervalue/replaceable If the second form I suggested is good enough, the first one seems redundant to me. Thanks for any help! Greetings, Holger
Re: DOCBOOK: Re: Markup for Ant/Makefile Targets
On Mon, Dec 03, 2001 at 02:13:59PM +0100, Holger Rauch wrote: To what extent is the role attribute handled by the style sheets? Some roles are handled for some elements by the generic stylesheets (eg. emphasis role=strong), but usually (eg. in this case) you have to add the special processing yourself. -- Yann Dirson [EMAIL PROTECTED] http://www.alcove.com/ Free-Software EngineerIngénieur Logiciel-Libre Free-Software time manager Responsable du temps Informatique-Libre Debian GNU/Linux developper [EMAIL PROTECTED]
DOCBOOK: DocBook Mailing List Guidelines
DocBook Mailing List Guidelines $Id: guidelines.xml,v 1.2 2001/08/10 16:12:08 ndw Exp $ 03 Dec 2001 - Table of Contents Posting Before You Post Replies Go to the Author Use Short Quotes of Previous Messages in Replies Do Not Post Attachments Cross-Posting Digests Unsubscribing from Docbook List Unsubscribing from Docbook-Apps List Unsubscribing from the Docbook Digest Unsubscribing from the Docbook-Apps Digest If You Stop Getting Messages Archive Reporting Bugs in Software Further Information on DocBook Contact This information[1] is posted to the DocBook and DocBook Applications mailing lists (and their digests) at regular intervals under the subject line DocBook list guidelines. Posting Only subscribers can post to mailing list, and only from the address they used when they subscribed. There are two DocBook-related lists: docbook and docbook-apps. The docbook list is for general questions about DocBook. The docbook-apps list is for questions about applications (stylesheets, transformation tools, publishing tools, processing requirements, etc.) that use or work with DocBook. Specifically: * Questions about DocBook markup (How do I markup a Widget? What's a FuncSynopsisInfo for?) should be sent to the docbook list. * Questions about XSL or DSSSL stylesheets, publishing DocBook documents on your platform of choice, support for PostScript, PDF, or other types of output, questions about Windows or Unix applications that can consume or produce DocBook should be sent to the docbook-apps list. Do not begin your subject line with help or subscribe since the list software will bounce the message because it looks like is an administrative request. Do not use un-informative subject lines like Urgent, Easy question, or Problem. Instead, use a meaningful subject line that will make sense to the people whose help you are trying to get. Both subscribers to [EMAIL PROTECTED] and [EMAIL PROTECTED] should post their messages to [EMAIL PROTECTED]. The messages will be received by both subscribers to the list and subscribers to the digest. Both subscribers to [EMAIL PROTECTED] and [EMAIL PROTECTED] should post their messages to [EMAIL PROTECTED]. The messages will be received by both subscribers to the list and subscribers to the digest. Do not start a new thread by replying to an unrelated message and just changing the subject line since the header of your message will contain references to the previous message and your new message will appear in the archive as one of the replies to the original message. It is better to start a new message for a new thread. Before You Post 1. Check that you are posting to the right list. 2. Make sure you are posting from the account that you used to subscribe. If you post from another account, your message will be delayed until it is approved by hand. 3. Check that your question isn't already answered in the mailing list archives at http://lists.oasis-open.org/archives/docbook/ or http://lists.oasis-open.org/archives/docbook-apps/. 4. If you are replying to a post, trim the quoted message to just the parts to which you are replying. Replies Go to the Author The DocBook lists don't set the Reply-to: header on messages (see Reply-To Munging Considered Harmful) so replies go to the author by default. If you want to reply to the list, make sure you include the list mailing address in your reply. Most mail readers make this easy by offering two forms of reply: reply/group-reply or reply/follow-up, for example. If you want to post to the list, make sure you select group-reply or follow-up or whatever your mail reader calls it. Use Short Quotes of Previous Messages in Replies Please do not quote entire messages just to add a few lines at the beginning or end. Instead, quote the parts to which you are directly replying or quote enough to establish the context. Everybody on the list has already received the message that you are quoting, and anyone searching the archive will find your message and the previous message listed under the same thread. Subscribers to the mailing list will just ignore most of the quoted messages and move to the next post, but subscribers to the mailing list Digest will mostly have to page past the quoted messages to reach the next material in which they are interested in reading. Do Not Post Attachments Since mailing lists have in the past been unwittingly used for spreading viruses in e-mail attachments, all e-mail attachments are banned from the DocBook lists. Most relevant documents (SGML and XML files, stylesheets, documents, etc.) are text files, so this does not affect the majority of posts to the list since you can include the files' text in the body of your message. If you need to refer to a binary file such as a PDF document, you should put the file on a Web site or FTP site and include
Re: DOCBOOK: XSLT stylesheet documentation
At 10:11 03/12/2001 +0100, Christoph Steinbeck wrote: Having to write a customization wrapper stylesheet is clear from your documentation of docbook.sf.net, but is there any documentation on the switches that can be used for customization? Say, to switch the line separation to 1.5 lines in the output document? http://www.dpawson.co.uk/docbook/styling/custom.html may help you more generally. Regards DaveP
Re: DOCBOOK: Re: Environment Variables in File/Directory Names
On Sun, 2001-12-02 at 22:18, Karl Eichwalder wrote: Gregory Leblanc [EMAIL PROTECTED] writes: This leads me to another question: What markup is appropriate for distinguishing between an environment variable and its value? (I'm simply talking about the difference between TOMCAT_HOME and $TOMCAT_HOME). I normally use varname... Really? And when your publischer decides, all environment variables I am my publisher, and will be for the forseeable future. should be prefixed with $ or printed with italics you've lost; better distinguish now: Why? It's the name of a variable. literal holds no contextual meaning for me, so I don't use it anywhere. It's (IMHO, of course) a hack for when you can't think of a better way to do something. I used envar to point to the value of the variable, instead of to the name of the variable, because that made sense to me at the time. I can see other intepretations, but I don't see any other markup that makes sense for the value of a variable. For envarDISPLAY/envar use literallocalhost:0.0/literal. varname is for such things like: varnamei/variable will increment from literal0/literal to literal9/literal. Sure, but only if you buy into envar being an environmental variable, instead of the value of an environmental variable. Clearly there are multiple possible interpretations here, that's why there are multiple stylesheets. :) Greg
Re: DOCBOOK: Re: Environment Variables in File/Directory Names
Gregory Leblanc wrote: Sure, but only if you buy into envar being an environmental variable, instead of the value of an environmental variable. Clearly there are multiple possible interpretations here, that's why there are multiple stylesheets. :) Hmm, I don't quite agree. Whether envar stands for a variable or the value it references is an important semantic distinction, not just something you should care for when adding presentational markup. And, as Norm repeatedly pointed out in the past, docbook being a documentation language, not a modeling language, I would not expect it doing variable lookup itself, i.e. I would expect to put values into the respective places myself. Regards, Stefan
Re: DOCBOOK: Re: Environment Variables in File/Directory Names
On Mon, 2001-12-03 at 10:32, Stefan Seefeld wrote: Gregory Leblanc wrote: Sure, but only if you buy into envar being an environmental variable, instead of the value of an environmental variable. Clearly there are multiple possible interpretations here, that's why there are multiple stylesheets. :) Hmm, I don't quite agree. Whether envar stands for a variable or the value it references is an important semantic distinction, not just something you should care for when adding presentational markup. Yes, exactly. I just think that they way it's used in the examples in TDG is wrong. :-) And, as Norm repeatedly pointed out in the past, docbook being a documentation language, not a modeling language, I would not expect it doing variable lookup itself, i.e. I would expect to put values into the respective places myself. I'm not expecting DocBook to do any variable lookup. I just can't find an element that makes sense for the value of a variable. People use literal, which I can't wrap my head around. Greg
DOCBOOK: Re: Replaceable Parameter Values
/ Holger Rauch [EMAIL PROTECTED] was heard to say: | What is the preferred way to mark up parameter values | | parameterreplaceablevalue/replaceable/parameter | | or simply | | replaceable class=parametervalue/replaceable | | If the second form I suggested is good enough, the first one seems | redundant to me. Can you provide a little more context? Often, I think parameter implies replaceable. Be seeing you, norm -- Norman Walsh [EMAIL PROTECTED] | When you can measure what you are http://www.oasis-open.org/docbook/ | speaking about, and express it in Chair, DocBook Technical Committee | numbers, you know something about | it; but when you cannot measure | it, when you cannot express it in | numbers, your knowledge is of a | meager and unsatisfactory kind: it | may be the beginning of knowledge, | but you have scarcely, in your | thoughts, advanced to the stage of | science.--William Thompson, Lord | Kelvin
DOCBOOK: Re: Environment Variables in File/Directory Names
Gregory Leblanc [EMAIL PROTECTED] writes: Yes, exactly. I just think that they way it's used in the examples in TDG is wrong. :-) Flagging nonsense with smilies doesn't turn it into sense. I'm not expecting DocBook to do any variable lookup. I just can't find an element that makes sense for the value of a variable. People use literal, which I can't wrap my head around. This is _your_ problem and not trying to solve it means causing trouble for co-workers (or for your readers). Whenever you think an element is missing use phrase or create a cstomization. Misusing an existing element is the worst you can do (it undermines the idea of sementic markup). -- [EMAIL PROTECTED] (work) / [EMAIL PROTECTED] (home): | http://www.suse.de/~ke/ | ,__o Free Translation Project:|_-\_, http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
DOCBOOK: Re: Environment Variables in File/Directory Names
Norman Walsh [EMAIL PROTECTED] writes: Sorry, I should have been more clear. In my experience, the distinction isn't often important. All the markup we're doing isn't important -- contents count! ;) I haven't used systems that automatically put the leading $ on envars or anything and the principal value in marking them up was for searching. I saw it in books done with LaTeX. A user searching for the FOO envar is probably interested in both FOO and $FOO (provided the FOO in question is an environment variable). Sure, you are not wrong! Automatic indexing is another reason to use envar or literal role=envar. -- [EMAIL PROTECTED] (work) / [EMAIL PROTECTED] (home): | http://www.suse.de/~ke/ | ,__o Free Translation Project:|_-\_, http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
DOCBOOK-APPS: Xalan Problem
Hai, My Requirement is to produce PCL and PDF from Xml and XSL. I am using following Fop-0.20.2 and the following jars. fop.jar batik.jar xalan-2.0.0.jar xerces-1.2.3.jar avalon-framework-4.0.jar logkit-1.0b4.jar jimi-1.0.jar when i run the Fop from command line i am getting the following errors. Can anyone please help me how to solve this problem. D:\freeaccess\Fop-0.20.2java -cp build\fop.jar;lib\batik.jar;lib\xalan-2.0.0.jar;lib\xerces-1.2.3.j ar;lib\avalon-framework-4.0.jar;lib\logkit-1.0b4.jar;lib\jimi-1.0.jar org.apache.fop.apps.Fop -xml s .xml -xsl s.xsl -pcl s.pcl [INFO]: FOP 0.20.2 [INFO]: building formatting object tree [INFO]: rendering areas to PCL [INFO]: [1] [WARN]: Some static content could not fit in the area. [INFO]: [2] [WARN]: Some static content could not fit in the area. [INFO]: Parsing of document complete, stopping renderer [INFO]: writing out PCL javax.xml.transform.TransformerException at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j ava, Compiled Code) at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:2894) at java.lang.Thread.run(Thread.java:479) - java.lang.ArrayIndexOutOfBoundsException at org.apache.fop.render.pcl.PCLRenderer.printBMP(PCLRenderer.java, Compiled Code) at org.apache.fop.render.pcl.PCLRenderer.renderImageArea(PCLRenderer.java:382) at org.apache.fop.image.ImageArea.render(ImageArea.java:68) at org.apache.fop.render.AbstractRenderer.renderLineArea(AbstractRenderer.java, Compiled Cod e) at org.apache.fop.layout.LineArea.render(LineArea.java:162) at org.apache.fop.render.AbstractRenderer.renderBlockArea(AbstractRenderer.java , Compiled Co de) at org.apache.fop.layout.BlockArea.render(BlockArea.java:82) at org.apache.fop.render.AbstractRenderer.renderBlockArea(AbstractRenderer.java , Compiled Co de) at org.apache.fop.layout.BlockArea.render(BlockArea.java:82) at org.apache.fop.render.AbstractRenderer.renderAreaContainer(AbstractRenderer. java, Compile d Code) at org.apache.fop.layout.ColumnArea.render(ColumnArea.java:33) at org.apache.fop.render.AbstractRenderer.renderSpanArea(AbstractRenderer.java, Compiled Cod e) at org.apache.fop.layout.SpanArea.render(SpanArea.java:53) at org.apache.fop.render.AbstractRenderer.renderBodyAreaContainer(AbstractRende rer.java, Com piled Code) at org.apache.fop.render.pcl.PCLRenderer.renderPage(PCLRenderer.java:679) at org.apache.fop.render.pcl.PCLRenderer.render(PCLRenderer.java:753) at org.apache.fop.apps.StreamRenderer.queuePage(StreamRenderer.java:206) at org.apache.fop.layout.AreaTree.addPage(AreaTree.java:81) at org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java, Compiled Code) at org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java, Compiled Code) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:178) at org.apache.xalan.transformer.ResultTreeHandler.endElement(ResultTreeHandler. java:284) at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java, Compiled Cod e) at org.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.ja va, Compiled Code) at org.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.jav a:193) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java, Compiled Code) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2 097) at org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(Transformer Impl.java:202 9) at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j ava, Compiled Code) at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:2894) at java.lang.Thread.run(Thread.java:479) [ERROR]: null Thanks and Regards Ramakrishnan.G
DOCBOOK-APPS: Fop Problem
Hai, I hava a problem with Fop. I use Fop,Xalan and Xerces to convert xml and xsl into PDF and PCL. It was not supporting CMYK colorspace. So i modified a few classes in fop and added a few classes. Now it works fine for PDF but it is not working for PCL format it is giving me the following problem. I am using following Fop-0.20.2 and the following jars. fop-cmyk.jar (Jar modified by me) batik.jar xalan-2.0.0.jar xerces-1.2.3.jar avalon-framework-4.0.jar logkit-1.0b4.jar jimi-1.0.jar when i run the Fop from command line i am getting the following errors. Can anyone please help me how to solve this problem. D:\freeaccess\Fop-0.20.2java -cp build\fop.jar;lib\batik.jar;lib\xalan-2.0.0.jar;lib\xerces-1.2.3.j ar;lib\avalon-framework-4.0.jar;lib\logkit-1.0b4.jar;lib\jimi-1.0.jar org.apache.fop.apps.Fop -xml s .xml -xsl s.xsl -pcl s.pcl [INFO]: FOP 0.20.2 [INFO]: building formatting object tree [INFO]: rendering areas to PCL [INFO]: [1] [WARN]: Some static content could not fit in the area. [INFO]: [2] [WARN]: Some static content could not fit in the area. [INFO]: Parsing of document complete, stopping renderer [INFO]: writing out PCL javax.xml.transform.TransformerException at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j ava, Compiled Code) at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:2894) at java.lang.Thread.run(Thread.java:479) - java.lang.ArrayIndexOutOfBoundsException at org.apache.fop.render.pcl.PCLRenderer.printBMP(PCLRenderer.java, Compiled Code) at org.apache.fop.render.pcl.PCLRenderer.renderImageArea(PCLRenderer.java:382) at org.apache.fop.image.ImageArea.render(ImageArea.java:68) at org.apache.fop.render.AbstractRenderer.renderLineArea(AbstractRenderer.java, Compiled Cod e) at org.apache.fop.layout.LineArea.render(LineArea.java:162) at org.apache.fop.render.AbstractRenderer.renderBlockArea(AbstractRenderer.java , Compiled Co de) at org.apache.fop.layout.BlockArea.render(BlockArea.java:82) at org.apache.fop.render.AbstractRenderer.renderBlockArea(AbstractRenderer.java , Compiled Co de) at org.apache.fop.layout.BlockArea.render(BlockArea.java:82) at org.apache.fop.render.AbstractRenderer.renderAreaContainer(AbstractRenderer. java, Compile d Code) at org.apache.fop.layout.ColumnArea.render(ColumnArea.java:33) at org.apache.fop.render.AbstractRenderer.renderSpanArea(AbstractRenderer.java, Compiled Cod e) at org.apache.fop.layout.SpanArea.render(SpanArea.java:53) at org.apache.fop.render.AbstractRenderer.renderBodyAreaContainer(AbstractRende rer.java, Com piled Code) at org.apache.fop.render.pcl.PCLRenderer.renderPage(PCLRenderer.java:679) at org.apache.fop.render.pcl.PCLRenderer.render(PCLRenderer.java:753) at org.apache.fop.apps.StreamRenderer.queuePage(StreamRenderer.java:206) at org.apache.fop.layout.AreaTree.addPage(AreaTree.java:81) at org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java, Compiled Code) at org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java, Compiled Code) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:178) at org.apache.xalan.transformer.ResultTreeHandler.endElement(ResultTreeHandler. java:284) at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java, Compiled Cod e) at org.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.ja va, Compiled Code) at org.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.jav a:193) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java, Compiled Code) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2 097) at org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(Transformer Impl.java:202 9) at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j ava, Compiled Code) at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:2894) at java.lang.Thread.run(Thread.java:479) [ERROR]: null Thanks and Regards Ramakrishnan.G
DOCBOOK-APPS: line spacing in fo xslt stylesheets
Looking at the following URL was pretty helpful for customizing my PDF output document http://docbook.sourceforge.net/projects/xsl/doc/reference.html I could, however, not find the parameter for setting the line spacing in normal text. Can anyone instruct me on that topic. BTW, normal.para.spacing does not seem to do the job. Cheers, Chris -- Dr. Christoph Steinbeck (http://www.ice.mpg.de/departments/ChemInf) MPI of Chemical Ecology, Winzerlaer Str. 10, Beutenberg Campus, 07745 Jena, Germany Tel: +49(0)3641 571263 - Fax: +49(0)3641 571202 What is man but that lofty spirit - that sense of enterprise. ... Kirk, I, Mudd, stardate 4513.3..
DOCBOOK-APPS: sgml2x 0.99.1 released
I'm pleased to announce the release of sgml2x 0.99.1. This is a beta version, and the first official release to the world. Probably only bugfixes will be integrated until 1.0 comes out. It requires jade and jadetex to work, and you'll need docbook (sgml or xml), and docbook-dsssl to make immediate use of it. It was developped as a bash script, and should run on any platform where bash runs. You can get it at: http://freesoftware.fsf.org/download/alcovebook/sgml2x-0.99.1.tar.gz Here is a small excerpt from the manpage: DESCRIPTION sgml2x allows to easily format a SGML or XML document using DSSSL stylesheets, and provides the following fea tures: · Multiple possible stylesheets per document class · Easy specification of stylesheets using aliases · Easy integration of new stylesheets by adding a sim ple new definition file in a configuration directory · The caller can specify a PATH-like list of configu ration directories, defaulting to a system-wide, a per-user, and a per-project configuration directo ries · Automatic selection of a default stylesheet to be used, based on assigned priorities · Pass arbitrary options to jade(1) The document-class used to look for the stylesheets, and the output format, is for now only derived from from the name with which the program is called, so you will want to call this program through symbolic links like docbook2pdf. COPYRIGHT Copyright © 2001 Alcove. sgml2x is licenced under the GNU General Public Licence, version 2. This documentation is licenced under the GNU Free Documen tation Licence, version 1. -- Yann Dirson [EMAIL PROTECTED] http://www.alcove.com/ Free-Software EngineerIngénieur Logiciel-Libre Free-Software time manager Responsable du temps Informatique-Libre Debian GNU/Linux developper [EMAIL PROTECTED]
DOCBOOK-APPS: figure and flow of text question
Hi, I'm placing a large EPS into a file as a figure, and I'm noticing that when there isn't enough room to put it after any text on one page, the figure is rendered on the following page. This is fine, but is it possible to have any text that comes /after/ the figure in the flow of the document to be placed before it in the order of the rendering, such that there is no great gaping gap where the figure wouldn't fit on the page? I'm using the 1.7b DSSSL stylesheets for print. Cheers, hope that makes sense, -- roryh
DOCBOOK-APPS: Re: figure and flow of text question
/ Rory Hunter [EMAIL PROTECTED] was heard to say: | page, the figure is rendered on the following page. This is fine, but | is it possible to have any text that comes /after/ the figure in the | flow of the document to be placed before it in the order of the | rendering, such that there is no great gaping gap where the figure | wouldn't fit on the page? That would be a float. Unfortunately Jade doesn't do floats. Be seeing you, norm -- Norman Walsh [EMAIL PROTECTED] | One does what one is; one becomes http://www.oasis-open.org/docbook/ | what one does.--Robert Musil Chair, DocBook Technical Committee |
DOCBOOK-APPS: DocBook Mailing List Guidelines
DocBook Mailing List Guidelines $Id: guidelines.xml,v 1.2 2001/08/10 16:12:08 ndw Exp $ 03 Dec 2001 - Table of Contents Posting Before You Post Replies Go to the Author Use Short Quotes of Previous Messages in Replies Do Not Post Attachments Cross-Posting Digests Unsubscribing from Docbook List Unsubscribing from Docbook-Apps List Unsubscribing from the Docbook Digest Unsubscribing from the Docbook-Apps Digest If You Stop Getting Messages Archive Reporting Bugs in Software Further Information on DocBook Contact This information[1] is posted to the DocBook and DocBook Applications mailing lists (and their digests) at regular intervals under the subject line DocBook list guidelines. Posting Only subscribers can post to mailing list, and only from the address they used when they subscribed. There are two DocBook-related lists: docbook and docbook-apps. The docbook list is for general questions about DocBook. The docbook-apps list is for questions about applications (stylesheets, transformation tools, publishing tools, processing requirements, etc.) that use or work with DocBook. Specifically: * Questions about DocBook markup (How do I markup a Widget? What's a FuncSynopsisInfo for?) should be sent to the docbook list. * Questions about XSL or DSSSL stylesheets, publishing DocBook documents on your platform of choice, support for PostScript, PDF, or other types of output, questions about Windows or Unix applications that can consume or produce DocBook should be sent to the docbook-apps list. Do not begin your subject line with help or subscribe since the list software will bounce the message because it looks like is an administrative request. Do not use un-informative subject lines like Urgent, Easy question, or Problem. Instead, use a meaningful subject line that will make sense to the people whose help you are trying to get. Both subscribers to [EMAIL PROTECTED] and [EMAIL PROTECTED] should post their messages to [EMAIL PROTECTED]. The messages will be received by both subscribers to the list and subscribers to the digest. Both subscribers to [EMAIL PROTECTED] and [EMAIL PROTECTED] should post their messages to [EMAIL PROTECTED]. The messages will be received by both subscribers to the list and subscribers to the digest. Do not start a new thread by replying to an unrelated message and just changing the subject line since the header of your message will contain references to the previous message and your new message will appear in the archive as one of the replies to the original message. It is better to start a new message for a new thread. Before You Post 1. Check that you are posting to the right list. 2. Make sure you are posting from the account that you used to subscribe. If you post from another account, your message will be delayed until it is approved by hand. 3. Check that your question isn't already answered in the mailing list archives at http://lists.oasis-open.org/archives/docbook/ or http://lists.oasis-open.org/archives/docbook-apps/. 4. If you are replying to a post, trim the quoted message to just the parts to which you are replying. Replies Go to the Author The DocBook lists don't set the Reply-to: header on messages (see Reply-To Munging Considered Harmful) so replies go to the author by default. If you want to reply to the list, make sure you include the list mailing address in your reply. Most mail readers make this easy by offering two forms of reply: reply/group-reply or reply/follow-up, for example. If you want to post to the list, make sure you select group-reply or follow-up or whatever your mail reader calls it. Use Short Quotes of Previous Messages in Replies Please do not quote entire messages just to add a few lines at the beginning or end. Instead, quote the parts to which you are directly replying or quote enough to establish the context. Everybody on the list has already received the message that you are quoting, and anyone searching the archive will find your message and the previous message listed under the same thread. Subscribers to the mailing list will just ignore most of the quoted messages and move to the next post, but subscribers to the mailing list Digest will mostly have to page past the quoted messages to reach the next material in which they are interested in reading. Do Not Post Attachments Since mailing lists have in the past been unwittingly used for spreading viruses in e-mail attachments, all e-mail attachments are banned from the DocBook lists. Most relevant documents (SGML and XML files, stylesheets, documents, etc.) are text files, so this does not affect the majority of posts to the list since you can include the files' text in the body of your message. If you need to refer to a binary file such as a PDF document, you should put the file on a Web site or FTP site and include
