View Single Post
Old 07-17-2021, 06:57 AM   #19
MicroDrie
Connoisseur
MicroDrie ought to be getting tired of karma fortunes by now.MicroDrie ought to be getting tired of karma fortunes by now.MicroDrie ought to be getting tired of karma fortunes by now.MicroDrie ought to be getting tired of karma fortunes by now.MicroDrie ought to be getting tired of karma fortunes by now.MicroDrie ought to be getting tired of karma fortunes by now.MicroDrie ought to be getting tired of karma fortunes by now.MicroDrie ought to be getting tired of karma fortunes by now.MicroDrie ought to be getting tired of karma fortunes by now.MicroDrie ought to be getting tired of karma fortunes by now.MicroDrie ought to be getting tired of karma fortunes by now.
 
Posts: 58
Karma: 438844
Join Date: Aug 2019
Device: PC, Linux Mint, Tablet, and Telephone
Quote:
Originally Posted by jhowell View Post
I have never seen these “rules” in the EPUB specification.
Regardless of whether this is a formal epub rule, it is as Sigil expects how you organize your epub content.

If you add an HTML file to Sigil that refers to a CSS or JS file in the same directory, it will try to place these files in and the reference automatically to those sub directories. This does not always work, so you have to manually add the missing file to the correct directory and adjust it references in the Text directory file.

That's why sometimes things don't work because a js or css file is pointing to the wrong location. This is especially true for a css of js file that refers hardcoded to a font file location.
MicroDrie is offline   Reply With Quote