View Single Post
Old 05-19-2019, 08:04 PM   #26
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,705
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by lumpynose View Post
If I understand you correctly, I'm rather dismayed that you're forcing entity replacements.
Then you don't understand me correctly, because we're not forcing anything RE entity replacement.

& and < and > are entities that are always allowed due to coding specifications. They don't need preserving. They're always "legal" and need no special treatment. Adding them to the Preserve Entities list is causing them to be treated differently than they would otherwise would be.

Just remove & from your Preserve Entities list and your problem will go away.

Last edited by DiapDealer; 05-19-2019 at 08:08 PM.
DiapDealer is offline   Reply With Quote