← Back to team overview

zim-wiki team mailing list archive

Re: spell check on windows


I gotta believe that if the dependency chain can be well defined, it would just be a matter of installing those dependencies in the right places.  Perhaps the win distro could even be updated to include those in the packaging.

I'll down the source and investigate if I have to but does anyone know what the dependency chain looks like?

Zim -> gtk+ -> gtkspell -> pyenhcant -> enchant (native)?

This order correct? Missing anything?

-----Original Message-----
From: JP Vossen [mailto:jp@xxxxxxxxxxxxx] 
Sent: Saturday, November 24, 2012 12:58 AM
To: Charles Medcoff
Cc: zim-wiki@xxxxxxxxxxxxxxxxxxx; 'klo uo'
Subject: Re: [Zim-wiki] spell check on windows

I'm a pretty new user, but no, not that I've been able to find.

On 11/23/2012 09:00 PM, Charles Medcoff wrote:
> Hmm, nothing for non-source, windows/packaged installs?
> -----Original Message-----
> From: JP Vossen [mailto:jp@xxxxxxxxxxxxx]
> Sent: Tuesday, November 13, 2012 2:35 PM
> To: zim-wiki@xxxxxxxxxxxxxxxxxxx
> Cc: klo uo; Charles Medcoff
> Subject: Re: [Zim-wiki] spell check on windows
> See here: https://lists.launchpad.net/zim-wiki/msg01934.html
> and here: https://lists.launchpad.net/zim-wiki/msg01998.html
> and here: https://lists.launchpad.net/zim-wiki/msg01458.html
> On 11/13/2012 07:20 AM, klo uo wrote:
>> IMHO, not worth the trouble.
>> I tried and stucked after trying to pair enchant dependency to 
>> gtk-spell package, which although properly installed (after much
>> trouble) it simply didn't accept any dictionary. It was awful 
>> experience I won't recommend to anyone
>> Even Zim Windows installer doesn't have it
>> On Tue, Nov 13, 2012 at 12:47 PM, Charles Medcoff
> <cmedcoff@xxxxxxxxxxx>wrote:
>>> Is there a "recipe" for getting spellcheck to work on windows?****
>>> ** **
>>> --chuck****

JP Vossen, CISSP            |:::======|      http://bashcookbook.com/
My Account, My Opinions     |=========|      http://www.jpsdomain.org/
"Microsoft Tax" = the additional hardware & yearly fees for the add-on software required to protect Windows from its own poorly designed and implemented self, while the overhead incidentally flattens Moore's Law.

Follow ups