The Absolute Minimum Every Software Developer Must Know About Unicode in 2023 (Still No Excuses!) @ tonsky.me https://tonsky.me/blog/unicode/
Very good summary about the quirks of unicode one has to be aware of
#unicode
#unicode
Another reason to hate #Microsoft. I took data from a colleague's #Powerpoint slide to put into a #LaTeX document. When I processed my file I kept getting errors and I couldn't see anything with #Emacs that was wrong with the file. It turns out that the original file contained a #zero-width #Unicode character which I couldn't see! The solution was to us od -c | less to spot anything untoward in my #TeX source #TextFile. There it was and it was in many places and I had to find the locations, and replace the characters either side to be sure that the invisible character was deleted. What a waste of time.
If you drag an emoji family with a string size of 11 into an input with maxlength=10, one of the children will disappear.
https://ohai.social/@simevidas@mastodon.social/109919980698211659
#Unicode #bidi question: Is there any reason for Right-To-Left language users to use the “#RTL override” character xE2\x80\xAE at the end of their display name?
It’s making #Friendica’s notifications look funky and we're considering trimming the character from the end of display names to avoid that. #Unicode
Auch nach Jahrzehnten Unicode sind Schriftzeichen slawischer Sprachen weiterhin Sonderzeichen und bei etlichen Anmeldungen online einfach ungültig. Besonders in Deutschland schafft man es aus irgendeinem Grund auch 2022 immer noch statt UTF-8 weiterhin ISO-8859-1 zu nutzen und damit alles außer westeuropäische Schriftzeichen auszuschließen. Und auch 2022 ist es zu viel verlangt, dass Webdevs (nein, ich nenne euch bewusst nicht Programmierer:innen, sorry) einfach mal Webseiten vernünftig „coden“ wie ihr das nennt und flächendeckend Unicode in eure Datenbanken einzuführen. So was bleibt natürlich weiterhin Nischenthema, denn Diskriminierung gegen Slaw:innen interessieren Mehrheitsdeutsche einfach nicht.
Und nein, ich werde meinen Namen nicht mit tsch oder zsch für euch schreiben.
IMPORTANT UNICODE NOTICE:
The character "ꙮ" (U+A66E) is being updated in version 15.0.0.
Because it doesn't have enough eyes. It needs to have three more eyes.
https://www.unicode.org/wg2/docs/n5170-multiocular-o.pdf
#unicode
https://twitter.com/jonty/status/1571615998335123457
**** Drei Jahrzehnte Unicode: Alles außer Klingonisch ****
https://www.golem.de/news/drei-jahrzehnte-unicode-alles-ausser-klingonisch-2203-163340.html
Schöner Artikel!
#unicode
#ThisWeekInSecurity: #Unicode #Strikes, #NPM Again, and #First #Steps to #PS5 #Crack
Maybe we really were better off with ASCII. Back in my day, we had space for 256 characters, didn’t even use 128 of them, and we took what we got. Unicode opened up computers to the languages…
https://hackaday.com/2021/11/12/this-week-in-security-unicode-strikes-npm-again-and-first-steps-to-ps5-crack/ #ThisWeekInSecurity
"Really interesting research demonstrating how to hide vulnerabilities in source code by manipulating how #Unicode text is displayed. It’s really clever, and not the sort of attack one would normally think about." https://www.schneier.com/blog/archives/2021/11/hiding-vulnerabilities-in-source-code.html