Gnus development mailing list
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Cc: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: View articles with different charset
Date: Sun, 30 Nov 2008 16:23:07 -0500	[thread overview]
Message-ID: <m31vwsgb71.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <878wr1fje5.fsf_-_@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sun, 30 Nov 2008 14:11:46 +0100")

>>>>> "Reiner" == Reiner Steib <reinersteib+gmane@imap.cc> writes:

>> But it also must be easy to manually tell it to use some other charset
>> when one recognizes the need.

Reiner> Does this help?

Reiner> ,----[ (info "(gnus)Paging the Article") ]
Reiner> |      If given a numerical prefix, you can do semi-manual charset stuff

Damn.  I don't remember reading that.  But see below.

Reiner> There should be a better index entry here.  Any ideas for useful
Reiner> index entries?

Reiner> @cindex charset, view article with different charset
Reiner> @cindex view article with different charset

That looks helpful.

Reiner> Maybe we should consider to specify a non-nil default for
Reiner> `gnus-summary-show-article-charset-alist' [1].

I do have that set to ((1 . utf-8)).  I don't remember doing so, and it
was done via customize rather than ~/.gnus, so I don't have a RCS log to
see when I did it.  But it was presumably for using g with a prefix.

Too bad I forgot all about it.

Actually, I now do remember doing that.  I gave up because, w/o Stefan's
patch, it didn't do any good for the bug at hand.  The 8bit unclassified
utf-8 still wouldn't render.  (And I didn't know about said patch until
recently.)

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6



  reply	other threads:[~2008-11-30 21:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m37i89boe6.fsf@mid.gehheimdienst.de>
     [not found] ` <jeabd5vvug.fsf@sykes.suse.de>
     [not found]   ` <m363ntey23.fsf@mid.gehheimdienst.de>
     [not found]     ` <u63nso2wk.fsf@gnu.org>
     [not found]       ` <jebpxjvd53.fsf@sykes.suse.de>
     [not found]         ` <m3ej2fd2o0.fsf@mid.gehheimdienst.de>
     [not found]           ` <umyh3mttj.fsf@gnu.org>
     [not found]             ` <m33aivfsa8.fsf@mid.gehheimdienst.de>
     [not found]               ` <jwv8wsnjknd.fsf-monnier+emacsbugreports@gnu.org>
2008-10-17 18:19                 ` bug#1174: 23.0.60; Some UTF-8 mails displaying wrongly in Emacs 23 Reiner Steib
2008-10-17 18:36                   ` Frank Schmitt
2008-11-29 12:08                     ` Reiner Steib
2008-11-29 12:18                       ` Simon Josefsson
2008-11-29 15:30                         ` Reiner Steib
2008-11-29 21:30                           ` Stefan Monnier
2008-11-30 13:12                             ` Reiner Steib
2008-11-29 22:14                           ` James Cloos
2008-11-30 13:11                             ` View articles with different charset (was: bug#1174: 23.0.60; Some UTF-8 mails displaying wrongly in Emacs 23) Reiner Steib
2008-11-30 21:23                               ` James Cloos [this message]
2009-01-12 10:54                         ` bug#1174: 23.0.60; Some UTF-8 mails displaying wrongly in Emacs 23 Simon Josefsson
2009-01-12 11:03                           ` Frank Schmitt
2009-01-12 11:10                             ` Simon Josefsson
2009-01-14 11:20                               ` Gabor Z. Papp
2009-01-14 20:12                                 ` Reiner Steib
2009-01-14 22:08                                   ` Stefan Monnier
2008-12-01 21:04                       ` Stefan Monnier
2008-12-01 22:48                         ` Reiner Steib
2008-12-02  7:36                           ` Stefan Monnier
2008-12-04 19:43                             ` Reiner Steib
2008-12-04 21:43                               ` Frank Schmitt

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=m31vwsgb71.fsf@lugabout.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=ding@gnus.org \
    --cc=reinersteib+gmane@imap.cc \
    /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).