From: "Черепанов Андрей" <sibskull@mail.ru>
To: "KDE рассылка" <kde-russian@lists.kde.ru>
Subject: [kde-russian] Fwd: [Bug 41558] KMail put rfc2231-encoded parameter values into DQUOTES.
Date: Fri, 16 Apr 2004 14:25:58 +0400
Message-ID: <200404161425.58501.sibskull@mail.ru> (raw)
Надеюсь, кому-нибудь кроме меня это нужно!
Кодирует русские названия файлов, чтобы пользователи Outlook их могли видеть
нормально, а не как ATT0005.doc :)
---------- Пересланное письмо: [Bug 41558] KMail put rfc2231-encoded
parameter values into DQUOTES. ----------
Subject: [Bug 41558] KMail put rfc2231-encoded parameter values into DQUOTES.
Date: 16 Апрель 2004 14:19
From: Andrey S.Cherepanov <sibskull@mail.ru>
To: kmail-devel@kde.org
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=41558
------- Additional Comments From sibskull mail ru 2004-04-16 12:19 -------
Created an attachment (id=5658)
--> (http://bugs.kde.org/attachment.cgi?id=5658&action=view)
KMail patch for Outlook comppatible attachment names encoding
I reopen this bug because I still need to send files with russian names to my
partners who have Outlook Express. Tested on KMail 1.6.1 from KDE 3.2.1.
Additionally I put option in configuration tab for pure russian people who
has similar problem. Now attachment name encode by RFC2047 only if option
"Outlook compatible attachment encoding".
Possible this option name is ugly. Please, correct me.
_______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel
-------------------------------------------------------
--
Андрей Черепанов
sibskull@mail.ru
reply other threads:[~2004-04-16 10:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200404161425.58501.sibskull@mail.ru \
--to=sibskull@mail.ru \
--cc=kde-russian@lists.kde.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
рассылка русскоязычной группы пользователей и разработчиков KDE
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/kde-russian/0 kde-russian/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 kde-russian kde-russian/ http://lore.altlinux.org/kde-russian \
kde-russian@lists.kde.ru
public-inbox-index kde-russian
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.kde-russian
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git