[Bug 13392] New: i18n-ISSUE-72: BOM as preferred encoding declaration

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13392

           Summary: i18n-ISSUE-72: BOM as preferred encoding declaration
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML/XHTML Compatibility Authoring Guide (ed: Eliot
                    Graff)
        AssignedTo: eliotgra@microsoft.com
        ReportedBy: public-i18n-core@w3.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, eliotgra@microsoft.com


3. Specifying a Document's Character Encoding
http://www.w3.org/TR/html-polyglot/#character-encoding

"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.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 27 July 2011 17:51:43 UTC