This page is for posters to test comments prior to submitting them to WUWT. Here is a list of common formatting and special characters. You can try testing your comments below.
h/t to Ric Werme for compiling these tables.
Formatting in comments
Neither WUWT nor WordPress provide much documentation for the HTML formatting permitted in comments. There are only a few commands that are useful, and a few more that are pretty much useless.
A typical HTML formatting command has start and end pieces and has general form of <name>text to be formatted</name>.
A common mistake is to forget the closing tag like </b>. This can have consequences for the entire thread, so please be careful.
Also, WordPress does provide an autolink feature if you simply type in the URL into the comment form, there’s no need to use tags, but you can if you want. The risk is high, in that if you forget to close the tag, or format it improperly, you can cause you entire comment to become a link.
Don’t want to use codes? Try Comment Preview/Editing with Greasemonkey/CA Assistant
If you use Firefox, you can install Greasemonkey, and you can use it to do formatting and test it prior to submitting comments. Combine Greasemonkey with the CA Assistant (developed for Climate Audit by Mr. Pete) and you have a way to fully preview and edit comments prior to submitting – see details here
Commonly used codes for embedding in comments
|b (bold)||This is <b>bold</b> text||This is bold text|
|i (italics)||This is <i>italicized</i> text||This is italicized text|
|a (anchor)||See <a href=http://wermenh.com>My home page</a>||See My home page|
|blockquote (indent text)||My text<blockquote>quoted text</blockquote>More of my text||My text
More of my text
|strike||This is <strike>text with strike</strike>||This is text with strike|
|code (use for monospace display)||<code>Wordpress handles this completely differently</code>||
Special characters in comments
Those of us who remember acceptance of ASCII-68 (a specification released in
1968) are often not clever enough to figure out all the nuances of today’s
international character sets. Besides, most keyboards lack the keys for those
characters, and that’s the real problem. Even if you use a non-ASCII but useful
character like ° (as in 23°C) some optical character recognition software
or cut and paste operation is likely to change it to 23oC or worse,
Nevertheless, there are very useful characters that are most reliably entered
|Type this||To get||Notes|
|<||<||Less than signLeft angle bracket|
|°||°||Degree (Use with C and F, but not K (kelvins))
Alt + numeric keypad 0176 also works
|⁰¹²³⁴||⁰¹²³⁴||Superscripts (use 8304, 185, 178-179, 8308-8313 for digits 0-9)|
|₀₁₂₃||₀₁₂₃||Subscripts (use 8320-8329 for digits 0-9)|
|ñ||ñ||For La Niña & El Niño Alt + numeric keypad 0164 also works|
|±||±||Plus or minus|
| ||Like a space, with no special processing (i.e. word wrapping or multiple
|>||>||Greater than signRight angle bracketGenerally not needed|
[UPDATE] At the request of the mods, I’ve added this comment:
Mindert Eiting says:
January 30, 2014 at 2:36 pm
Could it be that the editor deletes sentences between unequal signs? I try it again: Comparing for example, from all stations included before 1970, those dropped during 1970-1991 and dropped (or not yet dropped) after 1991, I found a 27 sigma difference…
Good question, Mindert. In HTML, such as WordPress uses, the signs are reserved to indicate HTML instructions. They are not printed, but the instruction inside them is executed (like bold, italic, whatever).
So the excel style unequal signs will not print at all … but you can use what other computer languages use, which is != …
PS—If you want the “greater than” and “less than” signs to print, like I did above, use an ampersand (&) followed by either gt; or lt; for greater or less than. You need to include the semicolon.