How can I stop Write.as from adding big paragraph gaps between lines of my poems?
Can you please provide a screenshot of what you are publishing which looks incorrect? If you are not using the rich text editor, your text is interpreted as Markdown, and this page offers an explanation of how Markdown is interpreted.
You may be running into issues with our Rich Text editor, if you’re using that. Pressing Enter will insert a new paragraph, but pressing Shift + Enter will insert only a single-line break – so you’ll want to do that.
Otherwise, if you’re using our Plain Text editor, your poetry should come out looking pretty much exactly like what you type it in as. We made it especially for preserving text like this.
If you try those out, did either one help?
Thank you for your help.
I learned to navigate Rich text and Plain text together.
My current issue is getting my email subscription button to work. I tried using a few different emails to test the service out and see how it looks and to make any adjustments needed, but my IP has been blocked.
Can you please unblock my IP? I sent an email to you a couple days ago that has the IP address and request to be unblocked.
Thank you again for your help.
Jared
I’m having a similar issue. The Markdown guide page you linked said to use <br> (HTML) or 2 spaces at the end of the line (Markdown) to initiate a line break, but that isn’t seemingly working for me.
Both
Journal of Dr. Mary Stoole<br>
2105-06-22, 18:40 Local
and
Journal of Dr. Mary Stoole
2105-06-22, 18:40 Local
render as
Journal of Dr. Mary Stoole
2105-06-22, 18:40 Local
My post link: The Stoole Journals, Entry \#1 — Tetrahedronal Penguin
Try this:
Journal of Dr. Mary Stoole<br>2105-06-22, 18:40 Local
I think what happens is, when you use <br> and a linebreak (i.e., “2105” begins on the next line), that counts as two linebreaks. If the above works and does what you want, it’s because it uses only the <br> without the linebreak.
1 Like
As for why this:
Journal of Dr. Mary Stoole
2105-06-22, 18:40 Local
renders with two linebreaks, I don’t know.
I suspect much or all of this can be explained by the WriteFreely Markdown parser trying to be too clever. With the CommonMark Markdown parser, a Markdown parser that tries to be rigorously compliant with a published standard, all three of the formats we’ve been talking about render exactly the same:
It’s a pet peeve of mine when Markdown parsers try to be too clever, as the WriteFreely parser seems to be doing, because it just messes stuff up. Markdown can be easily learned, even by non-technical people. It’s predictable. However, no one can realistically keep track of the Markdown alterations and caveats that inevitably step on each other and cause problems.
WriteFreely devs, I would love if WriteFreely used vanilla CommonMark (no pre- or post- processing, for example to treat newlines differently), or at least gave the author the option of using that.
1 Like
Yup, that works. How odd… I’ve never seen that implementation for making a line break. Haha.
Good gods yes. I almost always absolutely hate it when a program tries to predict what it is I, the user, want.
A computer is there to do what I tell it. In my experience, when they try to then move into the territory of figuring out what I want before I do so, it usually ends with me having to spend twice as much time because I have to fix whatever it did.