Christian Geisert wrote:
> Hi,
>
> I haven't had much time recently to work on the next (final)
> maintenance release and will be on holiday the next two
> weeks (honeymoon ;-)
Congratulations. The first FOP wedding!
> but then we really should get the release
> ou
[EMAIL PROTECTED] wrote:
> I'm sorry, just want to clarify, so, it will support keep-together in table
> rows, but not in fo blocks right?
Right. No change compared to the current code.
Unless someone does change it, of course.
J.Pietschmann
---
To: [EMAIL PROTECTED]
cc:
10/16/2002 12:38 PM Sub
[EMAIL PROTECTED] wrote:
> Will the maintenance release in the first week of November support the
> keep-together property ?
Yes, in exactly the same way as the current version (table rows only).
J.Pietschmann
--
Hello,
Will the maintenance release in the first week of November support the
keep-together property ?
Thank You!
Shaifali Prakash
C&HT / Media & Entertainment
San Francisco
email: [EMAIL P
ne by then. That was my only real goal for
maintenance.
Felicitations on your matrimony, BTW.
-Original Message-
From: Christian Geisert [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 16, 2002 1:24 PM
To: [EMAIL PROTECTED]
Subject: Maintenance release
Hi,
I haven't had
Hi,
I haven't had much time recently to work on the next (final)
maintenance release and will be on holiday the next two
weeks (honeymoon ;-) but then we really should get the release
out and so I propose the end of the first week of november
as target date for the release candidate.
Then
Hi,
there is a new FOA release 0.4.0.
Here there is a short list of new features/bug fixes:
- Absolute Positioning Brick
- Page Number Formats and Counting
- Added US Page Formats
- Fixed bugs for JDK 1.4
- Fixed page/content sequence bugs
There is also a list of the currentlu supported
Hi all,
I haven't seen anything about the next maintenance release for about a
week now, but I noticed that there had been some discussion about
basic-link problems.
In the meantime, I have improved the basic-link positioning and also
made it work for external-graphic and foreign-i
[EMAIL PROTECTED] wrote:
> is there a way to clear the image cache in FOP 0.2.0.2?
>
> I saw some documentation suggesting a new static method on FopImageFactory
> org.apache.fop.images.FopImageFactory.clearCache();
>
> has this been implemented in newer versions?
Interesting question... looks
gzilla/show_bug.cgi?id=11760
java 1.2.2 not compatible with release
Summary: java 1.2.2 not compatible with release
Product: Fop
Version: 0.20.4
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority:
Extract from the Changes file :
- BaseDir property is now used for loading custom fonts (Bug #7608)
(thanks to Arnd Beissner and Brian O'Kelley)
Applying this fix broke some stuff as far as I can tell. Fop ships with a
config file that has this property commented out. As a result basedir
appea
Jeremias Maerki schrieb:
> Hi Christian
>
>>here is the plan for the 0.20.4 release
[..]
> There is a bug that needs to be fixed IMHO (or to be documented as known
> issue):
> - fo:list-item-label at the end of line
> http://nagoya.apache.org/bugzilla/show_bug.cgi?
Hi Christian
> here is the plan for the 0.20.4 release
>
> First there are the following uncommitted patches:
>
> - reload functionality for AWT viewer
> http://marc.theaimsgroup.com/?l=fop-dev&m=102415975220531&w=2
>
> - implementation of margin shorthand
&
Ok,
here is the plan for the 0.20.4 release
First there are the following uncommitted patches:
- reload functionality for AWT viewer
http://marc.theaimsgroup.com/?l=fop-dev&m=102415975220531&w=2
- implementation of margin shorthand
http://marc.theaimsgroup.com/?l=fop-dev&m=1024837
Hello,
there is a new FOA (Formatting Object Authoring tool) release: 0.3.0
Now there are these additional features:
- Complex Table Brick (full FO table implementation with Body, Headers and
Footers)
- Page Number Brick
- Multiple Headers/Footers for each Page Sequence
- Compliant with
Christian Geisert wrote:
> Another potential for saving space are the included jars
> (stuff like schema parser and html/wml-dom in xerces.jar,
> SAX/DOM in batik.jar etc.)
btw, what about crimson parser? Its jar is only about 200Kb and it's
apache also.
--
Oleg Tkachenko
Multiconn Internation
On Tue, 2002-06-18 at 22:36, J.Pietschmann wrote:
> [EMAIL PROTECTED] wrote:
> > Is it me, or do the examples in fop-0.20.4rc/docs/examples/svg not work.
> >
> > ../../../fop.sh external.fo external.pdf
> > [INFO] FOP 0.20.4rc
> > [INFO] building formatting object tree
> > [Fatal Error] external.
so large
> and also larger
> than the previous release.
> The src release contains the generated html and javadocs
> which is about
> an extra 2.5Mb compressed (18Mb uncompressed).
>
> The bin release contains the xml-docs and the html-docs,
> ant.jar and the
> hyphenatio
Hi all,
I was just wondering why the distributions are so large and also larger
than the previous release.
The src release contains the generated html and javadocs which is about
an extra 2.5Mb compressed (18Mb uncompressed).
The bin release contains the xml-docs and the html-docs, ant.jar and
Martin Peřina schrieb:
[..]
> It works fine, just two things:
>
> 1) If baseDir is set for example to "/opt/fop", FOP doesn't
> add "/" at the end of baseDir as other systems commonly does,
> so you can start use path for fonts like this:
>
> kerning="yes"
>
[EMAIL PROTECTED] wrote:
> Is it me, or do the examples in fop-0.20.4rc/docs/examples/svg not work.
>
> ../../../fop.sh external.fo external.pdf
> [INFO] FOP 0.20.4rc
> [INFO] building formatting object tree
> [Fatal Error] external.fo:79:81: The prefix "xlink" for attribute "xlink:href" is
>not
ive threads, sunwjit)
%uname -a
SunOS bmcls055 5.8 Generic_108528-14 sun4u sparc SUNW,Ultra-1
Regards
Paul.
Martin Peřina <[EMAIL PROTECTED]> on 14/06/2002 12:10:31
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: [ANNOUNCEMENT] FOP 0.20.4 Release Candidate availab
On Čt, 2002-06-13 at 18:10, Christian Geisert wrote:
> Hi all,
>
> the Release Candidate for 0.20.4 is available at
> http://xml.apache.org/dist/fop for downloading and testing.
>
> It is planed to make the actual release in about a week (or two?)
> if no serious bugs
Hi all,
the Release Candidate for 0.20.4 is available at
http://xml.apache.org/dist/fop for downloading and testing.
It is planed to make the actual release in about a week (or two?)
if no serious bugs show up.
Changes since 0.20.3 include:
- Support for background-image
- FOP should now work
you use the same image.
>
> Unless someone comes up with an actual fix (or applies an existing fix
> if there is one out there in the wild) sometime real soon now, then this
> will still be a problem in the next release.
>
> Mike.
I ran into the same problem; I solved it in the c
ge multiple times in a document. It will
get worse the more you use the same image.
Unless someone comes up with an actual fix (or applies an existing fix
if there is one out there in the wild) sometime real soon now, then this
will still be a problem in the next release.
Mike.
--
Michael G
ignificant differences now in the
> ImageFactory Class implementation. So it's difficult for me to modify the
> code for our purpose.
> When is the next release going to happen ? We are going live shortly, hence
> would like
fix
if there is one out there in the wild) sometime real soon now, then this
will still be a problem in the next release.
Mike.
--
Michael Gratton <[EMAIL PROTECTED]>
Recall Design <http://www.recalldesign.com/>
s: 53 Gilbert Street Adelaide SA 5000 Australia
t: +61 8 8217 0500 f: +61 8 8
me to modify the
code for our purpose.
When is the next release going to happen ? We are going live shortly, hence
would like to know our options.
Sorry for the questions, but I am under a lot of pressure.
I would appreciate any help in this direction.
Rishi
t there are still a lot of problems especially with SVG and
> fonts.
Ok, then I'll try to make the release candidate this evening.
Christian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
> -Original Message-
> From: Christian Geisert [mailto:[EMAIL PROTECTED]]
> Sent: June 10, 2002 1:20 PM
> To: [EMAIL PROTECTED]
> Subject: manifest classpath (was: Re: delay for release candidate)
>
> Arved Sandstrom schrieb:
> > Christian, if it's not alr
Arved Sandstrom schrieb:
> Christian, if it's not already changed, this release would be a good
> opportunity to modify the manifest file Class-Path so that it does not
> expect JARs inside a lib/ directory. As was discussed some time back this is
> awkward for a number of
on the PS renderer.
So I think one or two days later doesn't matter that much ..
> change the default, but I have not committed it yet. I would like to
> get an interested user to try it before general release, if possible.
I'd say commit it. I can make a quick test and besides it&
Rob,
Thanks. That's exactly the sort of thing I was concerned about. I've
had a quick look around and seen nothing, so it might be better for now
to put it on hold, and mention the work-around and its possible
consequences in the release notes. Anyone else have any other ideas?
> -Original Message-
> From: Peter B. West [mailto:[EMAIL PROTECTED]]
> Sent: 09 June 2002 16:39
> To: [EMAIL PROTECTED]
> Subject: Re: delay for release candidate
>
> What's the latest? I have just patched .../fo/flow/BasicLink.java to
> change the default
Christian,
What's the latest? I have just patched .../fo/flow/BasicLink.java to
change the default, but I have not committed it yet. I would like to
get an interested user to try it before general release, if possible.
Peter
Christian Geisert wrote:
> Hi all,
>
> as you
ng filters that don't throw occasional Exceptions
> anymore etc.). The bad message is: It got late last night and I haven't
> finished and I won't be able to finish today. So, Christian, if you
> manage to get the release candidate out today, go for it. I'll commit my
>
tian, if you
manage to get the release candidate out today, go for it. I'll commit my
changes after the final release. Sorry.
Cheers,
Jeremias Maerki
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Christian, if it's not already changed, this release would be a good
opportunity to modify the manifest file Class-Path so that it does not
expect JARs inside a lib/ directory. As was discussed some time back this is
awkward for a number of J2EE servers. If nothing else it can lead
> NB: I see the problem on NT4.0/sp6 -- I do not know what the results are
> on different platforms.
I can confirm that the same problems exist on Windows 2000.
Cheers,
Jeremias Märki
mailto:[EMAIL PROTECTED]
OUTLINE AG
Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern
Tel. +41 41 317 2020 - F
At 07:50 PM 6/3/02, you wrote:
>Any other patches missing ?
Yes, alas, the change I introduced recently which improved the appearance
(ie spacing within words) in the awt renderr (command line -awt) introduces
a problem with word-to-word spacing in printing -- both when printing from
the AWTRende
imsgroup.com/?l=fop-dev&m=102246257523766&w=2
> as you probably have noticed the date for the release candidate has been
> reached but I would like to see the following things done for 0.20.4:
> (new target date: next weekend ;-)
>
> - fix "broken" PDFs
>htt
Hi all,
as you probably have noticed the date for the release candidate has been
reached but I would like to see the following things done for 0.20.4:
(new target date: next weekend ;-)
- fix "broken" PDFs
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9054
http://marc.theaim
Yeah, that's OK. I'm not sure if I can get the bitmap renderer in this
weekend. I hope so, but I can't promise.
> > as a lot of people want a date for the next release I propose 1st
> > of june as target date for the release candidate for 0.20.4
> >
> &g
Christian Geisert wrote:
> Ok,
>
> as a lot of people want a date for the next release I propose 1st
> of june as target date for the release candidate for 0.20.4
>
> What do you think?
Christian,
OK by me. Anyone have any specifics he or she wants to get into t
Ok,
as a lot of people want a date for the next release I propose 1st
of june as target date for the release candidate for 0.20.4
What do you think?
Christian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
l there be another maintenance release before something comes
> out of the redesign?
Yes, why not ;-)
We already have improved logging, JAXP, background-image support,
new hyphenation patterns.
> If so, when? Roadmap?
I'd say in "some weeks" (don't know when batik 1.5 is re
line, therefore only moderatly hard. This is definitely
>a "must have".
> - PDF extensions, like encrypting. Perhaps integration with some
>other project.
>
> I think i'll leave Bugzilla alone until the next bug summary
> next weekend.
>
> Questions:
Thanks for doing the bugzilla stuff.
To answer some of your questions.
Yes we will need at least another release from the maintenance branch.
I have been thinking about extending the plan extension thing to produce a
roadmap picture (like mozilla has) so we can present the information about
I am not a committer nor a developer of fop (but prepared to do some work)
but mainly a user. However, here is my opinion on the matters raised.
1. I would like to see further maintenance releases on the 0.23 branch.
Valuable (to various users) updates to the last release have been posted to
ntil the next bug summary
next weekend.
Questions:
Will there be another maintenance release before something comes
out of the redesign?
If so, when? Roadmap?
If so, which should be the problems solved? Pick from above or
add whatever you think should be added.
Further question: Is the duplicate id
Hi all,
just in case someone hasn't noticed yet ;-)
FOP 0.20.3 is finally available at http://xml.apache.org/dist/fop
for downloading.
The main reason for this release is the conformance to the XSL-FO
Version 1.0 W3C Recommendation. Other changes include:
- support for CMYK and embedde
> I checked my patche. The resources.ja file which included my
> posted patch has NOT included in 0.20.3rc2.
>
> I repost only org/apache/fop/viewer/resources/resources.ja file.
> Please commit this file.
Done
> Regards.
>
> ---
> Satoshi Ishigami VIC TOKAI CORPORATION
Christian
---
Hi, Christian.
On Thu, 21 Feb 2002 17:30:32 +0100 , Christian Geisert wrote:
> the second Release Candidate for 0.20.3 (Maintenance release) is
> finally available at http://xml.apache.org/dist/fop for downloading
> and testing.
Great !!
> - Improved i18n support for AWT view
Hi all,
the second Release Candidate for 0.20.3 (Maintenance release) is
finally available at http://xml.apache.org/dist/fop for downloading
and testing.
There will be no new functionality added and if no new bugs show up
FOP 0.20.3 will be released next week (target date is 27. Februar
ent/fixes (no net new features) and then produce the final
FOP-0.20.4. Otherwise all we will ever produce are release candidates! :-)
Arved
-Original Message-
From: Christian Geisert [mailto:[EMAIL PROTECTED]]
Sent: February 8, 2002 3:03 PM
To: [EMAIL PROTECTED]
Subject: Status maintenace re
Ok,
just a short info about the current status of the maintenace release.
Things I want to do for the release:
-apply "proper font econding" patch by Peter S. Housel and Rainer Garus
I've tested it and it's looks good, 'build test' showed a small
difference
Arved Sandstrom wrote:
>Hi, Peter
>
>I've included an attachment which is a tree listing of what I obtained with
>wget.
>
>Please review and let me know what I missed. Thanks.
>
Arved,
All of the html-docs stuff is redundant as far as the docs build is
concerned - it will all be generated.
Hi, Peter
I've included an attachment which is a tree listing of what I obtained with
wget.
Please review and let me know what I missed. Thanks.
We have a couple of days yet before Christian builds and uploads the
release...there is some work to do, including incorporating your stuff
(wh
om wrote:
>Don't see why not, Peter. If you provide me with a precise list of
>instructions (what to get, where, and the location that you would like to
>see them go in html-docs) I will make that happen this weekend. I think we
>are looking at early next week for the actual release.
&g
Thanks for the list. I wish you had come out with it a few days before I
prepared the release candidate. :-) In any case it will come in useful over
the next few days.
Regards,
Arved Sandstrom
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rainer Garus
up to date? If not, the section should be deleted.
10. Resources / Other resources
There is no apache archive of [EMAIL PROTECTED] in "http://xml.apache.org/mail";. Is
this correct?
11. Home
In the home page http://xml.apache.org in section FOP "Java 1.1" should be changed to
&qu
I'll keep this in mind for this weekend. Thanks.
Arved
-Original Message-
From: Ralph LaChance [mailto:[EMAIL PROTECTED]]
Sent: January 24, 2002 7:45 AM
To: [EMAIL PROTECTED]
Subject: RE: [ANNOUNCEMENT] FOP 0.20.3 Release Candidate available
Arved et al,
Any interest in includin
Arved,
I have set up a book with my xml. It will require changes to
xml-fop/docs/xml-docs/fop.xml and to xml-fop/build.xml. I'll prepare -u
diffs for both. One question about the xml: when I was writing the xml
files, I used
to allow me acces to the dtd for editing. Is there a way to sp
Arved et al,
Any interest in including the printing servlet example I submitted last week:
...\examples\FopPrintServlet
It doesn't appear to be in the current rc.
' Best,
-Ralph LaChance
-
To uns
think we
>are looking at early next week for the actual release.
>
>I can do the getting...I have cable.
>
>Arved
>
>
>
>Arved,
>
>Keiron mentioned the possibility of including my recent html design
>notes in th
Don't see why not, Peter. If you provide me with a precise list of
instructions (what to get, where, and the location that you would like to
see them go in html-docs) I will make that happen this weekend. I think we
are looking at early next week for the actual release.
I can do the gettin
Arved,
Keiron mentioned the possibility of including my recent html design
notes in the distribution. Is that feasible for this release?
Peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email
At 1:32 PM +0100 1/22/02, Christian Geisert wrote:
>Hi all,
>
>the Release Candidate for 0.20.3 (Maintenance release) is finally
>available at http://xml.apache.org/dist/fop for downloading and testing.
>
Cool! Since this is labeled a "Release Candidate" is there actu
Hi all,
the Release Candidate for 0.20.3 (Maintenance release) is finally
available at http://xml.apache.org/dist/fop for downloading and testing.
This version has been updated to XSL 1.0 Recommendation syntax and
requires (now officially) JDK 1.2 or better.
Christian
Ok,
I'm ready for the maintenance release ;-)
The attached patch just updates the version number (and removes the JDK 1.1
stuff)
Here is my plan:
Make another release candidate (don't forget to update docs from cvs HEAD)
Give some days for testing (there seem to be a lot of people
I'm willing to do the actual release mechanics any time, apart from
Christmas Eve or Christmas Day. :-) I'd say any time during the 12 Days of
Christmas counts for calling it a "holiday release". :-)
Arved Sandstrom
- Original Message -
From: "Christian Geiser
I think Xmas release if it is done in the rush may appear to be Halloween
release ;-)
You should consider it will be new year's release.
Even if I would be glad to have some maintenance (REC and so on) I would
not want you to jeopardize this maintenance branch's quality.
Thanks
Cy
Hi,
I have committed the patch.
I have only update the cvs HEAD docs, I think it will be easier to handle
if we just stick to one version of the docs. Since there is only one
website.
So when the distribution is made the docs should be updated from the main
trunk.
On the plus side you don't
:32 1.12
+++ docs/xml-docs/fop/readme.xml2001/12/12 17:19:17
@@ -23,7 +23,9 @@
-The latest version of Fop is 0.20.2 and it supports the xsl:fo candidate
release.
+The latest version of Fop is 0.20.2 and it supports the xsl:fo
+ http://www.w3.org/TR/2001/REC-xsl-20011015/";>
Hi,
I've taken a first look at the documentation and updated some links etc.
You need to run makedoc in docs/xml-doc to generate the html documentation.
I had a lot of problems to get makedoc.bat to work and after fixing those I
realised that makedoc.sh had already been fixed.
(Doh, should have u
Christian Geisert <[EMAIL PROTECTED]> wrote:
> Arved already proposed 15 Dec as release date.
>
> I think it would be a good idea to do some testing before the actual
release,
> so we should do a code freeze some days in advance.
> What about Monday the 10th ?
Any hope of
Hi,
Arved already proposed 15 Dec as release date.
I think it would be a good idea to do some testing before the actual release,
so we should do a code freeze some days in advance.
What about Monday the 10th ?
Should we make another release candidate?
Christian
On Monday 03 December 2001 12:19, Christian Geisert wrote:
> What about jfor ?
> I think it would be a good idea to add it with "user-level" integration as
> proposed by Betrand.
Depends on schedule - I'm very busy for the next two weeks, it would be hard
for me to find time to do the code movin
Keiron Liddle wrote:
>
[..]
> The things that I can think of that need doing are:
> - change appropriate "master-name" to "master-reference" in code and
> example documents
> - update version number and such info
>
> Then do some testing and check that everything is in order.
What about jfor ?
Hi, all
I am feeling a bit grouchy about the CHANGES file, so please bear with me.
What I'd like to suggest is that each committer modify and re-commit the
CHANGES file as they commit files. In particular, this allows the person who
is closest to the scene to _synopsize_ what they just did to
Hey, all
Just got home after a very long day (it's coming up on 10 PM), so I'm going
to knock out the FOP-0.20.2 release tomorrow evening. If I do it tonight
I'll just make mistakes.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
I haven't downloaded the release candidate (slow network at home), but
I've noticed a small problem in my latest CVS which I assume is the
same.
When using runtest.sh in docs/examples with the new targets which use a
"" instead of listing all of the individual ".fo"
I want the fo:inline-container element will be implement!
thanks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Hi, all
I built and uploaded the tarballs for the binary and source distributions,
for FOP-0.20.2. They are labelled as release candidates. Please test and let
me know what needs to be fixed. Thanks.
I am shooting for a final build on Tuesday.
The CHANGES file is not yet updated - I will be
Hi, all
Keiron announced a code freeze. Pursuant to that, I will be building and posting
a release candidate on Saturday. I figure we should allow 2-3 days for feedback.
A final build of the next 0.20.x FOP would then happen Tuesday or Wednesday.
Regards,
Arved Sandstrom
[SNIP]
> > At 10:42 AM 8/14/01 +0200, Michel Lehon wrote:
> > >> From: Weiqi Gao [mailto:[EMAIL PROTECTED]]
> > >> On 13 Aug 2001 22:08:50 +, Arved Sandstrom wrote:
> > >> > ...I suggest that we mandate a code freeze starting N days
> > &g
Arved,
> -Original Message-
> From: Arved Sandstrom [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, 15 August, 2001 10:24
> To: [EMAIL PROTECTED]
> Subject: RE: Release Process Improvements, Versioning etc
>
>
> At 10:42 AM 8/14/01 +0200, Michel Lehon wrote:
>
At 10:42 AM 8/14/01 +0200, Michel Lehon wrote:
>> From: Weiqi Gao [mailto:[EMAIL PROTECTED]]
>> On 13 Aug 2001 22:08:50 +, Arved Sandstrom wrote:
>> > ...I suggest that we mandate a code freeze starting N days
>> > before the release. At the start of th
> From: Weiqi Gao [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, 14 August, 2001 05:27
> To: [EMAIL PROTECTED]
> Subject: Re: Release Process Improvements, Versioning etc
>
>
> On 13 Aug 2001 22:08:50 +, Arved Sandstrom wrote:
> >
> > I invite everyone to subm
On Tue, 14 Aug 2001 00:08:50 Arved Sandstrom wrote:
> Hi, all
>
> I invite everyone to submit ideas as to how we can improve the release
> process: versioning, builds and testing. It seems like almost everytime a
> 0.X.0 release comes out, there is almost instantaneously a sh
On Tue, 14 Aug 2001 05:27:26 Weiqi Gao wrote:
> I have not used the testing framework. I tried "./build.sh test" once
> and it threw me some error message. It would be benefitial if the
> testing frame work can be made to work in a way similar to the "make;
> make check" sequence for GNU project
On 13 Aug 2001 22:08:50 +, Arved Sandstrom wrote:
>
> I invite everyone to submit ideas as to how we can improve the
> release process: versioning, builds and testing. It seems like
> almost everytime a 0.X.0 release comes out, there is almost
> instantaneously a shows
Hi, all
I invite everyone to submit ideas as to how we can improve the release
process: versioning, builds and testing. It seems like almost everytime a
0.X.0 release comes out, there is almost instantaneously a showstopper bug
that necessitates a 0.X.1 release, as happened this time.
I
At 09:59 AM 8/13/01 +0200, Keiron Liddle wrote:
>On Mon, 13 Aug 2001 03:27:37 Arved Sandstrom wrote:
>> Confirmed, on all counts:
>>
>> 1) NPE running your 'dsrb2' example, something to do with the lazy font
>> code
>> it looks like;
>> 2) 500 K file for 17 pages with your 'emp' example. I'm not
On Mon, 13 Aug 2001 03:27:37 Arved Sandstrom wrote:
> Confirmed, on all counts:
>
> 1) NPE running your 'dsrb2' example, something to do with the lazy font
> code
> it looks like;
> 2) 500 K file for 17 pages with your 'emp' example. I'm not familiar with
>
> fonts, so someone else is going to
At 09:15 PM 8/12/01 +0200, Petr Andrs wrote:
>I forgot to attach files I am talking about so here it is.
>
>On 12 Aug 2001, at 20:47 Petr Andrs wrote about Re: FOP 0.20.0 Release now
availabl :
>
>> I have to say I tried yesterday current CVS version an I ran into
>> se
Please don't forget "fop.sh" file also.
Thanks in Advance
Thanks,
Mike
-Original Message-
From: Charlie Wu [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 09, 2001 7:24 PM
To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
Subject: RE: Release Schedu
Arved Sandstrom wrote:
>
> At 09:46 PM 8/9/01 -0500, Weiqi Gao wrote:
> >
> > This makes sense. People who are getting the source
> > release can build the Javadocs from the release.
> > People who are getting the binary release can't
> > build the Jav
101 - 200 of 218 matches
Mail list logo
