Borders disappearing in PDF

2008-05-29 Thread Alexander Stamenov
Hello to all! I am having problems with the borders of some tables rendered using FOP 0.94 and 0.95beta. I saw a similar topic (msg08525) regarding AWT renderer. Some of the borders on particular tables are rendered kind of randomly on different zoom levels. What I have noticed is that this

Re: Borders disappearing in PDF

2008-05-29 Thread Jeremias Maerki
That's a known problem. See: http://markmail.org/message/6jm6gfbmlv7z So far nothing has happened in this direction. Nobody seems to have had a hard-enough itch to do the necessary experiments. Please send questions about FOP to the fop-users mailing list in the future. Thanks. On 29.05.2008

Re: ZapfDingbats and Symbol not found whereas they are not needed

2008-05-29 Thread Vincent Hennebert
Hi Max, Max Berger wrote: Andreas, indeed. To support proper character auto-selection I've modified the default to include the symbol and zapf-dingbats fonts, as they contain many characters normally not found in the default fonts. I hope I'll have time to continue this work soon (can't

Re: svn commit: r660998 - in /xmlgraphics/fop/trunk: src/java/org/apache/fop/fo/ src/java/org/apache/fop/fonts/ src/java/org/apache/fop/layoutmgr/inline/ test/layoutengine/standard-testcases/

2008-05-29 Thread Max Berger
Dear Fop-devs, Just some comments on this work: - it implements a word-by-word selection as the auto font-selection strategy. It will always pick the first font, which is able to display the most characters in a word. This behavior needs to be documented (I'll do that) - character-by-character

DO NOT REPLY [Bug 45097] New: Questionable white-space-treatment behavior

2008-05-29 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45097 Summary: Questionable white-space-treatment behavior Product: Fop Version: 1.0dev Platform: PC OS/Version: Windows Vista Status: NEW Severity: normal

DO NOT REPLY [Bug 45097] Questionable white-space-treatment behavior

2008-05-29 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45097 --- Comment #1 from Sean Griffin [EMAIL PROTECTED] 2008-05-29 08:04:11 PST --- Created an attachment (id=22030) -- (https://issues.apache.org/bugzilla/attachment.cgi?id=22030) PDF example without wrapping block -- Configure

DO NOT REPLY [Bug 45097] Questionable white-space-treatment behavior

2008-05-29 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45097 --- Comment #2 from Sean Griffin [EMAIL PROTECTED] 2008-05-29 08:04:29 PST --- Created an attachment (id=22031) -- (https://issues.apache.org/bugzilla/attachment.cgi?id=22031) FO markup for example with wrapping block -- Configure

DO NOT REPLY [Bug 45097] Questionable white-space-treatment behavior

2008-05-29 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45097 --- Comment #3 from Sean Griffin [EMAIL PROTECTED] 2008-05-29 08:04:45 PST --- Created an attachment (id=22032) -- (https://issues.apache.org/bugzilla/attachment.cgi?id=22032) PDF example without wrapping block -- Configure

DO NOT REPLY [Bug 45097] Questionable white-space-treatment behavior

2008-05-29 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45097 Sean Griffin [EMAIL PROTECTED] changed: What|Removed |Added Attachment #22032|PDF example without wrapping|PDF example with

DO NOT REPLY [Bug 45100] New: Fop 0. 95 beta release is not able to load an graphics file

2008-05-29 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45100 Summary: Fop 0.95 beta release is not able to load an graphics file Product: Fop Version: all Platform: PC OS/Version: Windows XP Status: ASSIGNED

try without catch in BlockStackingLM.getNextKnuthElements

2008-05-29 Thread Vincent Hennebert
Hi, Could anybody explain me what is the purpose of the following piece of code: if (!breakBeforeServed) { try { if (addKnuthElementsForBreakBefore(returnList, context)) { return returnList; } } finally { breakBeforeServed =

Re: ZapfDingbats and Symbol not found whereas they are not needed

2008-05-29 Thread Andreas Delmelle
On May 29, 2008, at 12:03, Vincent Hennebert wrote: Max Berger wrote: Andreas, indeed. To support proper character auto-selection I've modified the default to include the symbol and zapf-dingbats fonts, as they contain many characters normally not found in the default fonts. I hope I'll

Re: svn commit: r660998 - in /xmlgraphics/fop/trunk: src/java/org/apache/fop/fo/ src/java/org/apache/fop/fonts/ src/java/org/apache/fop/layoutmgr/inline/ test/layoutengine/standard-testcases/

2008-05-29 Thread Andreas Delmelle
On May 29, 2008, at 13:47, Max Berger wrote: Hi Max Just some comments on this work: - it implements a word-by-word selection as the auto font-selection strategy. It will always pick the first font, which is able to display the most characters in a word. This behavior needs to be documented

DO NOT REPLY [Bug 45097] Questionable white-space-treatment behavior

2008-05-29 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45097 Andreas L. Delmelle [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED

DO NOT REPLY [Bug 45100] Fop 0. 95 beta release is not able to load an graphics file

2008-05-29 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45100 Andreas L. Delmelle [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED

DO NOT REPLY [Bug 45097] Questionable white-space-treatment behavior

2008-05-29 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45097 Sean Griffin [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|NEEDINFO ---

DO NOT REPLY [Bug 45097] Questionable white-space-treatment behavior

2008-05-29 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45097 Sean Griffin [EMAIL PROTECTED] changed: What|Removed |Added Status|NEEDINFO|ASSIGNED ---

DO NOT REPLY [Bug 45097] Questionable white-space-treatment behavior

2008-05-29 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45097 --- Comment #8 from Sean Griffin [EMAIL PROTECTED] 2008-05-29 17:08:39 PST --- (In reply to comment #7) ...if the line-breaking algorithm has a choice of either breaking before or after a space, it will always break before it.