From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: non-ascii chars in the Lisp source files
Date: Wed, 03 Sep 2003 15:22:57 +0900 [thread overview]
Message-ID: <b9yptiibdby.fsf@jpl.org> (raw)
Hi,
Can you decode the following morse code using the `W m' key?
-·-· --·- -·-· --·- -·-· --·- -·· · ·--- ·-· ·---- -·-· ·-· -··
I couldn't. It is caused by the broken gnus-sum.elc file.
Mis-decoding of the string "·" which is contained in the
gnus-summary-morse-message function was occurred when compiling
it by XEmacs 21.4 in my system. In that case,
buffer-file-coding-system is set to shift_jis when the
gnus-sum.el file is read.
It isn't a real problem on me since I seldom use that command
and changing the LANG environment variable from ja_JP.eucJP to C
when compiling (or putting the "-*-coding: iso-8859-1;-*-"
coding cookie in the file) helps it. However, it is suggested
that it may cause a serious problem in the future, isn't it?
The following files also contain non-ascii chars:
deuglify.el gnus-delay.el gnus-spec.el mml1991.el nnultimate.el
utf7.el (the last one already contains the coding cookie.)
--
Katsumi Yamaoka <yamaoka@jpl.org>
next reply other threads:[~2003-09-03 6:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 6:22 Katsumi Yamaoka [this message]
2003-09-03 7:01 ` Daniel Pittman
2003-09-03 9:06 ` Robert Epprecht
2003-09-03 7:38 ` Katsumi Yamaoka
2003-09-03 10:43 ` Reiner Steib
2003-09-03 11:20 ` Katsumi Yamaoka
2003-09-03 12:41 ` Katsumi Yamaoka
2003-09-03 15:10 ` Reiner Steib
2003-09-04 0:58 ` Katsumi Yamaoka
2003-09-04 10:13 ` Juha Autero
2003-09-04 11:09 ` Katsumi Yamaoka
2003-09-05 12:26 ` Katsumi Yamaoka
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=b9yptiibdby.fsf@jpl.org \
--to=yamaoka@jpl.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).