From: "Matthias Urlichs" <smurf@smurf.noris.de>
To: linux-kernel@vger.kernel.org
Subject: Re: UTF-8 in file systems? xfs/extfs/etc.
Date: Tue, 10 Feb 2004 05:53:16 +0100 [thread overview]
Message-ID: <20040210045315.GA20373@kiste> (raw)
In-Reply-To: <20040210043212.GF18674@srv-lnx2600.matchmail.com>
Hi,
Mike Fedyk:
>
> You can have "/" in the filename also, though that could be encoded somehow...
Such encoding isn't valid UTF-8.
Of course you could use ⁄ instead (fractional slash, U+2044).
Or perhaps ∕ (division slash, U+2215).
How to visually distinguish these from a / (U+002F) is left as an
exercise to the reader. :-/
The fun part about this email is that I'm writing it with plain old vi
(ummm.... I _do_ know that there's nothing "plain old" about vim ;-)
and I don't see silly square boxes here.
--
Matthias Urlichs
next prev parent reply other threads:[~2004-02-10 7:41 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 11:58 UTF-8 in file systems? xfs/extfs/etc Nico Schottelius
2004-02-09 12:26 ` Måns Rullgård
2004-02-09 12:28 ` Hugo Mills
2004-02-09 13:04 ` Matthew Reppert
2004-02-09 13:36 ` Matthias Urlichs
2004-02-10 4:32 ` Mike Fedyk
2004-02-10 4:53 ` Matthias Urlichs [this message]
2004-02-10 9:46 ` Robin Rosenberg
2004-02-10 23:04 ` jw schultz
2004-02-10 23:17 ` viro
2004-02-10 23:23 ` Måns Rullgård
2004-02-11 0:02 ` Mike Fedyk
2004-02-09 15:06 ` Matthew Garrett
2004-02-11 6:39 ` Tim Connors
2004-02-11 16:35 ` JFS default behavior (was: UTF-8 in file systems? xfs/extfs/etc.) Dave Kleikamp
2004-02-12 0:45 ` Andy Isaacson
2004-02-12 1:19 ` Tim Connors
2004-02-12 3:54 ` jw schultz
2004-02-12 12:03 ` Robin Rosenberg
2004-02-12 8:54 ` Jamie Lokier
2004-02-12 15:55 ` Robin Rosenberg
2004-02-12 16:17 ` John Bradford
2004-02-12 16:40 ` Robin Rosenberg
2004-02-12 17:16 ` John Bradford
2004-02-12 18:06 ` Robin Rosenberg
2004-02-12 19:08 ` John Bradford
2004-02-12 19:39 ` Robin Rosenberg
2004-02-12 21:13 ` John Bradford
2004-02-12 22:29 ` Robin Rosenberg
2004-02-12 22:50 ` Valdis.Kletnieks
2004-02-13 2:58 ` Jamie Lokier
2004-02-13 9:48 ` Robin Rosenberg
2004-02-13 3:15 ` Jamie Lokier
2004-02-14 15:24 ` Eduard Bloch
2004-02-13 0:17 ` Jamie Lokier
2004-02-13 0:38 ` Jamie Lokier
2004-02-13 1:16 ` Robin Rosenberg
2004-02-13 1:23 ` Jamie Lokier
2004-02-13 1:46 ` Robin Rosenberg
2004-02-13 2:29 ` viro
2004-02-13 3:23 ` Jamie Lokier
2004-02-14 15:09 ` Eduard Bloch
2004-02-15 1:01 ` Jamie Lokier
2004-02-16 14:03 ` Eduard Bloch
2004-02-16 14:28 ` Jamie Lokier
2004-02-16 19:22 ` Eduard Bloch
2004-02-16 21:44 ` Jamie Lokier
2004-02-16 15:18 ` Valdis.Kletnieks
2004-02-16 15:32 ` Jamie Lokier
2004-02-16 19:13 ` Eduard Bloch
2004-02-16 15:46 ` John Bradford
2004-02-16 15:48 ` viro
2004-02-16 16:43 ` John Bradford
2004-02-16 16:25 ` Robin Rosenberg
2004-02-16 15:27 ` Jamie Lokier
2004-02-16 15:44 ` Robin Rosenberg
2004-02-13 10:03 ` Robin Rosenberg
2004-02-13 10:22 ` vda
2004-02-13 10:29 ` Robin Rosenberg
2004-02-12 13:28 ` Dave Kleikamp
2004-02-12 15:26 ` Valdis.Kletnieks
2004-02-12 15:41 ` Dave Kleikamp
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=20040210045315.GA20373@kiste \
--to=smurf@smurf.noris.de \
--cc=linux-kernel@vger.kernel.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