HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
808122661Closer integration with encoding.spec.whatwg.org2013-07-23 23:16
@@ -1182,21 +1182,21 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
 <!--ADD-TOPIC:Security-->
    <dt>Errors that risk exposing authors to security attacks</dt>
 
    <dd>
 
     <p>Certain restrictions exist purely to avoid known security problems.</p>
 
     <div class="example">
 
      <p>For example, the restriction on using UTF-7 exists purely to avoid authors falling prey to a
-     known cross-site-scripting attack using UTF-7.</p>
+     known cross-site-scripting attack using UTF-7. <a href="#refsUTF7">[UTF7]</a></p>
 
     </div>
 
    </dd>
 <!--REMOVE-TOPIC:Security-->
 
 
    <dt>Cases where the author's intent is unclear</dt>
 
    <dd>
@@ -1816,35 +1816,34 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
   WHATWG Encoding standard. An <span>encoding</span> has an <dfn>encoding name</dfn> and one or more
   <dfn title="encoding label">encoding labels</dfn>, referred to as the encoding's <i>name</i> and
   <i>labels</i> in the Encoding specification. <a
   href="#refsENCODING">[ENCODING]</a></p>
 
   <p>An <dfn>ASCII-compatible character encoding</dfn> is a single-byte or variable-length
   <span>encoding</span> in which the bytes 0x09, 0x0A, 0x0C, 0x0D, 0x20 - 0x22, 0x26, 0x27, 0x2C -
   0x3F, 0x41 - 0x5A, and 0x61 - 0x7A<!-- is that list ok? do any character sets we want to support
   do things outside that range? -->, ignoring bytes that are the second and later bytes of multibyte
   sequences, all correspond to single-byte sequences that map to the same Unicode characters as
-  those bytes in ANSI_X3.4-1968 (US-ASCII). <a href="#refsRFC1345">[RFC1345]</a></p>
+  those bytes in Windows-1252<!--ANSI_X3.4-1968 (US-ASCII)-->. <a href="#refsENCODING">[ENCODING]</a></p>
 
   <p class="note">This includes such encodings as Shift_JIS, HZ-GB-2312, and variants of ISO-2022,
   even though it is possible in these encodings for bytes like 0x70 to be part of longer sequences
   that are unrelated to their interpretation as ASCII. It excludes UTF-16 variants, as well as
   obsolete legacy encodings such as UTF-7, GSM03.38, and EBCDIC variants.</p>
 
   <!--
    We'll have to change that if anyone comes up with a way to have a document that is valid as two
    different encodings at once, with different <meta charset> elements applying in each case.
   -->
 
-  <p>The term <dfn>a UTF-16 encoding</dfn> refers to any variant of UTF-16: self-describing UTF-16
-  with a BOM, ambiguous UTF-16 without a BOM, raw UTF-16LE, and raw UTF-16BE. <a
-  href="#refsRFC2781">[RFC2781]</a></p>
+  <p>The term <dfn>a UTF-16 encoding</dfn> refers to any variant of UTF-16: UTF-16LE or UTF-16BE,
+  regardless of the presence or absence of a BOM. <a href="#refsENCODING">[ENCODING]</a></p>
 
   <p>The term <dfn>code unit</dfn> is used as defined in the Web IDL specification: a 16 bit
   unsigned integer, the smallest atomic component of a <code>DOMString</code>. (This is a narrower
   definition than the one used in Unicode, and is not the same as a <i>code point</i>.) <a
   href="#refsWEBIDL">[WEBIDL]</a></p>
 
   <p>The term <dfn>Unicode code point</dfn> means a <i title="">Unicode scalar value</i> where
   possible, and an isolated surrogate code point when not. When a conformance requirement is defined
   in terms of characters or Unicode code points, a pair of <span title="code unit">code units</span>
   consisting of a high surrogate followed by a low surrogate must be treated as the single code
