View Single Post
Old 11-30-2011, 01:09 AM   #36
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
As has been discussed here before, certain alignments in certain elements do not behave properly in iBooks unless they (improperly) contain other empty elements, e.g., spans; however, you have something else entirely occurring, and I suspect it's the "sgc" styling codes.

If I were in your shoes, I'd go through and regex every instance of, say, "sgc-5" which you intended to be a p code, and then style sgc-5 with a meaningful name in your CSS sheet as you want it to be. If you are trying to FORCE the reader to use a fully-justified text (which is, BTW, considered by many to be bad form, meaning, people don't like to have full-justification "forced" on them, FWIW), then try using empty spans inside the paragraph tags if your CSS doesn't work alone for the p formatting.

I would not rely upon ANY div formatting for chapter- or book-wide formatting overrides. I'd get rid of all those "sgc" CSS classes and name everything, then regex and replace everything with their proper class names...otherwise, you're just going to be going around in circles forever, and no one here can help you--at least I can't--because it APPEARS as though all the CSS was copy-and-pasted from various file headers inside the xhtml--which means you could have all sorts of cascading messes going on in there.

That's my best advice. Clean up the whole epub by changing your CSS classes, one at a time, and giving them proper names. Regex the ePUB itself and replace the sgc classes with the new names, and test it, one styling change at a time. It's tedious, but it's the only way to really troubleshoot a problem this disorganized. If you change 5 things at once, you don't have a control element to know what the hell you did that worked.

HTH.
Hitch
Hitch is offline   Reply With Quote