MobileRead Forums - View Single Post - Why, During ePub to ePub Conversion does Calibre changes existing CSS classes?

JSWolf · 08-06-2011, 04:45 PM

But, can't things be changed so an ePub > ePub doesn't modify things that aren't asked to be modified? For one thing, if I have embedded font code, I end up with that being a really big mess. There is no way I want embedded font code in every XML file when it only needs to be in the CSS once. I cannot stand the 5pt margins added to every XML file. I don't like that some CSS gets modified and changed to calibre1 calibre2 etc while other CSS code is left alone.

The idea here is to get Calibre to not touch anything that's not being asked to be touched.

08-06-2011, 04:45 PM	#7
JSWolf Resident Curmudgeon Posts: 79,964 Karma: 147448039 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	But, can't things be changed so an ePub > ePub doesn't modify things that aren't asked to be modified? For one thing, if I have embedded font code, I end up with that being a really big mess. There is no way I want embedded font code in every XML file when it only needs to be in the CSS once. I cannot stand the 5pt margins added to every XML file. I don't like that some CSS gets modified and changed to calibre1 calibre2 etc while other CSS code is left alone. The idea here is to get Calibre to not touch anything that's not being asked to be touched.