content-translation-issues: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
m (→‎Issues: italicisie)
(Added comment about translate=no and class=notranslate)
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
=Content Translation Issues=
=Content Translation Issues=


Issues related to the use of microformats to influence the translation of content into other languages.
Issues related to the use of microformats to influence the [[content-translation|translation of content into other languages]], and their pronunciation by screen readers and aural browsers.


== Template ==
== Template ==
Line 15: Line 15:


* {{OpenIssue}} 2007-06-10 raised by [[User:AndyMabbett|Andy Mabbett]].
* {{OpenIssue}} 2007-06-10 raised by [[User:AndyMabbett|Andy Mabbett]].
*# Do we need a separate microformat for text which should not be translated, such as "''teacher, teacher''" in:
*# <p>Do we need a separate microformat for text which should not be translated, such as "''teacher, teacher''" in:<!--


:::The Great Tit, ''Parus major'', has a song that sounds like "teacher, teacher"  
--><blockquote>The Great Tit, ''Parus major'', has a song that sounds like "teacher, teacher"</blockquote><!--


::but which is not otherwise a component of a microformat? (Or maybe that should just be a style, attribute, or element, in HTML5).
-->but which is not otherwise a component of a microformat? (Or maybe that should just be a style, attribute, or element, in HTML5).</p><!--
 
--><p>(Comment by [[User:Bbos|Bbos]]:) Probably not needed for HTML5, which has a built-in <code>translate=no</code> attribute. But for HTML4 it might be useful to declare its predecessor, <code>class=notranslate</code>, to be a microformat on its own. See [http://www.w3.org/International/questions/qa-translate-flag Using HTML's translate attribute].</p>


==See also==
==See also==
*[[content-translation]]
*[[content-translation]]
*[[internationalization]]
*[[internationalization]]

Latest revision as of 17:00, 31 May 2016

Content Translation Issues

Issues related to the use of microformats to influence the translation of content into other languages, and their pronunciation by screen readers and aural browsers.

Template

Please use this format (copy and paste this to the beginning of the list to add your issues):

* {{OpenIssue}} YYYY-MM-DD raised by ~~~.
*# Here is the first issue I have.
*# Here is the second issue I have (delete if only one; add more if needed).

Issues

  • open issue! 2007-06-10 raised by Andy Mabbett.
    1. Do we need a separate microformat for text which should not be translated, such as "teacher, teacher" in:

      The Great Tit, Parus major, has a song that sounds like "teacher, teacher"

      but which is not otherwise a component of a microformat? (Or maybe that should just be a style, attribute, or element, in HTML5).

      (Comment by Bbos:) Probably not needed for HTML5, which has a built-in translate=no attribute. But for HTML4 it might be useful to declare its predecessor, class=notranslate, to be a microformat on its own. See Using HTML's translate attribute.

See also