View Single Post
Old 07-20-2014, 09:03 AM   #727
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,212
Karma: 148951761
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by Rev. Bob View Post
Stripspans sends that message whenever it makes any changes to the file. That covers everything from stripping spans to contracting/removing empty elements to de-indenting the <head> section.

If none of that is happening, that's a bug. If any of that is happening, the routine is doing as it should.
Why not have a separate message for the <head> routine and a separate message for the <span> removal? As it is, it looks (to the user) like it's removing spans when in fact, it may not be doing so. It's a false message for something it's not doing (in the case of the report I posted).
JSWolf is offline   Reply With Quote