On Tue, 15 Nov 2005 06:48 am, Jeremias Maerki wrote:
I agree with you two. Therefore, I've resurrected status.xml, added
it to our website again and prepared it so we can start using it
after the release.
BTW, I think I'm through with all the things I wanted to do. What's
left now:
- write
Debugging shows:
The FOText instances under fo:marker (just before and after the fo:block)
don't get processed for whitespace treatment. Block.handleWhitespace
isn't accessible to it. That's why the whitespace isn't removed and
causes additional lines. The fix is probably to extract
Jeremias Maerki wrote:
I agree with you two. Therefore, I've resurrected status.xml, added it
to our website again and prepared it so we can start using it after the
release.
BTW, I think I'm through with all the things I wanted to do. What's left
now:
- write the README/release notes
- Create
On 15.11.2005 10:28:19 Chris Bowditch wrote:
Jeremias Maerki wrote:
I agree with you two. Therefore, I've resurrected status.xml, added it
to our website again and prepared it so we can start using it after the
release.
BTW, I think I'm through with all the things I wanted to do.
Jeremias Maerki schrieb:
I agree with you two. Therefore, I've resurrected status.xml, added it
to our website again and prepared it so we can start using it after the
release.
BTW, I think I'm through with all the things I wanted to do. What's left
now:
- write the README/release notes
-
Jeremias Maerki wrote:
On 15.11.2005 10:28:19 Chris Bowditch wrote:
Sorry to be picky, but the word alpha gives the impression that the
release is alpha quality. I'd say it was beta quality by now. Anyway, I
thought in the past we had agreed on calling it 0.90pr1, with pr
meaning preview,
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=37505.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Jeremias Maerki schrieb:
On 15.11.2005 10:50:07 Christian Geisert wrote:
[..]
I don't think we need to vote on alpha/preview release (preview release
as in will be available on cvs.apache.org/builds/fop and not on the
official www.apache.org/dist) but should do it nevertheless.
But that
On 15.11.2005 11:42:31 Christian Geisert wrote:
Jeremias Maerki schrieb:
On 15.11.2005 10:50:07 Christian Geisert wrote:
[..]
I don't think we need to vote on alpha/preview release (preview release
as in will be available on cvs.apache.org/builds/fop and not on the
official
The example fo examples/fo/advanced/giro.fo wants a graphics called
mk1logo.tif. That file doesn't appear to be in svn. Any one come across
that file or has a local copy or knows anything about this?
Manuel
Hi Manuel,
I'm still intending to do this, but I misjudged the time I had available.
I'm not sure when I'll be able to spend the right amount of time and effort on this solution.
Let me know if this is OK
MarkOn 15/11/05, Manuel Mall [EMAIL PROTECTED] wrote:
On Wed, 19 Oct 2005 06:22 am, Mark
Hi Jeremias,
Not to rain on your parade, but doesn't there need to be a vote on
fop-dev by committers on the release before
bringing it to the PMC? Also doesn't a formal vote need to run at least
one full week? I understand your
desire to get the release out but...
Jeremias Maerki
mk1logo.tif seems to never have made it into the repository. Here's the
revision when this made it into the repository:
http://svn.apache.org/viewcvs?rev=194119view=rev
The whole thing seems to come from here:
http://www.elovirta.com/2001/06/28/giro/
I can't find any post in the archives that
Oh, I got sunshine outside. Not even fog today. :-) No, there's no need
for a committer vote prior to the PMC vote. In terms of the Apache
bylaws the PMC is the only body that can do project decisions [1]. BTW,
this is a topic that's currently discussed on legal-discuss [2]. Where
did you read
On Tue, 15 Nov 2005 09:15 pm, Jeremias Maerki wrote:
mk1logo.tif seems to never have made it into the repository. Here's
the revision when this made it into the repository:
http://svn.apache.org/viewcvs?rev=194119view=rev
The whole thing seems to come from here:
Hi Jeremias,
Jeremias Maerki [EMAIL PROTECTED] wrote on 11/15/2005 08:28:11 AM:
In terms of the Apache bylaws the PMC is the only body that can do
project decisions [1].
It appears that they are the 'binding body' from the ASF point of
view, but as a PMC member I would really like to see
Hi Thomas
Don't take what I wrote too much by the letter. Always add a little
common sense. See below.
On 15.11.2005 15:49:39 thomas.deweese wrote:
Hi Jeremias,
Jeremias Maerki [EMAIL PROTECTED] wrote on 11/15/2005 08:28:11 AM:
In terms of the Apache bylaws the PMC is the only body that
Manuel Mall wrote:
Hmm, just changed the value to 3000 (I think that's the value suggested
in the article) and there is no change in hyphenation behaviour with the
above mentioned example. That makes me a bit suspicious...
I traced the beheviour of the breaking algorithm applied to the first
On Nov 15, 2005, at 10:03, Jeremias Maerki wrote:
snip /
The fix is probably to extract handleWhitespace
from Block into a separate class and call it from Block and Marker.
In this respect: I still wonder whether it wouldn't be more
convenient to split up the whitespace handling, and deal
No, we cannot be sure if there are any legal issues unless we perform a
complete legal audit of the full FOP codebase. We'd have to go through
EVERYTHING. I think that's not in anybody's interest, nor would not
doing this be neglecting our duties. IMO it was a good move to remove
the hyphenation
Sounds like a good plan to me. Would you go after that?
On 15.11.2005 18:06:13 Andreas L Delmelle wrote:
On Nov 15, 2005, at 10:03, Jeremias Maerki wrote:
snip /
The fix is probably to extract handleWhitespace
from Block into a separate class and call it from Block and Marker.
In this
This is it. Just to make it clear again: This is a a release vote and
therefore a PMC vote, but every FOP committer is invited to place his
vote or raise any objections. Noone gets ignored. Although fop-dev is in
the CC, please place your votes on [EMAIL PROTECTED]
Even though I haven't fully
On the Wiki, ReleasePlanning:
fo:inline - Does not support block-level objects as children (isn't that
fixed?)
Mostly, but perhaps not completely. I seem to recall that Finn
reported an Exception related to a LM not recognizing the double list
structure of Knuth elements returned by some
Today, 15 November 2005, revision 344223 only gives an exception on
the first test file.
Simon
On Thu, Sep 01, 2005 at 02:45:30PM +0200, Finn Bock wrote:
Hi
Running the NIST test suite I get 2 table related exceptions and 1
KnuthElement related exception:
inline_block_nested_3.xml is disabled and produces a NPE. I assume
it's that. So it is one of our known problems. :-) That's exactly where
I see the XML-ification of the disabled-testcases.txt come into play. We
will be able to more clearly document what we can't do right now and
what our known
The wiki page ReleasePlanFirstPR says
Copy xdocs/trunk to xdocs/0.90alpha1 to create the release
documentation when it's good enough.
That is very unstable. Wouldn't xdocs/0.90 be good? I need to create a
reference to the hyphenation pages in OFFO.
Simon
--
Simon Pepping
home page:
On Nov 15, 2005, at 1:20 PM, Simon Pepping wrote:
The wiki page ReleasePlanFirstPR says
Copy xdocs/trunk to xdocs/0.90alpha1 to create the release
documentation when it's good enough.
That is very unstable. Wouldn't xdocs/0.90 be good? I need to create a
reference to the hyphenation pages in
Good point. In addition to what you propose, what about an empty
directory /latest which simply contains a .htaccess file that redirects
you to the latest release? That would be a stable URL. I can set that up.
On 15.11.2005 22:20:58 Simon Pepping wrote:
The wiki page ReleasePlanFirstPR says
On Wed, 16 Nov 2005 03:45 am, Jeremias Maerki wrote:
Sounds like a good plan to me. Would you go after that?
I have no problems with the suggestion to move the white space handling
from Block into its own class so other fo's that need it can make use
of it.
However, I still need to be
On Wed, 16 Nov 2005 12:14 am, Luca Furini wrote:
Manuel Mall wrote:
snip/
Tomorrow I should have some time to implement
hyphenation-ladder-count and fix the penalty values for justified /
unjustified text.
Not sure what other committers and the PMC think but as a vote on the
release has
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=37521.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
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=37521.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
32 matches
Mail list logo
