ISSUE-72: BOM as preferred encoding declaration

BOM as preferred encoding declaration

State:
CLOSED
Product:
polyglot
Raised by:
Richard Ishida
Opened on:
2011-07-22
Description:
"By using the Byte Order Mark (BOM) character (preferred)."

Although the BOM at the start of an HTML file is recognised by most major browsers these days, there are some issues associated with using it:

For example, a BOM can cause problems with files served using the latest version of PHP, it produces quirks mode in IE6, it overrides HTTP encoding declarations in some browsers - which can be problematic in the case of server-based transcoding, and some authoring tools either don't allow you to set the BOM or don't save with/without the bom properly.

We are happy to leave the above line in the spec, we would just like to see the text "(preferred)" removed.

Another reason for this is our preference for visible in-document encoding declarations, which you mention a little further down.
Related Actions Items:
No related actions
Related emails:
  1. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2013-09-05)
  2. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2013-09-04)
  3. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2013-09-04)
  4. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2013-09-04)
  5. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2012-11-10)
  6. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2012-11-10)
  7. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2012-07-12)
  8. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2012-07-12)
  9. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2012-07-12)
  10. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2012-07-11)
  11. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2012-07-11)
  12. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2012-07-11)
  13. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2012-05-03)
  14. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-11-03)
  15. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-08-13)
  16. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-08-11)
  17. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-08-05)
  18. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-08-04)
  19. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-08-04)
  20. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-08-01)
  21. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-07-29)
  22. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-07-29)
  23. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-07-29)
  24. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-07-28)
  25. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-07-28)
  26. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-07-28)
  27. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-07-28)
  28. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-07-28)
  29. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-07-28)
  30. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-07-27)
  31. [Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-07-27)
  32. [Bug 13392] New: i18n-ISSUE-72: BOM as preferred encoding declaration (from bugzilla@jessica.w3.org on 2011-07-27)
  33. [minutes] Internationalization WG telecon 2011-07-27 (from ishida@w3.org on 2011-07-27)
  34. I18N-ISSUE-72: BOM as preferred encoding declaration [Polyglot-prep] (from sysbot+tracker@w3.org on 2011-07-22)

Related notes:

[aphillip]: accepted for Polyglot LC

27 Jul 2011, 15:39:30

There seems to be convergence on the proposal to change the first two sub-bullets to say something to the effect of:

- By using the Byte Order Mark (BOM) character, which is an encoding
signature that both XML and HTML parsers are required to support.
- By using <meta charset="UTF-8"/> (the HTML encoding declaration) and
thus, for XML parsers, rely on XML´s encoding default (see above).

If this sticks, we can close this issue.

Richard Ishida, 12 Jul 2012, 11:34:31

Display change log ATOM feed


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