(In reply to era eriksson from comment #81) > Note that the majority of the non-English sites I come across seem to > specify English as their language. Developers are not always aware that > there is a setting that they need to change, and some tools are hard-coded > to output a template which specifies English, so that the site owner cannot > override it even if they wanted to.
Awareness: I once wrote to a university to alert them that the title page of their rector, administrator and more stated "vacancies" ;-) And we're speaking not only of a single global language setting but of the hope that language attributes will be defined for fields or paragraphs (please fix your page so that I can type in). Taking Google Translation as an example of knowhow, they try to translate <code> when they certainly shouldn't and I never saw any page adding notranslate to code (except mine ;-) ). So, we must choose between relying on the above fuzziness to determine language or of relying on the user's notion of what's the language he's typing. (In reply to era eriksson from comment #82) > Or bug 676500 should be fixed instead of this one, or as well. +1 for the > other bug as the preferred solution. Yes, I think that bug 676500 seems simple enough to implemented first. Then we can post a message in the 30 or so (including duplicates) bugs describing an issue with choosing the language to ask if a problem remains. I have used multi-language spell checking with Eudora for many years and I can testify it's delightful. The only drawback could be that some words exist in one language that can allow a mistake in another. But, having used the French+English pair for which the risk is much higher than generally, I can tell it's a smaller nuisance that is by far counterbalanced by the advantage of being able to use foreign (English) terms or phrases in a French text. Is it better to use heuristics to have words determine a dictionary to be used to check those words? Bug 676500 is primarily targeted at e-mail, but that's the same spelling checker, issues and reply, isn't it. The other improvement to speed up spell checking is to determine what is not a word (all-uppercase? long strings, esp with digits and special characters, <code>, fixed width? etc...). I have quoted this reply to bug 676500. See you there, maybe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/303269 Title: Automatically select language for spell check based on user input To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/303269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
