Thread: nbsps in titles
View Single Post
Old 03-01-2023, 12:46 PM   #5
isarl
Addict
isarl ought to be getting tired of karma fortunes by now.isarl ought to be getting tired of karma fortunes by now.isarl ought to be getting tired of karma fortunes by now.isarl ought to be getting tired of karma fortunes by now.isarl ought to be getting tired of karma fortunes by now.isarl ought to be getting tired of karma fortunes by now.isarl ought to be getting tired of karma fortunes by now.isarl ought to be getting tired of karma fortunes by now.isarl ought to be getting tired of karma fortunes by now.isarl ought to be getting tired of karma fortunes by now.isarl ought to be getting tired of karma fortunes by now.
 
Posts: 287
Karma: 2534928
Join Date: Nov 2022
Location: Canada
Device: Kobo Aura 2
Quote:
Originally Posted by theducks View Post
NBSP is not a valid file name character.
Not allowing, just saves the struggle to make a valid filename on ALL OS.
While I definitely agree with the sentiment that NBSPs in filenames is not good practice, I am going to nitpick the broadness of your claims here. What constitutes a valid filename character depends on the filesystem. For example, NTFS uses Unicode to encode path names and does not prohibit nbsp characters.

Furthermore, as I understand them, OP isn't bothered if a title has nbsps replaced with ordinary spaces in the filename itself, and is instead mostly interested in tweaking the metadata in their Calibre library to distinguish a value of “Unknown” from the special value Calibre looks out for, which is that same string of “Unknown”, so that in the end, OP's custom “Unknown” tag appears in the tag browser instead of being ignored.
isarl is offline   Reply With Quote