View Single Post
Old 03-06-2024, 06:28 AM   #11
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,341
Karma: 203719142
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by DNSB View Post
I was not aware of the existence of a TagEditor plugin. If this was a reference to TagMechanic, given the OP needs to choose which <i> tags stay as <i> or change to <em> or <cite>, I was not aware that TagMechanic could do more than a wholesale change.
If there's no named attributes that can determine which i tags should stay as i tags, then yes, TagMechanic probably won't help much. But it's certainly possible to do less than a wholesale change with TagMechanic when the attribute strings--like the class name--offer delineating criteria.The plugin can operate on only naked tags (no attributes), or only on tags with particular attribute values, or only on tags whose attribute strings match a particular regexp. It's not a blunt, whammy-all-or-nothing instrument (though it certainly can be used that way too).

Last edited by DiapDealer; 03-06-2024 at 06:41 AM.
DiapDealer is offline   Reply With Quote