W3C home > Mailing lists > Public > public-i18n-core@w3.org > July to September 2011

I18N-ISSUE-130: Health warning about no file-internal encoding in JS [HTML5-prep]

From: Internationalization Core Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Sat, 23 Jul 2011 19:14:50 +0000
To: public-i18n-core@w3.org
Message-Id: <E1Qkhf0-0004vF-3y@lowblow.w3.org>

I18N-ISSUE-130: Health warning about no file-internal encoding in JS [HTML5-prep]

http://www.w3.org/International/track/issues/130

Raised by: Addison Phillips
On product: HTML5-prep

4.3.1 The script element
http://www.w3.org/TR/html5/scripting-1.html#the-script-element

Talking about the <script> element. We find this description of 'charset':

--
The charset attribute gives the character encoding of the external script resource. The attribute must not be specified if the src attribute is not present. If the attribute is set, its value must be a valid character encoding name, must be an ASCII case-insensitive match for the preferred MIME name for that encoding, and must match the encoding given in the charset parameter of the Content-Type metadata of the external file, if any.
--

Not sure if there should be a health warning here. Note that, unlike CSS, JavaScript files have no file-internal encoding announcement .
Received on Saturday, 23 July 2011 19:14:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 23 July 2011 19:14:51 GMT