Quote:
Originally Posted by geek1011
What is more complex about kobopatch? Most people have said it's simpler due to the combined instructions (like FindReplaceString), zlib support, and the overrides in kobopatch.yaml.
|
As Jackie_w says, people (in this case me
) is reluctant to change, specially when something is working and you have a known process that have not been changed for a long time. It is just that I am not a programmer and some of these things you mention sound like "Chinese" for me
.
Your system seems to be more "elaborated" and with additional options, and probably in the future I will move to it, but today I only use six or seven patches, not the full set, and with GeoffR patcher system, I only change numbers in some txt files following the instructions inside and run it. The system has not changed for a long time, whilst yours is moving very quickly, with some features that are tricky for me (e.g. it has overrides, that depend in a specific number of spaces in the line, different way to visually separate the patches inside the file ...), just little things but with a "higher" probability for me to mesh the fw, and just now I prefer spending more time
than
.
Anyway, I encourage you to follow the development of kobopatch, as it seems to be a good tool, and probably in the near future I will use it, as I do now with kepubify
(that by the way, I prefer over the use of calibre conversion through kobo addons).