- From: CVS User jkosek <cvsmail@w3.org>
- Date: Mon, 17 Jun 2013 09:10:10 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv15211
Modified Files:
its20.html its20.odd
Log Message:
Copy-edits in Abstract and section 1.1
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/17 09:07:41 1.450
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/17 09:10:10 1.451
@@ -6,9 +6,9 @@
</style><link rel="stylesheet" href="local.css" type="text/css"/><link rel="stylesheet" type="text/css" href="base.css"/></head><body><div class="head">
<h1><a name="title" id="title" shape="rect"/>Internationalization Tag Set (ITS) Version 2.0</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Copy</h2><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright" shape="rect">Copyright</a> © 2013 <a href="http://www.w3.org/" shape="rect"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/" shape="rect"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/" shape="rect"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/" shape="rect">Keio</a>, <a href="http://ev.buaa.edu.cn/" shape="rect">Beihang</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer" shape="rect">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks" shape="rect">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents" shape="rect">document use</a> rules apply.</p</div><hr/><div>
-<h2><a name="abstract" id="abstract" shape="rect"/>Abstract</h2><p>The technology described in this document - the <em>Internationalization Tag Set (ITS)
- 2.0</em> - enhances the foundation to integrate automated processing of human language
- into core Web technologies. ITS 2.0 bears many commonalities with is predecessor, <a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0</a> but provides additional
+<h2><a name="abstract" id="abstract" shape="rect"/>Abstract</h2><p>The technology described in this document – the <em>Internationalization Tag Set (ITS)
+ 2.0</em> – enhances the foundation to integrate automated processing of human language
+ into core Web technologies. ITS 2.0 bears many commonalities with its predecessor, <a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0</a> but provides additional
concepts that are designed to foster the automated creation and processing of multilingual
Web content. ITS 2.0 focuses on HTML, XML-based formats in general, and can leverage
processing based on the XML Localization Interchange File Format (XLIFF), as well as the
@@ -147,13 +147,13 @@
<div class="toc1">I <a href="#acknowledgements" shape="rect">Acknowledgements</a> (Non-Normative)</div>
</div><hr/><div class="body"><div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="introduction" id="introduction" shape="rect"/>1 Introduction</h2><p>
- <em>This section is informative</em>
+ <em>This section is informative.</em>
</p><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="overview" id="overview" shape="rect"/>1.1 Overview</h3><p>
Content or software that is authored in one language (so-called
- original
+ source
language) for one locale (e.g. the French-speaking part of
@@ -161,9 +161,7 @@
with regard to other cultural aspects. A prevailing paradigm for
- the
-
- corresponding approach to multilingual production in many cases encompasses
+ multilingual production in many cases encompasses
three phases: internationalization, translation, and localization (see the <a href="http://www.w3.org/International/questions/qa-i18n/" shape="rect"> W3C's Internationalization Q&A</a>
@@ -197,137 +195,36 @@
internationalization.
-A proprietary XML vocabulary may for example may be internationalized by defining special markup to specify directionality in mixed direction text.
-
- </p><p>During the translation phase, the meaning of a source language
-
- text
-
- is
-
- analyzed, and a target language text that is equivalent in
-
- meaning
-
- is
-
- determined. In order to promote or ensure a translation's
-
- fidelity,
-
- national or international laws may for example regulate
-
- linguistic
-
- dimensions like mandatory terminology or standard
-
- phrases.
-
- </p><p>
-
- Although an agreed-upon definition of the localization phase is
-
- missing,
-
-this phase is usually seen as encompassing activities such as
-
- creating locale-specific content (e.g. adding a link for a
-
- country-specific reseller), or modifying functionality (e.g. to
-
- establish a fit with country-specific regulations for financial
-
- reporting).
-
- Sometimes, the insertion of special markup to support a
-
- local language
-
- or script is also subsumed under the localization phase.
+A proprietary XML vocabulary may be internationalized by defining special markup to specify directionality in mixed direction text.
- For
-
- example, people authoring in languages such as Arabic, Hebrew,
-
- Persian or Urdu need special markup to specify directionality in
-
- mixed
-
- direction text.
-
- </p><p>
-
- The technology described in this document - the
-
- <em>Internationalization Tag Set (ITS)
-
- 2.0</em>
-
- addresses some of the challenges and opportunities related to
-
- internationalization,
-
- translation, and localization. ITS 2.0 in
-
- particular contributes to concepts in the realm of meta data for
-
- internationalization,
-
- translation, and localization related to core Web
-
- technologies such as XML. ITS does for example assist in production scenarios in which parts of an
-
- XML-based document should not be translated. ITS 2.0 bears many
-
- commonalities with is
-
- predecessor,
-
- <a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0</a>
-
- but provides additional
-
- concepts that are designed to foster enhanced
-
- automated processing - e.g. based on language technology such as
-
- entity recognition - related to multilingual
-
- Web content.
-
- </p><p>
-
- Like ITS 1.0, ITS 2.0
-
- both identifies
-
- concepts (such as
-
- “Translate”
-
- ), and
-
- defines implementations of these concepts (termed “ITS data
-
- categories”)
-
- as a set of elements and attributes called the
-
- <em>Internationalization Tag Set
-
- (ITS)</em>
-
- . The
-
- definitions of ITS elements and attributes are provided in the
-
- form of RELAX NG
-
- <a title="Regular-grammar-based validation -- RELAX NG" href="#relaxng" shape="rect">[RELAX NG]</a>
-
- (normative).
-
- Since one major step from ITS 1.0 to ITS 2.0 relates to coverage for HTML, ITS 2.0 also establishes a relationship between ITS markup and the various HTML flavors. Furthermore, ITS 2.0 suggests when and how to leverage processing based on the XML Localization Interchange File Format (<a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> and <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a>), as well as the Natural Language Processing Interchange Format <a title="" href="#nif-reference" shape="rect">[NIF]</a>.</p><p>For the purpose of an introductory illustration, here is a series of examples related to the question, how ITS can indicate that certain parts of a document must not be translated.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-1" id="EX-motivation-its-1" shape="rect"/>Example 1: Document in which some content must not be translated</div><p>In this document it is difficult to distinguish betwee those <code>string</code> elements that should be translated and those that must not be translated. Explicit meta data is needed to resolve the issue.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><resources></strong>
+ </p><p>During the translation phase, the meaning of a source language text is analyzed,
+ and a target language text that is equivalent in meaning is determined. For example
+ national or international laws may regulate linguistic dimensions like mandatory
+ terminology or standard phrases in order to promote or ensure a translation's
+ fidelity.</p><p>Although an agreed-upon definition of the localization phase is missing, this
+ phase is usually seen as encompassing activities such as creating locale-specific
+ content (e.g. adding a link for a country-specific reseller), or modifying functionality
+ (e.g. to establish a fit with country-specific regulations for financial reporting).
+ Sometimes, the insertion of special markup to support a local language or script is also
+ subsumed under the localization phase. For example, people authoring in languages such
+ as Arabic, Hebrew, Persian or Urdu need special markup to specify directionality in
+ mixed direction text. </p><p>The technology described in this document – the <em>Internationalization Tag
+ Set (ITS) 2.0</em> addresses some of the challenges and opportunities related to
+ internationalization, translation, and localization. ITS 2.0 in particular contributes
+ to concepts in the realm of meta data for internationalization, translation, and
+ localization related to core Web technologies such as XML. ITS does for example assist
+ in production scenarios in which parts of an XML-based document should not be
+ translated. ITS 2.0 bears many commonalities with its predecessor, <a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0</a> but provides
+ additional concepts that are designed to foster enhanced automated processing – e.g.
+ based on language technology such as entity recognition – related to multilingual Web
+ content. </p><p> Like ITS 1.0, ITS 2.0 both identifies concepts (such as “Translate” ),
+ and defines implementations of these concepts (termed “ITS data categories”) as a set of
+ elements and attributes called the <em>Internationalization Tag Set (ITS)</em>. The
+ definitions of ITS elements and attributes are provided in the form of RELAX NG <a title="Regular-grammar-based validation -- RELAX NG" href="#relaxng" shape="rect">[RELAX NG]</a> (normative). Since one major step from ITS 1.0 to
+ ITS 2.0 relates to coverage for HTML, ITS 2.0 also establishes a relationship between
+ ITS markup and the various HTML flavors. Furthermore, ITS 2.0 suggests when and how to
+ leverage processing based on the XML Localization Interchange File Format (<a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> and <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a>), as
+ well as the Natural Language Processing Interchange Format <a title="" href="#nif-reference" shape="rect">[NIF]</a>.</p><p>For the purpose of an introductory illustration, here is a series of examples related to the question, how ITS can indicate that certain parts of a document must not be translated.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-1" id="EX-motivation-its-1" shape="rect"/>Example 1: Document in which some content must not be translated</div><p>In this document it is difficult to distinguish between those <code>string</code> elements that should be translated and those that must not be translated. Explicit meta data is needed to resolve the issue.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><resources></strong>
<strong class="hl-tag" style="color: #000096"><section</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"Homepage"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><arguments></strong>
<strong class="hl-tag" style="color: #000096"><string></strong>page<strong class="hl-tag" style="color: #000096"></string></strong>
@@ -361,7 +258,7 @@
<strong class="hl-tag" style="color: #000096"></component></strong>
<strong class="hl-tag" style="color: #000096"><component</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"789"</span> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"caption"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"text"</span> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>Cancel<strong class="hl-tag" style="color: #000096"></data></strong>
- <strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"position"</span><strong class="hl-tag" style="color: #000096">></strong>60,40<strong class="hl-tag" style="color: #000096"></data></strong>
+ <strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"position"</span><strong class="hl-tag" style="color: #000096">></strong>60,40<strong class="hl-tag" style="color: #000096"></data></strong>
<strong class="hl-tag" style="color: #000096"></component></strong>
<strong class="hl-tag" style="color: #000096"><component</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"792"</span> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"string"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"text"</span> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>Number of files: <strong class="hl-tag" style="color: #000096"></data></strong>
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/17 09:07:41 1.451
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/17 09:10:10 1.452
@@ -63,9 +63,9 @@
<translationloc role="spec-conditional" href="http://www.w3.org/2003/03/Translations/byTechnology?technology=its"/>
-->
<abstract>
- <p>The technology described in this document - the <emph>Internationalization Tag Set (ITS)
- 2.0</emph> - enhances the foundation to integrate automated processing of human language
- into core Web technologies. ITS 2.0 bears many commonalities with is predecessor, <loc
+ <p>The technology described in this document – the <emph>Internationalization Tag Set (ITS)
+ 2.0</emph> – enhances the foundation to integrate automated processing of human language
+ into core Web technologies. ITS 2.0 bears many commonalities with its predecessor, <loc
href="http://www.w3.org/TR/2007/REC-its-20070403/">ITS 1.0</loc> but provides additional
concepts that are designed to foster the automated creation and processing of multilingual
Web content. ITS 2.0 focuses on HTML, XML-based formats in general, and can leverage
@@ -132,7 +132,7 @@
<div xml:id="introduction">
<head>Introduction</head>
-<p><emph>This section is informative</emph></p>
+<p><emph>This section is informative.</emph></p>
<div xml:id="overview">
@@ -144,7 +144,7 @@
Content or software that is authored in one language (so-called
- original
+ source
language) for one locale (e.g. the French-speaking part of
@@ -152,9 +152,7 @@
with regard to other cultural aspects. A prevailing paradigm for
- the
-
- corresponding approach to multilingual production in many cases encompasses
+ multilingual production in many cases encompasses
three phases: internationalization, translation, and localization (see the <ref target="http://www.w3.org/International/questions/qa-i18n/"> W3C's Internationalization Q&A</ref>
@@ -190,144 +188,47 @@
internationalization.
-A proprietary XML vocabulary may for example may be internationalized by defining special markup to specify directionality in mixed direction text.
-
- </p>
-
- <p>During the translation phase, the meaning of a source language
-
- text
-
- is
-
- analyzed, and a target language text that is equivalent in
-
- meaning
-
- is
-
- determined. In order to promote or ensure a translation's
-
- fidelity,
-
- national or international laws may for example regulate
-
- linguistic
-
- dimensions like mandatory terminology or standard
-
- phrases.
-
- </p>
-
- <p>
-
- Although an agreed-upon definition of the localization phase is
-
- missing,
-
-this phase is usually seen as encompassing activities such as
-
- creating locale-specific content (e.g. adding a link for a
-
- country-specific reseller), or modifying functionality (e.g. to
-
- establish a fit with country-specific regulations for financial
-
- reporting).
-
- Sometimes, the insertion of special markup to support a
-
- local language
-
- or script is also subsumed under the localization phase.
-
- For
-
- example, people authoring in languages such as Arabic, Hebrew,
-
- Persian or Urdu need special markup to specify directionality in
-
- mixed
-
- direction text.
+A proprietary XML vocabulary may be internationalized by defining special markup to specify directionality in mixed direction text.
</p>
- <p>
-
- The technology described in this document - the
-
- <emph>Internationalization Tag Set (ITS)
-
- 2.0</emph>
-
- addresses some of the challenges and opportunities related to
-
- internationalization,
-
- translation, and localization. ITS 2.0 in
-
- particular contributes to concepts in the realm of meta data for
-
- internationalization,
-
- translation, and localization related to core Web
-
- technologies such as XML. ITS does for example assist in production scenarios in which parts of an
-
- XML-based document should not be translated. ITS 2.0 bears many
-
- commonalities with is
-
- predecessor,
-
- <ref target="http://www.w3.org/TR/2007/REC-its-20070403/">ITS 1.0</ref>
-
- but provides additional
-
- concepts that are designed to foster enhanced
-
- automated processing - e.g. based on language technology such as
-
- entity recognition - related to multilingual
-
- Web content.
-
- </p>
- <p>
-
- Like ITS 1.0, ITS 2.0
-
- both identifies
-
- concepts (such as
-
- <q>Translate</q>
-
- ), and
-
- defines implementations of these concepts (termed “ITS data
-
- categories”)
-
- as a set of elements and attributes called the
-
- <emph>Internationalization Tag Set
-
- (ITS)</emph>
-
- . The
-
- definitions of ITS elements and attributes are provided in the
-
- form of RELAX NG
-
- <ptr target="#relaxng" type="bibref" />
-
- (normative).
-
- Since one major step from ITS 1.0 to ITS 2.0 relates to coverage for HTML, ITS 2.0 also establishes a relationship between ITS markup and the various HTML flavors. Furthermore, ITS 2.0 suggests when and how to leverage processing based on the XML Localization Interchange File Format (<ptr target="#xliff1.2" type="bibref"/> and <ptr target="#xliff2.0" type="bibref"/>), as well as the Natural Language Processing Interchange Format <ptr target="#nif-reference" type="bibref"/>.</p>
+ <p>During the translation phase, the meaning of a source language text is analyzed,
+ and a target language text that is equivalent in meaning is determined. For example
+ national or international laws may regulate linguistic dimensions like mandatory
+ terminology or standard phrases in order to promote or ensure a translation's
+ fidelity.</p>
+
+ <p>Although an agreed-upon definition of the localization phase is missing, this
+ phase is usually seen as encompassing activities such as creating locale-specific
+ content (e.g. adding a link for a country-specific reseller), or modifying functionality
+ (e.g. to establish a fit with country-specific regulations for financial reporting).
+ Sometimes, the insertion of special markup to support a local language or script is also
+ subsumed under the localization phase. For example, people authoring in languages such
+ as Arabic, Hebrew, Persian or Urdu need special markup to specify directionality in
+ mixed direction text. </p>
+
+ <p>The technology described in this document – the <emph>Internationalization Tag
+ Set (ITS) 2.0</emph> addresses some of the challenges and opportunities related to
+ internationalization, translation, and localization. ITS 2.0 in particular contributes
+ to concepts in the realm of meta data for internationalization, translation, and
+ localization related to core Web technologies such as XML. ITS does for example assist
+ in production scenarios in which parts of an XML-based document should not be
+ translated. ITS 2.0 bears many commonalities with its predecessor, <ref
+ target="http://www.w3.org/TR/2007/REC-its-20070403/">ITS 1.0</ref> but provides
+ additional concepts that are designed to foster enhanced automated processing – e.g.
+ based on language technology such as entity recognition – related to multilingual Web
+ content. </p>
+ <p> Like ITS 1.0, ITS 2.0 both identifies concepts (such as <q>Translate</q> ),
+ and defines implementations of these concepts (termed “ITS data categories”) as a set of
+ elements and attributes called the <emph>Internationalization Tag Set (ITS)</emph>. The
+ definitions of ITS elements and attributes are provided in the form of RELAX NG <ptr
+ target="#relaxng" type="bibref"/> (normative). Since one major step from ITS 1.0 to
+ ITS 2.0 relates to coverage for HTML, ITS 2.0 also establishes a relationship between
+ ITS markup and the various HTML flavors. Furthermore, ITS 2.0 suggests when and how to
+ leverage processing based on the XML Localization Interchange File Format (<ptr
+ target="#xliff1.2" type="bibref"/> and <ptr target="#xliff2.0" type="bibref"/>), as
+ well as the Natural Language Processing Interchange Format <ptr target="#nif-reference"
+ type="bibref"/>.</p>
<p>For the purpose of an introductory illustration, here is a series of examples related to the question, how ITS can indicate that certain parts of a document must not be translated.</p>
<exemplum xml:id="EX-motivation-its-1">
Received on Monday, 17 June 2013 09:10:16 UTC