View Single Post
Old 05-30-2011, 12:49 PM   #42
jackie_w
Wizard
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 2,911
Karma: 4329601
Join Date: Sep 2009
Location: UK
Device: Sony PRS-350, PB360, Kobo Glo/AuraHD/Aura6"/AuraH2O
Quote:
Originally Posted by kiwidude View Post
Hi Jackie,

I guess the question I have is how do you "know" that there are only .xpgt margins available? Is this something that only manual visual inspection of the css can reveal? In which case presumably a separate checkbox option would suffice for this. I guess my concern would be that if it is something you can only determine by using Tweak ePub, is it not just as easy to manually edit the .xpgt file at the same time?
I was not really thinking of automated decision-making by the plugin, just a user decision on an epub by epub basis. The first a user may know of the problem is when they try and read it on the device. The plugin would give them an option to correct and resend. I was thinking of it being targetted at less technical 'non-tweaking' users who aren't comfortable with the surgical approach.
jackie_w is offline   Reply With Quote