Why can't I get WYSIWYG to work when I'm writing. [B.]I always get something that looks like this. [/B] (without the period after the initial B). That is to say, the post comes out looking correct, but I thought it should be WYSIWYG while I was composing.

Cos the text box is in plain text and only shows you the HTML markup and not the end result (which would require the text box to support rich text. Just one of the drawbacks of the forum platform this forum is built on, I guess.

I use "Preview Post" button before "Submit Reply". It doesn't show exactly everything as it will be (no YouTube links resolution, etc.) but pretty much everything about formatting. Plain text has certain advantages about editing, by the way.

snareman wrote

Why can't I get WYSIWYG to work when I'm writing. [B.]I always get something that looks like this. [/B] (without the period after the initial B). That is to say, the post comes out looking correct, but I thought it should be WYSIWYG while I was composing.

Currently, there is no difference between the "Standard Editor" and "Enhanced Interface" choices for the "Message Editor Interface" setting. I'm not sure if this is intentional or not. But you're right, it's not actually WYSIWYG.

Perhaps Mark can chime in?

No one wrote

I use "Preview Post" button before "Submit Reply". It doesn't show exactly everything as it will be (no YouTube links resolution, etc.) but pretty much everything about formatting. Plain text has certain advantages about editing, by the way.

Yea, I do that as well.

mkoesel wrote

Currently, there is no difference between the "Standard Editor" and "Enhanced Interface" choices for the "Message Editor Interface" setting. I'm not sure if this is intentional or not. But you're right, it's not actually WYSIWYG.

Perhaps Mark can chime in?

Ah. Good to know. It's never worked for me on any forums with this software so I thought maybe it was on my end somehow.

No one wrote

I use "Preview Post" button before "Submit Reply". It doesn't show exactly everything as it will be (no YouTube links resolution, etc.) but pretty much everything about formatting. Plain text has certain advantages about editing, by the way.

Do you know how much of a mess my sig file looks like in the plain text editor?

snareman wrote

Do you know how much of a mess my sig file looks like in the plain text editor?

No I don't, but you can clean the mess if there's something unnecessary (like localizing a link, etc.). This was what I meant.

No one wrote

No I don't, but you can clean the mess if there's something unnecessary (like localizing a link, etc.). This was what I meant.

Yes, I agree. It does work well for some things.

Here is a pic of the long version of my sig. It does take a little brain power when I want to edit it

snareman wrote

Here is a pic of the long version of my sig. It does take a little brain power when I want to edit it

Don't overstrain your brain. Apply coding basics: use structured text. That is put every section ([FONT],, etc.) on a separate line (split complex sections the same way) and visualize nesting by indentation (multiply tab by nesting level). There should be free simple tools automating it available online, I guess.

No one wrote

Don't overstrain your brain. Apply coding basics: use structured text. That is put every section ([FONT],, etc.) on a separate line (split complex sections the same way) and visualize nesting by indentation (multiply tab by nesting level). There should be free simple tools automating it available online, I guess.

You have already gone over my head from your undisclosed location.