* article editing oddity
@ 1999-11-12 8:39 Vladimir Volovich
1999-11-15 20:51 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 6+ messages in thread
From: Vladimir Volovich @ 1999-11-12 8:39 UTC (permalink / raw)
Hi,
i've got a message which was in windows-1251 encoding, but
Content-Type header said that it was in koi8-r, so the message was
unreadable.
I pressed C-u g e, and changed "charset=koi8-r" to
"charset=windows-1251" in the Content-Type header.
Then i pressed C-c C-c
But the saved article still contained "charset=koi8-r" !
What's going wrong? AFAIR, this worked with older gnus versions.
Best regards, -- Vladimir.
P.S. windows-1251 is defined in my .emacs file by
(codepage-setup 1251)
(define-coding-system-alias 'windows-1251 'cp1251)
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: article editing oddity
1999-11-12 8:39 article editing oddity Vladimir Volovich
@ 1999-11-15 20:51 ` Lars Magne Ingebrigtsen
1999-11-15 21:23 ` Shenghuo ZHU
0 siblings, 1 reply; 6+ messages in thread
From: Lars Magne Ingebrigtsen @ 1999-11-15 20:51 UTC (permalink / raw)
Vladimir Volovich <vvv@vvv.vsu.ru> writes:
> i've got a message which was in windows-1251 encoding, but
> Content-Type header said that it was in koi8-r, so the message was
> unreadable.
>
> I pressed C-u g e, and changed "charset=koi8-r" to
> "charset=windows-1251" in the Content-Type header.
>
> Then i pressed C-c C-c
>
> But the saved article still contained "charset=koi8-r" !
Uhm. `C-c C-c' after editing the message will create brand new
Content-Type headers. And since Gnus thought that the text was
koi8-r, Gnus put that in the new header.
*sigh*
Anyway, `C-u W M c' will let you re-interpret the message using a
different charset.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: article editing oddity
1999-11-15 20:51 ` Lars Magne Ingebrigtsen
@ 1999-11-15 21:23 ` Shenghuo ZHU
1999-12-01 14:37 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 6+ messages in thread
From: Shenghuo ZHU @ 1999-11-15 21:23 UTC (permalink / raw)
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
LMI> Vladimir Volovich <vvv@vvv.vsu.ru> writes:
>> i've got a message which was in windows-1251 encoding, but
>> Content-Type header said that it was in koi8-r, so the message was
>> unreadable.
>>
>> I pressed C-u g e, and changed "charset=koi8-r" to
>> "charset=windows-1251" in the Content-Type header.
>>
>> Then i pressed C-c C-c
>>
>> But the saved article still contained "charset=koi8-r" !
LMI> Uhm. `C-c C-c' after editing the message will create brand new
LMI> Content-Type headers. And since Gnus thought that the text was
LMI> koi8-r, Gnus put that in the new header.
How about not rebuilding headers if the article is shown by `C-u g'?
Or not reuilding headers when check in by `C-u C-c C-c'?
LMI> *sigh*
LMI> Anyway, `C-u W M c' will let you re-interpret the message using a
LMI> different charset.
[...]
I don't think this works, unless press `C-u g C-u W M c', since it
washes an article in the article buffer, where characters have been
decoded by (wrong) charset, then the result is double-decoded,
i.e. `\201's shows.
Even `C-u g C-u W M c' does not decode subject and other headers.
*sigh*
My unofficial solution is advicing gnus-summary-show-article. When
number argument comes, pick a charset from predefined charsets or
minibuffer, set gnus-newsgroup-charset and
gnus-newsgroup-ignored-charsets, then ad-do-it.
If this solution is acceptable, I can patch the
gnus-summary-show-article, and maybe a little work let gnus ignored
all charsets.
--
Shenghuo ZHU
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: article editing oddity
1999-11-15 21:23 ` Shenghuo ZHU
@ 1999-12-01 14:37 ` Lars Magne Ingebrigtsen
1999-12-01 18:30 ` FAQ: show an article with a specified charset (was: Re: article editing oddity) Shenghuo ZHU
0 siblings, 1 reply; 6+ messages in thread
From: Lars Magne Ingebrigtsen @ 1999-12-01 14:37 UTC (permalink / raw)
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> I don't think this works, unless press `C-u g C-u W M c', since it
> washes an article in the article buffer, where characters have been
> decoded by (wrong) charset, then the result is double-decoded,
> i.e. `\201's shows.
>
> Even `C-u g C-u W M c' does not decode subject and other headers.
>
> *sigh*
>
> My unofficial solution is advicing gnus-summary-show-article. When
> number argument comes, pick a charset from predefined charsets or
> minibuffer, set gnus-newsgroup-charset and
> gnus-newsgroup-ignored-charsets, then ad-do-it.
>
> If this solution is acceptable, I can patch the
> gnus-summary-show-article, and maybe a little work let gnus ignored
> all charsets.
Yes, that sounds like a good idea.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~1999-12-01 23:00 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-11-12 8:39 article editing oddity Vladimir Volovich
1999-11-15 20:51 ` Lars Magne Ingebrigtsen
1999-11-15 21:23 ` Shenghuo ZHU
1999-12-01 14:37 ` Lars Magne Ingebrigtsen
1999-12-01 18:30 ` FAQ: show an article with a specified charset (was: Re: article editing oddity) Shenghuo ZHU
1999-12-01 23:00 ` Lars Magne Ingebrigtsen
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).