[democrite]

Sounds like it'll either be hard to track down or we'd need to await a newer Qt 6. Minor issue, can be ignored.

Of other things I mentioned before, ...

Originally Posted by KevinH

Mass renaming, mass renumbering and mass changing of extensions are easily done. A Regular Expression Renamer was added to pretty much rename many things in any way. Manually renaming one file after another in a long list is not the way to go.

I am referring to after any rename or mass rename, cursor focus moves out of that panel. With certain publishers, file names are not helpful for locating a chapter, thus for future corrections of typos or other, naming them as such helps me. As the file names do not indicate chapter or metadata, I usually need to use some other editor to quickly locate range of files to rename, select, and rename. If cursor focus remained in pane, I could then more easily after, to continue with the next set like next section/part, simply use arrow key to go to next file, shift-down arrow to select next range, and continue renaming, e.g. select, cmd-option-R, arrow key to select more, repeat, without need to use mouse.

Same as, though I haven't tried it, maybe search/replace or other places within app, after performing an action, cursor focus remains.

I have yet to see a valid case where Sigil's gumbo repair parser broke anything, ever. I will need a full test case that clearly illustrates this happening.

That is the whole point of the Checkpointing feature added to Sigil. Say "no" to any changes on import. Hit make checkpoint. Now reload the epub but this time let Sigil fix things (Mend on open) and then compare to earlier Checkpoint's via the Sigils compare tools to see exactly what was changed and where.

Maybe for some their profession is EPUB-making. Some like us, modify purchased ebooks, most of the time. For similar reasons of another feature, it would be difficult to checkpoint all edited EPUBs in my calibre library.

What I am uncomfortable is code fixing that is from some syntax error. For various reasons, I tend to use BBEdit - search/replace multiple files is easier, file name I can use arrow keys to move between files and contents is shown in file view pane immediately (thus I can easily view chapter order, I tend to like restoring print order of front matter that's sometimes/often changed, ….

Header fix is fine. Other, over time I may make various edits. Perhaps unfamilar with how gumbo works, if there is some fix in missing close tag, misspelling of span/div/em/strong/etc., I am not sure if then when fixed, if there is some text where such tag is misapplied, some paragraph break combined, some unwanted paragraph break introduced, and so forth.

If it were possible to have distinct messages, such that "missing a DOCTYPE …", files that are not well formed", or a message that indicated both, I'd know what's happening. If that is not too much trouble and is possible, I'd be so much more at ease. For now, I may randomly edit any EPUB in my library, and I'm always uncomfortable seeing that message, and not knowing have I ever opened such in Sigil, is it first time, did I edit it once somewhere before and made an error, etc.

If it such is possible, it'd be much easier for me compared to epubcheck or other.

Sigil already allows users to install their own custom icon sets. If you create a set of mac-like svg icons and most importantly are willing to keep them updated and add new icons when needed in a timely manner, we would be happy to add them to our custom theme repo.

May get to that someday. I was thinking maybe some file format where one could specify and use installed fonts. As with some native APIs, one can specify typical OS UI fonts by character identifier, I think there are Qt libs on GitHub where one could do such or use unicode point. Maybe Qt will add such later if not, who knows. Would some possible change, such as an XML file specifying code point per icon someday make theme making easier over creating images? I don't know. Worth the effort, who knows. Minor thing.