DO NOT REPLY [Bug 43815] If Block Container doesn't have width/ height properties then strange effects can occur on layout of child elements

2008-05-06 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=43815


Chris Bowditch [EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution||FIXED




--- Comment #3 from Chris Bowditch [EMAIL PROTECTED]  2008-05-06 04:48:16 PST 
---
Thanks everyone - this bug is fixed!


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.


DO NOT REPLY [Bug 38264] Hyphenation does not play well with preserved linefeed-treatment or white-space-treatment

2008-05-06 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=38264





--- Comment #10 from Andreas L. Delmelle [EMAIL PROTECTED]  2008-05-06 
08:06:37 PST ---
Status update:

The main difficulty seems to be that the principal iteration in
LineLM.createLineBreaks() iterates in reverse order. As a result,
applyChanges() is called first for the last Paragraph if the TextLM generates
multiple paragraphs.
Now, while we can keep track of the changed position indices and limit both
applyChanges() and getChangedKnuthElements() to operate only on the portion
corresponding to oldList, by the time the next-to-last paragraph is processed,
the changed positions for the last one should again be modified to take into
account added/removed areas for the changes to the preceding one.

I made such changes locally, and this does avoid the duplication, however,
keeping track of the bounding indices is turning out to be quite a pain. As
soon as the first paragraph has hyphenation points, the positions pointing into
the later paragraphs will be wrong...


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.


Question about FOP 0.94 and 0.20.5

2008-05-06 Thread Juanjo Alejandro
I try to run in a seem application the two versions of fop 0.94 and
0.20.5.I rebuild version FOP 0.94 changing the names of folders
(org.apache.fop by
org.jcom.fop) and jars to let de ClassLoader upload both librarys. As a
result I get an error of type class not definition found for FopFactory and
another strange errors.
Is it posible to run both versions togheter?


Thanks In advance

Juanjo


Re: Question about FOP 0.94 and 0.20.5

2008-05-06 Thread Andreas Delmelle

On May 6, 2008, at 18:00, Juanjo Alejandro wrote:
I try to run in a seem application the two versions of fop 0.94 and  
0.20.5. I rebuild version FOP 0.94 changing the names of folders  
(org.apache.fop by org.jcom.fop) and jars to let de ClassLoader  
upload both librarys. As a result I get an error of type class not  
definition found for FopFactory and another strange errors.

Is it posible to run both versions togheter?


AFAIK, this will always cause trouble.
Both versions are not meant to work together inside the same VM, and  
definitely not when loaded by the same ClassLoader.


Anyways, modifying the sources to try to work around this limitation  
would be a bit too invasive for my taste.
A workaround you might consider is to set up a second container that  
hosts the old version. That one can then be phased out over time once  
you're certain that 0.94 suits your needs, and this is one sure way  
to keep both versions completely isolated from each other.



HTH!

Cheers

Andreas