[docbook-apps] [ANN] XMLmind XML Editor Customization Service
XMLmind XML Editor Customization Service XMLmind XML Editor (http://www.xmlmind.com/xmleditor/) is a highly extensible application. But what if you want to adapt it to your needs and cannot do it yourself or hire a consultant to do it for you? We now have an easy-to-purchase, affordable, solution to this problem: product XML Editor - Customization Service (reference xe-su). USD150/EUR125 buys you one hour of customization service. Explain us by email what you want and we'll tell you how much units of product xe-su you'll have to purchase. Once we receive your payment, we'll start working for you and after at most seven working days, you'll receive your customization packaged as an easy-to-install add-on. More information in http://www.xmlmind.com/xmleditor/customization_service.html - 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] Using DocBook Stylesheets and Java Heap Problems
Hi Bob, I changed the code like you proposed. Now I am facing problems with the PDF output. Every time a new page-sequence is started it is interpreted as first page which has a totally different layout than the odd and even pages. Furthermore all pages after the second page-sequence have a wrong indent by means of admoniations, examples and text rendering in the nirvana. Any solutions? Cheers, Tobias On Wed, May 6, 2009 at 12:37 AM, Bob Stayton b...@sagehill.net wrote: Hi, Yes, that is one workaround that should work in FOP. Two things need to happen. The template that matches article will generate a page-sequence, so the section content and any elements that come after sections (glossary, appendix) must be excluded from that page-sequence because you cannot nest page-sequences. Then you need to put each top level section and any elements after sections in in their own page-sequences. In the template with match=article in fo components.xsl, change: xsl:apply-templates/ near the end of the template to xsl:apply-templates select=*[not(self::section)][not(preceding-sibling::section)]/ That removes sections and any elements after sections from the article page-sequence. Then after the closing tag of the article page-sequence, add this: ... /fo:page-sequence xsl:for-each select=*[self::section or preceding-sibling::section] xsl:call-template name=page.sequence xsl:with-param name=content xsl:apply-templates select=./ /xsl:with-param /xsl:call-template /xsl:for-each /xsl:template This processes all the sections and elements that follow sections, each in their own page-sequence. Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: Tobias Anstett [k15t.com] tob...@k15t.com To: Bob Stayton b...@sagehill.net; docbook-apps docbook-apps@lists.oasis-open.org Sent: Tuesday, May 05, 2009 2:28 PM Subject: Re: [docbook-apps] Using DocBook Stylesheets and Java Heap Problems ... so one possible solution would be to close the existing fo:page-sequence and start a new one before every major section (1. 2. 3. ...). How could I do something like this? I must use fo:page-sequence and not break-after page, but you know best. Cheers, Tobias On Tue, May 5, 2009 at 6:23 PM, Tobias Anstett [k15t.com] tob...@k15t.com wrote: Hi Bob, I analyzed the problem by splitting the whole generation chain like you suggested. The problem occurs when the Apache FO processor does the transformation to PDF. After contacting the Apache FO mailinglist I know what my problem is, but not how to solve it. Adrian Cumiskey from the Apache FO mailinglist pointed out to check if I use many page sequences in the resulting FO document, because FOP processes documents by page sequence. Thus if I can section the document contents into lots of small page sequence segments this can help a lot with memory consumption. So I checked the generated FO documents (size from 300kb to 20mb) and noticed that there is really one single page sequence that wrapps all the content. = Thus my question is = is there a way to change this behaviour and how would it influence the look of my document? I am exporting in article style using a own page sequence master in the customization layer. Cheers, Tobias On Fri, May 1, 2009 at 7:40 PM, Bob Stayton b...@sagehill.net wrote: Hi, Are you using FOP to apply the XSL stylesheet as well as converting the XSL-FO to PDF? If so, you might try splitting those functions by first generating an FO file with Saxon or such, and then processing the FO file with FOP. That would at least tell you which step was having the problem. Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: Tobias Anstett [k15t.com] tob...@k15t.com To: docbook-apps docbook-apps@lists.oasis-open.org Sent: Friday, May 01, 2009 10:02 AM Subject: [docbook-apps] Using DocBook Stylesheets and Java Heap Problems Hi, we are using the DocBook stylesheets in combination with Apache FOP inside a web app. I already assigned more than 1024m to -Xms and -Xmx but some (large) DocBook to PDF conversions still cause Java Heap Exceptions. Is there a way to reduce the consumed memory ? Cheers, Tobias - 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 - 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] Re: [dblatex] With ulink, displaying the URL in the PDF output?
On Tue, Apr 28, 2009 at 03:49:06PM +0200, Michael Wiedmann m...@miwie.in-berlin.de wrote a message of 23 lines which said: An alternative might be use a 'type' attribute in the 'ulink' and customize the 'ulink' template in 'xref.xsl' to output the wanted code. That's finally what I did. I copied the templates from the distribution and modified them to display the URL. A bit complicated, I wish there would be an option for that but I'm too busy at this time to produce a proper patch for dblatex. I attached the customization script. Thanks for the tip. custom-afnic.xsl Description: XML document - 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] Using DocBook Stylesheets and Java Heap Problems
Hi,
The solution to the first-page problem is to define a new
page-sequence-master that has only 'odd' and 'even' pages, assign it a new
name, and use that name in the param named 'master-reference' when you call
the 'page.sequence' template:
xsl:call-template name=page.sequence
xsl:with-param name=master-referencesectionbody/xsl:with-param
etc.
The 'page.sequence' template accepts other params too ('content' was used
initially), and you can see those params in the template as it is defined in
fo/component.xsl.
Information about creating new page masters is described here:
http://www.sagehill.net/docbookxsl/PageDesign.html
I'm not sure what's going on with the second problem, as I did not see that
issue. Is your customization setting indents for body text? Can you
describe that problem in more detail?
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
- Original Message -
From: Tobias Anstett [k15t.com] tob...@k15t.com
To: Bob Stayton b...@sagehill.net
Cc: docbook-apps docbook-apps@lists.oasis-open.org
Sent: Wednesday, May 06, 2009 4:26 AM
Subject: Re: [docbook-apps] Using DocBook Stylesheets and Java Heap Problems
Hi Bob,
I changed the code like you proposed. Now I am facing problems with
the PDF output. Every time a new page-sequence is started it is
interpreted as first page which has a totally different layout than
the odd and even pages. Furthermore all pages after the second
page-sequence have a wrong indent by means of admoniations, examples
and text rendering in the nirvana.
Any solutions?
Cheers,
Tobias
On Wed, May 6, 2009 at 12:37 AM, Bob Stayton b...@sagehill.net wrote:
Hi,
Yes, that is one workaround that should work in FOP.
Two things need to happen. The template that matches article will generate
a page-sequence, so the section content and any elements that come after
sections (glossary, appendix) must be excluded from that page-sequence
because you cannot nest page-sequences. Then you need to put each top
level
section and any elements after sections in in their own page-sequences.
In the template with match=article in fo components.xsl, change:
xsl:apply-templates/
near the end of the template to
xsl:apply-templates
select=*[not(self::section)][not(preceding-sibling::section)]/
That removes sections and any elements after sections from the article
page-sequence.
Then after the closing tag of the article page-sequence, add this:
...
/fo:page-sequence
xsl:for-each select=*[self::section or preceding-sibling::section]
xsl:call-template name=page.sequence
xsl:with-param name=content
xsl:apply-templates select=./
/xsl:with-param
/xsl:call-template
/xsl:for-each
/xsl:template
This processes all the sections and elements that follow sections, each in
their own page-sequence.
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
- Original Message - From: Tobias Anstett [k15t.com]
tob...@k15t.com
To: Bob Stayton b...@sagehill.net; docbook-apps
docbook-apps@lists.oasis-open.org
Sent: Tuesday, May 05, 2009 2:28 PM
Subject: Re: [docbook-apps] Using DocBook Stylesheets and Java Heap
Problems
...
so one possible solution would be to close the existing
fo:page-sequence and start a new one before every major section (1. 2.
3. ...). How could I do something like this? I must use
fo:page-sequence and not break-after page, but you know best.
Cheers,
Tobias
On Tue, May 5, 2009 at 6:23 PM, Tobias Anstett [k15t.com]
tob...@k15t.com wrote:
Hi Bob,
I analyzed the problem by splitting the whole generation chain like
you suggested.
The problem occurs when the Apache FO processor does the
transformation to PDF. After contacting the Apache FO mailinglist I
know what my problem is, but not how to solve it.
Adrian Cumiskey from the Apache FO mailinglist pointed out to check if
I use many page sequences in the resulting FO document, because FOP
processes documents by page sequence. Thus if I can section the
document contents into lots of small page sequence segments this can
help a lot with memory consumption.
So I checked the generated FO documents (size from 300kb to 20mb) and
noticed that there is really one single page sequence that wrapps all
the content.
= Thus my question is = is there a way to change this behaviour and
how would it influence the look of my document?
I am exporting in article style using a own page sequence master in
the customization layer.
Cheers,
Tobias
On Fri, May 1, 2009 at 7:40 PM, Bob Stayton b...@sagehill.net wrote:
Hi,
Are you using FOP to apply the XSL stylesheet as well as converting the
XSL-FO to PDF? If so, you might try splitting those functions by first
generating an FO file with Saxon or such, and then processing the FO
file
with FOP. That would at least tell you which step was having the
problem.
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
- Original Message - From: Tobias Anstett [k15t.com]
tob...@k15t.com
To: docbook-apps docbook-apps@lists.oasis-open.org
Sent: Friday, May 01,
Re: [docbook-apps] Using DocBook Stylesheets and Java Heap Problems
Hi Bob,
my own pagemaster only modifies the first page, thus I set the
xsl:with-param name=master-reference to body-odd. Now everything
is working like a charm :) After adding this modification the indent
is correctly rendered again.
I guess there is some customization that caused something like indent
+= indent when the same pagemaster is used or the first page is
rendered. Have to check this...
Thank you so much for your excellent help,
Cheers,
Tobias
On Wed, May 6, 2009 at 6:10 PM, Bob Stayton b...@sagehill.net wrote:
Hi,
The solution to the first-page problem is to define a new
page-sequence-master that has only 'odd' and 'even' pages, assign it a new
name, and use that name in the param named 'master-reference' when you call
the 'page.sequence' template:
xsl:call-template name=page.sequence
xsl:with-param name=master-referencesectionbody/xsl:with-param
etc.
The 'page.sequence' template accepts other params too ('content' was used
initially), and you can see those params in the template as it is defined in
fo/component.xsl.
Information about creating new page masters is described here:
http://www.sagehill.net/docbookxsl/PageDesign.html
I'm not sure what's going on with the second problem, as I did not see that
issue. Is your customization setting indents for body text? Can you
describe that problem in more detail?
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
- Original Message - From: Tobias Anstett [k15t.com]
tob...@k15t.com
To: Bob Stayton b...@sagehill.net
Cc: docbook-apps docbook-apps@lists.oasis-open.org
Sent: Wednesday, May 06, 2009 4:26 AM
Subject: Re: [docbook-apps] Using DocBook Stylesheets and Java Heap Problems
Hi Bob,
I changed the code like you proposed. Now I am facing problems with
the PDF output. Every time a new page-sequence is started it is
interpreted as first page which has a totally different layout than
the odd and even pages. Furthermore all pages after the second
page-sequence have a wrong indent by means of admoniations, examples
and text rendering in the nirvana.
Any solutions?
Cheers,
Tobias
On Wed, May 6, 2009 at 12:37 AM, Bob Stayton b...@sagehill.net wrote:
Hi,
Yes, that is one workaround that should work in FOP.
Two things need to happen. The template that matches article will generate
a page-sequence, so the section content and any elements that come after
sections (glossary, appendix) must be excluded from that page-sequence
because you cannot nest page-sequences. Then you need to put each top
level
section and any elements after sections in in their own page-sequences.
In the template with match=article in fo components.xsl, change:
xsl:apply-templates/
near the end of the template to
xsl:apply-templates
select=*[not(self::section)][not(preceding-sibling::section)]/
That removes sections and any elements after sections from the article
page-sequence.
Then after the closing tag of the article page-sequence, add this:
...
/fo:page-sequence
xsl:for-each select=*[self::section or preceding-sibling::section]
xsl:call-template name=page.sequence
xsl:with-param name=content
xsl:apply-templates select=./
/xsl:with-param
/xsl:call-template
/xsl:for-each
/xsl:template
This processes all the sections and elements that follow sections, each in
their own page-sequence.
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
- Original Message - From: Tobias Anstett [k15t.com]
tob...@k15t.com
To: Bob Stayton b...@sagehill.net; docbook-apps
docbook-apps@lists.oasis-open.org
Sent: Tuesday, May 05, 2009 2:28 PM
Subject: Re: [docbook-apps] Using DocBook Stylesheets and Java Heap
Problems
...
so one possible solution would be to close the existing
fo:page-sequence and start a new one before every major section (1. 2.
3. ...). How could I do something like this? I must use
fo:page-sequence and not break-after page, but you know best.
Cheers,
Tobias
On Tue, May 5, 2009 at 6:23 PM, Tobias Anstett [k15t.com]
tob...@k15t.com wrote:
Hi Bob,
I analyzed the problem by splitting the whole generation chain like
you suggested.
The problem occurs when the Apache FO processor does the
transformation to PDF. After contacting the Apache FO mailinglist I
know what my problem is, but not how to solve it.
Adrian Cumiskey from the Apache FO mailinglist pointed out to check if
I use many page sequences in the resulting FO document, because FOP
processes documents by page sequence. Thus if I can section the
document contents into lots of small page sequence segments this can
help a lot with memory consumption.
So I checked the generated FO documents (size from 300kb to 20mb) and
noticed that there is really one single page sequence that wrapps all
the content.
= Thus my question is = is there a way to change this behaviour and
how would it influence the look of my document?
I am exporting in article style using a own page sequence master in
[docbook-apps] ANNOUNCE: DocBook XSL and XSL-NS 1.75.0 released
Version 1.75.0 of the DocBook XSL XSL-NS Stylesheets, for processing DocBook 4 and namespaced (DocBook 5) documents, is now available: http://docbook.sf.net/files/xsl/latest The release notes are included below, and also available online. The reference docs are available as a separate package, and online. http://docbook.sf.net/files/xsl-doc/latest Release Notes: 1.75.0 The following is a list of changes that have been made since the 1.74.3 release. Gentext The following changes have been made to the gentext code since the 1.74.3 release. ● Robert Stayton: locale/sv.xml; locale/ja.xml; locale/pl.xml Check in translations of Legalnotice submitted on mailing list. ● Robert Stayton: locale/es.xml Fix spelling errors in Acknowledgements entries. ● Robert Stayton: locale/es.xml Check in translations for 4 elements submitted through docbook-apps message of 14 April 2009. ● David Cramer: locale/zh.xml; locale/ca.xml; locale/ru.xml; locale/ga.xml; locale/gl.xml; l⋯ Internationalized punctuation in glosssee and glossseealso ● Robert Stayton: Makefile Check in fixes for DSSSL gentext targets from submitted patch #1689633. ● Robert Stayton: locale/uk.xml Check in major update submitted with bug report #2008524. ● Robert Stayton: locale/zh_tw.xml Check in fix to Note string submitted in bug #2441051. ● Robert Stayton: locale/ru.xml Checkin typo fix submitted in bug #2453406. Common The following changes have been made to the common code since the 1.74.3 release. ● Robert Stayton: gentext.xsl Fix extra generated space when xrefstyle includes 'nopage'. ● Robert Stayton: table.xsl Add support for some format properties on tables using HTML table markup. These include: - frame attribute on table (or uses $default.table.frame parameter). - rules attribute on table (or uses $default.table.rules parameter). - align attribute on td and th - valign attribute on td and th - colspan on td and th - rowspan on td and th - bgcolor on td and th ● Robert Stayton: olink.xsl Add placeholder template to massage olink hot text to make customization easier, per Feature Request 1828608. ● Robert Stayton: targets.xsl Add support for collecting olink targets from a glossary generated from a glossary.collection. ● Robert Stayton: titles.xsl Handle firstterm like glossterm in mode=title.markup. ● Robert Stayton: titles.xsl Add match on info/title in title.markup templates where missing. ● Mauritz Jeanson: titles.xsl Changed ancestor::title to (ancestor::title and (@id or @xml:id)). This enables proper formatting of inline elements in titles in TOCs, as long as these inlines don't have id or xml:id attributes. ● Robert Stayton: labels.xsl Add two new qanda.defaultlabel values so that numbered sections and numbered questions can be distinguished. Satisfies Feature Request #1539045. ● Robert Stayton: stripns.xsl; pi.xsl Convert function-available(exsl:node-set) to use the new param so Xalan bug is isolated. ● Mauritz Jeanson: titles.xsl Added fixes for bugs #2112656 and #1759205: 1. Reverted mistaken commits r7485 and r7523. 2. Updated the template with match=link and mode=no.anchor.mode so that @endterm is used if it exists and if the link has no content. ● Mauritz Jeanson: titles.xsl Added code to handle acknowledgements in book and part. The element is processed similarly to dedication. All acknowledgements will appear as front matter, after any dedications. ● Robert Stayton: olink.xsl Fix bug #2018717 use.local.olink.style uses wrong gentext context. ● Robert Stayton: olink.xsl Fix bug #1787167 incorrect hot text for some olinks. ● Robert Stayton: common.xsl Fix bug #1669654 Broken output if copyright year contains a range. ● Robert Stayton: labels.xsl Fix bug in labelling figure inside appendix inside article inside book. FO The following changes have been made to the fo code since the 1.74.3 release. ● Jirka Kosek: highlight.xsl Inclusion of highlighting code was simplified. Only one import is now necessary. ● Robert Stayton: fop1.xsl Add the new fop extensions namespace declaration, in case FOP extension functions are used. ● Robert Stayton: formal.xsl Add support for pgwide on informal objects. ● Robert Stayton: docbook.xsl Fixed spurious closing quote on line 134. ● Robert Stayton: docbook.xsl; autoidx-kosek.xsl; autoidx.xsl Convert function-available for node-set() to use new $exsl.node.set.available param in test. ● David Cramer: xref.xsl Backed out previous change. Bob had already fixed it the right way in gentext.xsl. ● David Cramer: xref.xsl Suppress extra space after xref when xrefstyle='select: label nopage' (#2740472) ● Mauritz Jeanson: pi.xsl Fixed doc bug
