[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#344304: marked as done (qa.debian.org: no charset specified when browsing news)

Your message dated Thu, 7 Aug 2008 23:26:18 -0300
with message-id <20080808022618.GA28385@usha.takhisis.invalid>
and subject line Re: Bug#344304: qa.debian.org: no charset specified when browsing news
has caused the Debian Bug report #344304,
regarding qa.debian.org: no charset specified when browsing news
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
344304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344304
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: qa.debian.org
Severity: important
Tags: l10n


When browsing news in Package Tracking System, e.g.

http://packages.qa.debian.org/r/rus-ispell/news/1.html

there is no charset specified neither in HTTP headers, nor in META tag
within the web page. So, non-ASCII characters are not displayed
correctly.

The solution may be to output UTF-8 encoding by default in Content-Type
HTTP header. Documents that use a non-UTF-8 encoding can override this
using the META tag in the HTML document's header.

-- System Information:
Debian Release: 3.1
Architecture: i386 (i586)
Kernel: Linux 2.6.8-2-386
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)

--- End Message ---
--- Begin Message --- 
On Mon, Feb 20, 2006 at 06:46:11AM +0100, Adeodato Simó wrote:
> > First, the mail in question didn't specifify a Content-Type-Encoding
> > header, while being utf8. It should've done so.
> 
>   (#337968, jftr.)

And in fact, that bug being now fixed, the charset used in PTS news is
now fixed as well. Using rus-ispell as an example, you can verify that
the last broken news is:

  http://packages.qa.debian.org/r/rus-ispell/news/20070827T120206Z.html

while starting from:

  http://packages.qa.debian.org/r/rus-ispell/news/20071223T153207Z.html

the charset is properly set and hence the UTF-8 characters are properly
displayed.

As such, I'm closing this bug. Note that this will not fix all old .html
messages, but I personally do not think it is worth going through the
hassle of fixing the past.

Cheers.

-- 
Stefano Zacchiroli -*- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
I'm still an SGML person,this newfangled /\ All one has to do is hit the
XML stuff is so ... simplistic  -- Manoj \/ right keys at the right time

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: