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=5221.
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=7147.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi Developers,
The current way that breaks are found with the layout managers has a
couple of problems.
Currently the information is contained in both the layout managers and
the break positions. This means that it must follow the order: get
breaks: add areas: get breaks etc. So columns are not
On Friday 15 November 2002 09:30, Keiron Liddle wrote:
. . .(does anyone even know what I am talking
about)
Not much on my side as the whole layout thing is still a mystery to me
(because I have no experience in computing layouts and never took
the time to study this part the code in detail).
On 15 Nov 2002 09:30:17 +0100 Keiron Liddle wrote:
So does that sound right. (does anyone even know what I am talking
about)
:-) It sounds reasonable from a very high point of view. I hope I will
soon be able to join this kind of discussion. From next week on I'll be
a free man for a few
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=13295.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On Fri, 2002-11-15 at 09:42, Bertrand Delacretaz wrote:
On Friday 15 November 2002 09:30, Keiron Liddle wrote:
. . .(does anyone even know what I am talking
about)
Not much on my side as the whole layout thing is still a mystery to me
(because I have no experience in computing layouts and
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=13866.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Devs,
I don't know how many of you committers are on the community and party
mailing lists. There was the idea to organize a meeting among Apache
committers next year in the german-speaking part of the world (Germany,
Austria and Switzerland). Christian, Keiron and I already registered.
Since a
copying this to forrest-dev for feeback.
Thanks :-)
Victor Mote wrote:
Keiron Liddle wrote:
I wouldn't recommend putting the dtd's in our cvs, one version is
better.
In principle I agree. I think the best solution is for Forrest to make them
available in a small download.
The are some
On Friday 15 November 2002 10:02, Jeremias Maerki wrote:
. . .There was the idea to organize a meeting among Apache
committers next year in the german-speaking part of the world
. . .
I might be interested too, depending on where and when. I am subscribed to
party@.
-Bertrand
The location and date is still TBD. It will probably be somewhere
between Munich and Frankfurt, I guess. The textfile to register is in
CVS module committers under docs/de-meeting/people.txt.
On Fri, 15 Nov 2002 10:22:23 +0100 Bertrand Delacretaz wrote:
On Friday 15 November 2002 10:02, Jeremias
keiron 2002/11/15 03:56:29
Modified:src/org/apache/fop/apps StructureHandler.java
src/org/apache/fop/datatypes LengthBase.java
src/org/apache/fop/fo FONode.java FOText.java FObj.java
FObjMixed.java RecursiveCharIterator.java
Comments below.
-Original Message-
From: Keiron Liddle [mailto:keiron;aftexsw.com]
Sent: Friday, November 15, 2002 3:30 AM
To: FOP
Subject: Getting breaks: revisited
The current way that breaks are found with the layout managers has a
couple of problems.
Currently the information is
Keiron Liddle wrote:
Hi Developers,
The current way that breaks are found with the layout managers has a
couple of problems.
Currently the information is contained in both the layout managers and
the break positions. This means that it must follow the order: get
breaks: add areas: get breaks
Jeremias,
Be sure to let me know when the Brisbane meeting is being arranged. I
think I'll be able to make it. In the meantime, have a beer for me.
Peter
Jeremias Maerki wrote:
The location and date is still TBD. It will probably be somewhere
between Munich and Frankfurt, I guess. The
Hi all,
I've worked out (and will submit via bugzilla) both
an explanation and a solution to the text measuring layout
problems that I reported recently in the awt and
awt/print renderers.
I believe it makes sense to add the changes to the maintenance
branch (in the event that there is ever an
Response below.
-Original Message-
From: Victor Mote [mailto:vic;outfitr.com]
Sent: Friday, November 15, 2002 1:48 PM
To: [EMAIL PROTECTED]
Subject: RE: Getting breaks: revisited
Just to be clear, I should point out that there is not a layout that is
impossible to perform. The standard
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=14606.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Rhett Aultman wrote:
Hm...and what about a fusion of the two. If the LMs submitted
potential breaks and some sort of information about the
constraint that has to be removed to use them, and this
information was held on to, then at some point down the line in
processing, FOP could rewind
Victor Mote wrote:
Just to be clear, I should point out that there is not a layout that is
impossible to perform. The standard allows (and would have to)
implementation-specific handling of what they call over-constrained
requirements. In other words, requirements can be prioritized and allowed
21 matches
Mail list logo
