Repost Enhancement Request: Polish Tool

[SteveB]

I want to repost 1314744 Enhancement Request: Polish tool which was knocked back. If it gets knocked back again I won't post it again but I honestly think it's an important point meriting a second try.

Here is the key point which I think I may have phrased badly the first time round.

The tool always ***wipes out the latest .EPUB without warning***.

Honestly I think it's the job of well-designed software to protect Joe User (me!) from their own stupidity!

Therefore it's my suggestion that the tool should either (a) warn the user when it's going to overwrite a newer .epub from an older .original_epub, or (b) make a sequenced backup of the .epub to .original_epub_nnn or suchlike

If you kill this again obviously I won't trouble you again, but seriously I won't be the last "stupid user" to lose work from this behaviour.

By the way the relevant tweak is quite well hidden...

Cheers, Steve

[Kovid Goyal (kovid)]

There is no guarantee that the .epub is the "latest" version. And the
feature is designed to protect joe stupid users, as *you* call them, from
doing an automated action that can potentially greatly change the book
being operated on. That is the more important use case to protect people
from, not yours. As the Polish tool says in its introductory text, use it
as the last step in your workflow, not as an intermediate step. If you
insist on using it in a way it was not designed to be used, the tweak
exists to accomodate you.

And no, I am not going to have calibre generate infinte numbers of
original_epub.nn copies, every time the tool is used. That would be
unduly burdening everyone to protect a few.

Software, like most things in life, is about tradeoffs, and almost
always, the tradeoffs are far more complex than someone approaching an
issue from a single perspective realizes.

 status wontfix

[Kovid Goyal (kovid)]

See
https://github.com/kovidgoyal/calibre/commit/5b009747b7d7c32338069ac917b844eed500b36a