- From: <bugzilla@jessica.w3.org>
- Date: Wed, 27 Jul 2011 18:32:32 +0000
- To: public-html@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13397 Summary: i18n-ISSUE-78: Spellchecking in editors and sc services Product: HTML WG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: public-i18n-core@w3.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org 7.6 Spelling and grammar checking http://www.w3.org/TR/html5/editing.html#spelling-and-grammar-checking On behalf of the i18n WG. The spellcheck attribute currently is limited to user-edited text. It would be useful to have some way of identifying content that should not be spellchecked in an editor or by an automated spellchecking service. It would seem most intuitive to use the same attribute for this, but more carefully distinguish between the case where the user agent is dealing with user editable text and non-user-editable text, if necessary. On the other hand, perhaps a different attribute would keep the two different usages clearer. (Browsers should also consider the language set by the lang (or xml:lang) attribute when choosing which content to check. It is very useful if the editor or service ignores content that is not in the language of the currently set spellchecker dictionary (oXygen and XMeTaL both do this, for example). Particularly useful for handling text containing fragments in more than one language.) -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Wednesday, 27 July 2011 18:32:33 UTC