View Single Post
Old 09-10-2020, 02:05 PM   #19
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,709
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
@KevinH, do you know if the plugin framework's bk.addfile function honors a custom epub layout? I ask because the plugin in question (CssFromFont) will always create a "Styles/font.css" file if no css files exist. Even if the epub was created using a custom flat epub layout. But it's not the plugin requiring the creation of the "Styles" folder that I can see.

If I create a completely flat custom epub layout, and add font files to the new epub, they are properly added to the root of the epub. If I add an empty stylesheet file from the Sigil context menu, it correctly adds it to the root of the epub. But for some reason, the call to bk.addfile() in the plugin will always create the "Styles" subfolder if no css file exists in the epub for the plugin to modify. That's why I'm curious about how bk.addfile goes about determining where a file should be created (and if it honors a custom epub layout).
DiapDealer is offline   Reply With Quote