Bug 154560 - [RFE] [PATCH] Enchant backend for KSpell2 (backported from Sonnet)
Summary: [RFE] [PATCH] Enchant backend for KSpell2 (backported from Sonnet)
Status: RESOLVED INTENTIONAL
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kspell (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: Zack Rusin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-24 00:40 UTC by Kevin Kofler
Modified: 2009-11-09 08:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Enchant backend for KSpell2 (backported from Sonnet) (61.21 KB, patch)
2007-12-24 00:44 UTC, Kevin Kofler
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Kofler 2007-12-24 00:40:51 UTC
Version:            (using KDE KDE 3.5.8)
Installed from:    Fedora RPMs

In Fedora, we are trying to reduce the proliferation of dictionaries and spellchecking tools. Therefore, we want to make as many applications as possible use the hunspell spellchecker, either directly or through the enchant abstraction layer. See http://fedoraproject.org/wiki/Releases/FeatureDictionary for details. This will also ensure KDE 3 and KDE 4 apps use the same spellchecking dictionaries (and incidentally also the same ones as other applications).

KDE 4's Sonnet already has an enchant backend, so I backported that backend to KDE 3's KSpell2.
Comment 1 Kevin Kofler 2007-12-24 00:44:01 UTC
Created attachment 22664 [details]
Enchant backend for KSpell2 (backported from Sonnet)

See also http://bugs.kde.org/show_bug.cgi?id=154561 for the legacy KSpell.
Comment 2 Zack Rusin 2008-08-27 16:59:00 UTC
This sounds like a very nice patch. Unfortunately I simply do not have resources to maintain that code. It's also a new feature which on KDE3 likely makes little sense.
If it's incredibly important then you can feel free to commit it but like I said, I simply do not have resources to maintain or even test it so you'd need to take full responsibility for it.
I'm closing with WONTFIX but because I just won't go back to KDE3 development, not because I think it's wrong and as mentioned you're of course free to commit it (assuming the release team will be ok with it) as long as you'll maintain it.