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 16:03:56 +0200 [thread overview]
Message-ID: <87tyfydcqb.fsf@myhost.localdomain> (raw)
In-Reply-To: <m2d3mmakma.fsf@igel.home> (Andreas Schwab's message of "Sun, 20 Feb 2011 14:41:49 +0100")
Andreas Schwab <schwab@linux-m68k.org> writes:
> If you send an arbitrary byte stream you send it as
> application/octet-stream. Case closed.
Okay.
>
> What's wrong with putting it in the charset declaration?
>
Gnus should ask an user what codepage to mention in the header. It
shouldn't be some random guessing (often incorrect).
>> I enclose two reports about that (from aforementioned thread):
>
> All I can see in the second attachment are two basically equivalent
> files, one encoded in UTF-8 and one encoded in Latin-1.
>
localhost$ iconv -f cp1251 letter_before.txt
русский текст в кп1251 <------- normal text
localhost$ iconv -f cp1251 letter_after.txt
ðóññêèé òåêñò â êï1251 <---- gibberish
localhost$ iconv -f UTF8 letter_after.txt -t iso-8859-1 |
iconv -f cp1251
русский текст в кп1251 <------ normal text
File letter_after.txt isn't equivalent to letter_before.txt, because to
read it I not only had to know it's codepage. I need to do some strange
transformations to see normal text. That's not right and described in
report #1.
> The third attachment is missing vital information, so I cannot say
> anything about it.
What vital information?
Besides, do you mind answering to the third attachment directly
(i. e. to news://news.gnus.org/gnus.gnus-bug thread 'bug#8070: gnus
damages attached file', third message article in the thread (which I
cited)?
next prev parent reply other threads:[~2011-02-20 14:03 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
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 [this message]
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=87tyfydcqb.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).