Your message dated Thu, 20 Mar 2008 15:46:58 +0100
with message-id <[EMAIL PROTECTED]>
and subject line solved by archive regeneration
has caused the Debian Bug report #366027,
regarding lists.debian.org online lists archive do not properly decode
q/b-encoded subjects with koi8-r or utf-8 encoding in debian-russian
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 [EMAIL PROTECTED]
immediately.)
--
366027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=366027
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: lists.debian.org
Severity: normal
Debian online lists archive do not properly decode q/b-encoded subjects
(at least in debian-russian@ archive) in list of messages if they are
encoded with KOI8-R or UTF-8 encoding.
Have a look at
http://lists.debian.org/debian-russian/2006/05/threads.html
most of the subjects are non properly decoded, while the link
to http://lists.debian.org/debian-russian/2006/05/msg00027.html
is properly encoded.
Non-decoded subjects specify koi8-r, KOI8-R, utf-8 or UTF-8
as encoding, while the properly decoded subject uses 'windows-1251'.
I suppose something weird with encodings is here, as only properly
decoded encoding is 'windows-1251'.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (800, 'testing'), (700, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.16-1-686
Locale: LANG=C, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
--- End Message ---
--- Begin Message ---
Hi,
it seems that this bug is completely solved for all of our archive at
least since the recent list archive regeneration.
Kind regards
T.
--
Thomas Viehmann, http://thomas.viehmann.net/
--- End Message ---
