Re: Work to release Abiword 3.0

 On Sun, Dec 16, 2012 at 12:45 PM, Simon Larochelle
 <larochelle.simon.1@gmail.com> wrote:
>
> Hi all,
>
> I would like to start a discussion on the work needed to complete
> Abiword version 3.0. Here is my list,
 <snip>

> Bug 13389: Spell checker. According to Per Larsson, we need to
> provide
> a version of Enchant compiled with MSVC. Also there are some issues
> with the hunspell dictionaries.

 Perhaps someone else has had different results, but I haven't had any
 luck
 getting spell checking to work *at all* in our 2.9 releases for
 windows.
 Please chime in if you have seen it work.
 Started to investigate and found a few things.

 * The enchant we shipped with 2.8 worked, but not the current one for
 2.9.
 * Using the 2.8 dlls with 2.9 makes spelling work again.
 * They both come from the opensuse repositories from what I've read.
 * They are both compiled with mingw and relinked, so should work.
 
 So what is really different? Is it
 a) a source change affecting the mingw build that has gone bad?
 b) A compiler option?
 c) A compiler issue? differing gcc versions were most likely used

 I'm starting to suspect that the main enchant.dll fails to find the
 provider
  dlls in ../lib/enchant, trying instead to use
 /usr/i686-mingw32/sys-root/lib/enchant or something equally silly.
 
 The easiest way may indeed be to recompile enchant with MSVC, since
 all of a,b,c are then bypassed.

 Apart from the compiler issue, there's something else that should be
 considered.
 I noted that the 2.9 enchant from opensuse is, unlike the 2.8 enchant,
 compiled with the flag --with-system-hunspell
 This shouldn't cause the breakage described above since the
 ispell-provider
 should still work.
 However, do we want that, and how do we then tell our users where to
 get a _compatible_ system-installed hunspell?
Received on Fri Dec 21 11:30:21 2012