Quote:
Originally Posted by user_none
The names of the files do not matter. If you don't like the name right click and select rename.
|
I understand that I can rename them, it can just get cumbersome over time with tons of files if you always rename certain parts the same ways and some books having over a hundred chapter files - automating the file naming on splits would be the greatest boon (if it can be done and if there is the time to implement such a thing - that would be an awesome thing for me - since I mostly use a template I'd be able to put the appropriate new file name properties with the split markers once and never have to fuss with it again). Or perhaps if each file starts (as mine almost all do) with a heading that goes in the TOC, using the heading/ToC label as a filename for that section - but I don't imagine nearly everyone doing that so that could be a lot more complex/impossible/less helpful.
For now though, yeah, I figure I'll do my files simple and similar to how I did them before as "Section" as my starting file name and let the split append numbering to it as before. I'm just trying to find a way to hopefully share ways to make the process as useful/simple/and helpful as possible for people like me I suppose.
I don't want to come across sounding like a petulant child who wants things her way just for the heck of it. I want very much to offer ideas that might help make the results from splits be more usefully named for those who do the kind of thing I do and like to have very consistent file names within all their created final ePub files. (At this point for example, I could let it go and accept that my older files will differ from my newer ones, redo all my old files to a new name-scheme based on a still possibly fluid name-scheme for splits, or try to come up with a possible way to make it so the internal file names will be consistent ten versions from now or fifty versions even if the way auto-split filenaming changes again - preferably without renaming every last split file every time I create another epub...).
My preference would be to help shape the process while bugs are still being worked out of file naming and proper ordering post-split instead of coming across it months from now and trying to get changes made to a system that may not need much work after all the little quirks have been worked out here and now...and I do know the current bugs are likely very minor, but at least presently that part of the code is still being mucked about with here and there for even minor fixes. That may be less true over time - as I stated previously - I'm not a programmer (though I do know a large number of programmers and have a bit of a clue about some codebases) - and that code may be frequently "touched" throughout developing other portions of Sigil over time.