--=-bg3jAnsUDzHwwt7x6KTq Content-Type: text/plain Content-Transfer-Encoding: 7bit
On Mon, 2006-05-29 at 12:44 +0300, Nadav Har'El wrote: > On Mon, May 29, 2006, Oded Arbel wrote about "Re: inline spell checking in > GNOME browsers [was Hallelujah!Hspell 1.0 is released.]": > > > > dictionaries site) but I can't select more then one dictionary - I can > > > > use only either the hebrew one which doesn't spell check english, or the > > > > english dicitonary which doesn't spell check hebrew. annoying. > > > > > > This is indeed a Mozilla limitation. > > > > Is there a bugzilla ticket on this that I can subscribe to, or should I > > open one ? > > I don't know - you can try searching for it in their bugzilla database. I could find none, so I opened ticket #339574: https://bugzilla.mozilla.org/show_bug.cgi?id=339574 > But note that this issue is far from being trivial: > A different solution can be to simply let the user enable more than one > spell-checker, and then run both of them (say, passing a word as correct > if one of these spell-checkers said it was correct). This makes perfect > sense for Hebrew+English, but might perhaps make less sense in other > situations, I'm not saying that by default all dictionaries should be used - instead let the user "enable" more then one dictionary, where a word is considered valid if it indeed succeeds at least one enabled dictionary - which also works if you have only one enabled. This is, BTW, how I assumed it work as the UI for the spell check dictionaries uses checkboxes which to me means that more then one can be selected. In the case of the german+english user, the user can enable german and disable english if he's not typing english in a form (and he thinks he gets false positives). Admittedly there is some loss of functionality for that use case, but (a) I would argue that this loss is much more limited then the loss of functionality for the hebrew+english case if multiple dictionaries are not available, and (b) it can be countered easily by a better UI for dictionary management - for example setting spell checking profiles, and maybe even attaching them to sites. -- Oded ::.. "Implementation is the sincerest form of flattery." -- L. Peter Deutsch --=-bg3jAnsUDzHwwt7x6KTq Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.10.1"> </HEAD> <BODY> On Mon, 2006-05-29 at 12:44 +0300, Nadav Har'El wrote: <BLOCKQUOTE TYPE=CITE> <PRE> <FONT COLOR="#000000">On Mon, May 29, 2006, Oded Arbel wrote about "Re: inline spell checking in GNOME browsers [was Hallelujah!Hspell 1.0 is released.]":</FONT> <FONT COLOR="#000000">> > > dictionaries site) but I can't select more then one dictionary - I can</FONT> <FONT COLOR="#000000">> > > use only either the hebrew one which doesn't spell check english, or the</FONT> <FONT COLOR="#000000">> > > english dicitonary which doesn't spell check hebrew. annoying.</FONT> <FONT COLOR="#000000">> > </FONT> <FONT COLOR="#000000">> > This is indeed a Mozilla limitation.</FONT> <FONT COLOR="#000000">> </FONT> <FONT COLOR="#000000">> Is there a bugzilla ticket on this that I can subscribe to, or should I</FONT> <FONT COLOR="#000000">> open one ?</FONT> <FONT COLOR="#000000">I don't know - you can try searching for it in their bugzilla database.</FONT> </PRE> </BLOCKQUOTE> I could find none, so I opened ticket #339574: <A HREF="https://bugzilla.mozilla.org/show_bug.cgi?id=339574";>https://bugzilla.mozilla.org/show_bug.cgi?id=339574</A><BR> <BR> <BLOCKQUOTE TYPE=CITE> <PRE> <FONT COLOR="#000000">But note that this issue is far from being trivial:</FONT> </PRE> </BLOCKQUOTE> <BR> <BLOCKQUOTE TYPE=CITE> <PRE> <FONT COLOR="#000000">A different solution can be to simply let the user enable more than one</FONT> <FONT COLOR="#000000">spell-checker, and then run both of them (say, passing a word as correct</FONT> <FONT COLOR="#000000">if one of these spell-checkers said it was correct). This makes perfect</FONT> <FONT COLOR="#000000">sense for Hebrew+English, but might perhaps make less sense in other</FONT> <FONT COLOR="#000000">situations,</FONT> </PRE> </BLOCKQUOTE> I'm not saying that by default all dictionaries should be used - instead let the user "enable" more then one dictionary, where a word is considered valid if it indeed succeeds at least one enabled dictionary - which also works if you have only one enabled. This is, BTW, how I assumed it work as the UI for the spell check dictionaries uses checkboxes which to me means that more then one can be selected.<BR> <BR> In the case of the german+english user, the user can enable german and disable english if he's not typing english in a form (and he thinks he gets false positives). Admittedly there is some loss of functionality for that use case, but (a) I would argue that this loss is much more limited then the loss of functionality for the hebrew+english case if multiple dictionaries are not available, and (b) it can be countered easily by a better UI for dictionary management - for example setting spell checking profiles, and maybe even attaching them to sites.<BR> <BR> <TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%"> <TR> <TD> -- <PRE> Oded </PRE> ::..<BR> "Implementation is the sincerest form of flattery." <BR> -- L. Peter Deutsch <BR> <BR> </TD> </TR> </TABLE> </BODY> </HTML> --=-bg3jAnsUDzHwwt7x6KTq-- ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
