Title: [Plugin: TinyMCE Entities Patch] yes, but&#8230;
Last modified: August 19, 2016

---

# [Plugin: TinyMCE Entities Patch] yes, but…

 *  [maddler](https://wordpress.org/support/users/maddler/)
 * (@maddler)
 * [17 years, 10 months ago](https://wordpress.org/support/topic/plugin-tinymce-entities-patch-yes-but/)
 * I understand your point of view, and don’t have anything against your plugin (
   I apreciate your effort!), but what you say could be rendered with three words:“
   writing bad html”
 * If you want to indent your code you can use BLOCKQUOTE, or keep spaces using 
   PRE
 * Also &ampersand;lt; and &ampersand;gt; have special meaning in HTML, so if something
   is enclosed among &ampersand;lt; and &ampersand;gt; it will be seen as a tag (
   an invalid tag, most likely) that’s why they are being translated as &ampersand;
   gt; and &ampersand;lt;
 * So if you write something like “<this won’t work>” without html entities being
   transleted you would only see “” (withound any text).
 * If you don’t want your text being (badly?) modifid:
 * 1) just use proper tags
    2) do not use visual editor
 * [http://wordpress.org/extend/plugins/tinymce-entities-patch/](http://wordpress.org/extend/plugins/tinymce-entities-patch/)

Viewing 1 replies (of 1 total)

 *  [EnglishMike](https://wordpress.org/support/users/stringfold/)
 * (@stringfold)
 * [17 years, 10 months ago](https://wordpress.org/support/topic/plugin-tinymce-entities-patch-yes-but/#post-808668)
 * Hey maddler, I understand your comment, but I respectfully disagree. The whole
   point of this little plugin is to make it easier to write posts without having
   to switch to HTML mode and use tags that at least some bloggers won’t know about.
 * Visual mode is a WYSIWYG mode and should *be* a WYSIWYG mode (or as close as 
   possible) and not convert HTML entities that typed in visual mode — it should
   leave them alone (or, at least convert them to HTML that will make sure they 
   appear in the post as they were typed).
 * When I am in visual mode, when I type &ampersand;lt; and &ampersand;gt that’s
   because I *want* &ampersand;lt; and &ampersand;gt; to appear in my post, not 
   < and >. I should not have to jump though hoops whenever I want to insert any
   HTML entity in a post. When I type < and > TinyMCE converts that to &ampersand;
   lt; and &ampersand;gt; under the covers to make sure that you always get < and
   > in the post, so why shouldn’t users expect the same to happen when they want
   an HTML entity to be displayed in a post (and not the character it represents)?
 * Sorry, but forcing users to switch to HTML every time they want to do a little
   formatting or insert anything beginning with an ampersand is just bad usability—
   especially when there is a very simple fix/patch available.

Viewing 1 replies (of 1 total)

The topic ‘[Plugin: TinyMCE Entities Patch] yes, but…’ is closed to new replies.

 * 1 reply
 * 2 participants
 * Last reply from: [EnglishMike](https://wordpress.org/support/users/stringfold/)
 * Last activity: [17 years, 10 months ago](https://wordpress.org/support/topic/plugin-tinymce-entities-patch-yes-but/#post-808668)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
