Your message dated Tue, 21 Feb 2006 01:10:41 +0100
with message-id <[EMAIL PROTECTED]>
and subject line closing sylpheed-gtk2 bugs
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.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: sylpheed-gtk2
Version: 0.9.99-2
Severity: normal
Tags: l10n
Upstream; not debian-specific.
My system locale is ISO-8859-1. If I send characters that are in this
character set, Sylpheed (correctly) uses "encoded word" to ensure that they
appear in the headers. All fine.
I recently began corresponding with Russian friends, using KOI8-R. I can
easily (easily enough) set the encoding for Sylpheed to KOI8-R, and type
Russian in the body of the email. Again, fine.
Sylpheed displays headers received from correspondents which contain
cyrillic characters in encoded-word format correctly. However, because
ISO-8859-1 doesn't include these characters, Sylpheed replaces them on
outgoing mail with underscores (really replaces them, that is, not just
replaces them on display; what's worse is that they seem to display
correctly, while composing, but are replaced with _____ _____ _____ when the
message is sent).
This happens even on replies. That is, for a reply, Sylpheed has seen the
encoded-word format for KOI8-R, and decoded it properly, and displays it.
But it won't wrap the headers back up in KOI8-R encoded word; instead it
discards them, replacing them with underscores.
Recommended: currently, the preferences for the client as a whole have to be
set to a different encoding in order to use a different encoding for a
particular message. Instead, add "Select Encoding" to the Message menu when
composing a message. Then, when preparing headers, check the message
encoding first, and use encoded-word with that charset in preference even to
the system locale.
This would significantly improve ease of use for users who correspond with
people whose native language is different.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages sylpheed-gtk2 depends on:
ii libatk1.0-0 1.8.0-4 The ATK accessibility toolkit
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libcompfaceg1 1989.11.11-24 Compress/decompress images for mai
ii libglib2.0-0 2.4.8-1 The GLib library of C routines
ii libgpgme6 0.3.16-2 GPGME - GnuPG Made Easy
ii libgtk2.0-0 2.4.14-2 The GTK+ graphical user interface
ii libldap2 2.1.30-3 OpenLDAP libraries
ii libpango1.0-0 1.6.0-3 Layout and rendering of internatio
ii libpisock8 0.11.8-10 Library for communicating with a P
ii libssl0.9.7 0.9.7e-3 SSL shared libraries
ii libx11-6 4.3.0.dfsg.1-10 X Window System protocol client li
ii xlibs 4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
> * #282187: sylpheed-gtk2 crashes when try to receive e-mails
> * #259448: sylpheed-gtk2: "From" name cut off at non-ascii characters
> * #265664: sylpheed-gtk2: text wrapping while typing broken for
> specific situation
> * #272398: sylpheed-gtk2 segfaults when sending attachments.
> * #292760: sylpheed-gtk2: discards characters in header with high bit
> set
> * #272369: sylpheed-gtk2: "reply-to mailing list" is not reliable
> * #254884: sylpheed-gtk2: GTK1 version is a lot faster
> * #257983: sylpheed-gtk2: Use system fonts, if available
These bugs were filed against the sylpheed-gtk2 package, now out of debian
because it was superseded by the official sylpheed gtk2 version (package
sylpheed). The bugs were assumed by the sylpheed package, but as far as I
can test these bugs are not present in current sylpheed (2.2.0). Therefore
I'm closing them with this mail.
Please, don't hesitate to file a new bug against sylpheed if you think
some of these bugs is still there. Other bug reports welcomed too! :)
thanks for reporting,
--
Ricardo Mones
~
You have the capacity to learn from mistakes. You'll learn a lot
today. /usr/games/fortune
--- End Message ---
