Quote:
Originally Posted by PeterT
I thought it was recommended not to use any special characters in the file names; just a-z A-Z and 0-9
|
But as some would have it, "... it is a custom more honour'd in the breach than the observance."
Code:
D:\CalibreLibraries\_Test\William Shakespeare\Romeo et Juliette (401)\Romeo et Juliette - William Shakespeare.pdf
I've been wondering what a Kobo device does if a URI within an ncx file has an encoded space (%20) in it. Does it deal with them OK? If so then why not an encoded comma (%2C). They're both specified as encoding candidates in RFCs dated as long ago as August 1998.
FWIW: - according to the IETF, underscore, hyphen/minus, full stop, and tilde are acceptable in URI names.
BR
<rant>Why is it that in the content.opf, the manifest and spine refer to the XHTML files by their 'physical' file names, whereas in the toc.ncx the same files are referred to by their 'percent encoded' URI names. Inconsistencies such as this drives those of us not steeped in the intricacies of 'current technology' nuts. I sometimes wonder if the TPTB do it to feed their love of obscurantism.</rant>