Quote:
Originally Posted by charleski
Well, the reason for the naming change was that the old method only worked if you had everything in one html file and then split that. If you were compiling a book from several files with chapter markers and then split them it could result in a great jumble in which it wasn't clear how the split files related to the original ones.
It might be possible to allow the split name to be specified in the hr tag, something like
<hr id="New_Filename" class="sigilChapterBreak" />
which would then specify the name for the file created after the tag. The filename would be limited to valid properties for the xhtml id attribute:
which is probably a good thing, though the colons would have to be stripped out.
As for the problem you had with the ToC - did you have spaces in the file name? I hope all the issues with spaces should be fixed in the next release.
|
Firstly - the ToC issues I had were on the older version mis-ordering the split files. I always started those splits using "Section0001.xhtml" as my single html file I was splitting from. I would import my "authorlast, authorfirst - seriesname ## - booktitle.html" file complete with spaces and rename it first thing to "Section0001.xhtml" then I'd do the auto-split-on-markers thing. But that was in the March 24th (?) release package for Windows x64. I'm not sure why I never tried the newer versions between then and the official 0.4.0 release - but I'm fairly sure that's the version I've been using until the last several days. Now it seems to split and remain in order in 0.4.0, I just have to work on the naming thing.
And yes, for me personally - being able to specify the new filename post-split in the hr tag would be excellent - if it can be done it would be a gigantic help for me personally (and I understand that being a big help for me doesn't particularly make it a worthwhile addition for Sigil's programming and worthwhile expenditure of programmer time - though I'd love it, I get that I'm not the only person using Sigil
). Even if it were limited to things like a filename of Cover or Chapter001 and the like without spaces or complex symbols would be awesome. I could then make the starter file "Cover.xhtml" then using the splits have simple but descriptive and helpful filenames as a result. I can do that currently, sure, but it can get rather cumbersome when some of the books end up with over 100 splits/chapter-breaks/files to rename. Even a one by one option for semi-manual splits using intact markers would help that issue - so I could split off the handful at the beginning that aren't chapters before doing the main split on the chapters (fewer to rename if I started off the mass chapter splits with a file named "chapter" or something).