9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Nigel Roles ngr@symbionics.co.uk
Subject: [9fans] allowing space (ASCII 0x20) in file names
Date: Tue, 14 Apr 1998 07:38:58 +0100	[thread overview]
Message-ID: <19980414063858.ZGQZxb95QTIHNihAWrVST5B0Fi7VNDb97ErZ3_LxRQY@z> (raw)

I use the non-breaking space when translating Win95 VFAT names in a
hacked dossrv. Win95 fienames are stuffed full of spaces because
Microsoft don't care whether the DOS shell can parse path names anymore.


> -----Original Message-----
> once when i had to worry about conveying names with spaces (x.400
> addresses)
> i used iso no-break space (+U'00A0' i think).  it was adequate,
> which is more than i can say for some of the RFCs i've read or had
> to implement over the years.  i found i nearly always had to check
> someone else's code to see what clients or servers actually expected.
> implement the rfc precisely (or as accurately as you can determine
> it),
> and you often hit problems.
> 




             reply	other threads:[~1998-04-14  6:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-14  6:38 Nigel [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-04-14 15:18 Russ
1998-04-14 15:16 Tom
1998-04-14 13:50 Rob
1998-04-14 13:35 Elliott.Hughes
1998-04-14 13:04 Russ
1998-04-14  9:50 Elliott.Hughes
1998-04-14  9:08 Elliott.Hughes
1998-04-14  6:24 forsyth
1998-04-14  5:33 forsyth
1998-04-13 23:03 geoff
1998-04-13 13:50 G.David
1998-04-13  6:00 geoff
1998-04-12  3:27 ozan
1998-04-10 14:49 G.David
1998-04-10 14:43 forsyth
1998-04-10  4:04 geoff
1998-04-10  1:03 G.David
1998-04-09 23:44 Tom
1998-04-09 22:08 G.David
1998-04-09  3:10 G.David
1998-04-08 23:56 G.David
1998-04-08 22:05 Rob
1998-04-08 21:54 G.David
1998-04-08 20:32 Russ
1998-04-08 19:58 G.David
1998-04-08 17:45 Tom
1998-04-08 17:08 Russ
1998-04-08 16:56 G.David

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=19980414063858.ZGQZxb95QTIHNihAWrVST5B0Fi7VNDb97ErZ3_LxRQY@z \
    --to=9fans@9fans.net \
    /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).