View Single Post
Old 06-23-2018, 09:43 PM   #6
retiredbiker
Evangelist
retiredbiker ought to be getting tired of karma fortunes by now.retiredbiker ought to be getting tired of karma fortunes by now.retiredbiker ought to be getting tired of karma fortunes by now.retiredbiker ought to be getting tired of karma fortunes by now.retiredbiker ought to be getting tired of karma fortunes by now.retiredbiker ought to be getting tired of karma fortunes by now.retiredbiker ought to be getting tired of karma fortunes by now.retiredbiker ought to be getting tired of karma fortunes by now.retiredbiker ought to be getting tired of karma fortunes by now.retiredbiker ought to be getting tired of karma fortunes by now.retiredbiker ought to be getting tired of karma fortunes by now.
 
retiredbiker's Avatar
 
Posts: 450
Karma: 3886916
Join Date: May 2013
Location: Ontario, Canada
Device: Kindle KB, Oasis, Pop_Os!, Kobo Forma
Thanks everyone...

Yep, I agree that styles belong in a css file, not a text file. That's what I ended up doing. I just hit this weird behaviour while I was trying to figure out how this particular book worked, and it bugged me no end.

And yes, beautifying files can help...along with "\s+" in the right places to allow for variable spaces and lines. Sometimes I'll even do a regex: replace \n with a space character, then replace two space characters with one until the replacements hit zero...that really cleans up a raggety file.


I've hit other odd - very odd - cases where the "select all files" did not seem to work, but this was the first one that seemed to have some consistency to it, enough that I could try and figure it out. Still confused, but at a higher level!

Last edited by retiredbiker; 06-23-2018 at 09:48 PM.
retiredbiker is offline   Reply With Quote