- From: poot <cvsmail@w3.org>
- Date: Sun, 4 Oct 2009 20:17:53 +0900 (JST)
- To: public-html-diffs@w3.org
hixie: Elaborate on 'non-legacy'; fix misuse of 'recommended'. (whatwg r4071) http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3232&r2=1.3233&f=h http://html5.org/tools/web-apps-tracker?from=4070&to=4071 =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.3232 retrieving revision 1.3233 diff -u -d -r1.3232 -r1.3233 --- Overview.html 4 Oct 2009 10:14:00 -0000 1.3232 +++ Overview.html 4 Oct 2009 11:17:39 -0000 1.3233 @@ -1318,11 +1318,11 @@ as "DOM5 HTML".<p>There are various concrete syntaxes that can be used to transmit resources that use this abstract language, two of which are defined in this specification.<p>The first such concrete syntax is the HTML syntax. This is the - format recommended for most authors. It is compatible with most - legacy Web browsers. If a document is transmitted with the - <a href="#mime-type">MIME type</a> <code><a href="#text-html">text/html</a></code>, then it will be - processed as an HTML document by Web browsers. This specification - defines version 5 of the HTML syntax, known as "HTML5".<p>The second concrete syntax is the XHTML syntax, which is an + format suggested for most authors. It is compatible with most legacy + Web browsers. If a document is transmitted with the <a href="#mime-type">MIME + type</a> <code><a href="#text-html">text/html</a></code>, then it will be processed as an + HTML document by Web browsers. This specification defines version 5 + of the HTML syntax, known as "HTML5".<p>The second concrete syntax is the XHTML syntax, which is an application of XML. When a document is transmitted with an <a href="#xml-mime-type">XML MIME type</a>, such as <code><a href="#application-xhtml-xml">application/xhtml+xml</a></code>, then it is treated as an XML document by Web browsers, to be parsed by an @@ -54004,9 +54004,11 @@ <li><p>Otherwise, return an implementation-defined or user-specified default character encoding, with the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> - <i>tentative</i>. In non-legacy environments, the more + <i>tentative</i>. In controlled environments or in environments + where the encoding of documents can be prescribed (for example, for + user agents intended for dedicated use in new networks), the more comprehensive <code title="">UTF-8</code> encoding is - recommended. Due to its use in legacy content, <code title="">windows-1252</code> is recommended as a default in + suggested. Due to its use in legacy content, <code title="">windows-1252</code> is suggested as a default in predominantly Western demographics instead.</li> </ol><p>The <a href="#document-s-character-encoding">document's character encoding</a> must immediately
Received on Sunday, 4 October 2009 11:18:25 UTC