ConsolidateSpellingLibs

Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2005-12-07 06:53:13 →
Size: 1747
Editor: 0x50c71cc7
Comment:
← Revision 3 as of 2006-01-01 05:15:21 → ⇥
Size: 1767
Editor: S0106000000cc07fc
Comment: cat spec
Deletions are marked like this. Additions are marked like this.
Line 45: Line 45:
----
CategorySpec

Summary

Replace three of the spelling libraries by one implementation and use that one for all applications supported in main. Currently up to four implementations are in use:

  • ispell: still used by some applications, its getting replaced by aspell.
  • aspell: ispell replacement, biggest users in main are gnome and KDE
  • myspell: ispell replacement, currently used by thunderbird, mozilla, openoffice.
  • hunspell: fork/replacement for myspell, dictionaries beeing compatible with aspell.

Dictionaries are currently packaged either separately for each spelling checker, or in some cases, derived from one common dictionary source.

ispell and aspell do provide a C interface, myspell and hunspell do provide a C++ interface.

Rationale

Support only one implementation in the long term, and more importantly, only support the dictionaries for on spelling library.

Use cases

Scope

Design

Implementation

Code

Data preservation and migration

Outstanding issues

BoF agenda and discussion

It would be universally cool if we could somehow tie in Rosetta, language packs and this unified spellchecking library. This way translators and users would be using the same defacto list and translators could on the fly correct the list if there happened to be a problem. This would definately make my life as a translator just a tad easier.

CategorySpec

ConsolidateSpellingLibs (last edited 2008-08-06 16:16:08 by localhost)