Quote:
Originally Posted by JSWolf
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.