[Tickets #5629] Re: aspell + html composition == no spell check

bugs at bugs.horde.org bugs at bugs.horde.org
Tue Aug 28 23:43:05 UTC 2007


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=5629
-----------------------------------------------------------------------
 Ticket             | 5629
 Updated By         | dimante at dimante.net
 Summary            | aspell + html composition == no spell check
 Queue              | IMP
 Version            | HEAD
 Type               | Bug
 State              | Feedback
 Priority           | 2. Medium
 Owners             | 
-----------------------------------------------------------------------


dimante at dimante.net (2007-08-28 16:43) wrote:

These are my versions:
Horde  Horde (horde)  3.2-cvs  	   	 Application is ready.
Mail Mail (imp) H3 (4.2-cvs) 		Application is ready.

I have been using Horde / IMP since 2000.  I am not saying that you are
completely off base telling me my upgrade is wrong but, I have replaced all
the files in config with the .dist files and I believe my Horde setup is
correct.  I just downloaded the latest snapshots of Horde and IMP Head. 
The changes as your link points to are in the files and have updated
however the spellchecking is still not working.  Not sure what else to do. 
If you email I can send a username and password so you can see the issue in
action.  If you think I have mis-configured Horde I would appreciate any
feedback you could give as to what you think it may be.  Thank you.



> 1. I think this should fix things:
> 
http://cvs.horde.org/diff.php?r1=1.6&r2=1.7&f=imp%2Fjs%2Fsrc%2Fcompose.js
>
> Chuck - you might want to look at it as you made these changes when 
> doing the HTML signature changes a couple of months ago.  However, 
> the old version of xinha truly does use the DOM element node as a key 
> - weird but true.
>
> 2. If you truly are still seeing this error (before applying this 
> patch), that means that you did not upgrade Horde to 3.2 correctly as 
> your error would only occur if you were using IMP 4.2 and Horde < 3.2.




More information about the bugs mailing list