Quote:
Originally Posted by unboggling
[*] Differences for Other Operating Systems and File Systems. Windows uses a volume designator such as "C:\" and a backslash between path components, while on current versions of OS X, Linux, and other Unix-variants the path component separator is usually forwardslash (depending on specific file system). Also, I have not used Windows in years, so am unsure if Windows still requires a 3 character file extension following the dot.[*] Constant, File Extension. The file extension at the end of the path string for the filename component can be approximated by using a string constant, which can be customized per user. For precision it should include the preceding dot plus all the characters of the extension. But string length of potential extensions varies. Many are 4 characters such as epub, mobi, azw3, while some are 3 characters such as rtf, txt, lit. Some are 5 or more. Most of my books have only one format, EPUB, though there are a few exceptions that also have a PDF or MOBI. To cover the file extension for most of my cases, for filename templates I just use .epub as the constant, and do not worry about possible small differences. |
Windows does care about extensions (you can have a naked file name). The ShellExt is the part that uses the Extension to launch the file/provide an Open With list).
Windows(NT Kernal on) also permits longer extension names. EPUB is 4, Mobi is 4, AZW3 is 4
'metadata.calibre' causes no grief
RIP 8 dot 3