From: Bryce Nesbitt (bryce-mailinglists@attbi.com)
Date: Wed Apr 03 2002 - 18:56:03 EST
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?
The traditional solution is:
rpm -e abiword
This archive was generated by hypermail 2.1.4 : Wed Apr 03 2002 - 18:58:34 EST