View Single Post
Old 04-07-2014, 02:27 PM   #630
Perkin
Guru
Perkin calls his or her ebook reader Vera.Perkin calls his or her ebook reader Vera.Perkin calls his or her ebook reader Vera.Perkin calls his or her ebook reader Vera.Perkin calls his or her ebook reader Vera.Perkin calls his or her ebook reader Vera.Perkin calls his or her ebook reader Vera.Perkin calls his or her ebook reader Vera.Perkin calls his or her ebook reader Vera.Perkin calls his or her ebook reader Vera.Perkin calls his or her ebook reader Vera.
 
Perkin's Avatar
 
Posts: 657
Karma: 64171
Join Date: Sep 2010
Location: Kent, England, Sol 3, ZZ9 plural Z Alpha
Device: Sony PRS-300, Kobo Aura HD, iPad (Marvin)
Just been re-reading the last few pages of the thread.

This was from post #574 made on 30-March
Quote:
Originally Posted by Rev. Bob View Post
Similarly, an option to remove SPAN tags with no attributes, and to merge adjacent SPAN tags with the same attributes, would also be nifty. Phoenix Pick is horrible about that last one. Merging adjacent or empty bold/italic tags would also be useful; cases like </i><i>, <i/>, and <b></b> should always be removed.
I thought about this and it could cause problems unless the previous starting tag has no extra class/styles, which would/could only be caught with a full parser rather than simple s&r's

Say you had
Code:
<i class="something">Here's</i><i> some text</i>
and removed the </i><i> then the ' some text' would also get the something class styling as well, which wasn't what was wanted.

Also thought about removing the empty tags i.e. '<i/>' or even '<i></i>'

Could there be a reason not to remove them ~ maybe they could be changing the layout somehow, that if they're removed the layout may be different ~

Somewhere in my mind there's a niggle - something to do with seeing an empty tag that caused an alteration of linespacing or widths or ????.

Anyway maybe it's more of a 'Do them by hand' rather than automated.
Perkin is offline   Reply With Quote