Hi, On 03/08/2019 14:50, Robert Nichols wrote: >> The way to work around this in rdiffweb at least it's to manage path as >> bytes. That is how rdiffweb 1.2.8 is working. Path are bytes. That is >> also >> how most filesystem are working too. Paths are bytes and those are >> decoded >> to be displayed to the user. > > Indeed. Paths are bytes, and there is no requirement that they be printable > strings. The forward slash is the separator, and the individual path > components can contain any byte except 0x00 (ASCII NUL). rdiff-backup > should accept that.
I never challenged that, I was just highlighting the difficulties. OK, I've created a sub-branch ericzolf-py2to3-bytes and will work on this aspect, moving away from str for paths to bytes. KR, Eric _______________________________________________ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
