Just speculating, but have you tried putting the page-number element inside
a variable?
i.e.:
xsl:variable name=currentpagefo:page-number//xsl:variable
Then xsl:value-of select=$currentpage * 2/, etc...
I haven't tried this, but it's just what pops into my head...
-David
At 08:44 AM 3/30/2002
I've been occassionally getting this error:
[ERROR]: Page subsequences exhausted. Using previous subsequence.
I haven't really nailed down what causes it - it's happened with both very
large and very small input XML. It doesn't seem to affect the output.
I was just wondering what this means?
I have a sinking feeling another xalan/xerces combination is somewhere in
my classpath.
The problem? I don't have a classpath env. variable set.
I wonder where that list of places the 1.4JVM looks for classes on
win32 is?
On Thu, 14 Mar 2002, Peter Jacobs wrote:
Strange, the difference was
That's interesting that it made a difference for you. On our XML/XSL, it
didn't make much difference - maybe it shaved 1-2 seconds of a 60 second
rendering.
-David
On Wed, 13 Mar 2002, Peter Jacobs wrote:
Are you using the included Xalan and Xerces.jar? I replaced them with Xalan
2.2 and
I've been making pretty big PDFs with a similar system and can share a few
off-the-cuff comments.
It's obvious to me that the structure of your fo document - sequences,
page layout, flows, etc - can make a significant difference in memory
usage and speed. However, I don't have enough concrete
I'm afraid I have extensive experience scripting MS Word. It's not
something I like to talk about much, but sometimes the painful memories do
surface...
I think the RTF idea is a good one, because it will help you avoid having
anything to do with programming Word. But let's just say you wanted to
I'm actually using the PDF renderer. I've got the source and am hunting
around now. If I have anything to say about it, this bug isn't going to
last until Friday.
Of course, anyone with knowledge of PDFRenderer who would like to comment
on this bug is more than welcome... No answer to my post on
head about what was going on
inside the renderer, but I won't bore the crowd with speculation. At any
rate, problem solved. :)
Thanks for your responses Jeremias.
-David
On Tue, 26 Feb 2002, David Wood wrote:
I'm actually using the PDF renderer. I've got the source and am hunting
around now
No, I don't think so. The Multiple Master Font Extensions have not been
implemented, yet.
Hmm. I have to assume PDF is capable of carrying both the PFB and the MMM;
So let me guess: assuming the weight-axis data is in the MMM file, FOP
needs to revise it's PFMReader to extrapolate metrics for
I have a bunch of justified text. If I use
fo:inline font-style=italic.../fo:inline
I get inconsistent and random-seeming gaps on either end of the inline
block. These are often large and ugly and are impossible to miss.
On every line where italics occur, the right margin is exceeded, as
though
On Sat, 23 Feb 2002, Carlos wrote:
While it is cumbersome and I would prefer not to, I can make an extra step
and unescape the the tags before FOP sees the XML; then I can use the
template to convert them into blocks and recover my paragraph breaks.
One solution would be to use another
I should be more specific - what I mean is; I would like to try to get
keep-with-next/previous working with fo:block elements.
On Wed, 30 Jan 2002, David Wood wrote:
I am a Java coder and know my way around the standard. I volunteer to try
to fix this, if someone who is more familiar
In the interests of being typographically correct, I'm attempting to use
oriented double and single quotes, ellipses, etc... These are typically
referenced in HTML as ldquo; rdquo; (amp;ldquo; amp;rdquo;) and so
on... however, FOP is informing me these entities are not declared.
I would be
On Wed, 16 Jan 2002, Robert C. Leif, Ph.D. wrote:
I don't think a lengthy Java v. Ada conversation going on in this list
would do much for the state of FOP as we know it, either
Too late, here we go... :)
-David
The tutorial that is available on FOA's website should clear most things
up. The upper-right window is where you'll be accessing your XML; you use
the open button on that window to open your file.
If you have not read through the FOA tutorial, I recommend that you do;
the program was
15 matches
Mail list logo
