From kde-core-devel  Tue Apr 26 18:32:51 2005
From: Baris Metin <baris () uludag ! org ! tr>
Date: Tue, 26 Apr 2005 18:32:51 +0000
To: kde-core-devel
Subject: Re: Spell Checking in KDE4 (KSpell2)
Message-Id: <20050426183251.GB14118 () uludag ! org ! tr>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=111458181706123
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--xXmbgvnjoT4axfJE"


--xXmbgvnjoT4axfJE
Content-Type: text/plain; charset=iso-8859-9
Content-Disposition: inline

Hello,

Tue, Apr 26, 2005 at 07:21:04PM +0200 , Mashrab Kuvatov :
> Hi all,
> 
> though I'm not a KDE developer, but a KDE user who wishes a success to
> the project, I'd like to say a few words on this issue.
> 
> Even at the moment, from the user's point of view KSpell2 is a very nice
> lib, IMHO. Why? Take KSpell2 plus ASpell-0.60+, there is no need of manually
> setting the encoding. All "conversation" with libaspell done in UTF-8, since
> starting with 0.60 it supports UTF-8 naturally. So, encoding item from
> Settings->Spellchecker has gone (usability +10). If we imagine that by default
> KSpell2 uses ASpell, there is no need of setting a backend. So, spellchecking
... snip ...

I don't share the same idea with you, there will be a need for setting a
backend in any way. Just for an example, I use newly added zpspell
(zemberek) backend while I write in Turkish and Ispell (currently) in
English.

I like the KSpell2 way but having a common backend mechanism for all
desktops has benefits (if this is the reason for considering Enchant as
an option).

regards,
-- 
Baris Metin
http://www.metin.org

--xXmbgvnjoT4axfJE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: http://metin.org

iD8DBQFCbolTQY59PDyY1JsRAifVAJ9xlrjlE42+S+u2ifs3ABv5qdahtgCfeO+Y
iq3xmVAa5+xJsNHIvwrQb0w=
=37Y3
-----END PGP SIGNATURE-----

--xXmbgvnjoT4axfJE--