Your message dated 31 Jul 2000 17:22:31 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Bug#62700: Acknowledgement (charset should be specified before
TITLE)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 19 Apr 2000 21:19:17 +0000
Received: (qmail 4482 invoked from network); 19 Apr 2000 21:19:15 -0000
Received: from mail.enteract.com (207.229.143.33)
by master.debian.org with SMTP; 19 Apr 2000 21:19:15 -0000
Received: from shell-3.enteract.com ([EMAIL PROTECTED] [207.229.143.42])
by mail.enteract.com (8.9.3/8.9.3) with SMTP id QAA34917
for <[EMAIL PROTECTED]>; Wed, 19 Apr 2000 16:19:11 -0500 (CDT)
(envelope-from [EMAIL PROTECTED])
Date: Wed, 19 Apr 2000 16:19:10 -0500 (CDT)
From: Klaus Weide <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: charset should be specified before TITLE
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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:[EMAIL PROTECTED]">
<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
---------------------------------------
Received: (at 62700-done) by bugs.debian.org; 31 Jul 2000 14:22:49 +0000
>From [EMAIL PROTECTED] Mon Jul 31 09:22:48 2000
Return-path: <[EMAIL PROTECTED]>
Received: from twilight.cs.hut.fi [130.233.40.5]
by master.debian.org with esmtp (Exim 3.12 2 (Debian))
id 13JGSt-0003VT-00; Mon, 31 Jul 2000 09:22:47 -0500
Received: (from localhost user: 'tvainika' uid#31164 fake: STDIN
([EMAIL PROTECTED])) by mail.niksula.cs.hut.fi
id <S20972317AbQGaOWb>; Mon, 31 Jul 2000 17:22:31 +0300
Sender: Tommi Henrik Vainikainen <[EMAIL PROTECTED]>
Fake-Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Bug#62700: Acknowledgement (charset should be specified before
TITLE)
From: Tommi Vainikainen <[EMAIL PROTECTED]>
Date: 31 Jul 2000 17:22:31 +0300
Message-ID: <[EMAIL PROTECTED]>
Lines: 5
User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.5
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
I just checked some pages (index.ru.html, index.fi.html) and I think
this bug has been fixed. Therefore I'm closing this bug now.
--
Tommi Vainikainen
