Now I’m about to do something that May…be… stupid, I’m no dev but
I’ll try and replace the U+201 in the script with a space and see what
happens …

lets test this now yadi yadi yada a gray fox jumped from I don’t know what over something or someone! … nope! still does the thing …

Wait a second! I did get the new line in my editor but the s dissapeared from the twtxt.txt file. let’s add in a new line just to make sure I did not break anything. 😂👍

borked it! no new lines for me 😂👍🏻

Are you playing around with the Multi Line Extension? I’m not really sure what client you’re using, but in most modern clients, we support multi-lines. e.g:

• This is a line
  
• This is another line.

Renders like this:

@bender@anthony.buc.ci Ahh, well it should support mult-line, pretty sure it does

I have checked the raw feed, and “spurious” characters are still making its way to it. Maybe something to do with locale, or keyboard?

Is the server setting the right content encoding?

@prologic@twtxt.net well, I think OP mother tongue isn’t English, so certainly not an encoding I might be familiar with.

@prologic@twtxt.net doesn’t UTF-8 covers Arabic as well?

@bender@twtxt.net Yea it does 👌

@prologic@twtxt.net it actually does!

But I broke something trying to get rid of the random characters showing on my twts as mentioned here #k7tcqwq.
I taught it was as easy as swapping the ‘\u2028’ in jenny’s new_twt_from_file function but there’s a reason I’m not a developer (yet) 😅

It kinda got rid of them in a way but broke the new lines in the process. So I put things back the way the were till I figure out something else.

@aelaraji@aelaraji.com Yeah we use the Unicode new line character to represent “new lines”