AW: AW: [docbook-apps] Centered table cells

:-) Thanks Ben Von: Kallauch, Benjamin (EEIN/5) Gesendet: Freitag, 5. Februar 2016 08:57 An: Docbook Betreff: AW: AW: [docbook-apps] Centered table cells Hi Bob, dear all you say, the block inside the cell may reset the text-align attribute. This is indeed the case in my fo-export. Here is a cod

AW: AW: [docbook-apps] Centered table cells

gliche Nachricht- Von: Bob Stayton [mailto:b...@sagehill.net] Gesendet: Donnerstag, 4. Februar 2016 18:18 An: Kallauch, Benjamin (EEIN/5); Docbook Betreff: Re: AW: [docbook-apps] Centered table cells The text-align property is an inherited property in FO, so setting it on the cell should

AW: [docbook-apps] Centered table cells

Dear Ron, it's about centering only the content/text within a single or more cells. regards, Ben -Ursprüngliche Nachricht- Von: Ron Catterall [mailto:r...@catterall.net] Gesendet: Donnerstag, 4. Februar 2016 16:01 An: Kallauch, Benjamin (EEIN/5); Docbook Betreff: Re: [docbook

[docbook-apps] Centered table cells

Dear community I encountered a problem using XSL --> FO where I can't get centered table cells (horizontally). In my opinion the cause is in a false fo-structure, where the 'text-align' attribute is set in the fo:table-cell element rather than in the fo:block child element. The problem is mayb

AW: [docbook-apps] Tools to make DocBook easier

Dear all, in the past few months I established a small and ordinary tool chain with XMLSpy, XSLT and FOP. Setting up the tool chain (on Windows) was not too hard, although I had also some difficulties. But at the "end" I wouldn't call this a torture. I customized pretty much in the XSL-Styleshe

AW: [docbook-apps] should become in another book

Hi Richard, I've read your post and it looks like you're using the xpointer() scheme, right? Unfortunately, my tool chain with Xalan and Xerces does not support that scheme as described in the FAQ on the Xerces-Website by Apache. Rather it says Xerces supports the element() scheme. But this see

AW: [docbook-apps] Default for scale factor for images

Hi Lars, I’d suggest the following (which holds at least for the FO formatting): First, insert (thus: create) an XSL parameter in your customization layer: Second, modify the image.scale template to acknowledge the parameter: 0 1.0

[docbook-apps] line breaks / hyphenation in tables

Dear folks, I faced an issue with hyphenation in table cells. We automatically export strings from a database, that cannot be matched by the FOP hyphenation. I use the precompiled JAR made available through OFFO. The strings in the table cells are kind of: "v_x_yy_z" with under

AW: [docbook-apps] Bibliography in DocBook5, continued problems

Hi Niels, Despite using a totally different software setup, I made also some tests. There is maybe one hint: If I was renaming the referenced bibliography file (so the system could not find it anymore), I got the same error message: file:///foo/docbook-xsl-1.78.1/fo/biblio.xsl; Zeilennummer234;

AW: [docbook-apps] Listings placeable at the End of Printed Output?

é, I regrettably must say that all of this here is a complete waste of time for me and the next thing, I shall do is to unsubscribe from this - in my view - useless mailing list. Best regards Kai Von: Kallauch, Benjamin (EEIN) [mailto:benjamin.kallau...@volkswagen.de] Gesendet: Mittwoch, 22. Apr

AW: [docbook-apps] Listings placeable at the End of Printed Output?

lved ID reference "app_a" found." which is "WARNING: Page 3: Unresolved ID reference "d61e2804" found." otherwise, when not specifying an 'id' attribute value. Kai Von: Kallauch, Benjamin (EEIN) [mailto:benjamin.kallau...@volkswagen.de] Gesendet:

AW: [docbook-apps] Listings placeable at the End of Printed Output?

the American style printing LOTs at the beginning of the document. :-) Regards, Ben Von: Kallauch, Benjamin (EEIN) Gesendet: Montag, 20. April 2015 17:24 An: docbook-apps@lists.oasis-open.org Betreff: AW: [docbook-apps] Listings placeable at the End of Printed Output? Kai, I checked the example

AW: [docbook-apps] Listings placeable at the End of Printed Output?

Kai, I checked the example as well, using Xalan/FOP1.1 and DB4.5. Everything is fine, and I received the LOTs within my appendix at the end of the document. Maybe some ideas: - Check if you had an appendix element with a role attribute filled with 'lot'. - Check your templat

AW: [docbook-apps] Using imageobject twice on title page fails (FO)

Fantastic, this works fine. Still it's not easy for me to wrap my head around all the modes in DocBook XSL. Thanks, Ben -Ursprüngliche Nachricht- Von: Bob Stayton [mailto:b...@sagehill.net] Gesendet: Freitag, 17. April 2015 20:56 An: Kallauch, Benjamin (EEIN); docbook-apps@lists.

AW: [docbook-apps] AW: Graphical admonition in FO: Alignment?

FOP 1.1. regards, Ben -Ursprüngliche Nachricht- Von: Bob Stayton [mailto:b...@sagehill.net] Gesendet: Freitag, 17. April 2015 18:36 An: Kallauch, Benjamin (EEIN); docbook-apps@lists.oasis-open.org Betreff: Re: [docbook-apps] AW: Graphical admonition in FO: Alignment? Hi, The way I

[docbook-apps] AW: Graphical admonition in FO: Alignment?

Any suggestions, how I can control the behavior? Maybe leave out the element, because a block will already be rendered due to apply-templates? best regards, Ben Von: Kallauch, Benjamin (EEIN) Gesendet: Donnerstag, 16. April 2015 11:25 An: docbook-apps@lists.oasis-open.org Betreff: [docbook

[docbook-apps] Graphical admonition in FO: Alignment?

Dear all, I have some difficulties to understand how to align the List Item Graphic with the first text line in the list body. In my example (attachment) the list body seems to be aligned with the top of the graphic (the graphic has actually no surrounding white space around). The background co

[docbook-apps] Solution: Page numbers not aligned in TOC

Dear group! I noticed a fuzzy looking TOC some time ago with my FO-results from FOP 1.1 and DocBook-XSL 1.78.1. The page numbers seemed to be "misaligned" slightly. They ought to be aligned on the right side, but they were not. The reason for that lies in the "toc.line" named template in fo/au

AW: [docbook-apps] Problems with bibliography

Hi Niels, sure about the xml Namespace at your id? Try once without it. In my case I never use the xml:id notation with my bibliorefs, but if I did I ran into the same conflict as you did: id was not found. regards, Ben -Ursprüngliche Nachricht- Von: Niels Müller [mailto:neinalw...@gmai

AW: [docbook-apps] Edge case with dbfo-need

I ran your example xml with my combination of Xalan-J-2.7.1 and FOP 1.1. No problems there. The vertical space between the first para and admonition and the second respectively ist absolutely the same. The processing instruction was definitely recognized by the system, I changed the height value

AW: [docbook-apps] Getting a list of XInclude'd files

Hi Dean, I think you need to instruct your parser not to resolve the xincludes. I use Xalan with Xerces instead of xsltproc as processor. But in your case, isn't it sufficient to switch off your -xinclude option before parsing? Then you could easily trace your elements by any suitable template