AW: [docbook-apps] Programlising question
Hi, My programlistings are not inside example elements but they are inside other block elements - most notably, para and sidebar. I'll do some further testing and post the results. Thanks All. Scott Von: Bob Stayton [mailto:b...@sagehill.net] Gesendet: Mittwoch, 10. November 2010 17:57 An: Speights, Scott; docbook-apps@lists.oasis-open.org Betreff: Re: [docbook-apps] Programlising question Is your programlisting inside an example element? If so, then it is getting a keep-together.within-column=always property on the block containing the title and content. The attribute-set named 'example.properties' uses the attribute-set named 'formal.object.properties', which has that keep-together property by default. If you don't want that behavior, you can use: xsl:attribute-set name=example.properties xsl:attribute name=keep-together.within-columnauto/xsl:attribute /xsl:attribute-set The auto value turns off the keep. If you programlisting is not inside an example, then something in your customization layer is adding that property, because it is not in the default stylesheet for programlisting itself. Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: Speights, Scott mailto:scott.speig...@haufe-lexware.com To: docbook-apps@lists.oasis-open.org Sent: Wednesday, November 10, 2010 1:10 AM Subject: [docbook-apps] Programlising question Hello All, I need to format large pieces of code in my documents that are longer than one page. When the message in the program listing reaches the end of the page, it doesn't break but disappears into the bottom margin. Is there a good way to get programlisting to break pages - like para - automatically? Thanks, Scott Scott Speights Technical Writer -- Haufe-Lexware GmbH Co. KG Munzinger Str. 9, D-79111 Freiburg Tel. +49 761 898-5313 E-Mail: scott.speig...@haufe-lexware.com Internet: http://www.haufe-lexware.com http://www.haufe-lexware.com/ -- Kommanditgesellschaft, Sitz und Registergericht Freiburg, HRA 4408 Komplementäre: Haufe-Lexware Verwaltungs GmbH, Sitz und Registergericht Freiburg, HRB 5557; Martin Laqua Geschäftsführung: Isabel Blank, Birte Hackenjos, Jörg Frey, Matthias Mühe, Markus Reithwiesner, Joachim Rotzinger, Dr. Carsten Thies Beiratsvorsitzende: Andrea Haufe
RE: [docbook-apps] Docbook XML and Catalog
Hi Dave Pawson, As per your suggestion I have downloaded saxon 6.5.5. In this case the following error appears F:\ADVENT\APP\xslf0_samples\DOCBOOK-samples\completedjava -cp C:/saxon/saxon.jar;C:/docbook-xsl-1.76.1-RC2/extensions/ saxon65.jar;C:/xml-commons-resolver-1.2/resolver.jar;C:/fop-1.0/ com.icl.saxon.StyleSheet -x org.apache.xml.resolver.to ols.ResolvingXMLReader -y org.apache.xml.resolver.tools.ResolvingXMLReader -r org.apache.xml.resolver.tools.CatalogResol ver -u -o DK1182_C003.fo DK1182_C003.xml file:///L:/xml/docbook-xsl-ns-1.76.1-RC2/fo/docbook.xsl Class org.apache.xml.resolver.tools.CatalogResolver is not a URIResolver Can anybody help me to fix this? Thanks, Srikrishnan -Original Message- From: Dave Pawson [mailto:da...@dpawson.co.uk] Sent: Wednesday, November 10, 2010 3:58 PM To: SriKrishnan Cc: docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] Docbook XML and Catalog On Wed, 10 Nov 2010 15:23:03 +0530 SriKrishnan srikrish...@techset.co.uk wrote: Hi Dave Pawson, Thanks for your immediate reply. I will keep this in mind always. But still there are some errors in the next steps. Can anybody help me to solve this? It seems that it throws error on docbook.xsl. But I didn't found any error when I created FO without using catalog (by adding system path straightaway in xml) F:\ADVENT\APP\xslf0_samples\DOCBOOK-samples\completedjava -cp C:/saxonhe9-2-1-5j/saxon9he.jar; Warning: at xsl:stylesheet on line 9 column 31 of docbook.xsl: Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor The error is clear and correct. The stylesheets require a 1.0 processor and you are using Saxon 9 which is XSLT 2.0 Change to saxon 655 which supports 1.0 -- regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] acronyms, abbreviations, definitions
Hello Dave, thank you for the reassuring feedback :) Since docbook has no 'proper' expansion of an acronym, I've used the universal phrase with a condition? After pondering this a bit, I do understand why you'd qualify the phrase with an attribute: it's not just any old phrase, but a phrase that serves a specific function, i.e. to expand the acronym/abbreviation. However, I do not understand why mark it with a condition? It would seem more logical to me to attribute it a role, no? Perhaps you might like to submit a feature request, for the expansion of acronym to include it's 'spelling out'? http://sourceforge.net/tracker/?group_id=21935atid=373750 It is IMHO a valid addition. Thanks for submitting this already! I will try my luck in requesting the same for abbrev too, since the improvement in accessibility can be considerable in screen reader output for both. Nathalie - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] acronyms, abbreviations, definitions
Hello David, I once started to implement an acronym expanding xslt with the idea that I could write acronymTLA/acronym and have the first occurrence automatically be expanded to TLA (Three Letter Acronym). Things were going fine till I hit GNU and ended up with GNU (GNU (GNU (...) is not Unix) is not Unix) ;-) That of course is not what one would want to happen - what an example :) You might check out the Glossary database feature: http://www.sagehill.net/docbookxsl/GlossDatabase.html Thanks for pointing me at this - the mechanism may be a good (or even improved) substitute for the XHTML dfn/, especially if we try to assist people with cognitive disabilities in understanding texts - in German (the language our project is dealing most with), there's a science of its own determining what are hard words; these could be dealt with in this way, increasing the accessibility of texts not translated into easy language... Nathalie - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] add ulink to imageobject
Hi All, How can I add a link to an imageobject? (I found an old blog post that did not work for me: http://www.mail-archive.com/docb...@lists.oasis-open.org/msg03316.html) Example code on how I use imageobject is below. I tried to add 'ulink' at all possible levels, without success. Thanks in advance and best regards, Martin figure titleFigure/title mediaobject imageobject imagedata format='SVG' fileref='http://example.org/pic.svg' / /imageobject captioncaption/caption /mediaobject /figure -- Dipl-Inf. Martin Gütlein Phone: +49 (0)761 203 8442 (office) +49 (0)177 623 9499 (mobile) Email: guetl...@informatik.uni-freiburg.de - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Centering Tables in Print with Fop 1.0
I have no problems now for tables spanning the print width, nor with tables of any width in html. But I need to center less-than-page-width tables in print. I have used Bob Stayton's xsl fo chunk on p. 474 as a start to try to get my narrow tables centered in print. Here is my current version: !-- center tables in print, from p. 474 in Stayton: -- xsl:template name=table.layout xsl:param name=table.content/ fo:table width=100% table-layout=fixed!-- I dded table-layout attribute -- fo:table-column column-width=proportional-column-width(1)/ !- [1] hack next line: added actual table width here -- fo:table-column column-width=3in/ fo:table-column column-width=proportional-column-width(1)/ fo:table-body start-indent=0pt fo:table-row !-- fo:table-cell/ -- !-- [2] fo complains about missing table-cell children, I added Bob's zero space char from p. 261 -- fo:table-cellfo:block#xFEFF;/fo:block/fo:table-cell fo:table-cell fo:table fo:table-body start-indent=0pt fo:table-rowfo:table-cellfo:block xsl:copy-of select=$table.content/ /fo:block/fo:table-cell/fo:table-row /fo:table-body /fo:table /fo:table-cell !-- ditto from [2] -- fo:table-cellfo:block#xFEFF;/fo:block/fo:table-cell /fo:table-row /fo:table-body /fo:table /xsl:template That works for the one specific table when I hardwire the actual table width. Is there any xsl:fo magic that can get the total original table width at [1]? If not I suppose I can post process the fo to fix it, but there must be a more elegant way. Thanks, -Tom Thomas M. Browder, Jr. Niceville, Florida USA - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] acronyms, abbreviations, definitions
Hi Larry, The advantage of storing it centrally in the glossary is that the expansion doesn't have to be added to every instance of the acronym (while convention says it only needs to be expanded at first occurrence, in electronic media, determining the first occurrence for a reader can be difficult so we frequently used an acronym tag the first time an acronym was used in a topic). It also provides a mechanism for explaining what the expanded acronym means, since expansion is not always sufficient to explain why it matters. At first I found the prospective offered by the glossary database feature rather enticing, exactly because of the repetitiveness (during the production phase) of adding the extended version - ideally to each - instance of an abbreviation/acronym. So the idea of having an external glossary that is run over a text in which the acronyms/abbreviations are also marked as glossterms (which, when explanation is necessary, can also be linked to a real glossary - slick!), and xslt'ing the lot into nicely formed, fully functional XHTML-Elements would be something that could greatly enhance the reading experience of online versions, while in PDF/print versions, just the classical glossary could be output... However, the question arises for me how viable this is when dealing with a very large text base. (in my case I'm working on a growing online library with currently 1600 texts - from short articles to whole books - dealing with diverse aspects of disability on a variety of levels). - I'd be afraid that the glossary itself would soon grow to dimensions that are not so easily to be edited anymore. - And, as I understood it, the text is processed in loops for each single glossary term (even if 3/4 of them are not relevant for the text in question). Since our HTML-versions are cached, this would not happen every time the pages are loaded, but still... wouldn't that create an enormous processing overhead? Asked the other way around, how large is the text base you apply this technique to? Also, I'm not sure about how your output looks: Getting expansion on hover or similar is slightly trickier, but not a major stretch (the match to the glossentry is already being made by the extended glossterm auto link code) by adding a title attribute with the content of the glossterm to the anchor element around the acronym in the output (at least in HTML). Do I understand rightly that you are adding the expansion as a title to the a element? I hate to say so, but I am just currently being made aware of the fact that title does not work reliably on links in screen readers. Apart from the fact that the expansion is no longer attributed to the acronym itself, but rather becomes additional information about the content being linked to... So what may look the same for sighted people is a completely different (and possibly invisible) creature for screen reader output. This mechanism should thus actually insert the glossterm into acronym to make it fully functional (perhaps only creating the glossary link when there is, in fact, an additional explanation...). Thanks for the interesting input :) Nathalie - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
AW: [docbook-apps] Programlising question
Hi Bob, The attribute set tip was correct. The conflict was caused because my programlistings were nested inside of sidebars. As always, many thanks. Best, Scott Von: Bob Stayton [mailto:b...@sagehill.net] Gesendet: Mittwoch, 10. November 2010 17:57 An: Speights, Scott; docbook-apps@lists.oasis-open.org Betreff: Re: [docbook-apps] Programlising question Is your programlisting inside an example element? If so, then it is getting a keep-together.within-column=always property on the block containing the title and content. The attribute-set named 'example.properties' uses the attribute-set named 'formal.object.properties', which has that keep-together property by default. If you don't want that behavior, you can use: xsl:attribute-set name=example.properties xsl:attribute name=keep-together.within-columnauto/xsl:attribute /xsl:attribute-set The auto value turns off the keep. If you programlisting is not inside an example, then something in your customization layer is adding that property, because it is not in the default stylesheet for programlisting itself. Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: Speights, Scott mailto:scott.speig...@haufe-lexware.com To: docbook-apps@lists.oasis-open.org Sent: Wednesday, November 10, 2010 1:10 AM Subject: [docbook-apps] Programlising question Hello All, I need to format large pieces of code in my documents that are longer than one page. When the message in the program listing reaches the end of the page, it doesn't break but disappears into the bottom margin. Is there a good way to get programlisting to break pages - like para - automatically? Thanks, Scott Scott Speights Technical Writer -- Haufe-Lexware GmbH Co. KG Munzinger Str. 9, D-79111 Freiburg Tel. +49 761 898-5313 E-Mail: scott.speig...@haufe-lexware.com Internet: http://www.haufe-lexware.com http://www.haufe-lexware.com/ -- Kommanditgesellschaft, Sitz und Registergericht Freiburg, HRA 4408 Komplementäre: Haufe-Lexware Verwaltungs GmbH, Sitz und Registergericht Freiburg, HRB 5557; Martin Laqua Geschäftsführung: Isabel Blank, Birte Hackenjos, Jörg Frey, Matthias Mühe, Markus Reithwiesner, Joachim Rotzinger, Dr. Carsten Thies Beiratsvorsitzende: Andrea Haufe
RE: [docbook-apps] Olink logic between different trunk/branches folders of documentation (several projects)
Bob, Sam, thanks for the ideas, you have brought about 1 month ago! I've finally created the complete solution for using the olinks in my usecase. If anyone interested in it, I include the concept of it (look at the following text). So, the initial structure was: /doc - mars -- trunk (mars_userguide.xml, mars_adminguide.xml) -- branches --- 1.0 (mars_userguide.xml, mars_adminguide.xml) --- 2.0 (mars_userguide.xml, mars_adminguide.xml) - pluto -- trunk (pluto_userguide.xml, pluto_adminguide.xml) -- branches --- 0.4 (pluto_userguide.xml, pluto_adminguide.xml) --- 0.8 (pluto_userguide.xml, pluto_adminguide.xml) The same structure (except of extensions changed from .xml to .html) is for output. I use current.docid = /*/@id = doc filename The following ways of olinking are possible/prohibited: Possible: 1. trunk - trunk (within one project, the arrow shows the olink direction) 2. trunk - branch (within two different projects). Prohibited: 3. branch - trunk (within any project, within two different projects). Within one project - it has no sense; Within any 2 projects - it prohibited, because to the date of releasing trunk doc can lost the topic it has (or text can lost the initial meaning we mentioned at the time of creating olink). 4. trunk - trunk (within two different projects). Reasons - the same (see previous list item). When an author creates the olink he/she makes a combined targetdoc: docid-version_nr (targetptr used as is). If author links to trunk (same project) it uses no '-version_nr' Let's imagine we link from mars project (mars_userguide document). i.e. for trunk - trunk (1): olink targetdoc=mars_adminguide targetptr=mars_adminguide_intro i.e. for trunk - branch (2): olink targetdoc=pluto_userguide-0.4 targetptr=pluto_userguide_intro The master target database is generated automatically using dir structure and uses corresponding versions numbers. i.e. !ENTITY mars_adminguide-1.0 SYSTEM path/mars/branches/1.0/mars_adminguide.target.db !ENTITY mars_adminguide SYSTEM path/mars/trunk/mars_adminguide.target.db The current version # is supplied by cocoon tokens, so the current document always knows what version it belongs to (despite the fact it has the same root id, filename, etc as others mars_userguide docs). So olinks are always correctly resolved. The only problem I faced was with case (1) after branching. So, from the one hand documents still have the same links, but from the other, relative position of the documents are changed after branching (they belongs to branched numbered path) so it has to link to branched version (not trunk one), so it need to be updated. This issue was resolved using converting of all such links (using current branch #) at preprocess stage just before cocoon processing. -- Best regards, Eduard Tibet -Original Message- From: Sam Fischmann [mailto:sam.fischm...@gmail.com] Sent: Tuesday, October 12, 2010 10:54 PM To: Eduard Tibet Cc: docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] Olink logic between different trunk/branches folders of documentation (several projects) It seems that you want to link arbitrarily from any version of any document into any version of any other document. Generally, I don't think this is a good idea, because it's rather confusing to link to two different versions of one book from one version of another. I would think the customer only wants to have one version of each product installed. The blessed combination approach mentioned by Bob above seems like it would yield better results. That being said, if it's truly a requirement and that is the way your products are designed, then you have to do something about it... so provided that is the case: Unless filenames, section titles, element ids, and organization do not change whatsoever among any versions of any product, you really have to consider each version of each document as a unique item. Consider what Bob stated above: There should be no version information in those attribute values. This makes an olink a logical link between documents, not a physical link like an href. I still think the second part is correct, but in your case, the version information you need to add is really information that distinguishes between two different documents with potential differences in organization, titles, and ids. If this were my requirement, I would: 1) Maintain a branch file that keeps track of each project and each branch within each project. Each branch gets a unique prefix of some sort. This would be the only file you'd have to maintain by hand. 2) Write some script or transform to read the branch file and iterate over each branch for each project to build links and/or assemble the portion of the target database file for that branch, and store the final target database in trunk or some other external location. The targetdoc attributes get the prefixes mentioned above. 3) In your build process, invoke this script
Re: [docbook-apps] removing elements and attrs from title
On 11/11/2010 1:44 AM, Cramer, David W (David) wrote:
Interesting idea about removing xml:id from titles. Try the
following: ...
That seems to work...not sure if it's the best/easiest way.
Yes, that gets rid of the xml:id attr in titles. Thanks!
I think to remove remark you just add the following inside
yourinclude:
define name=db.remark notAllowed/ /define
Sorry, I wasn't clear; I *only* want to remove remark from inside
title, whereas the above removes it everywhere. The problem is that
there is something about the title defn in DB5 that prevents any
changes to its content elements. Even the ff. minimalist defn triggers
the interleave error msg:
define name=db.title
element name=title
text/
/element
/define
BTW, the reason I want to make these two changes has to do with our
processing to produce a PDF (what you call a toolchain, I think). Our
output method doesn't allow xrefs to titles (which is the only use we're
making of xml:id). And it appears that the LaTeX macro I cribbed for
outputting remarks with a colored background (to make them easy to
see) goes into an infinite loop when the remark (or the LaTeX
\comment{} command that this gets translated into) is inside a title
(\title{}). Maybe I'll go back and try to figure out why the LaTeX
macro does that, instead of prohibiting remarks inside titles...
--
Mike Maxwell
-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] add ulink to imageobject
Hi Martin, The following is valid and works in HTML output: figure titleFigure/title ulink url=http://www.sagehill.net; inlinemediaobject imageobject imagedata format='SVG' fileref='http://example.org/pic.svg' / /imageobject captioncaption/caption /inlinemediaobject /ulink /figure Are you trying to get this to work in PDF output? I've found that graphical links work with some XSL-FO processors and not others. But that would be an issue with the XSL-FO processor, not the stylesheet. Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: Martin Guetlein martin.guetl...@googlemail.com To: docbook-apps@lists.oasis-open.org Sent: Thursday, November 11, 2010 5:46 AM Subject: [docbook-apps] add ulink to imageobject Hi All, How can I add a link to an imageobject? (I found an old blog post that did not work for me: http://www.mail-archive.com/docb...@lists.oasis-open.org/msg03316.html) Example code on how I use imageobject is below. I tried to add 'ulink' at all possible levels, without success. Thanks in advance and best regards, Martin figure titleFigure/title mediaobject imageobject imagedata format='SVG' fileref='http://example.org/pic.svg' / /imageobject captioncaption/caption /mediaobject /figure -- Dipl-Inf. Martin Gütlein Phone: +49 (0)761 203 8442 (office) +49 (0)177 623 9499 (mobile) Email: guetl...@informatik.uni-freiburg.de - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] acronyms, abbreviations, definitions
On Thu, 11 Nov 2010 11:59:07 +0100 Nathalie Sequeira n...@n-faktor.net wrote: Hello Dave, thank you for the reassuring feedback :) Since docbook has no 'proper' expansion of an acronym, I've used the universal phrase with a condition? After pondering this a bit, I do understand why you'd qualify the phrase with an attribute: it's not just any old phrase, but a phrase that serves a specific function, i.e. to expand the acronym/abbreviation. However, I do not understand why mark it with a condition? It would seem more logical to me to attribute it a role, no? Yes, it could be role. I chose condition since that seemed right to me. YMMV but you do need it for the customization layer, To process these as you want them, hopefully until the Docbook committee agree it is a worthwhile addition. -- regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Docbook XML and Catalog
On Thu, 11 Nov 2010 14:05:05 +0530 SriKrishnan srikrish...@techset.co.uk wrote: Hi Dave Pawson, As per your suggestion I have downloaded saxon 6.5.5. In this case the following error appears F:\ADVENT\APP\xslf0_samples\DOCBOOK-samples\completedjava -cp C:/saxon/saxon.jar;C:/docbook-xsl-1.76.1-RC2/extensions/ saxon65.jar;C:/xml-commons-resolver-1.2/resolver.jar;C:/fop-1.0/ com.icl.saxon.StyleSheet -x org.apache.xml.resolver.to ols.ResolvingXMLReader -y org.apache.xml.resolver.tools.ResolvingXMLReader -r org.apache.xml.resolver.tools.CatalogResol ver -u -o DK1182_C003.fo DK1182_C003.xml file:///L:/xml/docbook-xsl-ns-1.76.1-RC2/fo/docbook.xsl Class org.apache.xml.resolver.tools.CatalogResolver is not a URIResolver Can anybody help me to fix this? Thanks, Srikrishnan The message (again) is correct org.apache.xml.resolver.tools.CatalogResolver is not a URIResolver It is a catalogue resolver? http://www.dpawson.co.uk/nodesets/entries/090528.html may help -x is the uri resolver? http://saxon.sourceforge.net/saxon6.5.5/using-xsl.html HTH -- regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Centering Tables in Print with Fop 1.0
Tom Here is an adjusted version that triggers only when align is used on the table. This has some peculiarities when processed with FOP 1.0. I would suggest that you use fixed column widths and not proportional in the XML tables because proportional is not quite right in FOP when used in a table in a table. But if you use fixed widths it should be fine (or at least in my setup it was). Cheers, Dean Nelson !-- center tables in print, from p. 474 in Stayton: -- xsl:template name=table.layout xsl:param name=table.content/ xsl:choose xsl:when test=self::tab...@align] fo:table width=100% table-layout=fixed fo:table-column column-width=proportional-column-width(1)/ fo:table-column/ fo:table-column column-width=proportional-column-width(1)/ fo:table-body start-indent=0pt fo:table-row fo:table-cellfo:block/fo:block/fo:table-cell fo:table-cell fo:table fo:table-body start-indent=0pt fo:table-rowfo:table-cellfo:block xsl:copy-of select=$table.content/ /fo:block/fo:table-cell/fo:table-row /fo:table-body /fo:table /fo:table-cell fo:table-cellfo:block/fo:block/fo:table-cell /fo:table-row /fo:table-body /fo:table /xsl:when xsl:otherwise xsl:copy-of select=$table.content/ /xsl:otherwise /xsl:choose /xsl:template In a message dated 11/11/10 06:40:35 Pacific Standard Time, tom.brow...@gmail.com writes: I have no problems now for tables spanning the print width, nor with tables of any width in html. But I need to center less-than-page-width tables in print. I have used Bob Stayton's xsl fo chunk on p. 474 as a start to try to get my narrow tables centered in print. Here is my current version: !-- center tables in print, from p. 474 in Stayton: -- xsl:template name=table.layout xsl:param name=table.content/ fo:table width=100% table-layout=fixed!-- I dded table-layout attribute -- fo:table-column column-width=proportional-column-width(1)/ !- [1] hack next line: added actual table width here -- fo:table-column column-width=3in/ fo:table-column column-width=proportional-column-width(1)/ fo:table-body start-indent=0pt fo:table-row !-- fo:table-cell/ -- !-- [2] fo complains about missing table-cell children, I added Bob's zero space char from p. 261 -- fo:table-cellfo:block#xFEFF;/fo:block/fo:table-cell fo:table-cell fo:table fo:table-body start-indent=0pt fo:table-rowfo:table-cellfo:block xsl:copy-of select=$table.content/ /fo:block/fo:table-cell/fo:table-row /fo:table-body /fo:table /fo:table-cell !-- ditto from [2] -- fo:table-cellfo:block#xFEFF;/fo:block/fo:table-cell /fo:table-row /fo:table-body /fo:table /xsl:template That works for the one specific table when I hardwire the actual table width. Is there any xsl:fo magic that can get the total original table width at [1]? If not I suppose I can post process the fo to fix it, but there must be a more elegant way. Thanks, -Tom Thomas M. Browder, Jr. Niceville, Florida USA - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Centering Tables in Print with Fop 1.0
On Thu, Nov 11, 2010 at 16:53, deannelson deannel...@aol.com wrote: Tom Here is an adjusted version that triggers only when align is used on the table. This has some peculiarities when processed with FOP 1.0. I would suggest that you use fixed column widths and not proportional in the XML tables because proportional is not quite right in FOP when used in a table in a table. But if you use fixed widths it should be fine (or at least in my setup it was). ... I'll try it, Dean, Thanks! -Tom Thomas M. Browder, Jr. Niceville, Florida USA - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
RE: [docbook-apps] Docbook XML and Catalog
Hi Dave Pawson, I am frankly saying I don't know anything about Java, Saxon and FOP. Now only I am trying to learn these for the purpose of generating PDF from the XML source. Now I am reading DocBook XSL: The Complete Guide, 4th Edition. In this on page 92 of 723, there is a sample coding. In that it has been mentioned as follows: For Saxon: /jausvar/ s h-acrpe /r/eussorl/vjearv.aj/asra;x/ouns.rj/asrh:a/rdeoc b\ook-xsl/extensions/saxon653.jar:\ c-oxm .oircgl..aspaaxcohne..Sxtmyll.erSehseoeltve r\. tools.ResolvingXMLReader \ -y org.apache.xml.resolver.tools.ResolvingXMLReader \ -r org.apache.xml.resolver.tools.CatalogResolver \ -u \ -o myfile.html \ myfile.xml docbook.xsl I just followed it, can you please guide me any other books available in the market to learn about Saxon and FOP as a beginners like me? FYI: I have purchased Michael Key's XSLT 2.0 Book. In this also I don't found how to configure catalog option for saxon? Thanks, Srikrishnan -Original Message- From: Dave Pawson [mailto:da...@dpawson.co.uk] Sent: Thursday, November 11, 2010 11:41 PM To: SriKrishnan Cc: docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] Docbook XML and Catalog On Thu, 11 Nov 2010 14:05:05 +0530 SriKrishnan srikrish...@techset.co.uk wrote: Hi Dave Pawson, As per your suggestion I have downloaded saxon 6.5.5. In this case the following error appears F:\ADVENT\APP\xslf0_samples\DOCBOOK-samples\completedjava -cp C:/saxon/saxon.jar;C:/docbook-xsl-1.76.1-RC2/extensions/ saxon65.jar;C:/xml-commons-resolver-1.2/resolver.jar;C:/fop-1.0/ com.icl.saxon.StyleSheet -x org.apache.xml.resolver.to ols.ResolvingXMLReader -y org.apache.xml.resolver.tools.ResolvingXMLReader -r org.apache.xml.resolver.tools.CatalogResol ver -u -o DK1182_C003.fo DK1182_C003.xml file:///L:/xml/docbook-xsl-ns-1.76.1-RC2/fo/docbook.xsl Class org.apache.xml.resolver.tools.CatalogResolver is not a URIResolver Can anybody help me to fix this? Thanks, Srikrishnan The message (again) is correct org.apache.xml.resolver.tools.CatalogResolver is not a URIResolver It is a catalogue resolver? http://www.dpawson.co.uk/nodesets/entries/090528.html may help -x is the uri resolver? http://saxon.sourceforge.net/saxon6.5.5/using-xsl.html HTH -- regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Docbook XML and Catalog
On Fri, 12 Nov 2010 09:52:44 +0530 SriKrishnan srikrish...@techset.co.uk wrote: Hi Dave Pawson, I am frankly saying I don't know anything about Java, Saxon and FOP. Now only I am trying to learn these for the purpose of generating PDF from the XML source. Now I am reading DocBook XSL: The Complete Guide, 4th Edition. In this on page 92 of 723, there is a sample coding. In that it has been mentioned as follows: For Saxon: /jausvar/ s h-acrpe /r/eussorl/vjearv.aj/asra;x/ouns.rj/asrh:a/rdeoc b\ook-xsl/extensions/saxon653.jar:\ c-oxm .oircgl..aspaaxcohne..Sxtmyll.erSehseoeltve r\. tools.ResolvingXMLReader \ -y org.apache.xml.resolver.tools.ResolvingXMLReader \ -r org.apache.xml.resolver.tools.CatalogResolver \ -u \ -o myfile.html \ myfile.xml docbook.xsl I just followed it, can you please guide me any other books available in the market to learn about Saxon and FOP as a beginners like me? FYI: I have purchased Michael Key's XSLT 2.0 Book. In this also I don't found how to configure catalog option for saxon? http://www.dpawson.co.uk/docbook/catalogs.html may help you. regards -- regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Docbook XML and Catalog
On Fri, 12 Nov 2010 09:52:44 +0530 SriKrishnan srikrish...@techset.co.uk wrote: Hi Dave Pawson, I am frankly saying I don't know anything about Java, Saxon and FOP. Now only I am trying to learn these for the purpose of generating PDF from the XML source. atalog option for saxon? One more thing.You need to appreciate the difference between a uri resolver and a catalog resolver? the basics are: When an XML application wants to find a file called out from a stylesheet or referenced from an XML instance, it *can* if told to do so, use a URI resolver to carry out that action of retrieving the file. The resolver may (again, if told to do so) use the facilities of a catalog resolver to use in this process. ndw Norm Walsh wrote a paper on this, but it was hosted on Arbortext web site and seems to have been taken down. Anyone know where it might be found? I think this was the most clear exposition I've read. The catalog resolver asks the application (e.g. the Saxon XSLT engine) what URI it wants, and according to the rules of catalogs, uses the catalog file to change the sought URI into another form. E.g. the docbook v5 catalog has a line uri name=http://www.oasis-open.org/docbook/xml/5.0/rng/docbook.rng; uri=rng/docbook.rng/ which shows the 'translation' from a web address to a local file. HTH -- regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
