This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17456 - 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
Summary: Regarding Section "The translate attribute": If I am writing prose of fiction...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 enhancement
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-09 23:44 UTC by contributor
Modified: 2015-06-26 05:37 UTC (History)
6 users (show)

See Also:


Attachments

Description contributor 2012-06-09 23:44:07 UTC
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
Comment 1 contributor 2012-07-18 07:22:59 UTC
This bug was cloned to create bug 17954 as part of operation convergence.
Comment 2 Erika Doyle Navara 2012-10-03 22:02:58 UTC
Moving to HTML.next as we work to lock down HTML5.0 for CR.
Comment 3 Robin Berjon 2013-01-21 15:59:34 UTC
Mass move to "HTML WG"
Comment 4 Robin Berjon 2013-01-21 16:02:19 UTC
Mass move to "HTML WG"
Comment 5 Michael[tm] Smith 2015-06-16 11:43:51 UTC
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.