Andreas L. Delmelle wrote:
fop.fo.flow.Table
line 157:CommonBackground bProps = propMgr.getBackgroundProps();
line 193:this.BackgroundColor =
this.propertyList.get(PR_BACKGROUND_COLOR).getColorType();
I thought porpertyList had been retired in HEAD?
How should I see this? Is one of the
-Original Message-
From: J.Pietschmann [mailto:[EMAIL PROTECTED]
I thought porpertyList had been retired in HEAD?
That's what I initially thought, but got a bit confused...
Shouldn't the latter be rewritten as :
this.BackgroundColor = bProps.backColor
I'd think
[J.Pietschmann]
I thought porpertyList had been retired in HEAD?
PropertyListBuilder was recently removed from HEAD.
[Andreas L. Delmelle]
How should I see this? Is one of the two superfluous? Do they complement
each other? Shouldn't the latter be rewritten as :
this.BackgroundColor =
Please fix it whenever you get write access.
Glen
--- Andreas L. Delmelle [EMAIL PROTECTED]
wrote:
Shouldn't the latter be rewritten as :
this.BackgroundColor = bProps.backColor
I'd think so.
__
Do you Yahoo!?
Yahoo! Hotjobs: Enter the
On Mon, 2003-12-01 at 02:45, Glen Mazza wrote:
--- John Austin [EMAIL PROTECTED] wrote:
The property strings are given to the Property
object
constructor by some path beginning with a SAX
parser.
It is reasonable to assume that the SAX parser loses
refs to most of these strings and
Input: The XSL-FO file produced from:
DocBook: The Definitive Guide
Document size: 648 Pages // for the O'Reilly edition
FO file size: 21,659,370 bytes
Properties: 526,648
Tags: 285,223
Height of tree: 17 // max height of the parse tree
Unique
--- John Austin [EMAIL PROTECTED] wrote:
The property strings are given to the Property
object
constructor by some path beginning with a SAX
parser.
It is reasonable to assume that the SAX parser loses
refs to most of these strings and that the Property
implementation retains the only
John Austin wrote:
In the interest of contributing (instead of just
trashing) to the proposed implementation, I wrote
a simple Perl script to get some counts out of a
real-world XSL-FO file.
Input: The XSL-FO file produced from a DocBook file
I have left from a dormant project. The perl program
Darn, racall the last post.
John Austin wrote:
Note that storing the property name and value refs supplied
to the Property constructor will use 45,620 strings. If the
Property implementation employs canonical mapping to ensure
that only one copy of each unique string is stored, then just
over
On Sat, 2003-11-29 at 16:35, J.Pietschmann wrote:
Darn, racall the last post.
John Austin wrote:
Note that storing the property name and value refs supplied
to the Property constructor will use 45,620 strings. If the
Property implementation employs canonical mapping to ensure
that only
Ing. Atilio Ranzuglia Buteler wrote:
i'm looking for information about the following:
- is the any way in securing a pdf document. to prohibit
that a user selects and copies the text?
- can the printer be selected from the pdf document?
I doubt this has something to do with fop, look for
the thing is that i'm producing the pdf document with fop,
otherwise i'll be looking for information about the pdf
specification
--- Oleg Tkachenko [EMAIL PROTECTED] wrote:
Ing. Atilio Ranzuglia Buteler wrote:
i'm looking for information about the following:
- is the any way in securing
Ing. Atilio Ranzuglia Buteler wrote:
the thing is that i'm producing the pdf document with fop,
otherwise i'll be looking for information about the pdf
specification
fop cannot accomplish what you want, but you can postprocess generated pdf by
some pdf-oriented library (iText is the most
Not really. As a fairly interested party, I must admit that mentions of
throwing it out and starting over don't leave me totally indifferent,
but I've got little enough time as it is for FOP these days, and I'm
trying not to let myself be distracted.
In any case, we all know that it's never right
Karen,
I was your opinion that I was most concerned about on this one. I, for
one, am quite happy to hold off to give you more time to make an
argument. Part of my point was that it *was* in pretty good shape the
first time around.
Peter
Karen Lease wrote:
Not really. As a fairly
Hello devs.
Does the near-silence on this one signify consent?
Peter
Keiron Liddle wrote:
Hi Peter and others,
What is the status of property handling?
Are we going to go with Peter's suggestion and commit the java source
to cvs and work on handling properties fully from there?
On Wednesday 01 May 2002 18:19, Peter B. West wrote:
Does the near-silence on this one signify consent?
I don't know enough about this to give meaningful advice, so in my case yes,
silence means consent.
- Bertrand
-
To
Bertrand Delacretaz wrote:
On Wednesday 01 May 2002 18:19, Peter B. West wrote:
Does the near-silence on this one signify consent?
I don't know enough about this to give meaningful advice, so in my case yes,
silence means consent.
Yes, it ought to be a reasonable idea.
J.Pietschmann
What is the status of property handling?
Are we going to go with Peter's suggestion and commit the java source to
cvs and work on handling properties fully from there?
+1.
As this is a section largely separate from the layout then it is a good
area to work on independantly. After all,
On 2002.01.02 15:10 Peter B. West wrote:
Keiron,
Thanks for clueing me up on the documentation. I strongly accept you
recommendation, and I will gladly use it in future. Btw, the heading
graphics from the the design documents seem to have been screwed up.
Have you noticed this?
Yes,
Hi Peter,
Thanks for the work. Maybe this can go with the rest of the design.
I would strongly suggest that you do not write the html.
The apache web site is done from xml and all the images, layout etc. is
done from a stylesheet. These will also be updated by others.
If you look at
Bernard,
Thanks for that. I have just had a long day trying to make the html at
least readable under Navigator 4.75. Isn't html wonderful?
I have also tried the current Opera 5.0 release on linux, with
reasonable results. The problem with using CSS is that the actual font
sizes on a
On Saturday 29 December 2001 02:57, Peter B. West wrote:
. . .let me know if there is some easy way to get full
conformance with the Apache XML norm, or if there are severe problems
viewing these pages with modern browsers.
Hi Peter,
FYI, with Konqueror (modern yes, 100% finished maybe not),
On Thu, 12 Jul 2001 22:50:44 Karen Lease wrote:
A few quick thoughts...
That was probably just my XML super-ego thinking that case-by-case
checks were a _bad_ thing... But on the other hand, as Arved points out,
the complexity of the model would make it rather problematic. It's
certainly
At 11:21 AM 7/13/01 +0200, Keiron Liddle wrote:
On Thu, 12 Jul 2001 22:50:44 Karen Lease wrote:
We also need to think about what to do when we encounter this kind of
case. Obviously we want to inform the user. We could either stop on an
exception or just ignore the offending FO and keep
A few quick thoughts...
That was probably just my XML super-ego thinking that case-by-case
checks were a _bad_ thing... But on the other hand, as Arved points out,
the complexity of the model would make it rather problematic. It's
certainly more important to focus on detecting cases which FOP
Keiron Liddle wrote:
Then after that I will see about handling the element child constraints (I
haven't worked out how this should be done yet, any ideas) and doing a
similar thing (to be impl.) with the rest of the elements that we don't
have yet.
For things like tables, I had
27 matches
Mail list logo
