Persona is no longer an option for authentication on BMO. For more details see Persona Deprecated.
Last Comment Bug 408824 - Use the W3C recommendations for (doctype and) charset
: Use the W3C recommendations for (doctype and) charset
Status: NEW
Product: SeaMonkey
Classification: Client Software
Component: Composer (show other bugs)
: Trunk
: x86 Windows XP
: -- enhancement (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
Depends on: 92525
  Show dependency treegraph
Reported: 2007-12-18 07:09 PST by Charles
Modified: 2010-02-18 07:00 PST (History)
2 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---


Description Charles 2007-12-18 07:09:17 PST
User-Agent:       Opera/9.24 (Windows NT 5.1; U; en)
Build Identifier: 

I see the default doctype that Composer uses is HTML 4.1 Transitional with charset iso-8859-1. There are more modern doctypes and charset that the W3C recommends and I think the default should be XHTML 1.0 Strict and UTF-8. The UTF-8 charset is especially important because with iso-8859-1, only western european languages work properly. Any other language breaks with iso-8859-1. So if you really want to keep HTML 4.1, at least use UTF-8 as default.

Reproducible: Always

Steps to Reproduce:
1. Open Composer
2. Click the "HTML Source" tab
Actual Results:  
HTML 4.1 Transitional + iso-8859-1

Expected Results:  
XHTML 1.0 Strict + utf-8
Comment 1 Serge Gautherie (:sgautherie) 2008-05-06 17:37:35 PDT
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9b4pre) Gecko/2008022601 SeaMonkey/2.0a1pre] (nightly) (W2Ksp4)

Confirming, but morphing to the charset issue only;
the doctype issue is bug 92525.

The charset can be edited in the Source View,
but is reverted to ISO-8859-1 when changing view,
and, this, without any warning :-<
Comment 2 Keith Higgs 2010-02-18 07:00:41 PST
I was able to get successful validation via W3C validator by updating ~/template/en/default/global/header.html.tmpl as follows:

Locate the following lines ...
    <title>[% title %]</title>

Insert this line immediately after ...
    <meta http-equiv="Content-type" content="text/html;charset=UTF-8">

Note You need to log in before you can comment on or make changes to this bug.