Blockquote tags

People! Lend me your ears!

One of my favorite parts of the Popehat blog is interacting with people in the comments.

…but I spend less time than I would like reading comments and more time than I would like fixing them.

If you want to quote someone, here's how you do it. You write this:

<blockquote>
this text is quoted.
</blockquote>

and the end result is this:

this text is quoted.

Here is your four part checklist:

1) do exactly what I said above.
2) make sure that there's a slash before the 'b' in closing blockquote tag. That makes all the difference.
3) nesting is legal, but COUNT. Make sure that there are exactly as many opening blockquote tags as there are closing blockquote tags.
4) there is no step four.

Last 5 posts by Clark

Comments

  1. Avi says

    2) make sure that there's a backslash before the 'b' in closing blockquote tag. That makes all the difference.

    / is a slash. \ is a backslash.

    A slash is required, not a backslash. Please update your instructions.

    Love, a typographic pedant.

    Clark: Done! Thanks, Avi.

  2. Todd S. says

    Thanks for this. I wanted to do this yesterday but didn't know how, and didn't care enough to look it up. *shame*

  3. Analee says

    Yay! Once again, I learned something from Popehat!

    Now could someone please tell me how to correctly comment with an image? There have been so many posts that I've wanted to use the Malshandir Butthurt Ointment picture on but could not because I apparently can't do it right.

  4. Erik says

    I understand that fixing people's comments when they get it wrong is annoying.

    Suggestion: help people to do a better job of fixing their own comments, for example with a Preview Comment button next to the Submit Comment button. That way people can check if they got it wrong before they post. (Allowing minor editing, for example only for 5 minutes after posting, could also work.)

  5. Richard says

    @Analee: I don't think this blog supports image tags. If it does, it would use the tag, with the src attribute set to whatever the link to your image is.
    For example:
    <img src="http://www.popehat.com/wp-content/themes/disciple/images/48.png"> with the result:

    To post a link to an image it would be the a tag, with the href attribute set to the link you want to link to:
    <a href="http://www.popehat.com/wp-content/themes/disciple/images/48.png">This is the link. with teh result:
    This is the link.

  6. cpast says

    What does the "cite" option do?

    Without:

    I understand that fixing people's comments when they get it wrong is annoying.

    With:

    I understand that fixing people's comments when they get it wrong is annoying.

    [I expect this comment to answer my question]

  7. Richard says

    Shit. It mangled my closing tags.
    Okay, so the img tag doesn't work (no way to post images).
    The correct a tag looks as follows:

    To post a link to an image it would be the a tag, with the href attribute set to the link you want to link to:
    <a href="http://www.popehat.com/wp-content/themes/disciple/images/48.png">This is the link.</a>
    with the result:
    This is the link.

  8. princessartemis says

    Now could someone please tell me how to correctly comment with an image?

    You cannot include an image because <img> is not one of the allowed tags. Use <a href="http:\www.example.com\image.jpg">Link<a> to generate a link to your image.

  9. princessartemis says

    Well, better close the anchor tag with a forward slash, like so: </a> lest your whole comment turn into a link. Forgot that in the midst if the andlessthansemicolons.

  10. Richard says

    princessartemis: I hate to make your day worse, but it's http:// (forward slashes, not backslashes)

  11. Analee says

    @princessartemis and @Richard:

    That's odd…I was sure I saw images in comments fairly recently. Well, I must have been wrong. No shame in admitting that.

    Thanks for the help, though! Coincidentally, I was wondering about how to generate a picture link as well.

  12. says

    @Erik

    I understand that fixing people's comments when they get it wrong is annoying.

    Suggestion: help people to do a better job of fixing their own comments, for example with a Preview Comment button

    David is the Popehat IT guy and he has been made aware of this request.

  13. Paul E. "Marbux" Merrell says

    @cpast: the CITE element is used to indicate: [i] in HTML4 the title of a literary work; or [ii] in HTML5, a citation to a work. See w3cschools.com.

    The identification is for styling or other processing purposes. E.g., a web page's CSS stylesheet may specify that the content spanned by a CITE tag pair be italicized with a light yellow background. In HTML 5, a javascript may parse the content of such a tag pair and give different typographic treat to each element of the citation, or all of the citations on a page may be automatically copied and formatted at the end of the page as a bibliography.

  14. lelnet says

    Thank you. Also, please thank David on our behalf if he does that (either a preview button or an option to edit after posting). Because Erik is right.

  15. David C says

    4) there is no step four.

    Step 4 is to review everything to make sure you didn't type "blockquot" instead of "blockquote" or something.

    But now I'm really curious about the "q" tag. Is this a shortcut to blockquote? Because that might help with the spelling problem.

    This text used the "q" tag.

  16. Peyote Short says

    If people have to learn html to properly quote on your site, your commenting software is too primitive for the year 2013.

  17. David C says

    Nope, I guess q is just a normal quote. And yeah, it would be nice to be able to know what those tags do without having to actually make a post that uses them. Hopefully my namesake is on it.

  18. says

    @Peyote Short

    If people have to learn html to properly quote on your site, your commenting software is too primitive for the year 2013.

    Quite right.

  19. jimmythefly says

    I've had a wonderful time, but his wasn't it.

    I've had a wonderful time, but his wasn't it.

    Just testing if there's a way to attribute a quote to someone.

  20. Marcus says

    <blockquote>

    &lt;blockquote&lt;
    this text is quoted.
    &lt;/blockquote&lt;

    </blockquote>

    But who blockquotes the block quoter?

  21. says

    I have added a live preview pane below the typing box, so you can see the natural and probable outcome of your current effort to format a comment.

  22. princessartemis says

    princessartemis: I hate to make your day worse, but it's http:// (forward slashes, not backslashes)

    I know; I saw that at the last second and said screw it, I need coffee :)

  23. Erik says

    I have added a live preview pane below the typing box, so you can see the natural and probable outcome of your current effort to format a comment.

    That's awesome!

  24. Richard says

    I have added a live preview pane below the typing box, so you can see the natural and probable outcome of your current effort to format a comment.

    Wow! I've tested out all of the "allowed tags" and the preview pane works perfectly.

    Great job, David!

  25. eddie says

    Okay, so I've just got to try out this live preview thing.

    It works great!

    That's what she said.

    David, you are not libel!

  26. says

    Here's how a rich editor would look. Seems incompatible with the live preview, though.

     

    Which do you prefer?

     

    Whee!

  27. Richard says

    Which do you prefer?

    I prefer the live preview.
    However, I speak as someone comfortable coding in HTML, so maybe mine isn't the opinion you're looking for.

  28. says

    I think I'll restore the live comments, which offer some fun, and try to iron out the compatibility issue between that feature and the embedded rich text editor. Meanwhile, feel free to offer your thoughts.

  29. says

    Dear Diary,

    Although not affected by the shutdown because mission critical, I apportioned a certain amount of my lunch break to making the world safe for Popehat commenters.

    After eliminating some false or misleading guidance from the "Allowed tags" section, I shall resume criticially missioning.

    Save me some Affligem.

  30. Kilroy says

    not sure if anyone mentioned it yet, but that's a forward slash. here's an easy way to remember: if you have to climb up, your going forward, if you'd fall down, you're going back. Ever forward!

  31. ChicagoTom says

    Am i crazy — when the did the comment preview section show up?

    That's a nice addition.

    Also, since I am usually kind of a jerk to Clark in the comments let me say…

    Clark I agree with everything you wrote here and it was well said to boot!

    And it's helpful that the preview section shows if you blockquoteed correctly too!!

  32. Richard says

    not sure if anyone mentioned it yet, but that's a forward slash. here's an easy way to remember: if you have to climb up, your going forward, if you'd fall down, you're going back. Ever forward!

    I've heard it as "A forward slash is leaning forward towards the text you're about to write, and a backslash is leaning backward onto the text you've already written."

  33. ZarroTsu says

    Now I can dynamically see when my attempts to fool the system into literally printing "<blockquote>" fail dramatically because the webform actually checks if the opening tag is true (and removes false ones accordingly), while the closing tag is only truly required if there is more text afterward!
    Thanks Dave!

  34. sponge boy says

    I have removed some of the ugly from the allowed tags section.

    Thank you — the original "Allowed Tags" were not helpful — '<blockquote cite="">' was anything but helpful.

  35. Richard says

    I have removed some of the ugly from the allowed tags section.

    You mean we're no longer able to use the universally beloved <abbr> tags? Or the replacement for <strike>, <del>?
    The tragedy!

    <q> is no big loss.

    …Though I don't see why we need both <em> and <i>, nor both <strong> and <b>.

    Especially since this should all be done in CSS.

    …Oops. Does CSS actually work here?

  36. Richard says

    No, no it does not. Another thing (along with my interrobang) that the Preview window does not strip out, but actually posting does.

  37. Anonymous Coward says

    Issues were caused by having the "Allowed tags" line contain tags that were apparently useless, like [quote]. Appears to be fixed now.

  38. says

    1) do exactly what I said above.

    Anyone else see the irony in Clark requesting, nay, demanding, that we follow the rules exactly to the letter?

  39. sevesteen says

    If people have to learn html to properly quote on your site, your commenting software is too primitive for the year 2013.

    Since most Usenet Newsgroup software could do quoting right–and even nested, interleaved quoting easily and nearly automatically since at least 1994, it astonishes me how much manual effort is required to do quotes on forums and blogs nearly 20 years later.

  40. Jeremy says

    I admit I'm guilty of sometimes messing up html in blog comments. I feel bad about it, having been someone who has to fix complicated html code from time to time. I apologize for past mistakes and all future mistakes. I try not to make them, I honestly think message systems should be smart enough to catch those mistakes.

  41. Jeremy says

    oh, and, to add my 2c, i prefer an EDIT feature. I think any comment system without an "oopsie, I need to edit" is retarded.

  42. James Pollock says

    The problem being that people sometimes post comments on more than one blog, and when that happens, it gets tricky to remember which blogs permit what what special editing and/or html tags. To be safe, you have to stay with the plain vanilla basics that are supported everywhere, also known as untagged 7-bit ASCII.

  43. Matthew Cline says

    I have added a live preview pane below the typing box, so you can see the natural and probable outcome of your current effort to format a comment.

    Yes! No more doing visual scans for unclosed/mismatched tags!*gives David virtual hugs*

    EDIT: And an "edit within give minutes" feature. W00t!

  44. Roki B says

    What

    is

    the

    consensus

    on

    blockquote

    abuse?

    Oh, I see it doesn't break tables. Carry on then.

  45. Lists inside of nested quotes maybe?
    Is this helping?
  46. Richard says

    @David:
    I was playing with CSS in the <i> tag.
    So if I wrote <i style="font-weight:bold">test</i>, in the preview window it shows as test, but when posted, it shows as test.
    Not that I need CSS, I was just playing around and thought it cool (and a little alarming – font-size worked too, and that could have been a problem) when the CSS worked in the preview window.
    I figured that this was the thread to play around with HTML.

  47. says

    The preview pane is more tolerant than the HTML parser, and that's fine. The parser is judge and jury. (I'm torturer and executioner.)

  48. says

    A real "preview" option would have a couple of desirable features missing from the live preview window. First, we expect it would be more accurate. Second, it would not slow the entry of comment text by requiring some cycle-sucking javascript monster.

    The 5-minute edit option is a pretty fair substitute, however. It could certainly be enhanced by removing the javascript countdown timer.

    It should probably be understood that I use an actual word processor for my work, which processes the words upon command rather than trying to limit me to what I can type and see at once.

    When I call the new implementation a cycle-stealing monster, by the way, I refer to the fact that it appears to contain some sort of nasty buzz loop which keeps the system at a load average of not less than 1. Normally the load average here would be about zero. Fast CPU, plenty of core, and when I word process it is pretty darn fast.

  49. V says

    The implementation does not seem a cycle sucking monster to me.
    Live preview responds immediately, any CPU usage goes down as soon as you stop typing and livepreview is implemented as an onkeyup event (act when you release each key), so any loops or inefficiencies that inflicts might share blame with your choice of browser (perhaps there's something available for your browser to block scripts on a per site basis).

    I'd suspect an errant third-party script (counters, social media, ..) embedded on the page before suspecting your browser or the livepreview.