Manuel Mall | 1 Oct 2005 11:09
Picon

Re: svn commit: r292942 - /xmlgraphics/fop/trunk/build.xml

Simon,

I thought the whole hyphenation build was suppose to be removed from the 
trunk?

Manuel
On Sat, 1 Oct 2005 05:07 pm, spepping <at> apache.org wrote:
> Author: spepping
> Date: Sat Oct  1 02:07:10 2005
> New Revision: 292942
>
> URL: http://svn.apache.org/viewcvs?rev=292942&view=rev
> Log:
> Build the hyphenation patterns under the build/classes directory.
>
> Modified:
>     xmlgraphics/fop/trunk/build.xml
>
> Modified: xmlgraphics/fop/trunk/build.xml
> URL:
> http://svn.apache.org/viewcvs/xmlgraphics/fop/trunk/build.xml?rev=292
>942&r1=292941&r2=292942&view=diff
> =====================================================================
>========= --- xmlgraphics/fop/trunk/build.xml (original)
> +++ xmlgraphics/fop/trunk/build.xml Sat Oct  1 02:07:10 2005
>  <at>  <at>  -389,8 +389,8  <at>  <at> 
>        <pathelement location="${build.classes.dir}"/>
>      </path>
>      <taskdef name="serHyph"
> classname="org.apache.fop.tools.anttasks.SerializeHyphPattern"
(Continue reading)

Andreas L Delmelle | 1 Oct 2005 11:26
Picon

Re: svn commit: r292942 - /xmlgraphics/fop/trunk/build.xml

On Oct 1, 2005, at 11:09, Manuel Mall wrote:

Hi Manuel,

> I thought the whole hyphenation build was suppose to be removed from 
> the
> trunk?

Not entirely. It was the intention that there'd be no more patterns 
distributed with FOP, but it should still be possible, for people who 
check out the trunk sources, to download patterns from OFFO, put them 
in the right directory, and have them automatically be picked up when 
building. Or simply build a hyphenation JAR by running 'ant 
jar-hyphenation' (or whatever).

Convenient for the end-user :-)

Cheers,

Andreas

Manuel Mall | 1 Oct 2005 11:31
Picon

Re: svn commit: r292942 - /xmlgraphics/fop/trunk/build.xml

On Sat, 1 Oct 2005 05:26 pm, Andreas L Delmelle wrote:
> On Oct 1, 2005, at 11:09, Manuel Mall wrote:
>
> Hi Manuel,
>
> > I thought the whole hyphenation build was suppose to be removed
> > from the
> > trunk?
>
> Not entirely. It was the intention that there'd be no more patterns
> distributed with FOP, but it should still be possible, for people who
> check out the trunk sources, to download patterns from OFFO, put them
> in the right directory, and have them automatically be picked up when
> building. Or simply build a hyphenation JAR by running 'ant
> jar-hyphenation' (or whatever).
>
> Convenient for the end-user :-)
>
Andreas,

Thanks for clarifying this. Certainly makes sense to me now.

>
> Cheers,
>
> Andreas
Manuel

Simon Pepping | 1 Oct 2005 22:29
Picon

referenceBPD in TableLM

When I put a table in a block in an inline, I get a NPE, from this
line:

referenceBPD = context.getStackLimit().opt;

because the stack limit in the context is null. Obviously, the inline
does not pass a stack limit in the context.

The problem can be solved easily by removing the field referenceBPD. I
would think that with the current approach to page breaking it is not
needed by the TableLM and its child LMs. Am I correct?

Regards, Simon

--

-- 
Simon Pepping
home page: http://www.leverkruid.nl

J.Pietschmann | 2 Oct 2005 00:57
Picon
Favicon

Re: Another page-related question: page-position="last"

Jeremias Maerki wrote:
> On 27.09.2005 16:38:23 Luca Furini wrote:
[the usual layout oscillation/convergence problem]
>> What is the expected output?
> 
> In this case it has to generate a blank page IMO.

The expected output is that there is some content (area with bpd>0) on
the last page, even if this sounds suboptimal.

J.Pietschmann

bugzilla | 2 Oct 2005 01:04
Picon
Favicon

DO NOT REPLY [Bug 36815] - java.lang.NoSuchMethodError when working together with batik 1.6

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=36815>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36815

