Post reply font

[szinski]

Is there any way to change the font that the editor uses when composing a new message?

Right now it looks like Courier or some other monospaced font that's not how it appears after it's posted to the forum.

Using Curve2 theme.

Thanks.

[Kindred]

modify the CSS for the editor

[JBlaze]

/Themes/default/css/jquery.sceditor.css

Code Select Expand

.sceditor-container textarea {
font-family: "DejaVu Sans Mono", Monaco, Consolas, monospace;
}

[szinski]

Thanks, found it in jquery.sceditor.css and fixed using:

Code Select Expand

.sceditor-container textarea {
        font-family: Verdana, Arial, Helvetica, sans-serif;
        /* font-family: "DejaVu Sans Mono", Monaco, Consolas, monospace; */
}

Please use code tags when posting code, even code as short as this. ~ Steve

[Sesquipedalian]

Just because I want to make sure that you are aware, you can already get what you are asking for by simply switching the editor into "what you see is what you get" mode. Just click the editor toolbar button that looks like a page with lines on it. It's the one at the end of the toolbar, shown in the image below:
You cannot view this attachment.

You can control whether the editor starts in source mode or WYSIWYG mode in the Look and Layout section of your user profile.

The included CSS uses the monospace font only when the editor is in source mode, not WYSIWYG mode. If you click the button to toggle into WYSIWYG mode, it will use the variable-width font. This was an intentional design choice to help make it apparent to the end user which mode the editor is in. You are, of course, free to change the CSS as described above, but if all you want is to have the editor text closely resemble the final post text, then just switch to WYSIWYG mode.

[szinski]

@Sesquipedalian -- perfect!! that did the trick. I'll reset that theme option for all users.

[JBlaze]

You know, it's taken me 15 years to figure out what WYSIWYG meant...

What
You
See
Is
What
You
Get

I'm gonna go cry now.

[Antechinus]

Lol. Dude, how did you not get that before?

And why, oh why, did anyone ever think this was a sane font stack to use? Beats me how it ever became popular in the first place...

Code Select Expand

font-family: Verdana, Arial, Helvetica, sans-serif;

The included CSS uses the monospace font only when the editor is in source mode, not WYSIWYG mode. If you click the button to toggle into WYSIWYG mode, it will use the variable-width font. This was an intentional design choice to help make it apparent to the end user which mode the editor is in.

It was a shocking choice that had nothing to do with design. There would have been any number of far less crude ways to indicate which mode the editor was in.

[GL700Wing]

You know, it's taken me 15 years to figure out what WYSIWYG meant...

What
You
See
Is
What
You
Get

I'm gonna go cry now.

I remember first hearing the WYSIWYG acronym used almost 40 years ago (and at that time we also used to occasionally refer to a local and rather unsuccessful sporting team as SWYSIWYG - 'Sometimes what you see is what you get') ...

[zedd151]

the WYSIWYG acronym

Pronounced whizzie-wig 

[Steve]

No offense @JBlaze but that's too funny. Took me months to figure out that LOL didn't mean 'lots of love' ... 

[Sesquipedalian]

It was a shocking choice that had nothing to do with design. There would have been any number of far less crude ways to indicate which mode the editor was in.

[Antechinus]

[JBlaze]

Lol. Dude, how did you not get that before?

Honestly, I thought it was just another weird acronym and never gave it much thought. Just pronounced it WhySeeWig Editor XD

[Arantor]

Personally I think editing code (which source mode is), is a monospace font makes sense. But I'm weird, and I also remember when WYSIWYG was either more WYSIHWYMG (what you see is hopefully what you might get) or simply WYSIWTF.

There is an argument that bbcode is passé now and should be abandoned in favour of full WYSIWYG with no exceptions (as Invision Community has done for years) or tried to largely downplay bbcode (as XenForo does) and the fact both are moving to an editor that does not natively support bbcode in their next versions (they're both going to TipTap) should be an interesting observation.