• My copy of WordPress (1.5.2) yields end quotes rather than begin quotse following a left paren. For example, in this document the definition for the word “Snippets” appears as (a€?Snippetsa€?) rather than (a€?Snippetsa€?).

Viewing 4 replies - 1 through 4 (of 4 total)
  • 1. You have a lot of errors that need to be cleaned up, which may or may not include the solution to your problem.

    2. You also have a style sheet in the middle of a list. All style sheet links must be in the head section of your header.php, not just anywhere you please. (edited out file location)

    <li id="blogads">Xrlq Sells Out
    <link rel="stylesheet" type="text/css" href="https://proxy.........ia/ba_as.css" />

    3. Just below that is a huge encrypted bunch of “input” code that is very odd and suspicious looking. Have no idea what it is, but you might want to get rid of it or fix it.

    4. For whatever reason, your site is using apostrophes (‘) around HTML tag attributes instead of quotes (“) such as <p class="something"> you have <p class='something'>, which isn’t good form. This really needs to be fixed as it can lead to serious trouble in the future if you mix these.

    5. There are a lot of little and big problems with the code, so fix what you can and see if anything changes. Make sure that your character set in the header.php is “right” for what you are doing, and make sure that you DO NOT write your posts in a word processing program and then directly paste them in. It will guarantee you a mess every time. Write them in a good text editor with spell check and then move them in from there. WordProcessors change the quote marks to pretty them up and when those go into WordPress, messes happen.

    I’ll submit a fix for this, but in the mean time, here’s a solution:

    On line 30 (1.5.1.2) of wp-includes/functions-formatting.php, change to this:

    REMOVED DUE TO CODE REFORMATTING!

    @ Lorelle, #4 is certainly the recommended way of enclosing attribute values, but single quotes are valid XHTML.

    EDIT: #$&%&#$ forum… Here’s what line #30 should look like:

    https://pastebin.com/293108

    Thread Starter xrlq

    (@xrlq)

    Lorelle, none of that has anything to do with the smart quotes problem. I don’t use word processors, I simply type the text into the WP window as straight quotes, and WP “smartens” them on its own. It just “smartens” them the wrong way when they happen to be preceded by a left paren.

    Thread Starter xrlq

    (@xrlq)

    Kafkaesqui, that did the trick, thanks.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘“smart quote” malfunction’ is closed to new replies.