From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andreas Schwab <schwab@suse.de>,
emacs-devel@gnu.org, monnier@iro.umontreal.ca, jasonr@f2s.com,
lekktu@gmail.com
Subject: Re: Encoding for a file containing filenames?
Date: Fri, 09 Nov 2007 13:15:15 +0100 [thread overview]
Message-ID: <47344F53.3080602@swipnet.se> (raw)
In-Reply-To: <usl3fprcf.fsf@gnu.org>
Eli Zaretskii skrev:
>> From: Andreas Schwab <schwab@suse.de>
>> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, lekktu@gmail.com,
>> jasonr@f2s.com, emacs-devel@gnu.org
>> Date: Fri, 09 Nov 2007 12:07:23 +0100
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>> And Linux filesystems use UTF-8 for file names anyway, right?
>> Linux filesystems do not use any encoding, they use raw bytes.
>
> Yes, but what kind of bytes would those be on a typical box that uses
> non-ASCII characters in file names? I know it can be _anything_, but
> I think typically these characters will be encoded in UTF-8.
>
The trend for Gnome and KDE and other desktop environments is to use UTF-8
(just about everywhere, not just file names), so you can say UTF-8 is most likely.
Jan D.
next prev parent reply other threads:[~2007-11-09 12:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 15:05 Encoding for a file containing filenames? Juanma Barranquero
2007-11-08 16:32 ` Stefan Monnier
2007-11-08 16:49 ` Juanma Barranquero
2007-11-08 20:50 ` Eli Zaretskii
2007-11-08 22:38 ` Stefan Monnier
2007-11-08 23:42 ` Jason Rumney
2007-11-09 4:01 ` Stefan Monnier
2007-11-09 10:03 ` Eli Zaretskii
2007-11-09 11:05 ` Jan Djärv
2007-11-09 11:07 ` Andreas Schwab
2007-11-09 11:53 ` Eli Zaretskii
2007-11-09 12:15 ` Jan Djärv [this message]
2007-11-09 12:16 ` Kenichi Handa
2007-11-09 12:54 ` Andreas Schwab
2007-11-09 14:01 ` Eli Zaretskii
2007-11-09 10:34 ` Kenichi Handa
2007-11-09 16:25 ` Stefan Monnier
2007-11-10 1:10 ` Kenichi Handa
2007-11-09 0:41 ` Kenichi Handa
2007-11-09 0:50 ` Juanma Barranquero
2007-11-09 1:05 ` Kenichi Handa
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=47344F53.3080602@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@f2s.com \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@suse.de \
/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.