should be
added) of the table should change.
Decimal separator-based tab stops would also be nice in this same use
case, but the critical need is automatic table layout.
--
Jess Holle
One other bit of feedback:
Few other pieces of software appear to use Avalon. It's not a big deal,
but using JCL might be a bit more consistent with other libraries folk
are using (i.e. within a server environment).
Jess Holle wrote:
I noticed 0.90 and the request for feedback.
J
if any browsers obey it...) and was assuming FOP
should have something at least that clear and useful.
--
Jess Holle
yet :-) but I suspect
several people like myself have written various workarounds in XSLT
which could be
posted on a wiki page or in a FAQ somewhere. Just a thought...
I haven't had the time or energy to do anything more elaborate than
generate equal table column widths.
--
Jess Holle
As I said, this is not nearly so important as automatic table layout,
but it is a very important feature for tables of numeric (e.g.
financial, inventory, or scientific) data -- whether or not the table is
layed out automatically.
--
Jess Holle
Jeremias Maerki wrote:
Hey, you're
;font' related
stuff...). In addition, although it is very powerful, we are still
finding a few bugs with each release.
I'd still *really* like to see automatic table layout in 1.0...
Decimal cell alignment would also be nice, but is not as critical by a
long shot.
--
Jess Holle
in alignment to a decimal separation character.]
--
Jess Holle
gerhard oettl wrote:
I always found the compliance page of the documentation a
excelent help when to decide who is to blame: fop or me. What i
am missing is the status of the xsl-funtions [from-parent(),
etc].
If there is no object
, but that is now a somewhat cyclical
situation...
--
Jess Holle
Jeremias Maerki wrote:
Jess, we'll be happy to help you get started if you'd like to work on
these missing features.
On 05.01.2006 12:49:32 Jess Holle wrote:
This page does clearly document the two biggest re
s stable for simple cases" :-)
--
Jess Holle
Jeremias Maerki wrote:
As part of my upcoming optimization work I want to finalize the FOP API.
I've written down a proposal in the Wiki:
http://wiki.apache.org/xmlgraphics-fop/ApiDesign
If possible, I'd like to have that finished by the en
hate to have a whole
lot more of such code to do the same thing. [Note the 0.20.5 code is
just slightly longer so 0.91 is a good step in this respect.]
--
Jess Holle
Jeremias Maerki wrote:
Noted, but the fact that the API is not stable has been documented in [1].
We've been pushing finalizing
implement it myself...
--
Jess Holle
le,
of course, as my code is all using reflection as I have to support
0.20.5 until something 0.9x or later is actually officially marked as
stable -- and for a bit thereafter for other 0.20.5 usages to be altered
to be 0.9x API compliant.]
--
Jess Holle
Is there any sort of time table for a non-alpha/beta 0.9x or 1.0 release?
--
Jess Holle
.20.5 --
whatever's present. I don't want to step "up" to 0.93 and discover
memory usage for things that used to work in 0.20.5 is many times higher
or such, though...
--
Jess Holle
I had thought/hoped 0.93 supported table-layout="auto" as I know there
was a GSOC project along these lines, yet I note that the compliance
table does not indicate such support.
Is the table in error? If not, how far off is such support?
--
Jess Holle
As always, we value your input and feedback."
So I suppose auto table-layout is still out of the question? [That's
what I most want.]
--
Jess Holle
Manuel Mall wrote:
On Saturday 14 July 2007 23:37, Jess Holle wrote:
Andreas L Delmelle wrote:
On Jul 13, 2007, at 21:16, Andreas L Delmelle wrote:
On Jul 13, 2007, at 15:45, Vincent Hennebert wrote:
As always, we value your input and feedback."
I can't speak for the broader market but for my usages anything prior to
Java 5 is "dead wood" and of no interest.
As of October of this year anything prior to Java 5 will be officially
unsupported by Sun except where you have a paid support contract with
them (including that for Solaris). Ad
Max Berger wrote:
Jess Holle schrieb:
As of October of this year anything prior to Java 5 will be officially
unsupported by Sun except where you have a paid support contract with
them (including that for Solaris). Add to that the fact that Java 1.4
is so limiting for so many things and Java
Peter B. West wrote:
Jess Holle wrote:
Java 5 runs on HPUX and AIX machines as well -- as well as on Solaris
x86. When you've got Windows, Mac OS X, x86 Linux, Solaris, HPUX,
and AIX covered, I'd say that's pretty good. The other platforms
are, er, odd balls.
The question
Path were flakey as could be
for "real world" XPaths (giving incorrect results in many critical
cases) and didn't have JAXP compliant XPath APIs last I investigated.
XSLT is simpler -- Saxon currently rules. XSLT 1.0 is too limiting to
justify continued use of Xalan.
--
Je
[
https://issues.apache.org/jira/browse/FOP-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612020#comment-14612020
]
Jess Holle commented on FOP-2495:
-
I have to concur with the original complaint here --
22 matches
Mail list logo
