[prev in list] [next in list] [prev in thread] [next in thread]
List: xalan-dev
Subject: Re: What does popRTFContext() do?
From: keshlam () us ! ibm ! com
Date: 2011-06-20 12:51:13
Message-ID: OF91E34401.4D72036E-ON852578B5.00473492-852578B5.0047A144 () lotus ! com
[Download RAW message or body]
--=_alternative 0047A071852578B5_Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
> I would not use XML and XSLT for PDF document pagination.
> I instead use XSLT to convert XML into a LaTex markup language and then
> let the underlying troff/groff processors generate the actual content
for
> printing and publishing.
For what it's worth, something very similar to that was the original
intent for XSL -- use XSL Transformation (XSLT) to render the document's
content into the XSL Formatting Objects (XSL-FO) language, and then use an
XSL-FO processor to produce the actual on-screen or printed
representation.
Apache does have an XSL-FO implementation which can produce PDF output,
though it has been years since I tried using it:
http://xmlgraphics.apache.org/fop/
______________________________________
"You build world of steel and stone
I build worlds of words alone
Skilled tradespeople, long years taught:
You shape matter; I shape thought."
(http://www.songworm.com/lyrics/songworm-parody/ShapesofShadow.html)
From:
shathawa@e-z.net
To:
xalan-dev@xml.apache.org
Date:
06/17/2011 12:57 PM
Subject:
Re: What does popRTFContext() do?
Sebastian Leske,
I would not use XML and XSLT for PDF document pagination.
I instead use XSLT to convert XML into a LaTex markup language and then
let the underlying troff/groff processors generate the actual content for
printing and publishing. The XSLT stylesheets are customized to the
printing requirements for books, often using selected subsets of the
DOCBOOK XML standard. Therefore most XSLT processors suffice for my work.
The XSLT-to-LaTex stylesheets accommodate frontisepiece, copyright pages,
dedications, forewords, colophons, tables of contents, tables of tables,
tables of figures, sections, chapters, appendices, multi-page tables,
indexes, glossaries, footnotes, endnotes, references, and a wide array of
multi-pass document creation requirements including pagination,
hyphenation, computed headers, computed footers, floating illustrations,
and mathematical formulae creation.
I don't have a publicly releasable set of XSLT transformations, but this
is what the transformations accomplish using some structured XML as a
source.
- Steven J. Hathaway
> Hi,
>
> an internal project of ours uses Xalan to parse and convert XML files to
> reports in PDF format. We are having some trouble getting Xalan to do
> what we want, so I'd like to solicit advice.
>
> First, some background (sorry for so much text, I tried to make it
brief):
>
> The reports we produce have some very peculiar rules for pagination
> (placing of page breaks): Sometimes certain pairs of pages need to face
> each other, so empty pages must be inserted according to special rules,
> and sometimes paragraphs must be reordered to achieve this.
>
...
> Can anyone explain more about the internal workings of Xalan?
> Is our analysis correct?
> Are there any problems with disabling the above line?
> Are there any other pitfalls to be expected, or can we just continue
> working without popRTFContext()?
>
> Greetings,
>
> Sebastian Leske
>
> P.S. Sorry for not posting actual code. It's proprietary, and also a
> rather huge package, and I'm not sure how to simplify it, as the problem
> only occurs with large documents.
> I'll try to answer any specific questions by looking into the original
> code.
>
> --
> Sebastian Leske
> System- und Anwendungsentwicklung
> Tel: 0211/92495-146
>
> IOn AG
> http://www.ion.ag/
> Vorstand: Rudolf Franke, Erik Rehrmann, Manfred Siller
> Aufsichtsratsvorsitzender: Reinhard Möntmann
> Sitz der Gesellschaft: Erkrath
> Amtsgericht Wuppertal: HRB 14181
> USt Id-Nr.: DE 121642062
>
>
> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
--=_alternative 0047A071852578B5_Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
<font size=2 face="sans-serif">> </font><tt><font size=2>I would not
use XML and XSLT for PDF document pagination.</font></tt>
<br><tt><font size=2>> I instead use XSLT to convert XML into a LaTex
markup language and then<br>
> let the underlying troff/groff processors generate the actual content
for<br>
> printing and publishing.<br>
</font></tt><font size=2 face="sans-serif"><br>
For what it's worth, something very similar to that was the original intent
for XSL -- use XSL Transformation (XSLT) to render the document's content
into the XSL Formatting Objects (XSL-FO) language, and then use an XSL-FO
processor to produce the actual on-screen or printed representation.<br>
<br>
Apache does have an XSL-FO implementation which can produce PDF output,
though it has been years since I tried using it:<br>
</font><a href=http://xmlgraphics.apache.org/fop/><font size=2 \
face="sans-serif">http://xmlgraphics.apache.org/fop/</font></a> <br><font size=2 \
face="sans-serif"><br> <br>
______________________________________<br>
"You build world of steel and stone</font>
<br><font size=2 face="sans-serif">I build worlds of words alone</font>
<br><font size=2 face="sans-serif">Skilled tradespeople, long years taught:</font>
<br><font size=2 face="sans-serif">You shape matter; I shape thought."</font>
<br><font size=2 face="sans-serif">(</font><a \
href="http://www.songworm.com/lyrics/songworm-parody/ShapesofShadow.html"><font \
size=2 face="sans-serif">http://www.songworm.com/lyrics/songworm-parody/ShapesofShadow.html</font></a><font \
size=2 face="sans-serif">)</font> <br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">shathawa@e-z.net</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">xalan-dev@xml.apache.org</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">06/17/2011 12:57 PM</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">Re: What does popRTFContext() do?</font></table>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Sebastian Leske,<br>
<br>
I would not use XML and XSLT for PDF document pagination.<br>
<br>
I instead use XSLT to convert XML into a LaTex markup language and then<br>
let the underlying troff/groff processors generate the actual content for<br>
printing and publishing. The XSLT stylesheets are customized to the<br>
printing requirements for books, often using selected subsets of the<br>
DOCBOOK XML standard. Therefore most XSLT processors suffice for
my work.<br>
<br>
The XSLT-to-LaTex stylesheets accommodate frontisepiece, copyright pages,<br>
dedications, forewords, colophons, tables of contents, tables of tables,<br>
tables of figures, sections, chapters, appendices, multi-page tables,<br>
indexes, glossaries, footnotes, endnotes, references, and a wide array
of<br>
multi-pass document creation requirements including pagination,<br>
hyphenation, computed headers, computed footers, floating illustrations,<br>
and mathematical formulae creation.<br>
<br>
I don't have a publicly releasable set of XSLT transformations, but this<br>
is what the transformations accomplish using some structured XML as a<br>
source.<br>
<br>
- Steven J. Hathaway<br>
<br>
> Hi,<br>
><br>
> an internal project of ours uses Xalan to parse and convert XML files
to<br>
> reports in PDF format. We are having some trouble getting Xalan to
do<br>
> what we want, so I'd like to solicit advice.<br>
><br>
> First, some background (sorry for so much text, I tried to make it
brief):<br>
><br>
> The reports we produce have some very peculiar rules for pagination<br>
> (placing of page breaks): Sometimes certain pairs of pages need to
face<br>
> each other, so empty pages must be inserted according to special rules,<br>
> and sometimes paragraphs must be reordered to achieve this.<br>
><br>
...<br>
> Can anyone explain more about the internal workings of Xalan?<br>
> Is our analysis correct?<br>
> Are there any problems with disabling the above line?<br>
> Are there any other pitfalls to be expected, or can we just continue<br>
> working without popRTFContext()?<br>
><br>
> Greetings,<br>
><br>
> Sebastian Leske<br>
><br>
> P.S. Sorry for not posting actual code. It's proprietary, and also
a<br>
> rather huge package, and I'm not sure how to simplify it, as the problem<br>
> only occurs with large documents.<br>
> I'll try to answer any specific questions by looking into the original<br>
> code.<br>
><br>
> --<br>
> Sebastian Leske<br>
> System- und Anwendungsentwicklung<br>
> Tel: 0211/92495-146<br>
><br>
> IOn AG<br>
> </font></tt><a href=http://www.ion.ag/><tt><font \
size=2>http://www.ion.ag/</font></tt></a><tt><font size=2><br> > Vorstand: Rudolf \
Franke, Erik Rehrmann, Manfred Siller<br> > Aufsichtsratsvorsitzender: Reinhard \
Möntmann<br> > Sitz der Gesellschaft: Erkrath<br>
> Amtsgericht Wuppertal: HRB 14181<br>
> USt Id-Nr.: DE 121642062<br>
><br>
><br>
> ---------------------------------------------------------------------<br>
<br>
<br>
<br>
---------------------------------------------------------------------<br>
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org<br>
For additional commands, e-mail: xalan-dev-help@xml.apache.org<br>
<br>
</font></tt>
<br>
--=_alternative 0047A071852578B5_=--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic