3 ms·
> "But that's exactly what the leading space syntax is for -- to markup quotes" Per the HN docs, leading spaces are meant for code, not quotes. > "Text after
by grzm 8y ago
> "But that's exactly what the leading space syntax is for -- to markup quotes"
Per the HN docs, leading spaces are meant for code, not quotes.
> "Text after a blank line that is indented by two or more spaces is reproduced verbatim. (This is intended for code.)"
https://news.ycombinator.com/formatdoc https://news.ycombinator.com/formatdoc
HN doesn't have specific formatting for quotes. Many people use leading '>' along with quotation marks and italics to set off quoted text.
- srean 8y agoAh I see, I got it wrong.
- Stratoscope 8y agoNo worries, it's an easy mistake to make. The formatting options on HN are pretty meager: two leading spaces (not four like Markdown) for block code, asterisks for emphasis. So it's natural that people try to make do with what's available. I don't mind, I get a lot of upvotes for posting those mobile friendly quotes. Just call me the Quote Fixer Bot. ;-) Markdown recognizes the > quote convention and puts the text in a <blockquote> so it can be styled, typically indented a bit with a vertical bar on the left. I wish HN did that too! A convention that is often used for quotes here is to both use the > and italicize them, like this: > *You can quote me on this.* which renders as: > You can quote me on this. This is especially useful when you are interspersing quotes with your own text, as grzm did above. I can't make up my mind which I like better for longer multi-paragraph quotes: the italics make it look more like a quote, but I find long stretches of italic text harder to read.