Gnus development mailing list
 help / color / mirror / Atom feed
From: Hobbit <werehobbit@yandex.ru>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: bugs@gnus.org,  ding@gnus.org
Subject: Re: bug#8070: gnus damages attached file
Date: Sun, 20 Feb 2011 12:46:10 +0200	[thread overview]
Message-ID: <87ei73dlvx.fsf@myhost.localdomain> (raw)
In-Reply-To: <m2tyfz9gxp.fsf@whitebox.home> (Andreas Schwab's message of "Sun, 20 Feb 2011 10:46:42 +0100")

Andreas Schwab <schwab@linux-m68k.org> writes:

> It doesn't make sense to send a text without charset information, unless
> it is pure ASCII.  Why would you want the recipient to guess wrong?

Because almost all of my work recepients use Windows and expect only
CP1251. Especially my boss, which hates receiving files in any other
codepages. And sometimes I had to send files in CP866 (old DOS encoding)
to my colleagues which still use some old DOS programs. I use UTF8 only
when I'm talking with Open-Source hackers. So 98 % cases my recepients
know what they are going to view. I even doubt that

Content-Type: text/plain; charset=xxxxxxx

could make a difference, because in most of a cases they just save a
file to a hard drive and open it in some other program. Introducing some
Gnus ability for other 2 % just create unnecesary problems.

And some text formats (for example, LaTeX) have something like

\usepackage[cp1251]{inputenc}

which directly states document encoding.

> Are you sure it is Gnus that reencodes the attachment?  It could also be
> altered by any MTA.

At least when I evaluate (setq mm-coding-system-priorities
'(iso-8859-1)) before sending a mail I receive my files unchanged. Could
a MTA reencode files when it sees

Content-Type: text/plain; charset=xxxxxxx

string? Because some of my Internet interlocutors also have this problem
(and they use other MTA's).

Andreas Schwab <schwab@linux-m68k.org> writes:

> Hobbit <werehobbit@yandex.ru> writes:
>
>> Gnus should find out the correct charset only for inline attachment or
>> for Disposition='attachment' attachement too?
>
> How does that make any difference?
>

When I use an 'inline' attachment it part of a message and could be
reencoded (it's normal). If it's Disposition='attachment' then it's best
for Gnus to leave file unchanged. It's an 'attachment' ('burn after
reading, please'), imagine: you ordered a tech book and received it with
others man handwritten notes as 'improvement'.



  reply	other threads:[~2011-02-20 10:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <871v34nwdn.fsf@myhost.localdomain>
     [not found] ` <87aahss3yu.fsf@gnus.org>
     [not found]   ` <87hbbz6fg4.fsf@myhost.localdomain>
     [not found]     ` <87vd0fpvzv.fsf@gnus.org>
     [not found]       ` <874o7z662d.fsf@myhost.localdomain>
     [not found]         ` <87d3mnk1sy.fsf@myhost.localdomain>
2011-02-20  1:15           ` Lars Ingebrigtsen
2011-02-20  8:49             ` Andreas Schwab
2011-02-20  9:23               ` Hobbit
2011-02-20  9:46                 ` Andreas Schwab
2011-02-20 10:46                   ` Hobbit [this message]
2011-02-20 11:40                     ` Andreas Schwab
2011-02-20 13:27                       ` Hobbit
2011-02-20 13:41                         ` Andreas Schwab
2011-02-20 14:03                           ` Hobbit
2011-02-20 14:17                             ` Andreas Schwab
2011-02-20 14:34                               ` Hobbit
2011-02-20 15:03                                 ` Andreas Schwab
2011-02-20 16:47                                   ` Hobbit
2011-02-20 14:38                               ` Hobbit
2011-02-20 15:04                                 ` Andreas Schwab
2011-02-20 15:25                               ` Hobbit
2011-02-20  9:31               ` Hobbit
2011-02-20  9:48                 ` Andreas Schwab

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=87ei73dlvx.fsf@myhost.localdomain \
    --to=werehobbit@yandex.ru \
    --cc=bugs@gnus.org \
    --cc=ding@gnus.org \
    --cc=schwab@linux-m68k.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).