9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox rsc@plan9.bell-labs.com
Subject: [9fans] allowing space (ASCII 0x20) in file names
Date: Wed,  8 Apr 1998 16:32:10 -0400	[thread overview]
Message-ID: <19980408203210.DXZvwgeIk-KIggjmCFLwdtttbZvgg_dXuhuXyk42eog@z> (raw)

> The problem is that the RFC2060 "International Mailbox Naming
> Convention" has one more character in its alphabet than Plan9
> allows in names so there is no place to map the space.

There are more problems than that.  I'm pretty sure RFC2060 doesn't
specify a name length, and Plan9 limits you to 27 bytes.  So you're
going to have to keep some sort of translation table between IMAP
names and Plan9 names anyway.  

If this limit wasn't there and you were content to keep the mailbox
names in encoded form (probably a nice choice, since then you never
have to decode or encode them) you could substitute 0x7F for space
in the Plan9 names and you'd be all set -- both are one byte in
UTF-8, and RFC2060 can't have raw 7Fs while Plan9 can't have raw spaces.

Russ




             reply	other threads:[~1998-04-08 20:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-08 20:32 Russ [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:38 Nigel
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 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=19980408203210.DXZvwgeIk-KIggjmCFLwdtttbZvgg_dXuhuXyk42eog@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).