From: "Philipp Gühring" <p.guehring@futureware.at>
To: Hans Reiser <reiser@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Unicode policy
Date: Fri, 2 May 2003 03:18:33 +0200 [thread overview]
Message-ID: <200305020118.h421Ip205033@linux1.futureware.at> (raw)
In-Reply-To: <3EB1C209.1050808@namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Freitag, 2. Mai 2003 02:55 schrieben Sie:
> It is a VFS issue. We just conform. VFS can't handle / and null being
> in a filename, so Unicode can't work in Linux. If you get VFS to handle
> Unicode, I'll make ReiserFS work. Linus is the one to convince, not us.
Hi Hans,
UTF-8 (is also Unicode) has no nulls in it, and does not
generate '/' or other problematic charakters, and is actually working on
Reiserfs.
The problem with a migration to Unicode is that we either have to switch all
applications at once, or have the information in the filesystem, in which
encoding the filenames are ...
But you are right, it's a VFS issue ...
Many greetings,
- --
~ Philipp Gühring p.guehring@futureware.at
~ http://www.livingxml.net/ ICQ UIN: 6588261
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE+scdqlqQ+F+0wB3oRAn8gAKCBNzPvsRsaxJT96fCEGvO6MXeFKgCdEXY1
xmMW0hHJZTkHM7GhQj0FcdI=
=U423
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-05-02 1:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 15:38 Unicode policy Philipp Gühring
2003-05-01 15:48 ` Oleg Drokin
2003-05-02 0:55 ` Hans Reiser
2003-05-02 1:18 ` Philipp Gühring [this message]
2003-05-02 10:45 ` Hans Reiser
2003-05-02 10:51 ` Anders Widman
2003-05-07 7:12 ` Yury Umanets
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=200305020118.h421Ip205033@linux1.futureware.at \
--to=p.guehring@futureware.at \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
/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 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.