I have users who edit their quote syntax poorly and cause the quote function to fail. For example we have this one from a current topic. This is un-escaped: [quote=“CFO.Digest.Input, post:1, topic:3258”] he suggested that I put mineral oil back in. [/quote] The problem is that the /quote is in st…

This was a conscious change a few years ago: [이미지] Discourse CommonMark migration plans confetti_ball balloon Development I may pull this out to another topic, but I feel that I need to hammer_and_wrench hamster some stuff. Inline multiline quote[quote]t…

Oh my… so we’re basically enforcing coding standards on our customers and users? While I agree with Sam’s analysis of the format, there is a difference between being difficult for the writer to read and difficult for everyone viewing the post to read. Kinda seems like we’re punishing the readers fo…

[이미지] Cardinalflyer: Edit: Another option would be to force a line feed after the [/quote] if there isn’t one there… auto-edit the format for readability. That doesn’t seem like a bad idea, but if they just select text and use the quote button it works. They are going back and editing the quo…

Yes they are! Quite remarkable, really… and not noticing that they are breaking the format in the process. I guess they don’t have the preview up? Or may be doing it by mobile… And the person who did this one of the principles in the business… glad I didn’t make him an editor! :slight_smile:

Aha! Mobile is a good bet. It’s hard too select just right and then you’d be ham-handed and have no preview when you tried to “fix” it.

This is still a recurring issue in my system. Here’s a message which came up today: [image] I edited the post with a carriage return after the closing quote tag, but still find it surprising that the text stream isn’t parsed like HTML where line feeds and carriage returns don’t impact the functio…

No, that’s how the tags work. You can’t randomly insert them in random order and expect things to work.

The order isn’t random, it is just fine. But unlike HTML, in this system is matters where the linefeeds happen to fall. All it took to fix that broken post was adding a line feed / CR after the closing tag. I’m willing to keep manually editing posts when users fail to comply with the required str…

Take a look at the markdown spec. Unlike HTML markdown is entirely dependent on well-placed line breaks. An errant line break in an <h1> element wouldn’t have any impact on rendering, but: here in markdo wn world it does This is true for lots of elements, markdown tables are horribly broken by ad…

[이미지] Stephen: throwing tags in without respecting structure I’m fine with navigating these waters, like any coder, but our users are civilians and would think markdown has something to do with prices at Walmart. As you say, thankfully we’re not asking them to write HTML! What is gained b…

Quote context impacts functionality of quote

지원

Falco (Falco) 1월 7, 2020, 8:16오후 2

This was a conscious change a few years ago:

글		댓글	조회수
Can we have the old Markdown for quoting paragraphs please? Feature	17	1357	8월 22, 2018
BBCode [quote] tag and mixed newlines Feature	4	1415	1월 26, 2022
Markdown quote requires blank line to end quote Bug markdown-it-review , markdown	6	11114	6월 26, 2017
Quotes containing code block must start with newline Bug	9	3493	5월 14, 2020
"Broken" quoting of/into email Feature	17	1809	7월 18, 2017

Quote context impacts functionality of quote

Related topics