View Single Post
Old 10-22-2019, 06:18 PM   #8
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,718
Karma: 169712580
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by BetterRed View Post


If it's allowable in Linux and Windows (and as far as know on MacOS too), the question is: why is '+' replaced with '_' in the library file name?

Given that '#', '$', '&', '-' etc are not replaced.

I get why \/:*?"<>| are replaced, but not anything else. And I'm not 100% certain it's been ever thus.
PC/DR/MS-DOS did not allow the '+' sign as a character in a filename. And I vaguely remember when saving to a floppy (sadly, dating myself there...), you could not use a '+' in a filename saved from Windows 95. Going by a old DRDOS manual, you could not use any of " * + , / : ; < = > ? \ [ ] | in a filename and a space could not be used as the first character of a filename.
DNSB is offline   Reply With Quote