Qwen3.5 35B A3B had mixed Coptic script with ancient Greek, inspired from Phoenician. Honestly, if you are not an expert like Indiana Jones, it's impossible to tell if it is wrong. I have learnt something though:

Ϫ (minuscule : ϫ, U+03EA), called djandja (it sounds like danger meets Jumanji somehow) #language #unicode

https://en.wikipedia.org/wiki/Coptic_script

@simon_brooke

It's not the languages that have the interaction with #Unicode. The vulnerability in the languages is their ability to take code that is constructed at runtime in string form and interpret and execute it.

It's the text editors, IDEs, and pagers (that display the commit diffs) hiding the #PrivateUseArea (and, yes, unassigned code point) characters by rendering them as zero width.

But quite a lot of them don't. The code snippet in the article doesn't actually look like the screenshot given.

In the likes of text editors such as NeoVIM and VIM, and pagers such as less, more, most, and console-tty37-viewer, these characters are either emitted as narrow-width glyphs, which at minimum displays as mystery strings of replacement characters, or turned into reverse video hexadecimal code point values.

@otfrom

@JourneysInFilm
Sad 🪉 was a standard #Emoji as of 2024’s release of #Unicode 16

It was by far the most interesting of a dull few 🫩

But some devices that haven’t been updated may not support any of them
https://emojipedia.org/harp

https://emojipedia.org/unicode-16.0 🪏

@thias

I can only recommend to use #notepadpp and the little option at the top that makes non ASCII visible as coloured blocks with the name of that char within it e.g. <CR><LF>

All text editors and IDEs should have that option enabled and enable it by default.

That would effectively prevent these issues here...

#coding #unicode #texteditor #toolchain #computersecurity