# Font in editor no longer monospaced?

**URL:** <https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087>\
**Category:** Development\
**Created:** [11월 30, 2017, 12:09오후 UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087 "2017-11-30T12:09:15Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)\
**Post date:** [11월 30, 2017, 2:45오후 UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087/10 "2017-11-30T14:45:13Z")

</div>

I’ve thought about this a bit before and I don’t hate the idea. The benefit of using a monospaced font is that it’s a quick indication of “this isn’t a WYSIWYG editor” and further distinguishes the editing space from the preview in the composer.

There are some downsides though; monospaced fonts do take a bit longer to read and have some general quirks. [IA Writer has spun these as benefits](https://ia.net/topics/in-search-of-the-perfect-writing-font/), but kind of caved and developed their own new “kind-of monospace” typeface to avoid those quirks.

 ![23 AM](https://global.discourse-cdn.com/meta/original/3X/2/2/228e1159da947d919033e03a9cfe4d8df3ed1a8a.png)

Either way, there aren’t any significant problems this solves with our existing editor, and it’s pretty easy for admins to customize this themselves on their instance - so any sort of additional feature wouldn’t be high priority.

---

_[View the full topic](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087)._