MobileRead Forums - View Single Post

DiapDealer · 05-13-2025, 06:15 AM

Are these with preexisting epubs, or are they built from scratch? If the former, the easiest explanation for the difference is that the paths to the font files ARE actually different. Remember that Sigil no longer automatically restructures epubs to its older mandated layout.

The Book Browser tree is a logical one based on media types, and not a physical folder structure. So unless you're manually running "Restructure epub to Sigil Norm", the underlying paths could be different than what ../Fonts expects. Hold your mouse over resources in the Book Browser and the tooltip will show you the physical path to the resource within the archive. There's also a preference setting to show the full path in Book Browser.

Conversely: if you always run the "Restructure EPUB..." tool before adding embedded font css, then the ../Fonts path should always work.

05-13-2025, 06:15 AM	#2
DiapDealer Grand Sorcerer Posts: 28,473 Karma: 203853430 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Are these with preexisting epubs, or are they built from scratch? If the former, the easiest explanation for the difference is that the paths to the font files ARE actually different. Remember that Sigil no longer automatically restructures epubs to its older mandated layout. The Book Browser tree is a logical one based on media types, and not a physical folder structure. So unless you're manually running "Restructure epub to Sigil Norm", the underlying paths could be different than what ../Fonts expects. Hold your mouse over resources in the Book Browser and the tooltip will show you the physical path to the resource within the archive. There's also a preference setting to show the full path in Book Browser. Conversely: if you always run the "Restructure EPUB..." tool before adding embedded font css, then the ../Fonts path should always work. Last edited by DiapDealer; 05-13-2025 at 06:22 AM.