[BUG-11555] Setting certain characters in Display Name results in DN changing twice within minutes and resulting DN changes to Korean. #1726
Comments
Lucia Nightfire commented at 2016-03-11T03:25:09Z purdy purdy pew pew herpa derpa derka duu, lol |
RaevenSpiritwalker commented at 2016-03-11T06:53:34Z That is crazy as they wrote clearly in my profile box using firestorm, I did it inworld, and remained above my head until I logged out. When I relogged they were gone and I could not change again for a week. This happened the second time also. I see the characters perfectly in the notes tab of my inworld profile also. So basically once I can change I need to use characters I know for sure work? It seems crazy to me I can type them and they show up in world as well but not on the profile. |
Spidey Linden commented at 2016-03-14T16:50:25Z RaevenSpiritwalker - can you try setting your display name using a different font? And if that doesn't work, please contact support and they should be able to reset it for you. |
Whirly Fizzle commented at 2016-09-13T05:14:21Z, updated at 2018-04-09T14:16:55Z Another font that reproduces this: 𝕄𝕒𝕘𝕟𝕦𝕤 𝕄α𝕔𝕂𝕖𝕟𝕟𝕒𝕘𝕥𝕙 Edit to add |
Whirly Fizzle commented at 2017-06-12T09:59:45Z Another odd case at BUG-100823 with display name 𝓝𝔂𝔁 ℬ. ℛ. 𝒦𝒶ℊℯ |
Whirly Fizzle commented at 2017-12-10T15:04:33Z Still repros - new case on the forum today: https://community.secondlife.com/forums/topic/415486-bug-exibition-name/ |
Chaser Zaks commented at 2017-12-10T17:30:26Z Could be a coincidence, but all of the affected names contain or consist of 32-bit unicode values. |
Kyle Linden commented at 2019-01-24T16:54:10Z, updated at 2019-01-24T17:00:17Z We're still getting reports of this, so I wanted to share what one of our devs had discovered. This links to a site where you can check the individual characters: 𝓓𝒆𝓼𝓲𝓻𝒆 𝓓𝓾𝒇𝓸𝓾𝓻 is in the Unicode astral plane (codepoints 0x010000 & greater). When truncated to the Basic Multilingual Plane, the string becomes 퓓풆퓼퓲퓻풆 퓓퓾풇퓸퓾퓻. |𝓓|𝒆|𝓼|𝓲|…| |
Kadah Coba commented at 2019-01-29T03:31:55Z Delicious Unicode spaghetti.
Maybe put this truncation in to the preview for changing one's display name? |
Whirly Fizzle commented at 2020-06-05T17:35:41Z This bug now reproduces differently. |
This is a fun one and 100% reproducible.
Steps to Reproduce
Login to my.secondlife.com with Avatar A & edit profile.
Change display name to 𝓓𝒆𝓼𝓲𝓻𝒆 𝓓𝓾𝒇𝓸𝓾𝓻 and save changes.
See Fig 1 attached.
Observe Avatar A's display name set on the web profile and the display name changes logged on the feed.
Observed Behaviour
Avatar A's feed will show the display name changed to 퓓풆퓼퓲퓻풆 퓓퓾풇퓸퓾퓻 at a time before the display name was even changed.
After this there will be an entry in Avatar A's feed showing the display name correctly set to 𝓓𝒆𝓼𝓲𝓻𝒆 𝓓𝓾𝒇𝓸𝓾𝓻
However Avatar A's display name still displays everywhere as 퓓풆퓼퓲퓻풆 퓓퓾풇퓸퓾퓻
퓓풆퓼퓲퓻풆 퓓퓾풇퓸퓾퓻 seems to be Korean for "Pwitpurp pyutpyurm pyutpurp pwitpyut purhpyum pyutpyut" (WTF).
See Fig 2 attached.
I reproduced this with 2 different accounts:
https://my.secondlife.com/whirlytester
https://my.secondlife.com/firestormregapitester
Expected Behaviour
Display name should be set to 𝓓𝒆𝓼𝓲𝓻𝒆 𝓓𝓾𝒇𝓸𝓾𝓻
Other Information
Bug only reproduces if you set this display name in a web browser on the profile feed.
Bug does not reproduce when setting display name using a TPV (Firestorm) in the legacy profile user interface.
See for example https://my.secondlife.com/sparkles.alchemi
I changed Sparkles display name to 𝓓𝒆𝓼𝓲𝓻𝒆 𝓓𝓾𝒇𝓸𝓾𝓻 using Firestorm legacy profile: http://prntscr.com/adr8ed
Sparkles feed shows the changes correctly: http://prntscr.com/adr8nd
Also note that the characters 𝓓𝒆𝓼𝓲𝓻𝒆 𝓓𝓾𝒇𝓸𝓾𝓻 will not actually render anywhere in the viewer UI (seemingly any viewer on Win 7 or Win 10).
If you open an IM session with an avatar with this display name, the username will display on the IM tab.
The characters 𝓓𝒆𝓼𝓲𝓻𝒆 𝓓𝓾𝒇𝓸𝓾𝓻 just display as boxes in chat too.
This is probably expected with such funky characters.
It may be a good idea to disallow setting display names with characters which will never render in the UI without extended font support.
Attachments
Links
Related
Duplicates
Original Jira Fields
The text was updated successfully, but these errors were encountered: