> Message: 9 > Date: Mon, 28 Feb 2005 20:32:22 -0500 > From: John Thacker <thacker@xxxxxxxxxxxxxxxx> > Subject: Re: fedora-devel-list Digest, Vol 12, Issue 104 > To: fedora-devel-list@xxxxxxxxxx > Message-ID: <20050301013222.GA31096@xxxxxxxxxxxxxxxxxx> > Content-Type: text/plain; charset="us-ascii" > > On Tue, Mar 01, 2005 at 01:18:01PM +1100, Martin Sevior wrote: > > > > The AbiWord community is as vibrant as ever. We committed over 300,000 > > LOC of changes to the code base over 14 months to produce AbiWord-2.2. > > We implemented all sorts of cool stuff that neither MS Word or OOo has. > > We implemented features that make the users job of creating documents > > easier and more fun. We want that code to be seen and used and > > appreciated by as many people as possible. We're in a position to be > > widely deployed across heterogenic communities like Universities and > > Schools since we have Windows, Mac and Linux clients. > > I otherwise like the program, but it's an incredible PIA for me to use > because of its absolutely horrible CJK support. So I essentially never > use it, even though a few years ago Japanese support (on Linux) went from > "completely unavailable" to "laughably horrible." OOo has very nice, > mature, professional CJK features. > > http://bugzilla.abisource.com/buglist.cgi?keywords=cjk > > Now I see that someone made it "not totally suck" on MacOSX recently, > so maybe there's hope yet for AbiWord. > See the post from today. http://www.abisource.com/mailinglists/abiword-dev/2005/Mar/0002.html Join in. Be part of the solution. As I said we're a grass roots organisation that responds to real people with real problems. We're VERY responsive to people with patches. AbiWord takes less than 10 minutes to build from scratch on a modern computer so the threshold for testing stuff is not high. Just testing and telling us what works for CJK and what doesn't is really useful. Cheers Martin
