From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 8 Apr 1998 16:54:51 -0500 From: G. David Butler gdb@dbSystems.com Subject: [9fans] allowing space (ASCII 0x20) in file names Topicbox-Message-UUID: 745767d8-eac8-11e9-9e20-41e7f4b1d025 Message-ID: <19980408215451.PRXcR9rNx7NEw7DNbdU4U3qWm8cXLlA_LC_G9jDHeTU@z> >From: "Russ Cox" >> 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. I think each component limited to 27 octets is ok. Now what is fun is the namespace starting with a '#'! (not a real problem, just strip it or use ./#blah.) >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. Hold on, /sys/src/9/port/chan.c excludes 0x7f even though /sys/src/fs/port/dentry.c doesn't. Should we allow 0x7f? ------------------------------------------------------------------- G. David Butler | Who I? Zathras, a Plan9er. Nobody uses Zathras' | system, but Zathras not mind. Zathras used to | having others ignore Zathras. Besides, Zathras gdb@dbSystems.com | have best system, so Zathras happy.