13397 2011-07-27 18:32:31 +0000 i18n-ISSUE-78: Spellchecking in editors and sc services 2014-02-21 14:58:35 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC All RESOLVED NEEDSINFO P2 normal --- 1 public-i18n-core ian ayg ian ishida mike public-html-admin public-html-wg-issue-tracking www-international public-html-bugzilla oldest_to_newest 51570 0 public-i18n-core 2011-07-27 18:32:31 +0000 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.) 51583 1 ayg 2011-07-27 22:14:36 +0000 What are the use-cases? What applications would be expected to use this extra information, and what pages would want to support those applications? 53488 2 mike 2011-08-04 05:14:20 +0000 mass-move component to LC1 54925 3 ian 2011-08-14 06:29:50 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: see comment 1 — need more information for proper assessment 101108 4 ishida 2014-02-21 14:58:35 +0000 I'll give an example to try to make this clearer. It's currently possible to use the translate attribute to indicate to translation tools that content should remain untranslated - this is very useful for translation editing environments, but also for submission of pages to automated translation services. When I author an article I run it through a spellchecker in my editor. I may also run it through an online spellchecking service. Often my article contains text that throws up issues that are false positives. Take, for example, http://www.w3.org/2002/01/spellchecker?uri=http://www.w3.org/International/questions/qa-personal-names.en.php I'd like to be able to indicate that the spellchecker should ignore the elements surrounding examples of personal names in this article, so that I can see the important spelling errors that are buried in the list. It seems like an attribute similar to the translate attribute would be useful here. On the other hand, it would be more useful to be able to say in the document head that all elements of type x with classname y in section z should be ignored, which is a more ITS-like approach.