From: Jack Johnson <fragment@nas.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Beating the dead horse: blanks in filenames
Date: Tue, 23 Jul 2002 10:36:36 -0700 [thread overview]
Message-ID: <3D3D9424.2040902@nas.com> (raw)
I was forwarding part of the previous thread on to a friend who studies
Japanese in his spare time, regarding onji and haiku, and spaces in
language in general.
I'm guessing in most languages, not having spaces in filenames is
probably not such a big deal. Are there any common languages anyone can
think of where it might be a huge deal, or at least as troublesome as
typing filenames left-to-right instead of right-to-left (without doing a
little coding)?
-Jack
(alternate daily aside)
http://www.unicode.org/pending/phaistos/Phaistos.pdf
Not accepted by the UTC, so there goes my Phaistos Disk Turing Machine.
I was really looking forward to doing the CD labels, too.
reply other threads:[~2002-07-23 17:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D3D9424.2040902@nas.com \
--to=fragment@nas.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).