From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Bug: Incorrect encoding with `O F' or `O f' (was: how to save in "cooked" format?)
Date: Thu, 10 Nov 2005 18:56:38 +0100 [thread overview]
Message-ID: <v9psp82xpl.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <u1x1xxulv.fsf@gnu.org>
On Thu, Nov 03 2005, Sam Steingold wrote:
>> * Reiner Steib <ervarefgrvo+tznar@vznc.pp> [2005-11-03 22:01:47 +0100]:
>> `O f', `O F' or `o' with gnus-default-article-saver set to
>> gnus-summary-write-to-file or gnus-summary-save-in-file more or less
>> do what you want.
>
> thanks. this is nice.
> alas, there is just two small problems:
> 1. the Subject line remains in the "=?windows-1251?Q?=..." format
> 2. the text is not saved in the correct encoding. the file to which I
> append starts with
> -*- coding: utf-8-unix -*-
> it is not saved correctly:
>
> [...] Sam!
>
> instead of
>
> Привет Sam!
When I tried several days ago, it worked for me for the body. I
didn't test encoded Subject lines then. Now, it doesn't work for me
neither for the body or headers. :-/
Probably `gnus-article-save' and/or `gnus-summary-save-article' need
to be fixed if we want the commands `O f', `O F' and `O b' to save the
decoded content (ask for a coding system if required). From the
description in the manual [1], I conclude that this should be the
case. Alas, I don't have time to do this ATM. Anyone?
Bye, Reiner.
[1]
,----[ (info "(gnus)Saving Articles") ]
| `O f'
| Save the current article in plain file format
| (`gnus-summary-save-article-file').
|
| `O F'
| Write the current article in plain file format, overwriting any
| previous file contents (`gnus-summary-write-article-file').
|
| `O b'
| Save the current article body in plain file format
| (`gnus-summary-save-article-body-file').
`----
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2005-11-10 17:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 21:45 how to save in "cooked" format? Sam Steingold
2005-11-02 22:15 ` Bernard Adrian
2005-11-02 22:27 ` Sam Steingold
2005-11-02 23:50 ` Steve Youngs
2005-11-03 18:08 ` Sam Steingold
2005-11-03 18:26 ` Christoph Conrad
2005-11-03 20:12 ` Sam Steingold
2005-11-03 21:01 ` Reiner Steib
2005-11-03 21:57 ` Sam Steingold
2005-11-03 22:15 ` Steve Youngs
2005-11-10 17:56 ` Reiner Steib [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=v9psp82xpl.fsf_-_@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).