You do know that all of that can be done via a custom Sigil plugin right now.
So instead of expanding and creating our our automation language, it is much better to simply let users handle it in a well-established scripting language like python via our Sigil plugin system.
And, in case I was not clear earlier when I said "a zip file is NOT a file system", a zip is a write once type of thing. Any modified files have to be written to the end (duplicated) and then the old record zeroed out. Most zip implementations just recreate the zip (smaller and faster) than trying to modify compressed file contents in place since any size growth means a complete rewrite anyway.
You really need to think about unzipping your files and working with them in git using FolderIn/FolderOut or your own custom input and output plugins. That way only modified files are added to the repo after the initial checkin, changes can be made readily apparent, tags that represent versions/revisions can be made, modification dates easily kept, etc.
This is why we created the Sigil Checkpoint feature using dulwich (pure python based simple/limited git implementation) so that state, fast saves, seeing modifications, etc can all easily be done.
You are thinking of (or used to?) unpacking a zip to a file system, working on individual files (no caching, no auto opf updates, no font obfuscation/deobfuscation, no etc...) and then rezipping and using zip file based mod dates to manage things.
Sigil is not just an IDE for editing a set of existing html files (editing a website like most IDE's can do), it does much more than that as it makes automatic changes to the OPF, rebuilds the Nav/NCX, properly updates manifest properties, set semantics, allows editing of metadata in dc format, that most IDE's for xhtml won't do or care about.
You best bet is either to go back to what you do at the xhtml file level, or accept what Sigil does and how it works and use it to its full extent.
Suggestions that try to revert Sigil back to a non-cached, file based system are not going to be accepted. If that bothers you, Sigil might not be for you.
Hope this helps explain why most of your suggestions are not making my To-Do list as you seem to be completely unaware of what Sigil can do in many cases. Sigil has its own way of handling things that either works for you or it doesn't.
Hope this helps,
KevinH
Quote:
Originally Posted by democrite
Someday some expansion of automation lists, or some revised method of automation could be nice.
Various things I change with all purchased EPUBs. Such takes a bit of time. Some may not be easily automated as of now.
- replace cover w/same image, or set semantics
- remove justification
- if base text isn't 100%/1em, change and scale other styles
- remove font-family from body text styles
- remove line-height from non-headers
- convert to EPUB3 if not yet, change page # tags (e.g. if specified as anchor) to EPUB3, run pagelist plugin
- delete common fonts such as LinLibertine, Charis, etc.
- to make navigation easier for larger books, add to h2+ headers link back to chapter id in html toc
- if no html toc, create - some option to add to NAV/TCX if not there, like hold down alt/option w/menu selection?
possibly more I can't think of.
For some of that, unsure if asked before. Could be some amount of work. Possibly far off as maybe some future feature? As one can modify styles in some web inspector, some style panel where one could easily add or remove attributes to style at cursor point, oh would be so nice.
|