On 31/08/2015 08:12, Anne van Kesteren wrote:
HTML4 is long obsolete.
OK, the HTML5 definition is here:
http://www.w3.org/TR/html5/dom.html#the-lang-and-xml:lang-attributes
It comes to the same result.
4) Fall-back options including the locale and others.
"Polyglot users" unset "spellchecker.dictionary" and enter the text in the
language the site requires. However, they lose "spellchecker.dictionary" as
a fall-back, so their fall-back would be their locale (see point 4).
If you speak multiple languages you have to actively unset an
about:config setting?
If is was set in the past. Default install won't have it set.
As I said, this should be offered as an option in the UI, since
currently there is no direct access to "spellchecker.dictionary",
although the value is used in weird and wonderful ways. This bug is
about cleaning up behaviour that confuses the user and establishing a
clear priority.
The UI could read:
Preferred spell check language:
- Use language defined by website
- Override with (dictionary of your choice)
Note: In both cases a site specific language can be chosen.
FWIW, as someone who uses two languages, what I've always wanted is
that the spellchecker can use multiple dictionaries at once. Quite
often when a site accepts text input it's some kind of communication
tool. And the communication tool doesn't know what language you use to
communicate and the language you use to communicate will not always be
the same.
Multiple dictionaries in the same text field? That's unlikely to be
implemented any time soon.
Multiple dictionaries in different text fields already works, as long as
no overrides are set. Try:
<html><head>
<meta http-equiv="Content-Language" content="en-AU">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
</head>
<body>
<div style="background-color:#eee;border:1px solid #000;padding:10px"
contenteditable="">
<div>root en-AU</div>
</div>
<hr>
<div style="background-color:#eee;border:1px solid #000;padding:10px"
lang="en-GB" contenteditable="">
<div>root en-AU, but element en-GB</div>
</div>
</body></html>
The point of this discussion is whether there is objection to the new
priority suggested:
1) Content preference
2) "spellchecker.dictionary", if set
3) language determined by site
4) Fall-back options including the locale and others.
Jorg K.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
