View Single Post
Old 06-28-2015, 03:41 PM   #24
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,645
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Purple Lady View Post
Or at least look at the text after the replace before saving. And shouldn't 'class="normal" only be in the css anyway? No need to do the replace in the text.
No, that would occur in the normal (x)html markup. Something like:
Code:
<p class="normal">This is normal body text</p>
The CSS would then contain something like:
p.normal { text-indent: 1.2em; text-align: justify; }

So it is necessary to replace it in the text (if you want to change the class name), but it's definitely a rookie mistake to try and match & replace everyday "words" in the html attributes without taking into account the possibility of those everyday words occurring in the content. Need to refine the search to isolate the markup/attributes only.

Last edited by DiapDealer; 06-28-2015 at 03:54 PM.
DiapDealer is offline   Reply With Quote