3 ms·
So frustrating that both Markdown and this don't support underlines.
by kbd 11y ago
So frustrating that both Markdown and this don't support underlines.
- treve 11y agoI don't think this is the right way to look at this. They both transform to the most sensible html given the input. If you want to use an underline for emphasis instead of cursive, this is more of a style concern than anything else, so the appropriate place to change this would be in the stylesheet, which is perfectly possible. If you specifically want it to output the <u> html tag, I agree that this is not as convenient.
- grimman 11y ago> They both transform to the most sensible html given the input. I'm going to have to disagree with you. Long before Markdown came along, the convention was to use asterisks for * bold *, slashes for /italics/ and underscores for _underlined_ text. And that's just for starters. Those three examples perfectly convey the intended effect, quite unlike the Markdown versions where asterisks will somehow imply italics, but only if they're single asterisks? It's a strange thing!
- ape4 11y agoI agree. _this_should_be_underlined_
- bobisme 11y agoThat's because underlining is inferior typography. It's from back in the typewriter days when the only way to add emphasis was to back up and put underscores underneath the text. Either bold or italic is more preferable.
- TeMPOraL 11y agoUnderlining also represents the thing you often do with a pen on printed text. It's perfectly OK and useful type of formatting online.
- Mtinie 11y agoThat's well and good, but the reason that it is appropriate when using a pen on printed text is that the vast majority of people don't differentiate their penmanship when representing emphasized text. Historically underlined content == actionable hyperlink; for content that is intended for public consumption (ie. not a note that you're writing for your own use) there are usability issues with typographic styles that represent emphasis with an underline.