View Single Post
Old 11-23-2018, 05:38 AM   #13
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,906
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by fsantini View Post
I also use Dropbox so it will be easy for me to check Can you please post an example of a title that doesn't sync?

Does some Kobo guru know if it's maybe the Kobo itself that has some problems with some characters in the filename?
The KoboTouch driver in calibre does the following when creating filenames:

Code:
    def sanitize_path_components(self, components):
        invalid_filename_chars_re = re.compile(r'[\/\\\?%\*:;\|\"\'><\$!]', re.IGNORECASE | re.UNICODE)
        return [invalid_filename_chars_re.sub('_', x) for x in components]
Those are the specific Kobo changes. Calibre will also have sanitised the name so it was legal filename. It tends to overdo this as it makes sure the name is valid in all the OSes calibre runs on.
davidfor is offline   Reply With Quote