View Single Post
Old 06-28-2015, 09:54 PM   #28
Turtle91
A Hairy Wizard
Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.
 
Turtle91's Avatar
 
Posts: 3,375
Karma: 20212733
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
Quote:
Originally Posted by DiapDealer View Post
I'm merely pointing out the likely Search & Replace scenario that caused the snafu in the first place. I enjoy reverse engineering those kinds of S&R screw-ups.
Oh, I know...just thought I'd throw out the absurdity of putting something like <p class="normal"> or <p class="paragraph">

Quote:
Originally Posted by DiapDealer View Post
The memory bits "saved" in an ebook by not doing so are meaningless, IMO.
Perhaps... for a single paragraph, certainly. But when you have 7000 paragraphs in a book it adds up. Now add up the several thousand books in an elibrary... not something to pooh-pooh.
...and there is always the fact that the larger the file size, the more styling codes a device has to chunk through to properly render the text, the longer it takes... and the device tends to bog down.
...and it's just not good practice...it's like spaghetti programming...ewww
Turtle91 is offline   Reply With Quote