{"id":283,"date":"2020-03-22T22:45:39","date_gmt":"2020-03-22T21:45:39","guid":{"rendered":"https:\/\/pmortensen.eu\/world2\/?p=283"},"modified":"2025-12-06T15:32:15","modified_gmt":"2025-12-06T14:32:15","slug":"bold-and-italics-in-youtube-comments","status":"publish","type":"post","link":"https:\/\/pmortensen.eu\/world2\/2020\/03\/22\/bold-and-italics-in-youtube-comments\/","title":{"rendered":"Bold and italics in YouTube comments"},"content":{"rendered":"

If you use a search engine, you may find out the base rules for styling in YouTube comments, but they never<\/em><\/strong> tell you the whole story (for it to actually work in all cases). In fact, at first glance, it appears styling in YouTube comments is broken. But it is not! – read on to see how it can be made to work reliably. Note, however, that bold is currently broken<\/em><\/strong> (as of 2020-11-09).<\/p>\n

Base rules<\/h2>\n

Italics<\/h3>\n

Enclose the text in a pair of underscores, “_”.<\/p>\n

Example:<\/p>\n

Part of this is _to be in italics_ and other parts not.<\/code><\/p>\n

Result:<\/p>\n

Part of this is to be in italics<\/em> and other parts not.<\/p>\n

Bold<\/h3>\n

Enclose the text in a pair of asterisks, “*”.<\/p>\n

Example:<\/p>\n

Part of this is *to be in bold* and other parts not.<\/code><\/p>\n

Result:<\/p>\n

Part of this is to be in bold<\/strong> and other parts not.<\/p>\n

Bold and<\/em> italics <\/h2>\n

Just enclose the inner (italics) in bold, just like any other text.<\/p>\n

Example:<\/p>\n

Combining *_both italics and bold_* is easy.<\/code><\/p>\n

Result:<\/p>\n

Combining both italics and bold<\/em><\/strong> is easy.<\/p>\n

Strike through<\/h3>\n

Note: This is a poor form of a revision history and it should seldomly be used.<\/p>\n

Enclose the text in a pair of dashes (actually minus signs), “-“.<\/p>\n

Example:<\/p>\n

I -wildly guessed- did extensive research to find...<\/code><\/p>\n

Result:<\/p>\n

I wildly guessed<\/s> did extensive research to find…<\/p>\n

More rules<\/h2>\n

Without observing these, the styling may simply silently fail.<\/p>\n

There must not<\/em> be a space at the beginning and end of the enclosed text<\/h3>\n

That is, immediately<\/em> after the first underscore or asterisk, there must be a number, letter, or special character. If it is a space, the text styling does not work. In other words, the inner text must not have leading or trailing space. <\/p>\n

The same immediately<\/em> before the last underscore or asterisk.<\/p>\n

There must<\/em> be a space to either side of the formatting characters<\/h3>\n

That is, for example, a space before<\/em> the starting underscore and a space after<\/em> the ending underscore.<\/p>\n

This sometimes forces you to use the Indian space<\/a> (from the outdated 1935 Wren & Martin textbook<\/a><\/em>). It is not ideal, but some alternatives are: 1) Leave out the punctuation 2) Use dash\/minus to continue into a second part. 3) Use the hair space<\/em><\/a>, Unicode<\/a> U+200A<\/a> (“\u200a”. E.g., it can be entered with Ctrl<\/kbd> + Shift<\/kbd> + 200A + Return<\/kbd> on Linux (e.g. Ubuntu<\/a>\/Cinnamon<\/a>) and it also works copy-pasting it from this page). 4) Add some content in parentheses (as there is a space before the opening parenthesis). E.g., ” (see also XYZ)”<\/em>.<\/p>\n

Example where a space is needed before punctuation in order for the styling to work (bold):<\/p>\n

Well, I *lost a pawn* , but it's just a pawn.<\/code><\/p>\n

Result (note the Indian space between “pawn” and the second comma (“,”)):<\/p>\n

Well, I lost a pawn<\/strong> , but it’s just a pawn.<\/p>\n

A hard linebreak resets the formatting<\/h3>\n

For multiline text (where you insert hard line breaks), the formatting must be applied for each line. Hard breaks are necessary in YouTube comments when indenting is to be preserved.<\/p>\n

