On 26.11.2002 16:01:57 Chris Bowditch wrote:
> it could well be that there is a problem with hypenation. The messages I get
> seem to relate to just 2/3 files out of 22.
As far as I can tell hyphenation works file with the maintenance branch
in CVS. docs/examples/fo/hyphen.fo looks good.
> It was just that you seemed to be putting a lot of effort into solving this,
> when I thought Thilo's original question was just about getting and building
> 0.20.5cvs. Thilo started an earlier thread in the user list on this, in
> which Christian Geisert told him his particular problem was fixed in
> 0.20.5cvs. Note, the last paragraph in Thilo's first message:
Ok, let's wait and see what Thilo responds.
> Christian Geisert writes about a soon available 0.20.5 release that adresses
> the bug. Is there any information about the date? I looked for a 0.20.5
> version/branch tag in the cvs but could'nt find one.
> I dont mean to be offensive, I just hate to see people's time wasted.
No problem. Anyway, if there's a problem with the build in certain
environments I'd like to have that fixed.
> >From: Jeremias Maerki <[EMAIL PROTECTED]>
> >Reply-To: [EMAIL PROTECTED]
> >To: [EMAIL PROTECTED]
> >Subject: Re: Current CVS version won't build
> >Date: Tue, 26 Nov 2002 15:50:58 +0100
> >Actually, the hyphenation stuff is the same for the maintenance branch
> >and the trunk and does not generate any error messages during build in
> >either codebase when done on the command line. It might of course be
> >that Thilo is on the wrong branch but he will experience this particular
> >problem anyway. But thanks for speaking up because that may help him to
> >reduce the time to track down the problem with unexpected output after
> >having solved the build problem in Eclipse. I've concentrated on the
> >build problem too much.
> >On 26.11.2002 15:42:09 Chris Bowditch wrote:
> > > Thilo, Jeremias,
> > >
> > > After reading Thilo's first message my understanding is that the reason
> > > getting unexpected output in the resulting PDF is that he checked out
> > > Trunk, and not the maintenance branch.
> > >
> > > Thilo, if you want to get 0.20.5cvs, then you need to check out using
> > > branch label fop-0_20_2-maintain. If you didnt use a label to check out
> > > source from CVS then you will have the Trunk code which is still under
> > > development.
> > >
> > > I think the message about hypenation when building FOP is a red herring.
> > > also get that message when building but my output (for English anyway)
> > > fine.
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]