DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36935.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Not sure if this is another of those areas in the spec which is cause
for much confusion but I noticed that FOP trunk collapses white space
across fo:inlines. For example (I use a . to represent a white space
character):
Start.fo:inline.Text./fo:inline.End
is rendered as:
Start.Text.End
What I write next should be consumed with caution and the fact in mind
that English is a foreign language to me, because I have big trouble
translating 4.2.4. 4.2.4 defines preceding WRT to the area tree, but I
really can't parse that section. OTOH, 7.15.12 talks about flow objects,
not areas,
Jeremias Maerki wrote:
I think I've just stumbled over a problem in the Knuth algorithm.
I'm going to see what happens ...
Regards
Luca
On Thu, 6 Oct 2005 03:44 pm, Jeremias Maerki wrote:
What I write next should be consumed with caution and the fact in
mind that English is a foreign language to me, because I have big
trouble translating 4.2.4. 4.2.4 defines preceding WRT to the area
tree, but I really can't parse that
On Fri, Sep 30, 2005 at 08:27:45AM +0100, Peter B. West wrote:
Jeremias Maerki wrote:
On 29.09.2005 11:58:57 Peter B. West wrote:
I can understand that some sponsors may be sensitive to divulging such
information, for at least two reasons. Firstly, the treat of being
inundated with
On Thu, 6 Oct 2005 05:14 pm, Jeremias Maerki wrote:
That helps a lot. Thanks for looking it up! Yes, Karen was a
Fopper, and a good one. Now, the only thing left is to fix the bug.
:-)
Its a bug in the inline part of FOP so its probably me or Luca in the
moment.
snip/
Jeremias Maerki
Thank you so much for looking into it. From the sound of it I would have
continued my search for a long time.
On 06.10.2005 11:42:19 Luca Furini wrote:
Luca Furini wrote:
I'm going to see what happens ...
I've found the bug!
The width, stretch and shrink of the suppressed elements
[Peter B. West]
...
That code was alt-design properties code. It seems to me that many of
the ideas and implementation details of alt-design are now sitting in
the FOP code base. This is true whether Finn ever looked at the
alt-design properties code. It ain't over yet.[1]
I did, before
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36952.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Fixing a bug reported by Jeremias affecting the handling of glue and
penalty elements after a break when the algorithm restarts.
Now it should be ok. A nasty little bug, anyway ...
Unfortunately, I had to duplicate a few lines (a for loop looking for glue
elements after a feasible break): the
Great! Thanks, Luca, it works fine.
On 06.10.2005 17:07:01 Luca Furini wrote:
Fixing a bug reported by Jeremias affecting the handling of glue and
penalty elements after a break when the algorithm restarts.
Now it should be ok. A nasty little bug, anyway ...
Unfortunately, I had to
Finn Bock wrote:
[Peter B. West]
...
That code was alt-design properties code. It seems to me that many of
the ideas and implementation details of alt-design are now sitting in
the FOP code base. This is true whether Finn ever looked at the
alt-design properties code. It ain't over
On Oct 6, 2005, at 1:30 AM, Peter B. West wrote:
I've been stewing on this for quite a while, and as you, at least,
seem to have missed the point, I'll vent.
Sorry to hear that you were stewing about this. I suspect it feels
better now that it's out in the open (although I'm not convinced
Manuel Mall wrote:
What we also need for proper script support is a mapping from Unicode
code point to script.
On a second thought: isn't this what Class Character.UnicodeBlock
does?
J.Pietschmann
Manuel Mall wrote:
Not sure if this is another of those areas in the spec which is cause
for much confusion but I noticed that FOP trunk collapses white space
across fo:inlines.
This isn't the correct behavior, as well as collapsing across
a changed text decoration. Unfortunately, this isn't
On Fri, 7 Oct 2005 03:30 am, J.Pietschmann wrote:
Manuel Mall wrote:
What we also need for proper script support is a mapping from
Unicode code point to script.
On a second thought: isn't this what Class Character.UnicodeBlock
does?
Joerg,
Thank you - I didn't even know that this class
17 matches
Mail list logo
