DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1332.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2995.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Guys,
The attached patch implements PDFRenderer.drawImageClipped() properly,
so the right-most and bottom-most images of a tiled image background are
now clipped, rather than being scaled or overrun. It also removes a bit
of System.out cruft I left in the previous image bg patch.
Can a
Thanks missed that one.
Maybe should fix that in the examples provided.
Claes
|-+
| | Jeremias Maerki |
| | jeremias.maerki@|
| | outline.ch |
| ||
| |
-Original Message-
From: Peter B. West [mailto:[EMAIL PROTECTED]]
Sent: May 2, 2002 11:26 PM
To: [EMAIL PROTECTED]
Subject: Re: [REDESIGN] Line layout manager discussion
Karen Lease wrote:
[ SNIP ]
For the record, I disagree with Arved's reading of Line-Building. I read
4.7.2,
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=508.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=515.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=516.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=626.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=635.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi devs,
I have attached a picture of how I think this process should work (in
principle not necessarily with actual areas or code).
The spec should say something like:
4.7.2
A block level formatting object which contains inline level formatting
objects that will create inline areas will
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=651.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=652.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=658.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=635.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi devs,
I have attached a picture of how I think this process should work (in
principle not necessarily with actual areas or code).
The spec should say something like:
4.7.2
A block level formatting object which contains inline level formatting
objects that will create inline areas will
Keiron,
Keiron Liddle wrote:
I'm almost thinking of going a step further.
Maybe we could add annotations to the spec to clarify these things
with our understanding and then present this information.
Yes indeed. And an index, including especially a concept index.
It seems to me that
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=808.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=836.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Arved,
My apologies. I was just taking the opportunity to think aloud about
aspects of the interaction between inline-areas and block-areas. Trying
to make sense of the various elements of the spec leaves your ears buzzing.
Peter
Arved Sandstrom wrote:
For the record, I disagree with
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=907.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8778.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8778.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
If there are still any examples left in the current distribution would
you please point out which? All examples should have been upgraded by
now. Are you sure you don't have any old files in your FOP directory?
On 03.05.2002 11:05:51 claes.bergsten wrote:
Thanks missed that one.
Maybe should
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=964.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8778.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8778.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8778.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8778.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1211.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1231.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=635.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1242.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
There are
docs/xml2pdf.xsl
docs/xml-docs/xml2pdf.xsl
in fop-0.20.2-maintain branch with master-name attribute in page-sequence
tag.
-Original Message-
From: Jeremias Maerki [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 03, 2002 5:48 PM
To: [EMAIL PROTECTED]
Subject: Re: Master reference
chrisg 02/05/03 10:51:24
Modified:.Tag: fop-0_20_2-maintain build.xml
Log:
replaced manifest-task with ant's builtin stuff
Revision ChangesPath
No revision
No revision
1.44.2.14 +17 -10xml-fop/build.xml
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8778.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8785.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
OK, so I ran the following XPATH on the spec
//div3[(@id = ./head/quote) and (.//table/tbody/tr[./td = 'Inherited:
']/td[(position() = 2) and (text() = 'yes')])]/head/quote
And got the following universally inheritable attributes which I will
add into my schema
font-family
Peter,
Here's my point of view on where line-breaking (perhaps including
hyphenation) happens.
The end result of layout is a sequence of nested areas. However while
layout is happening, line-breaking logic has to pretend that it's only
working on a flat row of characters and other inline leaf
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
Arved,
I'm definitely in favor of deciding how we think things are supposed to
be laid out. Of course it would be nice if we were on the same
wavelength with the majority of FO users and implementors... but I'm not
too worried about that.
Besides the stuff we're talking about currently, we need
Hi Keiron,
I think this is a good start. I especially like the illustration which
covers all aspects of the problem.
I have some suggestions for the proposed text (see below).
-Karen
Keiron Liddle wrote:
Hi devs,
I have attached a picture of how I think this process should work (in
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
Keiron et al.,
Just a quick reaction to this - I'm off to sit next to the footpath
reading the newspapers and drinking tea.
From what I see here you are changing the shape of the tree. The
motivation seems to be to make it explicit that block areas contained
within an inline area must
I'm not sure what the exact name of the PDF feature is, but does FOP
support, directly or indirectly, the PDF technique that allows the
end-user of the PDF to click a page area and type in form information?
I've seen this best done on an IRS Tax Form (1040EZ), but I don't know
if this is a
I have extensively-formatted, 1-4 page PDF Form documents that I would
like to insert text annotations, equivalent to user-side form filling,
but embedded directly in the original PDF.
Does FOP's API, or any combination of supporting tools, have the ability
to render/import a simple FO-PDF
I will be converting a few paper forms into FOP for rendering into PDF.
I'm prioritizing reliability of rendering, with precise static layout,
and compatibility/printing accuracy for the current versions of Adobe
Acrobat on Windows. These documents won't need to flow or be
layout-influenced by
Comments below.
-Original Message-
From: Peter B. West [mailto:[EMAIL PROTECTED]]
Sent: May 3, 2002 10:42 PM
To: [EMAIL PROTECTED]
Subject: Re: [REDESIGN] Line layout manager discussion
[ SNIP ]
From what I see here you are changing the shape of the tree. The
motivation seems
48 matches
Mail list logo
