Quote:
Originally Posted by theducks
I am curious: Why does it matter what the internal filename is called, as long as it is correct.?
I understand the use of Meaningful naming: cvr.jpg is just as meaningful as 9781234567890_cover_image.jpg
having names for sections allows easy manipulation of order:
p01.html
c09.html
ded.html
inline.html
work for me just as well as a long name
Just how many times do the individual files exist separately (un-ziped) that they need their filenames encoded with the full Title and/or ISBN?
|
I'm not 100% clear on what you're asking - or even if the question is directed to me, but I can try to clarify my position.
My file names don't need to be long by any stretch of the imagination - but - I keep my source HTML files for use outside of ePub creation. So, I have a file/folder structure that is pretty simple for me to navigate and has all the info without opening files to read metadata to make sure "this file is part of this book/series/author/isbn.
All my final file names (the epub, lit, mobi/prc, pdf, word, rtf, html and cover) - whatever I convert the file to and the source file - are the same with the only difference being the extension. My folder structure is: %bookstoragelocation%\authorlast, first\all their books
My file name structure is set to give me the author name again because I don't always folderize on devices: authorlast, first - seriesname ## - book title followed by each extension. (also makes it easy to zip up the collection of file formats for a single book for archival - without using more folder sublevels as well)
I use a basic template for my html file which lets me quickly use replacement "masks" for each segment of naming (as well as easy replacements for my title page and metadata using the same "masks"). So internal to the html file, my naming is simple and provides quick and easy replacement for things that aren't solely filename references.
Within Sigil - I do try to keep my file names short - that's why I purposely rename the files instead of leaving the initial file and letting it split with that big long filename (the spaces being the other reason right now - but even if I used underscores in place of spaces, I'd still rename the first file to make it shorter and clearer). Having the old filename appear as the id - to me - is less desired due to the additional "clutter" and inaccuracy that the mis-match causes. 'bookcontent_0005' isn't as clear as 'ch_003' would be for example.
I do love that Sigil will replace all instances of the old name of a file with whatever I rename it to throughout the book's html code making renaming easier. I would just love to be able to put into my template that the section that splits off the dedication into its own file should be named "dedi.xhtml" instead of filename_0002.xhtml, or "ch_0001.xhtml" instead of filename_0004.xhtml.
I could do the splits manually and rename files split off one by one until I get to the beginning of the chapters - then rename the renaming chapter source to 'ch.xhtml' thus having all the remaining splits give me chapter identifying filenames (just needing to change the ch starter file to include _0001 and the final split or two to reflect the inline toc or epilogue). To me though - I put split markers in there to automate as much as possible and there isn't a way that I can tell to have Sigil find and split only the first marker short of finding it in the file and doing a manual split.
I guess what I'm getting at is that the new file name on split being based on the starter file name is no more "meaningful" (in my case) than naming each file in the series a basic number with no description at all as it was before with just "section" and a number. Now - IF I used multiple html source files - I could certainly see how it would be more useful, I could have each of the unique files separate and just one file for the book chapter content that I could then split. I just try to keep my own filesystem outside of epubs as simple and clean as possible too. I'd rather not have each book have its own folder with a series of html files for example - since I can get Sigil to split the single file where I want it split, why should I store more than one html file for the book otherwise?
Sorry I get long-winded - but I hope I explained a bit better here if that was directed by way?