Googiespell in SVN doesn't seem to actually do anything at the moment, is this still a WIP?
On Sat, 24 Jun 2006 11:09:20 +0100, Thomas Mangin thomas.mangin@exa-networks.co.uk wrote:
Colin Alston wrote:
Googiespell in SVN doesn't seem to actually do anything at the moment, is this still a WIP?
Same here, but It was working for me around two weeks ago. I would not rule out that something changed which broke the code in RC.
Edit main.inc.php in config dir and set enable_spellcheck:
// Make use of the built-in spell checker. It is based on GoogieSpell // which means that the message content will be sent to Google in order to check spelling $rcmail_config['enable_spellcheck'] = TRUE;
-- Regards, Erik
Erik wrote:
On Sat, 24 Jun 2006 11:09:20 +0100, Thomas Mangin thomas.mangin@exa-networks.co.uk wrote:
Colin Alston wrote:
Googiespell in SVN doesn't seem to actually do anything at the moment, is this still a WIP?
Same here, but It was working for me around two weeks ago. I would not rule out that something changed which broke the code in RC.
Edit main.inc.php in config dir and set enable_spellcheck:
// Make use of the built-in spell checker. It is based on GoogieSpell // which means that the message content will be sent to Google in order to check spelling $rcmail_config['enable_spellcheck'] = TRUE;
It already is by default.
On Sat, 24 Jun 2006, Thomas Mangin wrote:
Colin Alston wrote:
Googiespell in SVN doesn't seem to actually do anything at the moment, is this still a WIP?
Same here, but It was working for me around two weeks ago.
Yes, me too. I just upgraded to the latest svn, and see that it is now broken. It thinks for about 10 seconds (which is maybe longer than it used to?) and then returns no spelling errors found. I probably won't have time to look at it further.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jon Daley wrote:
Yes, me too. I just upgraded to the latest svn, and see that it is now broken. It thinks for about 10 seconds (which is maybe longer than it used to?) and then returns no spelling errors found. I probably won't have time to look at it further.
I done a svn up -r 260 where it was working for me and it is broken there. So this was not caused by any of the changes - which was unlikely anyway.
Thomas
Exa Networks Limited - UK - AS30740 - www.exa-networks.co.uk nic-handle : MANG-RIPE website : thomas.mangin.me.uk GPG key ID : 0xFB8B81A1 PGP key : /pgp.html Inoc-DBA # : 30740*TOM Office # : +44 (0) 845 145 1234
The Google spell checker isn't accessible over port 80 but only over HTTPS. I altered the file program/steps/mail/spell.inc (see revision 256) accordingly. Unfortunately the spell checker now only works on servers having Open SSL included with PHP.
Regards, Thomas
Colin Alston wrote:
Googiespell in SVN doesn't seem to actually do anything at the moment, is this still a WIP?
On Sun, 25 Jun 2006, Thomas Bruederli wrote:
The Google spell checker isn't accessible over port 80 but only over HTTPS. I altered the file program/steps/mail/spell.inc (see revision 256) accordingly. Unfortunately the spell checker now only works on servers having Open SSL included with PHP.
Yes, that was it, thanks.
PS. does subversion currently use a post-commit hook to send email anywhere? It would be great to have a mailing list (not sure if it should be on this dev list or not) where people could sign up to get every check-in.
On Sun, 25 Jun 2006 08:48:44 -0400 (EDT), Jon Daley roundcube@jon.limedaley.com wrote:
On Sun, 25 Jun 2006, Thomas Bruederli wrote:
The Google spell checker isn't accessible over port 80 but only over HTTPS. I altered the file program/steps/mail/spell.inc (see revision 256) accordingly. Unfortunately the spell checker now only works on servers having Open SSL included with PHP.
Here's the changelog, looks like was some changes to googiespell.js too
http://orangoo.com/labs/?page_id=45
Version 3.78 - 16. Juni 2006
- Google has switched to SSL. HTTPS instead of HTTP
So this might be the time I start looking at aspell integrations, since this will effectively close off most RC implementations. Anyone started on this yet/have any clues?
P
http://fak3r.com - you don't have to kick it
On Sun, 25 Jun 2006 10:51:58 -0500, phil phil@cryer.us wrote:
On Sun, 25 Jun 2006 08:48:44 -0400 (EDT), Jon Daley roundcube@jon.limedaley.com wrote:
On Sun, 25 Jun 2006, Thomas Bruederli wrote:
The Google spell checker isn't accessible over port 80 but only over HTTPS. I altered the file program/steps/mail/spell.inc (see revision 256) accordingly. Unfortunately the spell checker now only works on servers having Open SSL included with PHP.
Here's the changelog, looks like was some changes to googiespell.js too
http://orangoo.com/labs/?page_id=45
Version 3.78 - 16. Juni 2006
- Google has switched to SSL. HTTPS instead of HTTP
So this might be the time I start looking at aspell integrations, since this will effectively close off most RC implementations. Anyone started on this yet/have any clues?
More ideas: http://me.eae.net/archive/2005/05/27/dhtml-spell-checker/ http://me.eae.net/stuff/spellchecker/demo.html
http://www.lab4games.net/zz85/blog/wordpress-plugins/live-spell-checker/
http://www.broken-notebook.com/spell_checker/
-- http://fak3r.com - you don't have to kick it
phil wrote:
On Sun, 25 Jun 2006 08:48:44 -0400 (EDT), Jon Daley roundcube@jon.limedaley.com wrote:
On Sun, 25 Jun 2006, Thomas Bruederli wrote:
The Google spell checker isn't accessible over port 80 but only over HTTPS. I altered the file program/steps/mail/spell.inc (see revision 256) accordingly. Unfortunately the spell checker now only works on servers having Open SSL included with PHP.
Here's the changelog, looks like was some changes to googiespell.js too
http://orangoo.com/labs/?page_id=45
Version 3.78 - 16. Juni 2006
- Google has switched to SSL. HTTPS instead of HTTP
So this might be the time I start looking at aspell integrations, since this will effectively close off most RC implementations. Anyone started on this yet/have any clues?
As far as I know there isn't anybody working on this. I'd like to have aspell integrated in the same way google spell works. I mean just replacing the server side script but creating the same response that google now returns. With this, the client script doesn't have to be changed and it would still be possible to use the google spell checker if aspell is not installed (i don't know if there are more servers having SSL included with PHP or having aspell installed.)
Regards, Thomas
On Sat, 24 Jun 2006 12:23:03 +0200, Erik erik@prikbord.org wrote:
Edit main.inc.php in config dir and set enable_spellcheck:
// Make use of the built-in spell checker. It is based on GoogieSpell // which means that the message content will be sent to Google in order to check spelling $rcmail_config['enable_spellcheck'] = TRUE;
Shouldn't there be any kind of warnings related with config files changing in SVN (even worst in releases)? Maybe some kind of versioning of the config files.
--
Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador
This is something that will be described in the UPGRADING file. I forgot to add the latest changes but will to that before publishing a new release. If you update your SVN sandbox, the config file will be listed as changed.
There are even more ways to get informed about recent changes: http://trac.roundcube.net/trac.cgi/log/ (also available as RSS feed!)
Regards, Thomas
Martin Marques wrote:
On Sat, 24 Jun 2006 12:23:03 +0200, Erik erik@prikbord.org wrote:
Edit main.inc.php in config dir and set enable_spellcheck:
// Make use of the built-in spell checker. It is based on GoogieSpell // which means that the message content will be sent to Google in order to check spelling $rcmail_config['enable_spellcheck'] = TRUE;
Shouldn't there be any kind of warnings related with config files changing in SVN (even worst in releases)? Maybe some kind of versioning of the config files.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
This is something that will be described in the UPGRADING file. I forgot to add the latest changes but will to that before publishing a new release. If you update your SVN sandbox, the config file will be listed as changed.
I normally do a svn diff -r <version before update> of the configuration file after an svn up to catch the configuration changes.
Thomas
-
Colin Alston -
Erik -
Jon Daley -
Martin Marques -
phil -
Thomas Bruederli -
Thomas Mangin