[chromium-dev] Re: Inline spell checking.
Hi, I think (based on what Aaron Boodman said) that you could put a separator with the google suggestions and list at least the 2 top suggestions (3 will be good). Masses could be wrong, but with the 2 or 3 top suggestions I think that you could provide a more accurate rainbow of alternatives. Sorry, my english sucks, but I think that you get the point :) Cheers. On Mon, Dec 15, 2008 at 8:32 PM, Aaron Boodman wrote: > For me it is appropriate, since it is what I already do. I could see > there perhaps being some UI that separates the "google suggestions". > > My underlying complaint is really that the spell checker didn't seem > to work well, so I'll wait and see if like Brett said, it's better on > trunk. > > - a --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to chromium-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Re: Inline spell checking.
On Mon, Dec 15, 2008 at 1:52 PM, Ian Fette wrote: > We actually looked into this earlier. One thing that stopped us from doing > so is that the "corrections" are not based on proper spelling, but based > rather on searches and results. The masses are not always right, and we > thought it might be strange for your "dictionary" to be offering you > spelling "corrections" that were not actually correct, but rather popular. > Subjective question: Is it really appropriate for your dictionary to suggest > changing "lozx" to "lolz"? (Or a dictionary that thinks "twelf" is fine, > because it's the name of a logic programming language, when in reality most > people are probably looking for "twelfth"?) For me it is appropriate, since it is what I already do. I could see there perhaps being some UI that separates the "google suggestions". My underlying complaint is really that the spell checker didn't seem to work well, so I'll wait and see if like Brett said, it's better on trunk. - a --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to chromium-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Re: Inline spell checking.
We actually looked into this earlier. One thing that stopped us from doing so is that the "corrections" are not based on proper spelling, but based rather on searches and results. The masses are not always right, and we thought it might be strange for your "dictionary" to be offering you spelling "corrections" that were not actually correct, but rather popular. Subjective question: Is it really appropriate for your dictionary to suggest changing "lozx" to "lolz"? (Or a dictionary that thinks "twelf" is fine, because it's the name of a logic programming language, when in reality most people are probably looking for "twelfth"?) On Mon, Dec 15, 2008 at 1:43 PM, Peter Kasting wrote: > On Mon, Dec 15, 2008 at 1:27 PM, Evan Martin wrote: > >> The problem isn't technical, it's that to do that spell correction >> it'd involve sending all text form data up to a Google server. > > > Only "misspelled" words, right? > > PK > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to chromium-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Re: Inline spell checking.
On Mon, Dec 15, 2008 at 1:27 PM, Evan Martin wrote: > The problem isn't technical, it's that to do that spell correction > it'd involve sending all text form data up to a Google server. Only "misspelled" words, right? PK --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to chromium-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Re: Inline spell checking.
On Mon, Dec 15, 2008 at 12:14 PM, Aaron Boodman wrote: > It would be better if we could consult Google for spelling > recommendations. It seems like I frequently misspell a word, get the > red squiggly, get no recommendations from Chromium, then go to Google > and it gets it exactly right. The problem isn't technical, it's that to do that spell correction it'd involve sending all text form data up to a Google server. In fact, I believe Google Toolbar for IE already does it (glancing at this http://www.google.com/support/toolbar/bin/static.py?page=features.html page mentions spell check under the privacy section) But given the current perception of privacy and Chrome, I wonder if the negative perception of even an opt-in implementation would outweigh the user benefit in building in such a feature. (Consider how many people misunderstand our existing opt-in user metrics.) I agree it should be done as an extension -- hook keypresses on text input boxes and set a timer for contacting the server, etc. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to chromium-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Re: Inline spell checking.
On Mon, Dec 15, 2008 at 12:14 PM, Aaron Boodman wrote: > It would be better if we could consult Google for spelling > recommendations. It seems like I frequently misspell a word, get the > red squiggly, get no recommendations from Chromium, then go to Google > and it gets it exactly right. > > I know, this would be great for an extension. There is a bug in the current spellchecker where our suggestions don't work as well as they should. This was fixed a week or two ago on trunk. Brett --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to chromium-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Re: Inline spell checking.
Use this as the "example extension" for the extension design? On Mon, Dec 15, 2008 at 3:14 PM, Aaron Boodman wrote: > > It would be better if we could consult Google for spelling > recommendations. It seems like I frequently misspell a word, get the > red squiggly, get no recommendations from Chromium, then go to Google > and it gets it exactly right. > > I know, this would be great for an extension. > > - a > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to chromium-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
