Quote:
Originally Posted by slowsmile
"I noticed too that when I ran the plugin and did not request the serif language option, it added it anyway. "
This plugin will only remove all font declarations in the CSS and replace them with default serif throughout in your epub if you chose the "Convert all ebook text and headings to serif throughout" plugin option. I've just tested this option and it seems to be working as it should. However, if you haven't explicitly declared a particular font within your text or heading style then this plugin will convert that text or heading to serif by default. The rule here, when using this plugin, is not to assume or use undeclared default styling but always explicitly declare the font(with a fallback i.e. serif or sans-serif) that you actually want to use in all instances. But on further consideration, what I might do is change that so that, rather than my plugin forcing an unwanted default font on the user's epub, it allows the plugin user to determine their own default font. So I think that I'll change that and put out an update for this soon which will be more in line with what you want as the plugin user.
|
I have always just gone with whatever Sigil does with the font. It's not like I have a problem with Serif. I was just surprised to see it added when I didn't select that option.
All I do when I run the plugin is choose the 'Reformat ebook images using percentage screen values to help normalize smaller image sizes across all ereaders.'
But when I do that I notice that some of my <i> tags have been replaced with <span style="font-style: italic;"> tags. I did not choose that option to have them replaced. (Not that replacing them is a bad idea. Is there any advantage to using the span tags for the italics?) What I also noticed is that the <i> tags are replaced only the first time they appear in the paragraph. After that they remain <i> tags. (I'll PM you the original file and then what it was after I ran the plugin.)
I did convert the .epubs to .txt files and ran a comparison and they were identical except for one thing: your plugin closed the space on the copyright (attachment).
Quote:
Originally Posted by slowsmile
"Hey, what I've been doing is making a copy of my most recent epub and then running your plugin on the copy. Then copying and pasting the HTML info for the images into the original file. To do that, I don't need to do anything with CSS, do I?"
You shouldn't have to worry about the CSS if you do the above because I avoid using classes or styles(in the CSS) and always use inline styling for the image styling instead. So, yes, you should be able to directly copy and paste the image formatting without problems.
|
Following up on that thought. I can just use the HTML without running the plugin, right? (I'm hesitant to use it on my published ebooks since they've already been proofread.)
And on your main plugin page you say add smallcaps after running the plugin but as far as I can tell, the plugin didn't bother my smallcaps.
And the plugin changed my asterisks. (Again, I don't know if that was a bad thing. It just got rid of a lot of non-breaking spaces.)