From: Karl Eichwalder <keichwa@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: ISO-8859-1 encoded file names and UTF-8
Date: Sat, 08 Mar 2003 19:25:25 +0100 [thread overview]
Message-ID: <shzno5yaui.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <8582-Sat08Mar2003190654+0200-eliz@elta.co.il> ("Eli Zaretskii"'s message of "Sat, 08 Mar 2003 19:06:54 +0200")
"Eli Zaretskii" <eliz@elta.co.il> writes:
> And what is the value of `default-file-name-coding-system'? If it's
> anything but `utf-8', please try setting `file-name-coding-system' to
> `utf-8' and see if that helps.
I did ask for help; I reported a problem worth fixing ;) It is a
reather serious problem, IMO.
> This would contradict the whole purpose of a multilingual Emacs: it is
> meant to seamlessly display characters from different character sets
> without any special effects.
This might be appropriate when you use Emacs for reading mail and
news. But it's a wrong behavior when it come to "source code"
> How can Emacs know that in this particular case, you want it to
> display different character sets differently?
When a XML file or a PO file (that's a message file used by gettext) is
declared as UTF-8 encoded and Emacs detects an error within such a
file, it's surely worth notifying the user.
> I believe that if such a feature is added, it must be driven by
> user-level settings. For example, users could define a list of
> character sets or codepoints which they don't expect to see in their
> buffers, and Emacs will then flag characters from those sets with some
> visual cue.
Yes, approximately. But instead of a list of character sets it must
depend on a list of file types (.xml, .po, .java, etc.).
> It's even possible that you can do that yourself right now by using
> hi-lock.el or something similar, since IIRC regular expressions can be
> used to express character categories.
Thanks for advice :) I know how to work around the problem; for checking
.po files one can use 'msgfmt' etc. I'd rather vote to change Emacs to
make users happy -- that's probably not that urgent, but it should
happen for the next major release coming from CVS HEAD.
--
ke@suse.de (work) / keichwa@gmx.net (home): |
http://www.gnu.franken.de/ke/ | ,__o
Free Translation Project: | _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
next prev parent reply other threads:[~2003-03-08 18:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 6:15 ISO-8859-1 encoded file names and UTF-8 Karl Eichwalder
2003-03-08 9:16 ` Eli Zaretskii
2003-03-08 10:05 ` Karl Eichwalder
2003-03-08 17:06 ` Eli Zaretskii
2003-03-08 18:25 ` Karl Eichwalder [this message]
2003-03-08 22:35 ` Eli Zaretskii
2003-03-09 4:38 ` Karl Eichwalder
2003-03-19 13:33 ` Kenichi Handa
2003-03-19 16:15 ` Karl Eichwalder
2003-03-19 23:52 ` Kenichi Handa
2003-03-20 17:32 ` Karl Eichwalder
2003-03-21 6:01 ` Kenichi Handa
2003-03-21 19:53 ` Karl Eichwalder
2003-03-21 19:06 ` Richard Stallman
2003-03-20 8:46 ` Richard Stallman
2003-03-20 9:11 ` Kenichi Handa
2003-03-23 2:52 ` Richard Stallman
2003-03-24 0:28 ` Kenichi Handa
2003-03-24 19:27 ` Richard Stallman
2003-03-26 4:47 ` Kenichi Handa
2003-04-01 21:17 ` etags and UTF-8 encoded file names (Re: ISO-8859-1 encoded file names and UTF-8) Karl Eichwalder
2003-04-02 1:34 ` Kenichi Handa
2003-04-02 19:26 ` Richard Stallman
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=shzno5yaui.fsf@tux.gnu.franken.de \
--to=keichwa@gmx.net \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.