17456 2012-06-09 23:44:07 +0000 Regarding Section "The translate attribute": If I am writing prose of fiction, and I write a name I don't want the translation mechanism to translate, then I understand I would set the attribute to "no" on that particular word. But. When I write (for exam 2015-06-26 05:37:42 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#top P3 enhancement --- 1 contributor dave.null cmhjones erika.doyle mike public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 68900 0 contributor 2012-06-09 23:44:07 +0000 Specification: http://dev.w3.org/html5/spec/spec.html Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: Regarding Section "The translate attribute": If I am writing prose of fiction, and I write a name I don't want the translation mechanism to translate, then I understand I would set the attribute to "no" on that particular word. But. When I write (for example) in Polish, then a declension could be applied to the word. The problem is, I'd like to instruct the software that when a translation (for example) to English is applied, the software should not translate the word, but only change its grammatical form to match that of the target language. For example, I am using the word "realm" in the meaning of "space" AND "kingdom", so if it's translated, then the double meaning will be lost. Since the specification says that "no" means to "leave it unchanged", what I understand means to not apply any transformation at all to the text, I cannot possibly instruct the software to act the way I'd want it to. This could be solved by a new text-level element, since it only applies to a text, or a boolean attribute on the span element. I understand it's an obscure problem, though. Posted from: 2001:470:71:12d:211:5bff:fe35:9864 User agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1145.0 Safari/537.1 70370 1 contributor 2012-07-18 07:22:59 +0000 This bug was cloned to create bug 17954 as part of operation convergence. 75263 2 erika.doyle 2012-10-03 22:02:58 +0000 Moving to HTML.next as we work to lock down HTML5.0 for CR. 81726 3 robin 2013-01-21 15:59:34 +0000 Mass move to "HTML WG" 81844 4 robin 2013-01-21 16:02:19 +0000 Mass move to "HTML WG" 121082 5 mike 2015-06-16 11:43:51 +0000 Resolving due to lack of any identified reporter plus the fact that this is not a high enough priority for anybody for us to justify the cost of continuing to track it.