Support » Theme: Twenty Seventeen » blockquote:before is killing my double quotes

  • Greg Raven

    (@greg-raven)


    I have several pages that contain block quotes. I understand that I shouldn’t need actual quote marks around block quotes, but I have my reasons. However, TwentySeventeen zaps the opening double smart quotes on my block quotes, and replaces them with opening single smart quotes. I can’t see in the CSS where this is happening, so I can’t override it.

    This aberrant behavior occurs in the visual editor, as well.

    The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)
  • Greg Raven

    (@greg-raven)

    In the visual editor, it appears like this:

    https://www.dropbox.com/s/v29cef5gfzwjv0n/Screen%20Shot%202018-12-22%20at%206.49.49%20AM.jpg?dl=0

    In the rendered page, it appears like this:

    https://www.dropbox.com/s/t5b0472ot0jlz5w/Screen%20Shot%202018-12-22%20at%206.54.05%20AM.jpg?dl=0

    Editing the post as text shows a double open smart quote when the single open smart quote appears in the visual editor and the rendered page.

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    I don’t think this is a CSS problem, but a content issue. Try re-typing the quote character in the visual editor. I suspect the issue is because the speech mark has been copied from other software like Microsoft Word, which is causing issues in the Web.

    Greg Raven

    (@greg-raven)

    Great thinking, but not the case. Opening double smart quotes are being turned into opening single smart quotes, and not just at the beginning of the quote, but anywhere in the block-quoted text. If I view the text in the HTML editor, it appears as an opening double smart quote.

    Dumb quotes are not replaced.

    I’ve never seen anything like this.

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    When you say it’s not the case, did you try replacing it? Because it’s still showing up as a weird invalid speech mark character:

    Instead of:

    
    "
    
    Greg Raven

    (@greg-raven)

    Yes, I did try. That “weird invalid speech mark character” is a double opening smart quote.

    I want (“):

    I do not want ("):

    Greg Raven

    (@greg-raven)

    Maybe I should mention that this used to display properly on at least some of the themes before Twenty Seventeen.

    Greg Raven

    (@greg-raven)

    For example, here is a sample block quote with the opening double smart quote rendered correctly using Twenty Ten:

    https://www.hdcycling.org/2014/03/bicyclings-2014-win-a-bike-contest/

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    The issue is with the font family of “Libre Franklin”. When you switch to the font family being used on your other site, “Georgia”, the quotes work

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    Is it much work to take out the speech character from your content? If not, try adding this to the “Additional CSS” part of the dashboard:

    
    blockquote:before,
    blockquote:after {
        font-family: georgia, sans-serif;
    }
    
    blockquote:before,
    blockquote:after,
    blockquote p {
        display: inline;
    }
    
    blockquote:before {
        content: '“';
    }
    
    blockquote:after {
        content: '”';
    }
    
    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    Hmm scratch that

    Greg Raven

    (@greg-raven)

    Yep, it’s a font issue. Been years since I had to deal with one of those.

    Customized the CSS for

    to:

    { font-family: -apple-system, BlinkMacSystemFont, ‘Segoe UI’, Roboto, ‘Helvetica Neue’, Arial, sans-serif; }

    It still displays incorrectly in the visual editor, it is correct in the rendered page.

    Thank you so much for pointing me in the right direction, Andrew!

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘blockquote:before is killing my double quotes’ is closed to new replies.