4
What steps is the experiment of this attribute and when will the browsers begin to accept its use? And someone can understand and risks explaining what will be their real usefulness in the elements of HTML?
1 answer
5
No one can adequately answer the first part. The second part, at its core, will also serve no purpose. Futurology is not the goal here.
The attribute translate serves to give semantics to the content and tools will be created or better adapted to take advantage of this additional information. In theory the online content translation tools or some internal developer can make decisions on how to proceed with that content. It will probably have little relevance and use, much effort for a very select audience, depending on the need.
Example of use:
<p>I bring an apple and my <span translate="no">Apple</span> to school.</p>
Company name will not be translated.
Browser other questions tagged html html5
You are not signed in. Login or sign up in order to post.
A big question is: after the attribute starts to be accepted by the browsers, whenever you want to allow the translation of the elements I will have to inform Translate="yes" for each one? Usually wouldn’t it be better if all the elements accepted by default the translation and in the elements that should not allow translation use a Boolean attribute named "notranslate"? But as you have already said: futurology is not our goal. Thank you for the answer ;)
– Ingrid Farabulini
From what I understand of the proposal you don’t need, it’s more to mark what you shouldn’t translate. But I also understand that each tool will be able to adopt a different posture, I just think it will escape the pattern not to do so.
– Maniero