@@ -2204,20 +2203,24 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
 
      <li>The <dfn>UTF-8 decode</dfn> algorithm which takes a byte stream and returns a character
      stream, additionally stripping one leading UTF-8 Byte Order Mark (BOM), if any
 
     </ul>
 
     <p class="note">The <span>UTF-8 decoder</span> is distinct from the <i>UTF-8 decode
     algorithm</i>. The latter first strips a Byte Order Mark (BOM), if any, and then invokes the
     former.</p>
 
+    <p>For readability, character encodings are sometimes referenced in this specification with a
+    case that differs from the canonical case given in the encoding standard. (For example,
+    "UTF-16LE" instead of "utf16-le".)</p>
+
    </dd>
 
 
    <dt>XML</dt>
 
    <dd>
 
     <p>Implementations that support <span>the XHTML syntax</span> must support some version of XML,
     as well as its corresponding namespaces specification, because that syntax uses an XML
     serialization with namespaces. <a href="#refsXML">[XML]</a> <a href="#refsXMLNS">[XMLNS]</a></p>
@@ -96673,27 +96676,20 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
   href="#refsSCSU">[SCSU]</a></p>
 
   <p>Support for encodings based on EBCDIC is especially discouraged. This encoding is rarely used
   for publicly-facing Web content. Support for UTF-32 is also especially discouraged. This encoding
   is rarely used, and frequently implemented incorrectly.</p>
 
   <p class="note">This specification does not make any attempt to support EBCDIC-based encodings and
   UTF-32 in its algorithms; support and use of these encodings can thus lead to unexpected behavior
   in implementations of this specification.</p>
 
-  <p>When a user agent is to use the self-describing UTF-16 encoding but no Byte Order Mark (BOM)
-  has been found, user agents must default to little-endian UTF-16.</p>
-
-  <p class="note">The requirement to default UTF-16 to little-endian rather than big-endian is a
-  <span>willful violation</span> of RFC 2781, motivated by a desire for compatibility with legacy
-  content. <a href="#refsRFC2781">[RFC2781]</a></p>
-
 
   <h5>Changing the encoding while parsing</h5>
 
   <p>When the parser requires the user agent to <dfn>change the encoding</dfn>, it must run the
   following steps. This might happen if the <span>encoding sniffing algorithm</span> described above
   failed to find a character encoding, or if it found a character encoding that was not the actual
   encoding of the file.</p>
 
   <ol>
 
