From: "Artem K. Jouravsky" <ujo@ifirst.ru>
To: ALT community <community@altlinux.ru>
Subject: [Comm] Re: mutt & cyrillic fonts in headers
Date: Fri, 7 Mar 2003 13:10:27 +0300
Message-ID: <20030307101027.GA25818@ifirst.ru> (raw)
In-Reply-To: <20030307093219.GF23953@hell.immo>
[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]
On Fri, Mar 07, 2003 at 12:32:19PM +0300, Alexey I. Froloff wrote:
> > Господа, а можно ли научить mutt понимать русские имена
> > приложенных аттачей, так же как он это делает с сабжектами, они
> > ведь точно так же кодируются... А? Есть проблема с кучей
> > пользователей из вражеского окружения... Когда они шлют лично
> > мне, тут проблем не возникает, но ведь есть ещё и рассылки...
>
> 6.3.206. rfc2047_parameters
>
> Type: boolean
> Default: no
>
> When this variable is set, Mutt will decode RFC-2047-encoded MIME
> parameters. You want to set this variable when mutt suggests you to
> save attachments to files named like this:
> =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
>
> When this variable is set interactively, the change doesn't have the
> desired effect before you have changed folders.
>
> Note that this use of RFC 2047's encoding is explicitly, prohibited by
> the standard, but nevertheless encountered in the wild. Also note
> that setting this parameter will not have the effect that mutt
> generates this kind of encoding. Instead, mutt will unconditionally
> use the encoding specified in RFC 2231.
thanx
--
Best wishes, | ICQ 103399444
Artem K. Jouravsky, | JID ujo@jabber.ru
iFirst Ltd, System Administrator.
-----------------------
И даже Макашев немножечко Альберт.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-03-07 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 9:22 [Comm] " Artem K. Jouravsky
2003-03-07 9:32 ` Alexey I. Froloff
2003-03-07 10:10 ` Artem K. Jouravsky [this message]
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=20030307101027.GA25818@ifirst.ru \
--to=ujo@ifirst.ru \
--cc=community@altlinux.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
ALT Linux Community general discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/community/0 community/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 community community/ http://lore.altlinux.org/community \
mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
public-inbox-index community
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.community
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git