February 5, 2014 at 3:22 pm #88833
I'm using the Enterprise Pro theme and have noticed that when I begin a new sentence after a period, the double space I enter after the period and before the new sentence gets ignored when published and viewed in a browser. It looks like the following:
"...end of sentence.Then begins a new sentence..."
WTF? Is there a styling configuration I missed somewhere, because this is unacceptable. Thanks for the help.February 5, 2014 at 3:43 pm #88835February 5, 2014 at 3:54 pm #88837
Sorry. The site is not yet live. Localhost.February 5, 2014 at 4:00 pm #88840
How are you entering the text?
Are you entering it straight from the WP editor? Are you copying and pasting it in?
I am a web developerFebruary 5, 2014 at 4:13 pm #88842
I'm typing it right into the text editor. No copy / paste. No visual editor. I tried wrapping the paragraphs in p tags thinking that might trigger some universal formatting or something, but no change.February 5, 2014 at 5:14 pm #88850
As far as I know if you use the text editor (as opposed to the visual editor), no matter how many spaces you type in, only one will show up.
Perhaps this is because most typography experts insist that there should be only one space after a period.
Have you tried using the visual editor? This will usually insert as many spaces as you want.
EM DzineFebruary 6, 2014 at 5:37 am #88925
Switching to the visual editor did the trick, but what rubbish.
I never use the visual editor, as I code a lot of things by hand. In fact, I always disable the visual editor. So this means I have to go back through all my pages and posts and re-save them in visual editor mode just to get the text formatted correctly? This sucks.
Anybody have a solution?February 7, 2014 at 3:54 pm #89217
I really need to get an answer to this issue. I'm using Enterprise Pro and when I use the text editor, no spaces are retained after the "." at the end of a sentence and the beginning of the next sentence. I found that if I switch to visual editor and enter text, a single space can be retained, but for lots of reasons I usually deactivate the visual editor and use only the text editor.
Genesis is such a spectacular vehicle for web design...please tell me I'm not tethered to the visual editor just to enter text the way I'd like.
I welcome any clarification to help me out of this mess. Thanks.February 7, 2014 at 4:39 pm #89226
OzzyParticipantFebruary 7, 2014 at 5:25 pm #89244
I don't think this is a Genesis or Enterprise Pro thing, as it is a WordPress thing.
February 7, 2014 at 5:28 pm #89245
Ozzy: I think you're right about it being a WP issue, and not a theme issue. I'm messing around with the plugin raw html to see if that removes the WP idiosyncracies. I'll report back here if I learn anything.
PS: I'm developing the site localhost, so I have no link to provide. If the issue persists after I go live, I'll provide a link then. This formatting problem is happening on static pages and on posts. I don't use frontpage at all.
- This reply was modified 3 years ago by jhguynn.
February 7, 2014 at 5:34 pm #89247
- This reply was modified 3 years ago by jhguynn.
You could always disable autowp using something like
or use this to toggle it on and off for each post/page
February 7, 2014 at 5:42 pm #89249
It's not a WordPress thing. It's a HTML thing. Whitespace is collapsed (normalized) within textual content, down to a single space. When you use the visual editor, if you check the source, I bet it's "
", which is a space, followed by a forced non-breaking space.
HTML is correct here, and your insistence for double-spacing after full stops is incorrect. It originated from typewriters, which use a monospace font (where the width of a letter i, would be the same as an O for instance). Since your general text (not code snippets) will be using a variable-width / proportional font, the spacing around and particularly after a period is such that the new sentence already stands out.
The HTML4 spec has some details, though it may also be in earlier specs:
http://www.w3.org/TR/html4/struct/text.html#h-9.1 - "In particular, user agents should collapse input white space sequences [which includes the space character] when producing output inter-word space."
In short, your browser is correcting what you might be able to hack around with the visual editor, but for the sake of consistency, you should only use single spaces after full stops.
February 7, 2014 at 7:29 pm #89283
Gary Jones, thanks for the detailed response, lot's of good info there. FYI: I'm not hell bent on getting two spaces after the period of a sentence. Heck I'd settle for just one space. But I'm getting ZERO! Unless I use the visual editor, which allows me one space between sentences, I get nada from using the text editor, no matter how many spaces I type in.
As I said above, I prefer to disable the visual editor and work in text mode only. I just can't wrap my head around why it won't allow even one space after the end of a sentence.
Chillybin: thanks for the tip re: disabling wpautop. I gave it a shot but it doesn't seem to have any effect over the "space between sentences" issue. Please elaborate on this if you think I'm missing something.
The search for a global answer continues, until them I'll dabble in the visual editor.February 7, 2014 at 8:17 pm #89286
You must be logged in to reply to this topic.