[MCPE-13631] SIGNS- Can't type a full line of text when using colors Created: 18/Feb/16  Updated: 20/Jan/23  Resolved: 20/Jan/23

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.14.0, 0.15.1, 1.6.0, 1.7.0.5 Beta, 1.6.1, 1.9.0
Fix Version/s: None

Type: Bug
Reporter: CMCPE
Resolution: Incomplete Votes: 9
Labels: java-parity, vanilla-parity

Attachments: JPEG File Screenshot_20191031-170055.jpg     PNG File text-wrapping-bug.png    
Issue Links:
Duplicate
is duplicated by MCPE-36921 Color codes take up character space i... Resolved
is duplicated by MCPE-37481 Color codes take up character space i... Resolved
Relates
relates to MCPE-30202 Coloured text on signs not save the c... Resolved
relates to MCPE-16013 Signs - Text Length Inconsistency Acr... Resolved
relates to MCPE-16620 Some characters can cause overflow fr... Resolved
Confirmation Status: Confirmed
Platform: Multiple
CHK:
ADO: 65970

 Description   

When using § to change the color of text, I cannot type the full 15 letters of text due to the "§" being included in the line. Instead, I can only type 13 letters. When I try to do more than one "§", such as bold white text (§l§f), I am then limited to only 11 letters, and so on. (This is a huge problem for me as every sign in my world is composed of white and other colored text).

Steps to reproduce:
1) Create a new sign
2) Use the § technique to change the text color. Try doing a color then making it bold then italic. (§1§L§O)
3) Type a line of text. Instead of 15 characters, in this case you would only be able to type 9.



 Comments   
Comment by [Mojang] Mega_Spud (Jay Wells) [ 20/Jan/23 ]

Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.

For any account or purchasing related issues, please contact Minecraft Customer Support directly, as we cannot assist with those here at the bug tracker.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

Comment by [Mojang] Mega_Spud (Jay Wells) [ 17/Jul/21 ]

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response

Is this still an issue in the latest version? If so, please make sure the ticket description contains the following information:

Steps to Reproduce:
1.
2.
3.

Observed Results:
(Briefly describe what happens)

Expected Results:
(Briefly describe what should happen)

If your ticket does not look like the example given here, then it's likely to be closed as incomplete.

This ticket will automatically reopen when you reply.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

Comment by Skaijie [ 23/Nov/20 ]

Workaround (Win 10 only) is to type out the text without any formatting and fill in the formatting from the back after.

Comment by GinePik [ 23/Nov/20 ]

Affects 1.16.100

Affects 1.16.200.56 Beta

Comment by Levi Davidson [ 31/Oct/19 ]

Looks like this page is still open. In 1.13.0, the sign formatting is still wonky on all bedrock platforms (using Android version 9 for this example). Separate lines will not return to the normal color while on the sign (this part is a separate visual glitch), and this is similar enough to the issue reported here that I am replying here instead of making a duplicate.

Comment by [MCPE Helper] Dylan K. Taylor [ 28/Feb/19 ]

In 1.9.0 this issue is now utterly infuriating due to automatic text wrapping. Attaching a screenshot. Notice how the "fubar" ends up on the second line in the UI, while it's on the first line in the actual sign in the background.

Comment by ExamineCat [ 15/Sep/18 ]

 I can confirm this issue is still happening in 1.6.0, please fix.

Comment by [Mojang] Mega_Spud (Jay Wells) [ 11/Sep/18 ]

Reopening ticket.

Comment by [Mojang] Adrian Östergård [ 02/Nov/16 ]

Please reply and update affected versions if you're still able to reproduce this issue.

Comment by inxomnyaa [ 19/Feb/16 ]

They are actual characters, so this is correct to happen and intented to be that way.

Generated at Sat Jan 11 15:00:37 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.