W3C home > Mailing lists > Public > html-tidy@w3.org > July to September 2000

Sounds like a job for Tidy (was: Bug#62700: marked as done (charset should be specified before TITLE) (fwd))

From: Erik Rossen <rossen@freesurf.ch>
Date: Thu, 3 Aug 2000 16:37:34 +0200 (MEST)
To: html-tidy@w3.org
Message-ID: <Pine.LNX.4.21.0008031629370.16647-100000@laptop.rossen.ch>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This message recently showed up in the Debian Bug Tracking System.  I've 
editted it to cut down on headers and automatically generated text.

The problem is a bit nit-picky, but it brings up the question: is it
Tidy's job to fix standard <META> information as well as HTML/DHTML/XML?

Erik Rossen                         ^
rossen@freesurf.ch                 /e\
http://www.multimania.com/rossen   ---   GPG key ID: 2935D0B9

- --- Forwarded message ----------------------------------------------------
Date: Wed, 19 Apr 2000 16:19:10 -0500 (CDT)
From: Klaus Weide <kweide@enteract.com>
To: submit@bugs.debian.org
Subject: charset should be specified before TITLE

Package: www.debian.org
Version: current

The order of tags found in translated (as well as English) pages is
(This one is from <URL:http://www.debian.org/index.ru.html> - KOI8-R
encoding transliterated here for this mail):

   <HEAD>
   <TITLE>Debian GNU/Linux -- Universal'naya Operacionnaya Sistema</TITLE>
   <LINK REV="made" HREF="mailto:webmaster@debian.org">
   <META http-equiv="Content-Type" content="text/html; charset=koi8-r">
   .....

The META tag specifying the charset should appear *before* any text that
needs this information in order to be correctly decoded - here: the
TITLE element's content.

This would help browsers that do a one-pass through the document and
don't apply the charset info retroactively - specifically, lynx.
I haven't checked what other browsers do, but expect them to also be
helped by a different order.  It's more logical, after all.

Much better yet would be: put the charset info *where it belongs*,
in the HTTP header, instead of relying on HTTP-EQUIV.

   Klaus

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: Made with pgp4pine 1.75

iD8DBQE5iYOyY88aPik10LkRAkmsAKCj9pYd/ZIE+cx5clO4chFazfgG8ACeL05o
fkmu/Hwmoe332IogvFtUcnA=
=uEpp
-----END PGP SIGNATURE-----
Received on Thursday, 3 August 2000 11:43:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 April 2012 06:13:44 GMT