Double spacing after a sentence
How the New Post Editor transposes into code double spacing after a sentence
I love using the character entity
which the New Post Editor converts as code whenever I double space after a sentence. I notice the order in which the "non-breaking space" character entity is used is AFTER the first blank space. If this order was transposed, wouldn't it solve unneeded blank space at the beginning of the next line?
I always review my entries to check for flaws and typos. One of the things I've been doing when editing an entry which I created in the New Post Editor is to unitilize the old 'classic' editor to transpose the first blank space, at the end of a sentence, with the non-breaking space character entity
. It seems when I do this, the orphan of a double space, at the end of a sentence near the right margin, disappears (from breaking the consistency of a paragraph's left margin with an unwanted space before the new/next sentence.)
Looking closely, when a sentence of a paragraph ends at the right margin, the next line adds an unneeded space to the start of the following sentence because the New Post Editor converts double spaces into code. If the
code for non-breaking space were to immediately follow the period (at the end of a sentence,) and the following space after that was a blank, hard space generated by the space bar, perhaps the characteristic of
would retain it's definition of non-breaking.
I was asked to resubmit my suggestion with screenshots. Here it is in all its glory.
Double spacing after a sentence
How the New Post Editor transposes the code for double spacing after a sentence
I love using the character entity which the New Post Editor converts as code whenever a double space is used after a sentence. However, I am noticing a bug as a result of the order in which the "non-breaking space" character entity is used AFTER the first blank space. If this order were to be transposed, it would solve unneeded blank space at the beginning of the next line? I'm including sample screenshots of a blog entry at https://slavezombie.livejournal.com/883141.html
This is an image of the result of the flawed code: https://ic.pics.livejournal.com/slavezombie/2661370/293173/293173_800.png
This is an image of the flawed code: https://ic.pics.livejournal.com/slavezombie/2661370/293100/293100_800.png
LIST OF BENEFITS
I wouldn't have to use a text editor to find/replace the code for double spacing if this somebody addressed this bug. One of the things I've been doing when editing an entry which I create using the New Post Editor is to utilize the 'old' editor to change the order of the code and the blank space (representing double spaces). In other words, I swap the non-breaking space character entity in place of the blank space which follows a period, and I add a genuine blank space after the code (before the first letter of the next sentence.) The orphaned blank space then no longer results in the unwanted space at the start of the next line of text. I will show screenshots of the results.
This is an image of the same blog entry shown as the example of the flaw when an orphaned blank space affects the beginning of a new line in the middle of a paragraph, fixed: https://ic.pics.livejournal.com/slavezombie/2661370/292452/292452_800.png
This is an image of what the fixed code looks like after I've edited it: https://ic.pics.livejournal.com/slavezombie/2661370/292678/292678_800.png