39

That becomes unreadable in the mobile version (screenshot for iOS 6, iPhone 5):


30

Like this: > Case 1 > > 00:23 > > 00:54 > >   > > Case 2 > > 00:21 > > 00:51 Which produces: Case 1 00:23 00:54   Case 2 00:21 00:51 Alternatively, placing two spaces at the end of a line with no empty line after it creates a line break rather than a new paragraph, ...


22

It's called a "quote" for a reason. You use it when you're quoting something.... mostly. And how you use it will depend to some degree on the site you're on, so if you see them using it in a way that's not a quote, check in to see if that's standard for them on their meta. So, if you're answering a question and quoting a resource, you put the quoted text ...


18

yes sure why not it's not really that bad or worth making rules or special formatting logic to deal with ...


18

I think two issues are being confounded: copyright and plagiarism. From a copyright standpoint, if a work that I use but which is not mine is in the public domain, then there cannot be a legitimate copyright infringement claim against me, no matter how I use the work. From a plagiarism standpoint, if I take parts of the work and pass them as my own, then I'...


18

Use comment markup <!-- --> and an extra whiteline between the quote blocks: > Are questions about Microsoft Word Online on-topic here? I don't > really see any posted here, but perhaps I am not searching correctly. > - mweiss <!-- --> > Yes, they are. We even have a specific tag: [tag:word-online]. -ale <!-- --> > ...


15

This space intentionally left blank. ...


15

Is this what you wanted? > Are questions about Microsoft Word Online on-topic here? I don't > really see any posted here, but perhaps I am not searching correctly. > - mweiss <span></span> > Yes, they are. We even have a specific tag: [tag:word-online]. -ale <span></span> > Thanks! I'm sorry I missed that tag. -...


14

Yes, since this is a quote, you should indeed use markup to indicate that it came from that source and is not original.


13

What about this? Is this also trolling? :-)


12

You don't need HTML: a markdown list in quotes Even with numbers: more less > You don't need HTML: > > * a markdown > * list in quotes > > Even with numbers: > > 1. more > 2. less


11

To add the four spaces for code simply highlight the block of text and then hit Ctrl+K or select the {} icon. This will format all the lines of code for you. To quote just add a single > to the beginning of the first line of each paragraph you want to quote. There's no need to do it on every line. Alternatively, just highlight the block of text and hit ...


9

If you don't want a list, you can escape the dot: > 50\. Quoting point number 50. Produces: 50. Quoting point number 50. By the way, it works the same way without the quote block (>).


8

Personally I'd suggest style #2 to be used, because #1 already has a meaning in Markdown: it's used to indicated nested quotes. This markup: > Foo said: >> Something or another produces this output: Foo said: Something or another It doesn't really render in a nicely readable way, but it does exist (and the visual display is just ...


8

In Markdown, you have to insert two line breaks to cause an actual linebreak (a new paragraph, to be precise). That's not only true in blockquotes. For example, single line break gives single line break and > one deep >> two deep >>> three deep >> two deep > one deep gives one deep two deep ...


8

You just need to escape the # with a backslash, like this: > \#test which parses as: #test BTW, note that you can also have a code block inside a quote: > #like this which parses as: #like this


7

The way you have it formatted is a code block inside a blockquote. You still have 4 spaces in front of the text in the blockquote, so the Markdown parser still thinks it's code. Just clicking the blockquote button does not automatically undo code-formatted text inside it. Removing the spaces fixes the problem.


7

This is fixed in the next build (client-side change, server-side change). Tim Stone's analysis is absolutely correct. The problem (once again) was this Markdown behavior: If list items are separated by blank lines, Markdown will wrap the items in <p> tags in the HTML output. So you have this: <ul> ...


7

I use the trick to add a <!> in between: Blockquote A Blockquote B


6

If these awesome little tweaks are worth doing, I'd like to see something else done at the same time: Multi Line Quotes Those are the ones that I actually want to visually separate, after all. For a single line, I could just use... "quotation marks".


6

The editor does take this scenario into account, but the mechanism that does so is currently broken (it'll only not wrap if the line starts with "undefined", which isn't particularly useful). The wrap() method should be using commandProto.prefixes in place of this.prefixes when testing for special cases. Making that change will allow the test to pass and ...


6

If answers do not attribute the source, then they are instances of blatant plagiarism. This is dealt with in the help center: Plagiarism - posting the work of others with no indication that it is not your own - is frowned on by our community, and may result in your answer being down-voted or deleted. Here is how plagiarism should be dealt with. Also, ...


6

I recently brought up this topic on Meta ELU, Citation/attribution for quote in blockquote on ELU. In the course of investigating before posting about the issue, I discovered that the W3C HTML5 recommendation of October 2014 addresses citations/attributions within blockquotes. The cite attribute of blockquote suggests one approach; however, the cite ...


6

There is no way to do it in the toolbar. You can try adding a non breakable space after each blockquote > Are questions about Microsoft Word Online on-topic here? I don't > really see any posted here, but perhaps I am not searching correctly. > - mweiss &nbsp; > Yes, they are. We even have a specific tag: [tag:word-online]. -ale &...


5

What you have there is already rather ok, depending on the amount of code. It doesn't look too bad. Some description while (stuff) { doit(); } More stuff The other option is to put a code block inside the quotes, which requires five spaces after the >: Some description while (stuff) { doit(); } More stuff


5

Nice idea! I would like it to "trigger" when the whole blockquote is a link, e.g. [>The quick brown fox jumps over the lazy dog](https://en.wikipedia.org/wiki/The_quick_brown_fox_jumps_over_the_lazy_dog) Which right now renders as: >The quick brown fox jumps over the lazy dog And instead would be cool to have it as: The quick brown fox jumps over ...


4

Now if only everything was as easily fixed as that.


Only top voted, non community-wiki answers of a minimum length are eligible