unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: Kenichi Handa <handa@m17n.org>
Subject: Re: Strange behaviour with dired and UTF8
Date: Wed, 7 May 2003 19:40:22 +0200	[thread overview]
Message-ID: <FA5E7F49-80B2-11D7-BC28-00039363E640@swipnet.se> (raw)
In-Reply-To: <200305071631.h47GVQiM015312@rum.cs.yale.edu>


onsdagen den 7 maj 2003 kl 18.31 skrev Stefan Monnier:

>> Say I have two files, one in UTF-8 and one in latin-1.  Emacs has only
>> one coding system for file names, say it is latin-1.
>
> Question: how do other applications deal with such situations ?
>
> I mean, of course Emacs should do better than the rest of the crowd,
> but if most/all other applications fail miserably, then it's unlikely
> that people will use such setups and it would be wrong for Emacs to
> make it easier to create such a setup (unless maybe only Emacs
> will ever care about those file names, of course).

I can only say that GNOME (Nautilus) deals with this fine, better than
most.  It can actually display two files, one in latin-1 and the other
in UTF-8 that has the same display representation so it looks like
the two files have the same name.  When clicking on them (to open
for example), it opens the correct file (I use the size of the files
to tell them apart).  When renaming a file, it uses UTF-8 always.
I think this is as good as it gets.

I don't know in detail, but given that UTF-8 is so fundamental to GNOME,
I think Nautilus first tries UTF-8, and if the name isn't valid UTF-8, 
it
tries the users locale.  Actually Nautilus behaves better than most 
other
GNOME applications.  For example, gedit always tries UTF-8 for 
displaying
the file name and says "invalid UTF-8" if that fails.

KDE (Konquerer) seems to use the locale character set always.

Other systems can change the view character set.  Much like you
can do in Netscape/Mozilla.  Open up a directory and then you can
toggle the coding system used to display file names (in Mozilla:
View -> Character coding).  This is what I thought Emacs could do, but
it lost the original file name.

	Jan D.

      reply	other threads:[~2003-05-07 17:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24 11:43 Strange behaviour with dired and UTF8 Jan D.
2003-04-25 13:20 ` Kai Großjohann
2003-05-01  6:52 ` Kenichi Handa
2003-05-02  6:41   ` Kai Großjohann
2003-05-02  8:16   ` Jan D.
2003-05-02  8:56     ` Kenichi Handa
2003-05-02  9:59       ` Jan D.
2003-05-02 11:22         ` Kenichi Handa
2003-05-02 12:44           ` Jan D.
2003-05-03 15:03             ` Richard Stallman
2003-05-03 18:04               ` Jan D.
2003-05-05 14:32                 ` Richard Stallman
2003-05-07 15:51                   ` Jan D.
2003-05-07 16:09                     ` Stefan Monnier
2003-05-09 11:19                       ` Richard Stallman
2003-05-03 15:59             ` Stephen J. Turnbull
2003-05-03 17:59               ` Jan D.
2003-05-05  9:20             ` Kenichi Handa
2003-05-06 18:05               ` Jan D.
2003-05-07  1:08                 ` Kenichi Handa
2003-05-07 15:43                   ` Jan D.
2003-05-03 15:03       ` Richard Stallman
2003-05-03 18:11         ` Jan D.
2003-05-06  5:39         ` Kenichi Handa
2003-05-06 14:41           ` Richard Stallman
2003-05-07 15:49           ` Jan D.
2003-05-07 16:31             ` Stefan Monnier
2003-05-07 17:40               ` Jan D. [this message]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FA5E7F49-80B2-11D7-BC28-00039363E640@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=handa@m17n.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).