Any update on the following issues?

["Tibbetts, Jeffery A NGIC " <fr...@ngic.army.mil>]

Hello all, I am a new poster.  I have reveiwed the mail list and I would
like to know if there are any updates or workarounds to the following issues
or if resolution is planned with the redesign to version 1.0.  I checked out
the slides from the WIKI site on the convention but I don't believe these
issues were covered there.

A little bit about my configuration before I start,  we are running apache,
cocoon and fop, dynamically rendering static xml to html/xhtml (in a couple
of varieties) and pdf.  I work from the publishing (content) perspective, I
maintain and modify our XSLT and XSL-FO stylesheets and provide them to our
development team (systems-based web maintenance).

Issues:

1.  The auto setting on tables.  We frequently get errors (that cause fop
and cocoon to hang) if we set explicit widths on our columns in the XML
source file.  So we have taken to providing no widths and letting FOP figure
it out.  This works for the most part if I have a fixed width table.  Some
of our users want me to accommodate centering and smaller width tables,
which requires some method for figuring what the overall width should be.  I
read the post from Jbryant on the 21st of Sep that provided a workaround -
but we are not running XSLT 2.0 yet, so that option is out for now.  Any
other suggestions?

2. The Link rendering area inside tables.  We disabled links in our PDF's
due to this offset problem.  Any suggestions?

Re: Any update on the following issues?

[Jeremias Maerki <de...@jeremias-maerki.ch>]

Suggestions on 1: We need to find someone who wants to implement auto
table layout. I believe it's going to be easier with the new layout
engine but still there is some work to be done. Until then, the known
work-arounds apply.

Suggestions on 2: None really. I don't think the bug still exists in FOP
Trunk but if it does we will want to be be quick in fixing it.

And a general comment: Since you're running Cocoon I need to make sure
you know that the FOP API has changed and that the FOP Cocoon Block
hasn't been adapted to the new API, yet. That's something that is going
to be done after the first preview release. Or sooner if someone other
than me is going to do it. :-)

On 11.10.2005 15:37:34 Tibbetts, Jeffery A NGIC wrote:
> Hello all, I am a new poster.  I have reveiwed the mail list and I would
> like to know if there are any updates or workarounds to the following issues
> or if resolution is planned with the redesign to version 1.0.  I checked out
> the slides from the WIKI site on the convention but I don't believe these
> issues were covered there.
> 
> A little bit about my configuration before I start,  we are running apache,
> cocoon and fop, dynamically rendering static xml to html/xhtml (in a couple
> of varieties) and pdf.  I work from the publishing (content) perspective, I
> maintain and modify our XSLT and XSL-FO stylesheets and provide them to our
> development team (systems-based web maintenance).
> 
> Issues:
> 
> 1.  The auto setting on tables.  We frequently get errors (that cause fop
> and cocoon to hang) if we set explicit widths on our columns in the XML
> source file.  So we have taken to providing no widths and letting FOP figure
> it out.  This works for the most part if I have a fixed width table.  Some
> of our users want me to accommodate centering and smaller width tables,
> which requires some method for figuring what the overall width should be.  I
> read the post from Jbryant on the 21st of Sep that provided a workaround -
> but we are not running XSLT 2.0 yet, so that option is out for now.  Any
> other suggestions?
> 
> 2. The Link rendering area inside tables.  We disabled links in our PDF's
> due to this offset problem.  Any suggestions?



Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org

Re: Any update on the following issues?

[JB...@s-s-t.com]

> I read the post from Jbryant on the 21st of Sep that provided
> a workaround - but we are not running XSLT 2.0 yet, so that
> option is out for now.

Anything (well, almost) that can be done in 2.0 can be done in 1.0. It 
just takes more arcane weirdness and tends to be much more verbose. If you 
can create representative samples of the kind of input you have to process 
and the kind of output your users want, I can try to help you create a 1.0 
solution to it. Those kinds of questions are also welcome at the Mulberry 
XSL list, to which you can subscribe from this page:
http://www.mulberrytech.com/xsl/xsl-list/

Jay Bryant
Bryant Communication Services
(presently consulting at Synergistic Solution Technologies)

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org