Quote:
Originally Posted by KevinH
And linear="yes" makes no sense! Not using a linear attribute at all defaults to linear being "yes".
|
You know that. How many people using the plugin do? Or even know what "linear" means here?
I did not until yesterday after I spent hours looking around not knowing what I was looking for. Having the default actually written down would have given me a clue.
Quote:
Originally Posted by KevinH
So there is never a need to use "linear="yes". That is the spec.
|
The point is, you (or actually, people who aren't so familiar with the spec, like me) can see where to put "no".
I suggested "yes" as it would not change the current result. Making it "no" would be what I would want 99% of the time. So I would be happy with that.
Quote:
Originally Posted by DiapDealer
Because it's proprietary nonsense that people who have no intention of embedding fonts (let alone selling it on the iBooks platform) should have to have foisted upon their epubs just because they converted them to epub3?
|
Yes, it's proprietary nonsense. So is a lot of Amazon's stuff that we have to put up with if we use Kindle. And we have to accommodate Apple's nonsense if we use their hardware. If I want it to work on my iPad or my daughter's iPhone, I need to foist it into the OPF. We live in a proprietary world.
Having that line improves the formatting on a very popular platform, and has no effect otherwise, so again, aside from bloating the file by 52 bytes, what harm is done?
I brought these up because they are tweaks that I have to do every time I do an epub3 conversion. Ideally, they could be options in the plugin, either gui or some kind of ini file.
If no options are allowed, the above were suggested defaults that I think many users might find helpful.
Failing that, could be documented in a readme; there is none with the plugin now.
So, won't bug you about this any more.