Example where all of the text is to be in italics:<\/p>\n

_\"One of the spires of Zagreb Cathedral broke off and fell on_
\n _the Archbishop's palace. ... A part of the roof of the_
\n _Croatian Parliament building collapsed.\"_<\/code><\/p>\n

Result:<\/p>\n

“One of the spires of Zagreb Cathedral broke off and fell on
\nthe Archbishop’s palace. … A part of the roof of the
\nCroatian Parliament building collapsed.”<\/em><\/p>\n

Beware of asterisks and underscores in the original text<\/h3>\n

Example, in a URL:<\/p>\n

en DOT wikipedia DOT org\/wiki\/Ian_Nepomniachtchi<\/code><\/p>\n

This is difficult or impossible to get in italics because of the underscore between “Ian” and “Nepomniachtchi”. The workaround is to format in bold (using asterisks) instead.<\/p>\n

YouTube breaks stuff and never fixes anything<\/h2>\n

Exhibit 1<\/h3>\n

On 2020-05-21 YouTube comments broke. After having worked flawlessly for years, now it does not seem possible to have empty lines in YouTube comments (it could be an overreaction to the problem of too many empty lines when using the (physical) Return key). And leading space (for indent) may be removed.<\/p>\n

This was observed on Linux (Ubuntu 19.10 (Eoan Ermine)<\/a>, but with Cinnamon<\/a> as the desktop environment) with Firefox 76.0.1 (current on the date). Though the operating system shouldn’t matter, and probably not the particular web browser either.<\/p>\n

Workaround<\/h4>\n

For empty lines, the workaround is to add a space on the line that should appear empty. Also, Edit Overflow’s YouTube formatter<\/a> (button “Transform for YouTube comments”<\/em>) has also been extended with this workaround such that it can also be used to preserve empty lines.<\/p>\n

Exhibit 2<\/h3>\n

On 2020-07-09 bold<\/strong> in YouTube comments broke – it was rendered as normal text (italics<\/em> still worked). There didn’t seem to be a workaround. <\/p>\n

On 2020-07-30 it worked again (but didn’t a few days prior). It broke again in August 2020 and was broken until 2020-09-28. But then it was promptly broken the same day – as of 2020-10-09 it was still broken. <\/p>\n

On 2020-11-01 it started working again (both when adding new comments and old comments with bold formatting (asterisks)), but again only for a single day. <\/p>\n

As of 2020-11-09 it is still broken. Why in hell can’t they add a regression test for a simple thing like this????<\/p>\n

On 2021-03-11 it worked again, but it was broken again one day later. <\/p>\n

Exhibit 3<\/h3>\n

In 2021-02, editing of comments (effectively) broke. In about 50% of the cases, an error is displayed after submitting an edit. And the comment is deleted \/ lost! And resubmitting the content (e.g., it could be in a text document or in the clipboard) will fail with an error – you are essentially blocked from having that comment active that you just wanted to edit (it is not clear how long or under which conditions this persists – it may be possible to resubmit it at a later time. In any case, it is a huge hassle). <\/p>\n

Any action after the first failure, even adding new comments, may fail silently<\/em> (you are not even told it failed – content is lost). This is even on different pages, in different browser tabs, and also after restarting the web browser. It may or may not be necessary to wait 24 hours before attempting it again.<\/p>\n

The workaround is to never edit directly. Instead, open for editing, copy the content to the clipboard, cancel the edit, delete the comment, and create a new comment with the edits included.<\/p>\n","protected":false},"excerpt":{"rendered":"

If you use a search engine, you may find out the base rules for styling in YouTube comments, but they never tell you the whole story (for it to actually work in all cases). In fact, at first glance, it …<\/p>\n

Bold and italics in YouTube comments<\/span> Read More »<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[15,42],"tags":[],"_links":{"self":[{"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/posts\/283"}],"collection":[{"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/comments?post=283"}],"version-history":[{"count":95,"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/posts\/283\/revisions"}],"predecessor-version":[{"id":2282,"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/posts\/283\/revisions\/2282"}],"wp:attachment":[{"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/media?parent=283"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/categories?post=283"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pmortensen.eu\/world2\/wp-json\/wp\/v2\/tags?post=283"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}