@@ -115750,23 +115746,20 @@ if (s = prompt('What is your name?')) {
 
    <dt id="refsBECSS">[BECSS]</dt>
    <dd><cite><a href="http://www.w3.org/TR/becss/">Behavioral Extensions to CSS</a></cite>, I. Hickson. W3C.</dd>
 
    <dt id="refsBEZIER">[BEZIER]</dt>
    <dd><cite>Courbes &agrave; poles</cite>, P. de Casteljau. INPI, 1959.</dd>
 
    <dt id="refsBIDI">[BIDI]</dt>
    <dd><cite><a href="http://www.unicode.org/reports/tr9/">UAX #9: Unicode Bidirectional Algorithm</a></cite>, M. Davis. Unicode Consortium.</dd>
 
-   <dt id="refsBIG5">[BIG5]</dt>
-   <dd>(Non-normative) <cite>Chinese Coded Character Set in Computer</cite>. Institute for Information Industry, March 1984.</dd>
-
    <dt id="refsBOCU1">[BOCU1]</dt>
    <dd>(Non-normative) <cite><a href="http://www.unicode.org/notes/tn6/">UTN #6: BOCU-1: MIME-Compatible Unicode Compression</a></cite>, M. Scherer, M. Davis. Unicode Consortium.</dd>
 
    <dt id="refsCESU8">[CESU8]</dt>
    <dd>(Non-normative) <cite><a href="http://www.unicode.org/reports/tr26/">UTR #26: Compatibility Encoding Scheme For UTF-16: 8-BIT (CESU-8)</a></cite>, T. Phipps. Unicode Consortium.</dd>
 
    <dt id="refsCHARMOD">[CHARMOD]</dt>
    <dd>(Non-normative) <cite><a href="http://www.w3.org/TR/charmod/">Character Model for the World Wide Web 1.0: Fundamentals</a></cite>, M. D&uuml;rst, F. Yergeau, R. Ishida, M. Wolf, T. Texin. W3C.</dd>
 
    <dt id="refsCLDR">[CLDR]</dt>
@@ -115778,24 +115771,21 @@ if (s = prompt('What is your name?')) {
    <dt id="refsCOMPUTABLE">[COMPUTABLE]</dt>
    <dd>(Non-normative) <cite><a href="http://www.turingarchive.org/browse.php/B/12">On computable numbers, with an application to the Entscheidungsproblem</a></cite>, A. Turing. In <cite>Proceedings of the London Mathematical Society</cite>, series 2, volume 42, pages 230-265. London Mathematical Society, 1937.</dd>
 
    <dt id="refsCOOKIES">[COOKIES]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc6265">HTTP State Management Mechanism</a></cite>, A. Barth. IETF.</dd>
 
    <dt id="refsCORS">[CORS]</dt>
    <dd><cite><a href="http://fetch.spec.whatwg.org/">Cross-Origin Resource Sharing</a></cite>, A. van Kesteren. WHATWG.</dd>
 
    <dt id="refsCP50220">[CP50220]</dt>
-   <dd><cite><a href="http://www.iana.org/assignments/charset-reg/CP50220">CP50220</a></cite>, Y. Naruse. IANA.</dd> <!-- really should be "NARUSE, Y." or some such, but there's a western bias to these references for consistency. sorry. -->
-
-   <dt id="refsCP51932">[CP51932]</dt>
-   <dd><cite><a href="http://www.iana.org/assignments/charset-reg/CP51932">CP51932</a></cite>, Y. Naruse. IANA.</dd> <!-- really should be "NARUSE, Y." or some such, but there's a western bias to these references for consistency. sorry. -->
+   <dd>(Non-normative) <cite><a href="http://www.iana.org/assignments/charset-reg/CP50220">CP50220</a></cite>, Y. Naruse. IANA.</dd> <!-- really should be "NARUSE, Y." or some such, but there's a western bias to these references for consistency. sorry. -->
 
    <dt id="refsCSP">[CSP]</dt>
    <dd>(Non-normative) <cite><a href="http://dvcs.w3.org/hg/content-security-policy/raw-file/tip/csp-specification.dev.html">Content Security Policy</a></cite>, B. Sterne, A. Barth. W3C.</dd>
 
    <dt id="refsCSS">[CSS]</dt>
    <dd><cite><a href="http://www.w3.org/TR/CSS2/">Cascading Style Sheets Level 2 Revision 1</a></cite>, B. Bos, T. &Ccedil;elik, I. Hickson, H. Lie. W3C.</dd>
 
    <dt id="refsCSSANIMATIONS">[CSSANIMATIONS]</dt>
    <dd>(Non-normative) <cite><a href="http://dev.w3.org/csswg/css3-animations/">CSS Animations</a></cite>, D. Jackson, D. Hyatt, C. Marrin, S. Galineau, L. Baron. W3C.</dd>
 
@@ -115923,23 +115913,20 @@ if (s = prompt('What is your name?')) {
 
    <dt id="refsIEEE754">[IEEE754]</dt>
    <dd><cite><a href="http://ieeexplore.ieee.org/servlet/opac?punumber=4610933">IEEE Standard for Floating-Point Arithmetic (IEEE 754)</a></cite>. IEEE. ISBN 978-0-7381-5753-5.</dd>
 
    <dt id="refsISO3166">[ISO3166]</dt>
    <dd><cite><a href="http://www.iso.org/iso/home/standards/country_codes.htm">ISO 3166: Codes for the representation of names of countries and their subdivisions</a></cite>. ISO.</dd>
 
    <dt id="refsISO8601">[ISO8601]</dt>
    <dd>(Non-normative) <cite><a href="http://isotc.iso.org/livelink/livelink/4021199/ISO_8601_2004_E.zip?func=doc.Fetch&amp;nodeid=4021199">ISO8601: Data elements and interchange formats &mdash; Information interchange &mdash; Representation of dates and times</a></cite>. ISO.</dd>
 
-   <dt id="refsISO885911">[ISO885911]</dt>
-   <dd><cite><a href="http://std.dkuug.dk/jtc1/sc2/open/02n3333.pdf">ISO-8859-11: Information technology &mdash; 8-bit single-byte coded character sets &mdash; Part 11: Latin/Thai alphabet</a></cite>. ISO.</dd>
-
    <dt id="refsJLREQ">[JLREQ]</dt>
    <dd><cite><a href="http://www.w3.org/TR/jlreq/">Requirements for Japanese Text Layout</a></cite>. W3C.</dd> <!-- too many editors to list -->
 
    <dt id="refsJPEG">[JPEG]</dt>
    <dd><cite><a href="http://www.w3.org/Graphics/JPEG/jfif3.pdf">JPEG File Interchange Format</a></cite>, E. Hamilton.</dd>
 
    <dt id="refsJSON">[JSON]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc4627">The application/json Media Type for JavaScript Object Notation (JSON)</a></cite>, D. Crockford. IETF.</dd>
 
    <dt id="refsJSURL">[JSURL]</dt>
@@ -116019,51 +116006,51 @@ if (s = prompt('What is your name?')) {
    <dt id="refsRFC1034">[RFC1034]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc1034">Domain Names - Concepts and Facilities</a></cite>, P. Mockapetris. IETF, November 1987.</dd>
 
    <dt id="refsRFC1123">[RFC1123]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc1123">Requirements for Internet Hosts -- Application and Support</a></cite>, R. Braden. IETF, October 1989.</dd>
 
    <dt id="refsRFC1321">[RFC1321]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc1321">The MD5 Message-Digest Algorithm</a></cite>, R. Rivest. IETF.</dd>
 
    <dt id="refsRFC1345">[RFC1345]</dt>
-   <dd><cite><a href="http://tools.ietf.org/html/rfc1345">Character Mnemonics and Character Sets</a></cite>, K. Simonsen. IETF.</dd>
+   <dd>(Non-normative) <cite><a href="http://tools.ietf.org/html/rfc1345">Character Mnemonics and Character Sets</a></cite>, K. Simonsen. IETF.</dd>
 
    <dt id="refsRFC1468">[RFC1468]</dt>
-   <dd><cite><a href="http://tools.ietf.org/html/rfc1468">Japanese Character Encoding for Internet Messages</a></cite>, J. Murai, M. Crispin, E. van der Poel. IETF.</dd>
+   <dd>(Non-normative) <cite><a href="http://tools.ietf.org/html/rfc1468">Japanese Character Encoding for Internet Messages</a></cite>, J. Murai, M. Crispin, E. van der Poel. IETF.</dd>
 
    <dt id="refsRFC1494">[RFC1494]</dt>
    <dd>(Non-normative) <cite><a href="http://tools.ietf.org/html/rfc1494">Equivalences between 1988 X.400 and RFC-822 Message Bodies</a></cite>, H. Alvestrand, S. Thompson. IETF.</dd>
 
    <dt id="refsRFC1554">[RFC1554]</dt>
-   <dd><cite><a href="http://tools.ietf.org/html/rfc1554">ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP</a></cite>, M. Ohta, K. Handa. IETF.</dd>
+   <dd>(Non-normative) <cite><a href="http://tools.ietf.org/html/rfc1554">ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP</a></cite>, M. Ohta, K. Handa. IETF.</dd>
 
    <dt id="refsRFC1557">[RFC1557]</dt>
-   <dd><cite><a href="http://tools.ietf.org/html/rfc1557">Korean Character Encoding for Internet Messages</a></cite>, U. Choi, K. Chon, H. Park. IETF.</dd>
+   <dd>(Non-normative) <cite><a href="http://tools.ietf.org/html/rfc1557">Korean Character Encoding for Internet Messages</a></cite>, U. Choi, K. Chon, H. Park. IETF.</dd>
 
    <dt id="refsRFC1842">[RFC1842]</dt>
-   <dd><cite><a href="http://tools.ietf.org/html/rfc1842">ASCII Printable Characters-Based Chinese Character Encoding for Internet Messages</a></cite>, Y. Wei, Y. Zhang, J. Li, J. Ding, Y. Jiang. IETF.</dd>
+   <dd>(Non-normative) <cite><a href="http://tools.ietf.org/html/rfc1842">ASCII Printable Characters-Based Chinese Character Encoding for Internet Messages</a></cite>, Y. Wei, Y. Zhang, J. Li, J. Ding, Y. Jiang. IETF.</dd>
 
    <dt id="refsRFC1922">[RFC1922]</dt>
-   <dd><cite><a href="http://tools.ietf.org/html/rfc1922">Chinese Character Encoding for Internet Messages</a></cite>, HF. Zhu, DY. Hu, ZG. Wang, TC. Kao, WCH. Chang, M. Crispin. IETF.</dd>
+   <dd>(Non-normative) <cite><a href="http://tools.ietf.org/html/rfc1922">Chinese Character Encoding for Internet Messages</a></cite>, HF. Zhu, DY. Hu, ZG. Wang, TC. Kao, WCH. Chang, M. Crispin. IETF.</dd>
 
    <dt id="refsRFC2045">[RFC2045]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a></cite>, N. Freed, N. Borenstein. IETF.</dd>
 
    <dt id="refsRFC2046">[RFC2046]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a></cite>, N. Freed, N.  Borenstein. IETF.</dd> <!-- for text/plain and "Internet Media type"; not for definition of "valid MIME type". -->
 
    <dt id="refsRFC2119">[RFC2119]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a></cite>, S. Bradner. IETF.</dd>
 
    <dt id="refsRFC2237">[RFC2237]</dt>
-   <dd><cite><a href="http://tools.ietf.org/html/rfc2237">Japanese Character Encoding for Internet Messages</a></cite>, K. Tamaru. IETF.</dd>
+   <dd>(Non-normative) <cite><a href="http://tools.ietf.org/html/rfc2237">Japanese Character Encoding for Internet Messages</a></cite>, K. Tamaru. IETF.</dd>
 
    <dt id="refsRFC2246">[RFC2246]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc2246">The TLS Protocol Version 1.0</a></cite>, T. Dierks, C. Allen. IETF.</dd>
 
    <dt id="refsRFC2313">[RFC2313]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc2313">PKCS #1: RSA Encryption</a></cite>, B. Kaliski. IETF.</dd>
 
    <dt id="refsRFC2318">[RFC2318]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc2318">The text/css Media Type</a></cite>, H. Lie, B. Bos, C. Lilley. IETF.</dd>
 
@@ -116072,23 +116059,20 @@ if (s = prompt('What is your name?')) {
 
    <dt id="refsRFC2397">[RFC2397]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc2397">The "data" URL scheme</a></cite>, L. Masinter. IETF.</dd>
 
    <dt id="refsRFC2445">[RFC2445]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc2445">Internet Calendaring and Scheduling Core Object Specification (iCalendar)</a></cite>, F. Dawson, D. Stenerson. IETF.</dd>
 
    <dt id="refsRFC2483">[RFC2483]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc2483">URI Resolution Services Necessary for URN Resolution</a></cite>, M. Mealling, R. Daniel. IETF.</dd>
 
-   <dt id="refsRFC2781">[RFC2781]</dt>
-   <dd><cite><a href="http://tools.ietf.org/html/rfc2781">UTF-16, an encoding of ISO 10646</a></cite>, P. Hoffman, F. Yergeau. IETF.</dd>
-
    <dt id="refsRFC3676">[RFC3676]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc3676">The Text/Plain Format and DelSp Parameters</a></cite>, R. Gellens. IETF.</dd>
 
    <dt id="refsRFC2806">[RFC2806]</dt>
    <dd>(Non-normative) <cite><a href="http://tools.ietf.org/html/rfc2806">URLs for Telephone Calls</a></cite>, A. Vaha-Sipila. IETF.</dd>
 
    <dt id="refsRFC3023">[RFC3023]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc3023">XML Media Types</a></cite>, M. Murata, S. St. Laurent, D. Kohn. IETF.</dd>
 
    <dt id="refsRFC3279">[RFC3279]</dt>
@@ -116190,34 +116174,31 @@ if (s = prompt('What is your name?')) {
    <dt id="refsUNICODE">[UNICODE]</dt>
    <dd><cite><a href="http://www.unicode.org/versions/">The Unicode Standard</a></cite>. Unicode Consortium.</dd>
 
    <dt id="refsUNIVCHARDET">[UNIVCHARDET]</dt>
    <dd>(Non-normative) <cite><a href="http://www.mozilla.org/projects/intl/UniversalCharsetDetection.html">A composite approach to language/encoding detection</a></cite>, S. Li, K. Momoi. Netscape. In <cite>Proceedings of the 19th International Unicode Conference</cite>.</dd>
 
    <dt id="refsURL">[URL]</dt>
    <dd><cite><a href="http://url.spec.whatwg.org/">URL</a></cite>, A. van Kesteren. WHATWG.</dd>
 
    <dt id="refsUTF7">[UTF7]</dt>
-   <dd><cite><a href="http://tools.ietf.org/html/rfc2152">UTF-7: A Mail-Safe Transformation Format of Unicode</a></cite>, D. Goldsmith, M. Davis. IETF.</dd>
+   <dd>(Non-normative) <cite><a href="http://tools.ietf.org/html/rfc2152">UTF-7: A Mail-Safe Transformation Format of Unicode</a></cite>, D. Goldsmith, M. Davis. IETF.</dd>
 
    <dt id="refsUTF8DET">[UTF8DET]</dt>
    <dd>(Non-normative) <cite><a href="http://www.w3.org/International/questions/qa-forms-utf-8">Multilingual form encoding</a></cite>, M. D&uuml;rst. W3C.</dd>
 
    <dt id="refsUTR36">[UTR36]</dt>
    <dd>(Non-normative) <cite><a href="http://www.unicode.org/reports/tr36/">UTR #36: Unicode Security Considerations</a></cite>, M. Davis, M. Suignard. Unicode Consortium.</dd>
 
    <dt id="refsWCAG">[WCAG]</dt>
    <dd>(Non-normative) <cite><a href="http://www.w3.org/TR/WCAG20/">Web Content Accessibility Guidelines (WCAG) 2.0</a></cite>, B. Caldwell, M. Cooper, L. Reid, G. Vanderheiden. W3C.</dd>
 
-   <dt id="refsWEBADDRESSES">[WEBADDRESSES]</dt>
-   <dd><cite><a href="http://www.w3.org/html/wg/href/draft">Web addresses in HTML5</a></cite>, D. Connolly, C. Sperberg-McQueen.</dd>
-
    <dt id="refsWEBGL">[WEBGL]</dt>
    <dd><cite><a href="http://www.khronos.org/registry/webgl/specs/latest/">WebGL Specification</a></cite>, D. Jackson. Khronos Group.</dd>
 
    <dt id="refsWEBIDL">[WEBIDL]</dt>
    <dd><cite><a href="http://dev.w3.org/2006/webapi/WebIDL/">Web IDL</a></cite>, C. McCormack. W3C.</dd>
 
    <dt id="refsWEBLINK">[WEBLINK]</dt>
    <dd><cite><a href="http://tools.ietf.org/html/rfc5988">Web Linking</a></cite>, M. Nottingham. IETF.</dd>
 
    <dt id="refsWEBMCG">[WEBMCG]</dt>

|