Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mamot.fr is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mamot.fr est un serveur Mastodon francophone, géré par La Quadrature du Net.

Administered by:

Server stats:

3.1K
active users

mamot.fr: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

#utf8

1 post1 participant0 posts today
Public
argv minus one

#Unicode is one of those little things in life that I can't help but smile about.

Is it perfect? No, of course not. Is it better than the alternative? Yes, so much so that every time I'm confronted with a long list of character encodings I can choose from, I feel a sense of relief when I find #UTF8 among them.

I wouldn't have thought it possible to standardize a single character encoding for everyone, and yet, somehow, there is just such a standard.

#programming
Public
Tommi Nieminen

Imutin kaikki #Facebook'in julkaisuni – ainakin jos #Meta'a uskotaan. Pyysin #JSON-muodossa toivossa, että tulisi sutjakammin. Hieman ongelmia aiheutti JSONin koodaus: merkkijonot ovat validia #UTF8:aa mutta JSON ilmeisesti olettaa #UTF16:n, joten vaaditaan mukamuunnos eestaas; apua löytyi #StackOverflow’sta. Aikaleimat sentään olivat standardi-#POSIX’ia.

En tiedä, kuinka täydellinen ”arkisto” on, mutta ainakin jotakin saisi talteen, kun lähtee lätkimään. #some #atkjuttuja

Public *
screwlisp

Hey everyone. I must admit, I don't believe I have ever seen someone enter #utf8 #unicode characters on a #computer in a natural way. Which seems weird, because a bunch of languages use them.

I wrote a #commonLisp #asdf package that just looks up a list of symbols in a file that has every non-surrogate unicode codepoint in it, and an #emacs #elisp function that just calls the #lisp one.

codeberg.org/tfw/unicode-chars

Multilingual people, what can you tell me about doing this at all?

A screenshot of a readme showing (unsy '(sta si)) returning ("⍣" |#x2363| 9059 #\APL_FUNCTIONAL_SYMBOL_STAR_DIAERESIS "->⍣<-") and (multiple-value-list (unget:unsy '(sta si) '(apl))) returning ("✶" |#x2736| 10038 #\SIX_POINTED_BLACK_STAR "->✶<-")
Public
jfk

'worst-fit' attacks are the latest iteration of the classic "let's guess what the user wants" idea. This has always lead to issues down the line.

It will be really hard to reason about and fix for apps that rely on the affected Windows APIs.

blog.orange.tw/posts/2025-01-w

If you want a deep dive on the underlying mechanicss of these types of attacks, check out my colleague's blog post from a couple months ago: herolab.usd.de/en/the-security

Orange Tsai · WorstFit: Unveiling Hidden Transformers in Windows ANSI!📌 This is a cross-post from DEVCORE. The research was first published at Black Hat Europe 2024. Personally, I would like to thank splitline, the co-author of this research & article, whose help
#WorstFit#ANSII#utf8
Replied in thread
Public
Nils Goroll 🕊️:varnishcache:

@fanf it's absolutely fantastic. and if, like me, you want to see for yourself that it actually behaves correctly and in which sense of correct, here's something which might help: fosstodon.org/@slink/111019934 #utf8

FosstodonNils Goroll 🕊️:varnishcache: (@slink@fosstodon.org)Attached: 1 image An Exhaustive Test Program for the Legendary Höhrmann UTF-8 Decoder “The Höhrmann Decoder, implemented as a deterministic finite state machine, needs only a handful lines of C code and 364 bytes for a combined character class and state transition table. [...] hoehrmann-utf8-test.c exhaustively tests all possible inputs to the decoder, that makes 269492416 different byte sequences[^1], out of which 1112063[^2] are accepted.” https://git.sr.ht/~slink/hoehrmann-utf8 http://bjoern.hoehrmann.de/utf-8/decoder/dfa/ #unicode #utf8 #c
Public *
Eniko Fox

wow i think i actually managed to get utf8 working in my VM? i used `setlocale(LC_ALL, ".UTF8")` and then print the UTF32 char 0x0107 ć from my program. the interpreter uses c32rtomb to convert it to UTF8 and then i fwrite that to stdout

but the character doesn't show up in the windows console cause windows is bad. but i figured out a workaround! i put this in my run.bat file:

set run=./bismuth.exe prog.bst
powershell $OutputEncoding = [Console]::InputEncoding = [Console]::OutputEncoding = New-Object System.Text.UTF8Encoding; %run%

and it runs the VM through powershell with powershell forced to use UTF8 and then it works somehow, yay! more bizarrely, it doesn't show me the powershell prompt but the regular command prompt, but it works anyway? idk why but i'll take the win!

also i have no idea if any of this is the right way to do things so, yanno, don't take this as a tutorial or anything

windows command prompt showing it successfully printed the ć character as utf8
#PLDev#Bismuth#Unicode
ExploreLive feeds
About