You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by Steve Ebersole <st...@hibernate.org> on 2007/09/21 19:13:33 UTC
0.93/0.94 and tables
I have some DocBook sources I have been rendering via fop-0.20.5. On attempts
to upgrade to either 0.93 or 0.94, however, some of my tables render "goofy".
In particular, two phenomena I have noted:
1) Tables that span a page break. These get rendered "off page".
2) Quite a few of the tables are of the term/definition variety. Some of them
reference java class names (FQN), and as such represent long, unbroken text.
In a lot of cases, that causes horizontal "bleeding" of the left/right cells.
Is there perhaps some settings introduced after 0.20.5 I am missing that might
cause this behavior?
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Oct 3, 2007, at 21:53, Steve Ebersole wrote:
> <snip />
> I know you are not trying to, but at some point you switched to
> speaking a
> language I do not understand ;)
>
> But I did a search.
Good thinking. :-)
> Is something this what you mean?
> http://sourceware.org/ml/docbook-apps/2004-q1/msg00232.html
Indeed. That should work fine here.
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Steve Ebersole <st...@gmail.com>.
On Wednesday 03 October 2007 02:47:04 pm Andreas L Delmelle wrote:
> On Oct 3, 2007, at 03:53, Steve Ebersole wrote:
>
> [Me:]
>
> >> Well, in the meantime, I did end up copy/pasting the entire
> >> configuration.xml into the location of the xi:include node, fiddled
> >> some more, and I see the problem now. Starting from Table 1.3 onward,
> >> correct?
> >
> > Correct
>
> OK, managed to trim it down. For the interested parties, the FO in
> attach reproduces the issue.
>
> It's caused by the keep-together on the table's containing block.
> Remove that property and the table gets rendered very nicely. Would
> look even slightly better with a keep-together on the rows, I think.
Awesome! Thank you so much.
I know you are not trying to, but at some point you switched to speaking a
language I do not understand ;)
But I did a search. Is something this what you mean?
http://sourceware.org/ml/docbook-apps/2004-q1/msg00232.html
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Oct 4, 2007, at 18:46, Andreas L Delmelle wrote:
> <snip />
> That, unfortunately, I can't help you with. Maybe there is some
> parameter you can set in Docbook that would take care of this, but
> my experience with Docbook is rather limited, so I wouldn't know if
> there is such a parameter and what it's called...
>
> Your options:
> a) Wait for some Docbook-user or -guru to chime in here (may take a
> long time)
> b) Forward the question to docbook-apps@oasis (much more probable
> that someone will be able to help you out there)
This just occurred to me after posting the above:
Doesn't Docbook have stylesheets that are tailored for use with FOP
(and an accompanying parameter to indicate that these stylesheets
should be used)? If so, then it could be that this is the preferred
solution. I seem to remember from last night that the generated FO
contained a lot of references to RX and AntennaHouse's extension
namespace, so maybe...?
Long shot, though; as I said: limited experience with Docbook, over
here =(
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Oct 3, 2007, at 21:55, Steve Ebersole wrote:
Hi Steve
> On Wednesday 03 October 2007 02:47:04 pm Andreas L Delmelle wrote:
>> <snip />
>> It's caused by the keep-together on the table's containing block.
>> Remove that property and the table gets rendered very nicely. Would
>> look even slightly better with a keep-together on the rows, I think.
>
> Also, I do not set the keep-together on the table's containing
> block (I don't
> think so anyway), so how would I remove it?
That, unfortunately, I can't help you with. Maybe there is some
parameter you can set in Docbook that would take care of this, but my
experience with Docbook is rather limited, so I wouldn't know if
there is such a parameter and what it's called...
Your options:
a) Wait for some Docbook-user or -guru to chime in here (may take a
long time)
b) Forward the question to docbook-apps@oasis (much more probable
that someone will be able to help you out there)
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Steve Ebersole <st...@hibernate.org>.
On Wednesday 03 October 2007 02:47:04 pm Andreas L Delmelle wrote:
> On Oct 3, 2007, at 03:53, Steve Ebersole wrote:
>
> [Me:]
>
> >> Well, in the meantime, I did end up copy/pasting the entire
> >> configuration.xml into the location of the xi:include node, fiddled
> >> some more, and I see the problem now. Starting from Table 1.3 onward,
> >> correct?
> >
> > Correct
>
> OK, managed to trim it down. For the interested parties, the FO in
> attach reproduces the issue.
>
> It's caused by the keep-together on the table's containing block.
> Remove that property and the table gets rendered very nicely. Would
> look even slightly better with a keep-together on the rows, I think.
Also, I do not set the keep-together on the table's containing block (I don't
think so anyway), so how would I remove it?
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Oct 3, 2007, at 03:53, Steve Ebersole wrote:
[Me:]
>> Well, in the meantime, I did end up copy/pasting the entire
>> configuration.xml into the location of the xi:include node, fiddled
>> some more, and I see the problem now. Starting from Table 1.3 onward,
>> correct?
>>
> Correct
>
>
OK, managed to trim it down. For the interested parties, the FO in
attach reproduces the issue.
It's caused by the keep-together on the table's containing block.
Remove that property and the table gets rendered very nicely. Would
look even slightly better with a keep-together on the rows, I think.
Re: 0.93/0.94 and tables
Posted by Steve Ebersole <st...@gmail.com>.
> Well, in the meantime, I did end up copy/pasting the entire
> configuration.xml into the location of the xi:include node, fiddled
> some more, and I see the problem now. Starting from Table 1.3 onward,
> correct?
Correct
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Oct 2, 2007, at 21:26, Steve Ebersole wrote:
> <snip />
> The other issue is a problem I believe. There is only one
> XInclude, which is
> needed as it is what contains all the table definitions. I assume
> it is a
> problem resolving the needed chapter on your system. Not sure why
> though.
> This should be a relative resolution.
Aha, relative paths. Should've thought of that...
Well, in the meantime, I did end up copy/pasting the entire
configuration.xml into the location of the xi:include node, fiddled
some more, and I see the problem now. Starting from Table 1.3 onward,
correct?
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Steve Ebersole <st...@gmail.com>.
On Tuesday 02 October 2007 01:37:27 pm Andreas L Delmelle wrote:
> On Oct 2, 2007, at 19:31, Steve Ebersole wrote:
>
> Hi Steve,
>
> > Attached is the simplified docbook and xslt.
> >
> > Thanks for taking a look.
>
> No problem, although...
>
> I've tried to run the XSLT-step separately, and received a couple of
> warnings/errors, like:
>
> WARNING: javax.xml.transform.TransformerException: Making portrait
> pages on A4 paper (210mmx297mm)
> Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning
> WARNING: javax.xml.transform.TransformerException: ERROR: xref
> linking to tutorial has no generated link text.
> Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning
> WARNING: javax.xml.transform.TransformerException: Error: no ID for
> constraint linkend: tutorial.
> Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning
> WARNING: javax.xml.transform.TransformerException: XLink to
> nonexistent id: tutorial
> Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning
> WARNING: javax.xml.transform.TransformerException: ERROR: xref
> linking to architecture has no generated link text.
> Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning
> WARNING: javax.xml.transform.TransformerException: Error: no ID for
> constraint linkend: architecture.
> Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning
> WARNING: javax.xml.transform.TransformerException: XLink to
> nonexistent id: architecture
> Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning
> WARNING: javax.xml.transform.TransformerException: xi:include
> encountered in book, but no template matches.
>
> Could this be a consequence of the simplification?
The xlink warnings are (I assume) the link references in the master.xml; they
reference linkends no longer in the document because I stripped out the
needed XIncludes.
The other issue is a problem I believe. There is only one XInclude, which is
needed as it is what contains all the table definitions. I assume it is a
problem resolving the needed chapter on your system. Not sure why though.
This should be a relative resolution.
> Regardless of these errors, I end up with a valid FO document, but
> running this through FOP afterwards, gives me an error:
>
> java.lang.IllegalStateException:
> Flow 'xsl-region-body' does not map to the region-body in page-master
> 'blank'. FOP presently does not support this.
I would have to assume that this is caused by the issue with the XInclude.
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Oct 2, 2007, at 20:37, Andreas L Delmelle wrote:
<snip />
Forgot to add: the driving stylesheet used was pdf/main-pdf.xsl.
Using common/basic.xsl did produce the XML header, but no root node
(= a plain-text file).
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Oct 2, 2007, at 19:31, Steve Ebersole wrote:
Hi Steve,
> Attached is the simplified docbook and xslt.
>
> Thanks for taking a look.
No problem, although...
I've tried to run the XSLT-step separately, and received a couple of
warnings/errors, like:
WARNING: javax.xml.transform.TransformerException: Making portrait
pages on A4 paper (210mmx297mm)
Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning
WARNING: javax.xml.transform.TransformerException: ERROR: xref
linking to tutorial has no generated link text.
Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning
WARNING: javax.xml.transform.TransformerException: Error: no ID for
constraint linkend: tutorial.
Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning
WARNING: javax.xml.transform.TransformerException: XLink to
nonexistent id: tutorial
Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning
WARNING: javax.xml.transform.TransformerException: ERROR: xref
linking to architecture has no generated link text.
Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning
WARNING: javax.xml.transform.TransformerException: Error: no ID for
constraint linkend: architecture.
Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning
WARNING: javax.xml.transform.TransformerException: XLink to
nonexistent id: architecture
Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning
WARNING: javax.xml.transform.TransformerException: xi:include
encountered in book, but no template matches.
Could this be a consequence of the simplification?
Regardless of these errors, I end up with a valid FO document, but
running this through FOP afterwards, gives me an error:
java.lang.IllegalStateException:
Flow 'xsl-region-body' does not map to the region-body in page-master
'blank'. FOP presently does not support this.
...
Seems I can't really reproduce your problem in this way. :/
Anyone?
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Steve Ebersole <st...@gmail.com>.
Attached is the simplified docbook and xslt.
Thanks for taking a look.
On Thursday 27 September 2007 04:07:16 pm Andreas L Delmelle wrote:
> On Sep 27, 2007, at 15:58, Steve Ebersole wrote:
> > It's not all that easy. I am building the docs via the Maven plugin
> > for DocBook handing that I developed as part of migrating Hibernate
> > over to Maven.
> >
> > In addition to my basic lack of understanding of DocBook, FOP,
> > XSLT, etc I am also a noob at Maven, so of course I am the perfect
> > person to write such functionality ;) But seriously, I just learned
> > what I needed about each as I went along; so, unfortunately, at at
> > this point I have no idea how to "run FOP with the '-foout'
> > parameter". But if you tell me (or point me to resources) how to do
> > that I have no issue with doing that. (note that because I am using
> > maven as the infastructure I do not have fop properly 'installed').
>
> OK, as I indicated, it's not really a problem to send us the XML
> +XSLT, if you want.
>
> In a 'regular' FOP installation, you would navigate to the FOP-
> directory, and then run something like:
>
> fop -xml source.xml -xsl style.xsl -foout foresult.fo
>
> whereas for a rendering to PDF, the same command-line would be
>
> fop -xml source.xml -xsl style.xsl -pdf pdfresult.pdf
>
>
>
> I'm not sure what steps you follow currently (as I have never used
> Maven myself; that's something you know better ;-))
>
> Cheers
>
> Andreas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Sep 27, 2007, at 15:58, Steve Ebersole wrote:
> It's not all that easy. I am building the docs via the Maven plugin
> for DocBook handing that I developed as part of migrating Hibernate
> over to Maven.
>
> In addition to my basic lack of understanding of DocBook, FOP,
> XSLT, etc I am also a noob at Maven, so of course I am the perfect
> person to write such functionality ;) But seriously, I just learned
> what I needed about each as I went along; so, unfortunately, at at
> this point I have no idea how to "run FOP with the '-foout'
> parameter". But if you tell me (or point me to resources) how to do
> that I have no issue with doing that. (note that because I am using
> maven as the infastructure I do not have fop properly 'installed').
OK, as I indicated, it's not really a problem to send us the XML
+XSLT, if you want.
In a 'regular' FOP installation, you would navigate to the FOP-
directory, and then run something like:
fop -xml source.xml -xsl style.xsl -foout foresult.fo
whereas for a rendering to PDF, the same command-line would be
fop -xml source.xml -xsl style.xsl -pdf pdfresult.pdf
I'm not sure what steps you follow currently (as I have never used
Maven myself; that's something you know better ;-))
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Steve Ebersole <st...@gmail.com>.
It's not all that easy. I am building the docs via the Maven plugin for DocBook handing that I developed as part of migrating Hibernate over to Maven.
In addition to my basic lack of understanding of DocBook, FOP, XSLT, etc I am also a noob at Maven, so of course I am the perfect person to write such functionality ;) But seriously, I just learned what I needed about each as I went along; so, unfortunately, at at this point I have no idea how to "run FOP with the '-foout' parameter". But if you tell me (or point me to resources) how to do that I have no issue with doing that. (note that because I am using maven as the infastructure I do not have fop properly 'installed').
On Wednesday 26 September 2007 01:19:56 pm Andreas L Delmelle wrote:
> On Sep 26, 2007, at 04:17, Steve Ebersole wrote:
>
> Hi
>
> >> Can you please provide a small FO sample showing the problem? Not the
> >> source DocBook file (or, at least, not only), but the result of
> >> the XSLT
> >> transformation.
> >
> > I do not write an intermediate FO file.
>
> Good! As a general rule, nobody really should, unless for debugging
> purposes.
>
> > But I can get you a slimmed source and XSLT. Will that suffice?
>
> Although it isn't that much effort for us, I consider everyone on the
> team to be a good programmer (and hence, as the saying goes, also a /
> lazy/ programmer ;-))
>
> Seriously, minimal source XML+XSL is fine with me in this case, but
> if you want to spare us the effort and run FOP with the '-foout'
> parameter yourself, that is always much appreciated. The reasoning is
> that the XSL transform actually has nothing to do with FOP. In your
> particular case, the issue is definitely not in the XSLT, so we do
> not run the risk of running the same document with a different XSLT
> processor.
>
> >>> 2) Quite a few of the tables are of the term/definition variety.
> >>> Some of
> >>> them reference java class names (FQN), and as such represent long,
> >>> unbroken text. In a lot of cases, that causes horizontal
> >>> "bleeding" of
> >>> the left/right cells.
> >>
> >> If you want to keep your class names unbroken, then I’m afraid you’re
> >> stuck. Otherwise you may add zero-width spaces (u+200B) after the
> >> dots
> >> or soft hyphens (u+00AD) inside class/package names to have your
> >> class
> >> name broken over several lines.
> >
> > I'll just introduce a convention to shorten the 'domain portion' of
> > the
> > package name (i.e. org.hibernate.dialect.HSQLDialect ->
> > o.h.dialect.HSQLDialect)
>
> If that works for you, all the better, but I would take care: this
> does not really solve the issue if the packages are nested deeper
> than three levels, does it?
>
>
> Cheers
>
> Andreas
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Sep 26, 2007, at 04:17, Steve Ebersole wrote:
Hi
>>
>> Can you please provide a small FO sample showing the problem? Not the
>> source DocBook file (or, at least, not only), but the result of
>> the XSLT
>> transformation.
> I do not write an intermediate FO file.
Good! As a general rule, nobody really should, unless for debugging
purposes.
> But I can get you a slimmed source and XSLT. Will that suffice?
Although it isn't that much effort for us, I consider everyone on the
team to be a good programmer (and hence, as the saying goes, also a /
lazy/ programmer ;-))
Seriously, minimal source XML+XSL is fine with me in this case, but
if you want to spare us the effort and run FOP with the '-foout'
parameter yourself, that is always much appreciated. The reasoning is
that the XSL transform actually has nothing to do with FOP. In your
particular case, the issue is definitely not in the XSLT, so we do
not run the risk of running the same document with a different XSLT
processor.
>>> 2) Quite a few of the tables are of the term/definition variety.
>>> Some of
>>> them reference java class names (FQN), and as such represent long,
>>> unbroken text. In a lot of cases, that causes horizontal
>>> "bleeding" of
>>> the left/right cells.
>>
>> If you want to keep your class names unbroken, then I’m afraid you’re
>> stuck. Otherwise you may add zero-width spaces (u+200B) after the
>> dots
>> or soft hyphens (u+00AD) inside class/package names to have your
>> class
>> name broken over several lines.
> I'll just introduce a convention to shorten the 'domain portion' of
> the
> package name (i.e. org.hibernate.dialect.HSQLDialect ->
> o.h.dialect.HSQLDialect)
If that works for you, all the better, but I would take care: this
does not really solve the issue if the packages are nested deeper
than three levels, does it?
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Steve Ebersole <st...@hibernate.org>.
On Monday 24 September 2007 02:05:02 am Vincent Hennebert wrote:
> Hi Steve,
>
> Steve Ebersole a écrit :
> > I have some DocBook sources I have been rendering via fop-0.20.5. On
> > attempts to upgrade to either 0.93 or 0.94,
>
> Very good idea! ;-)
>
> > however, some of my tables render "goofy". In particular, two
> >phenomena I have noted:
> >
> > 1) Tables that span a page break. These get rendered "off page".
>
> Can you please provide a small FO sample showing the problem? Not the
> source DocBook file (or, at least, not only), but the result of the XSLT
> transformation.
I do not write an intermediate FO file. But I can get you a slimmed source
and XSLT. Will that suffice?
> > 2) Quite a few of the tables are of the term/definition variety. Some of
> > them reference java class names (FQN), and as such represent long,
> > unbroken text. In a lot of cases, that causes horizontal "bleeding" of
> > the left/right cells.
>
> If you want to keep your class names unbroken, then I’m afraid you’re
> stuck. Otherwise you may add zero-width spaces (u+200B) after the dots
> or soft hyphens (u+00AD) inside class/package names to have your class
> name broken over several lines.
I'll just introduce a convention to shorten the 'domain portion' of the
package name (i.e. org.hibernate.dialect.HSQLDialect ->
o.h.dialect.HSQLDialect)
> > Is there perhaps some settings introduced after 0.20.5 I am missing
> > that might cause this behavior?
>
> What’s sure is that FOP 0.94 better follows the Recommendation than
> 0.20.5. The result you got with the old version was perhaps not to be
> expected. But we will better be able to figure out once you provide
> a example.
>
> HTH,
> Vincent
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Steve Ebersole <st...@gmail.com>.
On Monday 24 September 2007 02:05:02 am Vincent Hennebert wrote:
> Hi Steve,
>
> Steve Ebersole a écrit :
> > I have some DocBook sources I have been rendering via fop-0.20.5. On
> > attempts to upgrade to either 0.93 or 0.94,
>
> Very good idea! ;-)
>
> > however, some of my tables render "goofy". In particular, two
> >phenomena I have noted:
> >
> > 1) Tables that span a page break. These get rendered "off page".
>
> Can you please provide a small FO sample showing the problem? Not the
> source DocBook file (or, at least, not only), but the result of the XSLT
> transformation.
I do not write an intermediate FO file. But I can get you a slimmed source
and XSLT. Will that suffice?
> > 2) Quite a few of the tables are of the term/definition variety. Some of
> > them reference java class names (FQN), and as such represent long,
> > unbroken text. In a lot of cases, that causes horizontal "bleeding" of
> > the left/right cells.
>
> If you want to keep your class names unbroken, then I’m afraid you’re
> stuck. Otherwise you may add zero-width spaces (u+200B) after the dots
> or soft hyphens (u+00AD) inside class/package names to have your class
> name broken over several lines.
I'll just introduce a convention to shorten the 'domain portion' of the
package name (i.e. org.hibernate.dialect.HSQLDialect ->
o.h.dialect.HSQLDialect). That should cover the majority of the cases.
> > Is there perhaps some settings introduced after 0.20.5 I am missing
> > that might cause this behavior?
>
> What’s sure is that FOP 0.94 better follows the Recommendation than
> 0.20.5. The result you got with the old version was perhaps not to be
> expected. But we will better be able to figure out once you provide
> a example.
>
> HTH,
> Vincent
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: 0.93/0.94 and tables
Posted by Vincent Hennebert <vi...@anyware-tech.com>.
Hi Steve,
Steve Ebersole a écrit :
> I have some DocBook sources I have been rendering via fop-0.20.5. On attempts
> to upgrade to either 0.93 or 0.94,
Very good idea! ;-)
> however, some of my tables render "goofy". In particular, two
>phenomena I have noted:
>
> 1) Tables that span a page break. These get rendered "off page".
Can you please provide a small FO sample showing the problem? Not the
source DocBook file (or, at least, not only), but the result of the XSLT
transformation.
> 2) Quite a few of the tables are of the term/definition variety. Some of them
> reference java class names (FQN), and as such represent long, unbroken text.
> In a lot of cases, that causes horizontal "bleeding" of the left/right cells.
If you want to keep your class names unbroken, then I’m afraid you’re
stuck. Otherwise you may add zero-width spaces (u+200B) after the dots
or soft hyphens (u+00AD) inside class/package names to have your class
name broken over several lines.
> Is there perhaps some settings introduced after 0.20.5 I am missing
> that might cause this behavior?
What’s sure is that FOP 0.94 better follows the Recommendation than
0.20.5. The result you got with the old version was perhaps not to be
expected. But we will better be able to figure out once you provide
a example.
HTH,
Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org