View Single Post
Old 04-07-2024, 05:10 PM   #26
hatuluang
Teluk Biru
hatuluang ought to be getting tired of karma fortunes by now.hatuluang ought to be getting tired of karma fortunes by now.hatuluang ought to be getting tired of karma fortunes by now.hatuluang ought to be getting tired of karma fortunes by now.hatuluang ought to be getting tired of karma fortunes by now.hatuluang ought to be getting tired of karma fortunes by now.hatuluang ought to be getting tired of karma fortunes by now.hatuluang ought to be getting tired of karma fortunes by now.hatuluang ought to be getting tired of karma fortunes by now.hatuluang ought to be getting tired of karma fortunes by now.hatuluang ought to be getting tired of karma fortunes by now.
 
hatuluang's Avatar
 
Posts: 156
Karma: 348662
Join Date: Jan 2023
Device: Kobo Clara 2E
Quote:
Originally Posted by jackie_w View Post
Yes, I suspected that this could possibly happen. It didn't on my testing but if it did on yours then we need to find something a little more robust.

The basic problem is that the 2 patches:
  • Custom synopsis details line spacing
  • Custom synopsis font size
are not really independent of each other because they are both trying to patch the same CSS resource (BookDetails.qss). Once we start making the Replace code longer than the Find code there is a possibility that kobopatch auto-removes what it considers "excess spaces" when the first patch runs. This results in the Find string from the patch which runs second failing because some spaces have been removed.

If you understood all that, well done! If not, never mind

The solution is to combine both patches into one. IMO this is what should have been done in the first place, but here we are many years later...

Leave this with me for a while. I think I can create a more robust patch which combines the 2 together. I'd like to test it myself before posting so check back here later.
ok, thank you...
hatuluang is offline   Reply With Quote