Summary
Text written on signs can ignore spacing/newline formatting under certain conditions. This might relate to MCPE-20759, but I am quite unsure on this, and I have encountered this only on Realms so far (thus reporting under REALMS).
Reproduction steps
There is no clear situation under which the problem will occur, however when it does occur, all of the following has been observed of the affected signs:
Newline(s)/space(s) is/are added before the affected text.
There is no space between the text; for example,Waterloo
will cause the bug to appear, butWater loo
will not. Formatting symbols also count as text in this case.The text does not overflow onto the next line; for example, if the text starts out on line 2 but more typing causes the text to go to line 3, the bug will not appear.
Video demonstrating the bug: https://youtu.be/pAyDxKMng0c
The bug has been checked to occur without any addons both server-side (Realms) and client-side. The bug may come and go without any clear explanation.
For the provided image the correctly formatted signs (centre-left and centre-right) were obtained by typing §r
at the start of the sign.
Related issues
is duplicated by
relates to
Attachments
Comments


I can confirm this in 1.17.
[media]
[media][media]

Been having the same issue but with books.
The game keeps ignoring the spaces i put in there and just groups words together.

I cannot reproduce this in 1.17.32 using either example shown here. Is this still an issue?

It appears to me that signs are retaining their formatting in 1.17.32... until you move to another chunk and the text disappears entirely when you return. Since that's not exactly the issue reported here, I opened MCPE-143812 to track it. I found a similar (but not identical) report from a BDS user, hence using the MCPE project instead of REALMS.

This is still reproducible with
<- Way Out
Image also attached,

I still cannot reproduce using that text in a creative mode testing realm of which I am not the owner, accessed through Windows 10. But, I cannot reproduce any of the new 1.17.30 text bugs either (REALMS-9191, REALMS-9231). I wonder if these are related to specific devices, or multiplayer, or add-ons?

Reproduced with the following sign on a bedrock realm (multiplayer, win10):
[media][media]

My test environment was a survival (normal terrain) realm, Windows 10, not the owner, no add-ons (both realm and client-wise). The world is about 1.3GB and is almost two years old, though this issue has dated back earlier than when I reported.
Both REALMS-9191 and REALMS-9231 are reproducible for me in the same world.

I keep having this issue on and off. Some days it works and others it doesn’t, some days it writes nothing at all and I also have the issue with renaming things!

I think i found the problem. when players write in signs, the sign updates when ever any text is entered. while on my freind's realm, while reading to screenshot my signs to save them in case the signs messed up, i noticed the signs themselves going though the exact process agean, as if the client and server are lagging horribly. durring this process, i notice the sign ignores ALL LINE BREAKS AND ANYTIME YOU SWITCH TO A NEW LINE as if the server was reading the sign as a continuos line of text, and not a multi line text. This is what must be casuing the issue.
Steps to replicate:
1. open any realm.
2, place a sign and write the following: "Dear Dirary," enter "after walking" enter "for 2471" enter "days, nothing".
3, Wait until the sign updates (around 5-10 minutes).
4, Observe the sign reinputing your keystokes.
Expected Results:
Dear Dirary,
after walking
for 2471
days, nothing
Actual Result:
Dear Dirary,
After walking
for 2571 days,
nothing
Proposal soution: make the server code check for sign spaces by detecting "Enter" or controller equivlent move that text to the next line and modify any text below it

It's reproducing for me now as the owner of a realm. Here is a video of what Zach Guth is talking about:
[media]
The reason it goes back-and-forth is that each time you type something the client updates its display, and it parses the line breaks correctly. Then a moment later the server parses the text incorrectly and sends the corrupted string data back to the the client. This is the same process with the other realms text bugs (MCPE-3491 and related), which have been misunderstood as censoring. My guess is that the realms server either uses a different unicode format than the client when it read/sends string data, or it is running string data parsing functions designed for a different unicode format that what the client uses.

@goldenhelmet when can we expect a fix for this?

I wish I could tell you. Mojang does not publish plans, prioritization notes, or timetables for fixing bugs.

I'm seeing this on a 1.18.12 Realms server consistently. It seems to be ignoring new lines completely.
Resolving this as CR as we can no longer reproduce this bug.
If this is still an issue please remake the bug report and include detailed reproduction steps, as well as a video showcasing the bug.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki