Am 28. Jänner 2026 19:08:15 MEZ schrieb "Peter P." <[email protected]>: > >> basically, my advice is to use the [string( message with unicode points: >> - use [file] to read the raw UTF-8 bytes >> - use [unicode/utf82codenumber] to convert the UTF-8 bytes into >> unicode-points >> - prefix [string( > >I tried to implement this (see attached) but [text2d] renders the actual >bytes as numbers...
I haven't checked your patch yet, but apart from the obvious (as Ben pointed out), I'd like to reiterate: the "string" message does **not** take bytes but Unicode points (there's about 2^20 of them) which are numbers (been 0 and ~1000000). bytes can only have values between 0 and 255. for ASCII characters (which only use Unicode points between 0 and 127), the UTF-8 representation is identical to the Unicode point representation. mfg.sfg.jfd IOhannes --- [email protected] - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/[email protected]/message/3HTQ2OT4USBHFLMCZR7HFV7EZA3TEETC/ To unsubscribe send an email to [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
