Quote:
Originally Posted by theducks
Not directed at you.
I have no issue having a Long name for the Book CONTAINER (EPUB,ZIP). My question on 'Production Rules' of really long names for contind files. You and I seem to use a terse naming, wich is good enough to find (the typo in ch6  ) and reorder the pieces (how did the dedication get between ch19 and ch20 ?...). |
Oh, good
So...does that mean I'm not the only who finds the newer naming more helpful but not /really/ helpful perhaps and might be able to use some kind of id based name on split function if it were possible/offered? >.>
And yeah - I tend to (now that I have a reader that makes it easy to keep track while reading) mark errors in my books as I read them, compare vs print edition or a master digital copy (generally pre-html-ifying a document for example) to figure out where the error came from, then fix as needed in the html file - presently I just remake the ePub from the HTML source again - even for one little error in say...'ch006' because it is easier FOR ME than hunting down which one of the file splits (though I know it'll be after the file with 0006 at the end by 1-6 files) contains chapter 6 content and then from there to locate the line with the issue and repair it. Since I had to fix the typo/punctuation/error-of-random-type in the HTML, reconversion/epub creation just seems to be the fastest fix - but if I'm trying to rename all the split files (sometimes nearing or exceeding - though rarely - the 100 html file mark for content) again, that suddenly becomes less 'simple' if it is one error, but I've gone through larger book files and fixed dozens or even hundreds of errors (one book source I'd received for example had pulled out all the apostrophes when attached to a proper name, so I had to hunt down all the instances and fix em - re-conversion/creation there was really the best solution post-fixing all of em. But, would mean renaming to as you called it 'terse-naming' for all the splits again - some more automated way to do the naming on splits - huge help here
But yeah, it isn't a critical issue for me to have useful naming internal to the epub structure, I can go with the simplest form and just remake the epub any time I change anything in the html - at least now that I've figured out a few things with metadata, I can use the super simple process of:
drag html file to sigil's icon to import the files
rename the cover and book html to shortest name I can
hit F6 - quick eyeball over the names in case any got jumbled (this can fade away once all the bugs get worked out with file order and splits)
generate TOC to update/fix for splits (it looks like Sigil creates a TOC upon initial import but now update when you do the splits maybe? I just know if I don't hit the generate toc button, validation is...ugly)
save epub and validate
Oh, and until/unless it gets fixed, update id bits of the renamed files in content.opf pre-split to reflect new names, because my OCD works that way...