Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: jidanni@jidanni.org
To: info-gnus-english@gnu.org
Subject: making ~/News/nnrss:* filenames utf-8
Date: Sun, 09 Nov 2008 06:49:33 +0800	[thread overview]
Message-ID: <87od0pu936.fsf@jidanni.org> (raw)

How do I clean up mule-utf-8 filenames? (guaranteed to give garbage
characters for non-ASCII to anybody who looks at them, made even when
RSS is UTF-8 already.)

$ ls News/nnrss:*|iconv>/dev/null
iconv: illegal input sequence at position 19

In (info "(gnus)RSS") it says
     The `nnrss' back end saves the group data file in `nnrss-directory'
  (see below) for each `nnrss' group.  File names containing non-ASCII
  characters will be encoded by the coding system specified with the
  `nnmail-pathname-coding-system' variable.  If it is `nil', in Emacs the
  coding system defaults to the value of
  `default-file-name-coding-system'.
Which says:
  default-file-name-coding-system is a variable defined in `C source code'.
  Its value is mule-utf-8
  This variable is set/changed by the command `set-language-environment'.
  User should not set this variable manually,
  instead use `file-name-coding-system' to get a constant encoding
  of file names regardless of the current language environment.

So how does one change those filenames to UTF-8 safely?
$ for i in nnrss:*; do mv $i `echo $i|WHAT`; done
then echo "(setq file-name-coding-system 'utf-8)">> .emacs
then start emacs?
I use Debian unstable, emacs-version "22.2.1".
Yes, I hear emacs 23 is UTF-8 already.

P.S., Ding list broken:
  pipe to |/local/majordomo/bin/mj_enqueue -r -d lists.math.uh.edu -l ding -P10 -p10
    generated by ding@lists.math.uh.edu
    local delivery failed

                 reply	other threads:[~2008-11-08 22:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87od0pu936.fsf@jidanni.org \
    --to=jidanni@jidanni.org \
    --cc=info-gnus-english@gnu.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).