You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there! Thanks for making the kobopatch system, it's very useful. When converting my existing set of enabled patches to the override yaml file, I noticed I'm not able (or I just don't know the correct way) to include customizable user strings for patches that use them, so I can just have one master override file rather than edit the individual patch file to include my strings.
Example kobopatch.yaml with the monospace font patch:
This has been discussed quite a bit before (see the kobopatch threads in MobileRead), but most approaches were considered to have more disadvantages than advantages (especially as you can already have more than one patch file per target file, which is a workaround for this).
The syntax you propose seems quite a bit better than the existing suggestions (like placeholders) though, so I may consider implementing it this way.
Hi there! Thanks for making the kobopatch system, it's very useful. When converting my existing set of enabled patches to the override yaml file, I noticed I'm not able (or I just don't know the correct way) to include customizable user strings for patches that use them, so I can just have one master override file rather than edit the individual patch file to include my strings.
Example
kobopatch.yaml
with the monospace font patch:When running to the tool I get the following error:
If this isn't supported behavior, please consider this a feature request!
The text was updated successfully, but these errors were encountered: