ISSUE-380: define an encoding for formerly latin1

define an encoding for formerly latin1

Raised by:
Addison Phillips
Opened on:

This issue tracks the bug listed above and was created as part of the WG LC process. The bug was created prior to the WG LC.


The web does not have latin1, but we do need it for HTTP and stuff. We should probably also expose it to the API.

"identity" makes some sense, but only in one direction. "bikeshed" also makes sense.

We should not expose this encoding to HTTP charset= or <meta> overrides. This is only for internal matters (such as XMLHttpRequest) and developers using the API.
Related Actions Items:
No related actions
Related emails:
  1. I18N-ISSUE-380 (BUG23971): define an encoding for formerly latin1 [encoding] (from on 2014-07-10)

Related notes:

These issues are now tracked at

Richard Ishida, 16 Sep 2015, 12:00:09

Display change log ATOM feed

Addison Phillips <>, Chair, Richard Ishida <>, Fuqiao Xue <>, Atsushi Shimono <>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $