Comment by kick
6 years ago
I tried it without, initially.
How'd you get the censored UNIX to work without italicizing half of the comment incorrectly? I tried escaping it in a few different ways, and no dice.
6 years ago
I tried it without, initially.
How'd you get the censored UNIX to work without italicizing half of the comment incorrectly? I tried escaping it in a few different ways, and no dice.
That must have been sheer luck! Or maybe because it was the last asterisk in the comment, and the ones before it were paired?
I took the original and replaced the doubled single quotes with regular double quotes, and surrounded the italicized quotes with asterisks. That seemed to do the trick.
Of course if the censored UNIX appeared earlier, or more than once, that would likely be a problem. Here are three of them in a row:
UNX UNX UN*X
Here's another idea. I suspect that the other Unicode asterisk-like characters might render without triggering italics. I'll use the asterisk operator (U+2217), heavy asterisk (U+2731), bold five spoked asterisk (U+1F7B1) in that order. Let's see how they look:
UN∗X UNX UN🞱X
OK, it looks like the heavy asterisk just disappears, bold five spoke is too big in Chrome on Windows and a box with an X in it in Chrome on Android, but the asterisk operator is a pretty good substitute for the regular one (albeit a bit small and light on desktop, a bit large on mobile). Now let's see if repeating it triggers any formatting:
UN∗X UN∗X UN∗X
I think we have a winner! Ah, the joys of HN comment formatting...