View Single Post
Old 10-03-2017, 06:30 PM   #9
jackie_w
Wizard
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 4,650
Karma: 11229177
Join Date: Sep 2009
Location: UK
Device: Sony:PRS-350, Kobo:Aura6"/H2O/GloHD/KA1/ClaraHD/Forma
Quote:
Originally Posted by JSWolf View Post
Can modifying the kepub header be made into a patch?
It depends. What modifications did you have in mind?

nickel patches are more difficult to share because the CSS to be modified is often compressed. This requires all changes to be hard-coded then converted into a hex-code GeoffR-style patch, i.e. one-size-fits-all - no ability to allow user customisation.

As a fictitious example, if the same compressed CSS stream could be patched to change 2 different style attributes - font-size, font-family. How many different combos of those 2 values would it take to keep everyone happy. You'd need a different patch created for each combo. Too many to be practical IMHO.

Using the pipcat-method for nickel patching is easier for users to apply the exact combo of values they want. Unfortunately there's quite a learning curve and is probably not suited to the casual user. Not to mention the amount of repetitive re-jigging involved every time a new firmware is released.
jackie_w is offline   Reply With Quote