- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Fri, 14 Dec 2012 09:40:58 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv8654
Modified Files:
its20.html its20.odd
Log Message:
another edit on issue-60, see http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2012Dec/0031.html
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2012/12/13 16:27:09 1.304
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2012/12/14 09:40:57 1.305
@@ -3288,7 +3288,7 @@
</td><td rowspan="1" colspan="1">Necessary text has been omitted from the localization or source.</td><td rowspan="1" colspan="1">
<ul><li><p>One or more segments found in the source that should have been translated are
missing in the target.</p></li></ul>
- </td><td rowspan="1" colspan="1">S or T</td><td rowspan="1" colspan="1">This type should not be used for missing whitespace or formatting codes, but
+ </td><td rowspan="1" colspan="1">S or T</td><td rowspan="1" colspan="1">This value should not be used for missing whitespace or formatting codes, but
instead should be reserved for linguistic content.</td></tr><tr><td rowspan="1" colspan="1">
<code>untranslated</code>
</td><td rowspan="1" colspan="1">Content that should have been translated was left untranslated.</td><td rowspan="1" colspan="1">
@@ -3346,7 +3346,7 @@
DD.MM.YYYY.</p></li><li><p>A text for the Irish market uses American-style foot and inch measurements
instead of centimeters.</p></li><li><p>A text intended for a U.S.-based audience uses U.K. spellings such as “centre”
and “colour.”</p></li></ul>
- </td><td rowspan="1" colspan="1">S or T</td><td rowspan="1" colspan="1">This category should be used for spelling errors only if they relate specifically
+ </td><td rowspan="1" colspan="1">S or T</td><td rowspan="1" colspan="1">This value should be used for spelling errors only if they relate specifically
to locale expectations (e.g., a text consitently uses British instead of U.S.
spellings for a text intended for the U.S.). If these errors are not systematic (e.g.,
a text uses U.S. spellings but has a single instance of “centre”), they should instead
@@ -3413,7 +3413,7 @@
</td><td rowspan="1" colspan="1">There is an issue related to the internationalization of content.</td><td rowspan="1" colspan="1">
<ul><li><p>A line of programming code has embedded language-specific strings.</p></li><li><p>A user interface element leaves no room for text expansion.</p></li><li><p>A form allows only for U.S.-style postal addresses and expects five digit U.S.
ZIP codes.</p></li></ul>
- </td><td rowspan="1" colspan="1">S or T</td><td rowspan="1" colspan="1">There are many kinds of internationalization issues. This category is therefore
+ </td><td rowspan="1" colspan="1">S or T</td><td rowspan="1" colspan="1">There are many kinds of internationalization issues. This value is therefore
very heterogeneous in what it can refer to.</td></tr><tr><td rowspan="1" colspan="1">
<code>length</code>
</td><td rowspan="1" colspan="1">There is a significant difference in source and target length.</td><td rowspan="1" colspan="1">
@@ -3424,23 +3424,23 @@
</td><td rowspan="1" colspan="1">The issue either has not been categorized or cannot be categorized.</td><td rowspan="1" colspan="1">
<ul><li><p>A new version of a tool returns information on an issue that has not been
previously checked and that is not yet classified.</p></li><li><p>A text is defective in ways to defy categorization, such as the appearance of nonsense garbled text of unknown origin (e.g., a translation shows an unintelligible result and/or appears unrelated to the source material).</p></li></ul>
- </td><td rowspan="1" colspan="1">S or T</td><td rowspan="1" colspan="1">This category has the following uses: <ol class="depth1"><li><p>A tool can use it to pass through quality data from another tool in cases
+ </td><td rowspan="1" colspan="1">S or T</td><td rowspan="1" colspan="1">This value has the following uses: <ol class="depth1"><li><p>A tool can use it to pass through quality data from another tool in cases
where the issues from the other tool are not classified (for example, a
localization quality assurance tool interfaces with a third-party grammar
- checker).</p></li><li><p>A tool's issues are not yet assigned to categories, and, until an updated
+ checker).</p></li><li><p>A tool's issues are not yet assigned to values, and, until an updated
assignment is made, they may be listed as <code>uncategorized</code>. In this case
- it is recommended that issues be assigned to appropriate categories as soon as
- possible since uncategorized does not foster interoperability.</p></li><li><p><code>uncategorized</code> can be used where a portion of text is defective in a way that defies assignment to a category in either the originating system or in any other ITS localization quality markup to indicate that it is uncategorizable.</p></li></ol>
+ it is recommended that issues be assigned to appropriate values as soon as
+ possible since <code>uncategorized</code> does not foster interoperability.</p></li><li><p><code>uncategorized</code> can be used where a portion of text is defective in a way that defies assignment to a value in either the originating system or in any other ITS localization quality markup to indicate that it is uncategorizable.</p></li></ol>
</td></tr><tr><td rowspan="1" colspan="1">
<code>other</code>
</td><td rowspan="1" colspan="1">Any issue that cannot be assigned to any values listed above.</td><td rowspan="1" colspan="1"/><td rowspan="1" colspan="1">S or T</td><td rowspan="1" colspan="1">
- <ul><li><p>This category allows for the inclusion of any issues not included in the
+ <ul><li><p>This value allows for the inclusion of any issues not included in the
previously listed values. This value <a href="#rfc-keywords" shape="rect">MUST NOT</a> be
used for any tool- or model-specific issues that can be mapped to the values
listed above.</p></li><li><p>In addition, this value is not synonymous with <code>uncategorized</code> in
that <code>uncategorized</code> issues may be assigned to another precise value,
- while other issues cannot.</p></li><li><p>If a system has an "miscellaneous" or "other" category, it <a href="#rfc-keywords" shape="rect">MUST</a> be mapped to this value even if the specific
- instance of the issue might be mapped to another category.</p></li></ul>
+ while other issues cannot.</p></li><li><p>If a system has an "miscellaneous" or "other" value, it <a href="#rfc-keywords" shape="rect">MUST</a> be mapped to this value even if the specific
+ instance of the issue might be mapped to another value.</p></li></ul>
</td></tr></tbody></table></div><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="its-schemas" id="its-schemas" shape="rect"/>D Schemas for ITS</h2><p>The following schemas define ITS elements and attributes and can be used as building
blocks when you want to integrate ITS markup into your own XML vocabulary. You can see
@@ -5699,7 +5699,7 @@
<code class="its-attr-markup">its-storage-size</code>, <code class="its-attr-markup">its-storage-encoding</code>?, <code class="its-attr-markup">lits-line-break-type</code>?</td></tr></tbody></table></div><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="revisionlog" id="revisionlog" shape="rect"/>I Revision Log (Non-Normative)</h2><p id="changelog-since-20121206">The following log records major changes that have been
made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20121206/" shape="rect">ITS 2.0 Working Draft 6 December 2012</a>.</p><ol class="depth1"><li><p>Fixed <a href="#EX-its-tool-annotation-1" shape="rect">Example 26</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/58" shape="rect">issue-58</a>.</p></li><li><p>Clarified text in <a class="section-ref" href="#basic-concepts-addingpointing" shape="rect">Section 2.3: Adding Information or Pointing to Existing Information</a> and
- <a class="section-ref" href="#selection-global" shape="rect">Section 5.2.1: Global, Rule-based Selection</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/59" shape="rect">issue-59</a>.</p></li><li><p>Clarified the definition of <code>uncategorized</code> in <a class="section-ref" href="#lqissue-typevalues" shape="rect">Appendix C: Values for the Localization Quality Issue Type</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/60" shape="rect">issue-60</a>.</p></li><li><p>Clarified definition of <a href="#lqissue-global" shape="rect">Localization Quality Issue</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/62" shape="rect">issue-62</a>.</p></li></ol><p id="changelog-since-20121023">The following log records major changes that have been
+ <a class="section-ref" href="#selection-global" shape="rect">Section 5.2.1: Global, Rule-based Selection</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/59" shape="rect">issue-59</a>.</p></li><li><p>Clarified the definition of <code>uncategorized</code> in <a class="section-ref" href="#lqissue-typevalues" shape="rect">Appendix C: Values for the Localization Quality Issue Type</a>, and (see <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2012Dec/0031.html" shape="rect">related mail</a>) used "<span class="quote">value</span>" consistently instead of "<span class="quote">category</span>" to refer to the value types. See <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/60" shape="rect">issue-60</a>.</p></li><li><p>Clarified definition of <a href="#lqissue-global" shape="rect">Localization Quality Issue</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/62" shape="rect">issu-62</a>.</p></li></ol><p id="changelog-since-20121023">The following log records major changes that have been
made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20121023/" shape="rect">ITS 2.0 Working Draft 23 October 2012</a>.</p><ol class="depth1"><li><p>Clarified usage of <a href="#domain" shape="rect">Domain</a> data category in HTML in
response to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/56" shape="rect">issue-56</a>.</p></li><li><p>Added the <a href="#lqissueDefs" shape="rect">enabled information</a> in <a class="section-ref" href="#lqissue" shape="rect">Section 8.17: Localization Quality Issue</a>.</p></li><li><p>Updated the <a href="#Disambiguation" shape="rect">Disambiguation</a> data category.</p></li><li><p>Fine tuned the algorithm to compute the result values of the <a href="#domain" shape="rect">Domain</a> data category.</p></li><li><p>Fix on <a href="#EX-locQualityIssue-html5-local-2" shape="rect">Example 81</a>:
<code>id</code> attribute of <code>script</code> element now the same as of containing
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2012/12/13 16:27:10 1.303
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2012/12/14 09:40:58 1.304
@@ -4823,7 +4823,7 @@
missing in the target.</item>
</list></cell>
<cell>S or T</cell>
- <cell>This type should not be used for missing whitespace or formatting codes, but
+ <cell>This value should not be used for missing whitespace or formatting codes, but
instead should be reserved for linguistic content.</cell>
</row>
<row>
@@ -4928,7 +4928,7 @@
and “colour.”</item>
</list></cell>
<cell>S or T</cell>
- <cell>This category should be used for spelling errors only if they relate specifically
+ <cell>This value should be used for spelling errors only if they relate specifically
to locale expectations (e.g., a text consitently uses British instead of U.S.
spellings for a text intended for the U.S.). If these errors are not systematic (e.g.,
a text uses U.S. spellings but has a single instance of “centre”), they should instead
@@ -5059,7 +5059,7 @@
ZIP codes.</item>
</list></cell>
<cell>S or T</cell>
- <cell>There are many kinds of internationalization issues. This category is therefore
+ <cell>There are many kinds of internationalization issues. This value is therefore
very heterogeneous in what it can refer to.</cell>
</row>
<row>
@@ -5082,16 +5082,16 @@
</list>
</cell>
<cell>S or T</cell>
- <cell>This category has the following uses: <list type="ordered">
+ <cell>This value has the following uses: <list type="ordered">
<item>A tool can use it to pass through quality data from another tool in cases
where the issues from the other tool are not classified (for example, a
localization quality assurance tool interfaces with a third-party grammar
checker).</item>
- <item>A tool's issues are not yet assigned to categories, and, until an updated
+ <item>A tool's issues are not yet assigned to values, and, until an updated
assignment is made, they may be listed as <code>uncategorized</code>. In this case
- it is recommended that issues be assigned to appropriate categories as soon as
- possible since uncategorized does not foster interoperability.</item>
- <item><code>uncategorized</code> can be used where a portion of text is defective in a way that defies assignment to a category in either the originating system or in any other ITS localization quality markup to indicate that it is uncategorizable.</item>
+ it is recommended that issues be assigned to appropriate values as soon as
+ possible since <code>uncategorized</code> does not foster interoperability.</item>
+ <item><code>uncategorized</code> can be used where a portion of text is defective in a way that defies assignment to a value in either the originating system or in any other ITS localization quality markup to indicate that it is uncategorizable.</item>
</list>
</cell>
</row>
@@ -5101,16 +5101,16 @@
<cell/>
<cell>S or T</cell>
<cell><list type="unordered">
- <item>This category allows for the inclusion of any issues not included in the
+ <item>This value allows for the inclusion of any issues not included in the
previously listed values. This value <ref target="#rfc-keywords">MUST NOT</ref> be
used for any tool- or model-specific issues that can be mapped to the values
listed above.</item>
<item>In addition, this value is not synonymous with <code>uncategorized</code> in
that <code>uncategorized</code> issues may be assigned to another precise value,
while other issues cannot.</item>
- <item>If a system has an "miscellaneous" or "other" category, it <ref
+ <item>If a system has an "miscellaneous" or "other" value, it <ref
target="#rfc-keywords">MUST</ref> be mapped to this value even if the specific
- instance of the issue might be mapped to another category.</item>
+ instance of the issue might be mapped to another value.</item>
</list></cell>
</row>
</table>
@@ -5550,9 +5550,9 @@
<item>Fixed <ptr target="#EX-its-tool-annotation-1" type="exref"/>, see <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/58">issue-58</ref>.</item>
<item>Clarified text in <ptr target="#basic-concepts-addingpointing" type="specref"/> and
<ptr target="#selection-global" type="specref"/>, see <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/59">issue-59</ref>.</item>
- <item>Clarified the definition of <code>uncategorized</code> in <ptr type="specref" target="#lqissue-typevalues"/>, see <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/60">issue-60</ref>.</item>
+ <item>Clarified the definition of <code>uncategorized</code> in <ptr type="specref" target="#lqissue-typevalues"/>, and (see <ref target="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2012Dec/0031.html">related mail</ref>) used <quote>value</quote> consistently instead of <quote>category</quote> to refer to the value types. See <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/60">issue-60</ref>.</item>
<item>Clarified definition of <ref target="#lqissue-global">Localization Quality Issue</ref>, see <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/62">issue-62</ref>.</item>
- </list>
+ </list>
<p xml:id="changelog-since-20121023">The following log records major changes that have been
made to this document since the <ref target="http://www.w3.org/TR/2012/WD-its20-20121023/"
>ITS 2.0 Working Draft 23 October 2012</ref>.</p>
Received on Friday, 14 December 2012 09:41:24 UTC