From: Alan Horkan (horkana@tcd.ie)
Date: Thu Apr 04 2002 - 06:02:57 EST
READ THIS:
http://abisource.com/support/expectations.phtml
cross posting wont help.
Many of the users do not use platforms that are
affected by this fonts bug this is a matter for the developers, not the
user mailing list. (for users who do care this is a unix issue that has
been discussed to death and the top voted outstanding bug)
bitching and moaning wont help,
agressive language will not help you get your way
the fonts have been renamed so there is a partial solution in place.
suggesting solutions and implementing them are two entirely different
matters.
The ideal solution for the UNPAID VOLUNTEER developers is not to make any
binaries at all for the affected platforms. Then the whole fonts issue
will not arise, it will be the problem of the specific distributor to make
sure that the necessary fonts are available to give Abiword proper WYSIWYG
(what you see is what you get) display and printing.
Developers cannot be forced to work on and fix a feature they are not
interested in, it is a small miracle that abiword is as stable as it is
and that the developers have resisted adding features in favour of fixing
bugs and stabilising abiword for the last few months.
Ultimatums about how and when Abiword v1.0 should be released are not
helpful.
It has been made clear to you that the developers will get to this when
they are ready, and if you are not happy with that you have the choice to
fork the code and fix the code in your own "reasonable" way but the
developers have the choice to decline your "reasonable" patch and fix it
properly the best way when they are ready.
to paraphrase Richard Nixon:
You can please some of the people some of the time
You can please all of the people some of the time but
You cannot please all of the people all of the time.
> The traditional solution is:
> rpm -e abiword
'Nuff Said
On Wed, 3 Apr 2002, Bryce Nesbitt wrote:
> Date: Wed, 3 Apr 2002 18:56:03 -0500
> From: Bryce Nesbitt <bryce-mailinglists@attbi.com>
> To: Dom Lachowicz <doml@appligent.com>,
> AbiWord Developer List <abiword-dev@abisource.com>,
> AbiWord User List <abiword-user@abisource.com>
> Subject: Re: Loss of enthusiasim for AbiWord
>
> Yes, I'm frustrated *, but only because reasonable solutions don't seem to
> take any traction here.
>
> AbiWord pollutes the system font list in a number of harmful ways. At the
> same time, AbiWord developers complain about problems and
> inconsistency with the font system. The pot is calling the kettle black.
>
> ----
>
> A very reasonable step for 1.0 AbiWord is to add fonts under only their
> true names (not false names), then implement a font substitution table.
> There is nothing half-baked about this. Half-baked is screwing up other
> innocent applications to benefit your own. Half-baked is implementing a
> font substitution table by adding false fonts to the system list. Half-baked
> is ignoring a substantial bug for dozens of months, and several release
> cycles. Half-baked is behavior that changes with the combination of currently
> running applications.
>
> ----
>
> Bake AbiWord 1.0 fully, at least to the point where it is not detrimental to
> other applications, then, and only then, release it.
>
>
> -Bryce
>
> * I'm pleased to hear that you are frustrated also. That's a step forward
> from a stance that ignores the seriousness of this issue, and plays a kingdom
> building game with denial or approval of bugfixes.
>
> PS: In case you refer to me your "expectations" document -- don't bother. I
> expect you to not screw up other applications. You're free to do whatever
> you want AS LONG AS you don't mess up other projects. The Linux community
> expects nothing less. You're vulnerable to a hammering from the rest of
> the community if this issue becomes more widely known, or gets slashdot
> visibility.
>
>
> Dom Lachowicz wrote:
> >
> > > Simple solution for 1030:
> > > DROP THE FONTS
> >
> > RMS: This is not so simple of a solution. We need to be able to embed
> > the fonts in our PS output so that printing is WYSIWYG. Unless you'd
> > rather we open up bug 2706: "AbiWord is not WYSIWYG" and watch the votes
> > pile up faster for that bug faster than they do for 1030. So I'm sorry,
> > "DROP THE FONTS" is NOT an acceptable solution, at least not yet. I'm
> > growing tired of people offering half-baked, not-thought-through "fixes"
> > for bug 1030.
> >
> > We've promised to fix this bug in a manner that we've deemed proper and
> > acceptable as soon as is humanly possible POST 1.0. Why can no one
> > understand this? I and the other developers do understand that many
> > people (developers included) consider this to be a large bug. Yet we're
> > committed to fixing this on our timeframe. Since this is a volunteer
> > project, you'll just have to live with this.
> >
> > Marc: We have alleviated many of these symptoms for the users via a few
> > patches (ones from Bryce included), but yet some problems still persist.
> > I'm working now on something that will hopefully cure GNOME users from
> > bug 1030 as we speak. If you can think of some ingenious work-around to
> > fix even more symptoms, please code up something and I really promise
> > that it will be considered.
> >
> > Bryce: Read the above paragraph. You're frustrated, we're frustrated,
> > we're all frustrated. Your complaining is just making us more
> > frustrated. We're all well aware of your stance on bug 1030 by now.
> >
> > Users: if you're affected by this bug, please be patient. We are going
> > to address this bug in the near future.
> >
> > Dom
>
>
> Pierre Abbat wrote:
> > It used to be that anything in Courier Bold in kwrite would appear scrawny
> > and in the wrong width if I started kwrite while AbiWord was running. If I
> > exit Abi and kwrite and restart kwrite, the font looks fine. Now Courier
> > Bold looks scrawny no matter when I start it. What is going on, and
> > how can I fix this?
>
This archive was generated by hypermail 2.1.4 : Thu Apr 04 2002 - 06:04:36 EST