------- Additional Comments From j3322ptm <at> yahoo.de  2005-10-02 01:04 -------
Batik 1.6 is not compatible with FOP 0.20.5.
FOP 0.20.5 will only run with the Batik release also included in the FOP
distribution. This is a documented restriction.
A better resolution of the bug would be "INVALID".

--

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

J.Pietschmann | 2 Oct 2005 01:46
Picon
Favicon

Re: DO NOT REPLY [Bug 36871] New: - Null Pointer exception in xsl mode

bugzilla <at> apache.org wrote:
> When your XSL file contains a condition that isn't met, so that you don't have a
> <fo:root to do anything with you get a null pointer execption.

Well, the bug report should read "no proper error message
if there is no fo:root". I vaguely remember Jeremias worked on
this, unfortunately I don't remember whether this got into
0.20.5, and I can't currently test it. Does someone else have
a 0.20.5 installation ready to run to do a quick test?

J.Pietschmann

bugzilla | 2 Oct 2005 23:08
Picon
Favicon

Bug report for Fop [2005/10/02]

+---------------------------------------------------------------------------+
| Bugzilla Bug ID                                                           |
|     +---------------------------------------------------------------------+
|     | Status: UNC=Unconfirmed NEW=New         ASS=Assigned                |
|     |         OPN=Reopened    VER=Verified    (Skipped Closed/Resolved)   |
|     |   +-----------------------------------------------------------------+
|     |   | Severity: BLK=Blocker     CRI=Critical    MAJ=Major             |
|     |   |           MIN=Minor       NOR=Normal      ENH=Enhancement       |
|     |   |   +-------------------------------------------------------------+
|     |   |   | Date Posted                                                 |
|     |   |   |          +--------------------------------------------------+
|     |   |   |          | Description                                      |
|     |   |   |          |                                                  |
|  635|Opn|Nor|2001-02-18|Doesn't support id= attribute in fo:page-sequence |
|  953|Opn|Nor|2001-03-12|Incorrect hyperlinks area rendering in justified t|
| 1063|New|Nor|2001-03-21|fop does not handle large fo files                |
| 1180|New|Maj|2001-04-02|Problem with monospaced font                      |
| 1859|Opn|Min|2001-05-22|org.apache.fop.apps.Driver.reset() doesn't fully r|
| 1998|New|Nor|2001-06-05|linefeed-treatment not understood                 |
| 2150|Ass|Maj|2001-06-13|New page with  a table-header but without any tabl|
| 2475|Ass|Nor|2001-07-06|Borders don't appear to work in <fo:table-row>    |
| 2740|New|Maj|2001-07-23|multi-page tables sometimes render badly          |
| 2909|New|Maj|2001-07-30|Gradient render error                             |
| 2964|Ass|Nor|2001-08-02|problems with height of cells in tables           |
| 2988|New|Maj|2001-08-03|0.19: list-item-label does not stick to list-item-|
| 3044|Ass|Maj|2001-08-08|keep-together not functioning                     |
| 3280|New|Nor|2001-08-27|PCL Renderer doesn't work                         |
| 3305|Opn|Nor|2001-08-28|list-block overlapping footnote body              |
| 3497|New|Cri|2001-09-07|id already exists error when using span="all" attr|
| 3824|New|Blk|2001-09-25|MIF option with tables                            |
(Continue reading)

Manuel Mall | 3 Oct 2005 02:58
Picon

Alignment handling wiki page

I have started a wiki page describing the issues I found in dealing with 
inline alignments and their proposed resolution:
http://wiki.apache.org/xmlgraphics-fop/LineLayout/AlignmentHandling

The page is written in a style as if FOP already does those things. Of 
course it doesn't (my copy sort of does in parts).  Comments, 
criticism, different points of view are most welcome as some of the 
suggested solutions may be contentious.

Manuel

Jeremias Maerki | 3 Oct 2005 16:11
Picon
Gravatar

Re: Another page-related question: page-position="last"

Ah, so we need to define first, what we really want to expect. :-) Does
the spec say anything about the expected behaviour?

On 02.10.2005 00:57:07 J.Pietschmann wrote:
> Jeremias Maerki wrote:
> > On 27.09.2005 16:38:23 Luca Furini wrote:
> [the usual layout oscillation/convergence problem]
> >> What is the expected output?
> > 
> > In this case it has to generate a blank page IMO.
> 
> The expected output is that there is some content (area with bpd>0) on
> the last page, even if this sounds suboptimal.
> 
> 
> J.Pietschmann

Jeremias Maerki


Gmane