Subj : Re: spaces in filenames
To   : Digital Man
From : tenser
Date : Thu Jan 20 2022 02:55 am

On 19 Jan 2022 at 12:02a, Digital Man pondered and said...
 
 DM> I think it's actually supposed to be '\xXX' (and just just \x20 for
 DM> space). This is what BinkIT does (for both encode and decode of filename
 DM> parameters) and it appears to jive with FTS-1026.

That was my reading, as well.  What I took away from 1026
is this:

* New code should use "\xHH" for two hex-digits "HH" to represent
  "escaped" characters in commands.
* Whitespace in filenames is prohibited at the protocol level,
  and must be escaped.
* The character "\" must always be escaped.
* The FSP-1011.003 escape method of "\HH" is deprecated.
* Systems should provide a configuration option on a per-node
  basis to use the FSP-1011.003 method for nodes running software
  written assuming the "\HH" encoding.
* Software should unconditionally transform "\20" (specifically)
  into a space character in file names.

In other words, use "\xHH" unless directed otherwise by a
configuration option.  Always translate "\20" to space.

--- Mystic BBS v1.12 A47 2021/11/06 (Linux/64)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.