Non breaking spaces are lost—and shouldn't be.

  • Unknown's avatar
    jaygreenstein · Member ·

    It’s nice that we have the ability to view a the visual as we edit, but there’s a major bug. If I use a non-breaking space as a means of indentation, and then switch to visual presentation the indentation shows But when I change back to text, the code and the spaces have been removed.

    The blog I need help with is: (visible only to logged in users)

  • Unknown's avatar
    justpi · Member ·

    Sorry, but if something doesn’t work when you misuse it, that’s not a bug (let alone a “major” one). The editor always strips out wrong code when you toggle between Text and Visual, and a non-breaking space that doesn’t join two words is wrong code. To create indentation you need the right coding for it (and the same goes for extra space above or below a paragraph). See these posts of mine:
    http://wpbtips.wordpress.com/2009/06/19/formatting-text-pt-2/

    Formatting text pt. 1: blank lines, alignment, wrap-around, two columns

  • Unknown's avatar
    jaygreenstein · Member ·

    • Sorry, but if something doesn’t work when you misuse it,

    Nonsense. While not all browsers support it, it’s the simplest way to create an indent, and your system accepts and posts using it quite happily. Demanding that your users learn HTML coding in order to past a simple blog is both unreasonable and non-productive. I know people who avoid WordPress because it’s a pain in the ass to use.

    Your users are writers, remember, not programmers. And most of them already have the post—as they wish to see it—sitting in front of them in their word processor. Requiring them to redo it, using a programming system they have no other use for but on this site is absurd.

    Most sites that are used by average people will accept Word and RTF file formats. Hell, you can publish a book on SmashWords with no input other than your Word file. Why make people jump through hoops for a simple blog entry?

    But that’s beside the point. What is, is that the system—which fixes or deletes bad code before it publishes a given post—accepts and displays NB spaces quite happily when a post is previewed or posted. And when a user selects graphic display, when editing you accept those spaces without either comment or problem. And if you do, you damn well should put the code back the way you found it when the user switches back.

    I’ve worked in the computer field since 1960, so I damn well know the difference between competent program and sloppy workmanship.

  • The topic ‘Non breaking spaces are lost—and shouldn't be.’ is closed to new replies.