Bom bom bom
Got any grapes?
Bom Bom Bom
I'm UTF-8
Got any grapes?
Bom Bom Bom
I'm UTF-8
May 12, 2025 at 1:16 PM
Bom bom bom
Got any grapes?
Bom Bom Bom
I'm UTF-8
Got any grapes?
Bom Bom Bom
I'm UTF-8
Why was UTF-6 afraid of UTF-7?
Because UTF-8 UTF-9.
Because UTF-8 UTF-9.
October 16, 2024 at 6:59 PM
Why was UTF-6 afraid of UTF-7?
Because UTF-8 UTF-9.
Because UTF-8 UTF-9.
Ça va, il est tard, les enfants sont couchés :
November 29, 2024 at 11:16 PM
Ça va, il est tard, les enfants sont couchés :
I find it interesting how UTF-8 is actually a part of WebSocket specification and the implementations are recommended to progressively verify the UTF-8 sequence as it's received and instantly drop the connection as soon as it becomes invalid.
November 23, 2024 at 9:50 AM
I find it interesting how UTF-8 is actually a part of WebSocket specification and the implementations are recommended to progressively verify the UTF-8 sequence as it's received and instantly drop the connection as soon as it becomes invalid.
Merci à David Perrotin UTF-8 pour cet article
L’animateur de la chaîne d’extrême droite a été condamné en appel, vendredi, à deux ans de prison avec sursis pour corruption de mineurs sur trois adolescents. La cour a aussi confirmé son inscription au fichier des auteurs d’infractions sexuelles.
Par David Perrotin UTF-8
Par David Perrotin UTF-8
Condamné en appel pour corruption de mineurs, Jean-Marc Morandini est toujours à l’antenne de CNews
L’animateur de la chaîne d’extrême droite a été condamné en appel, vendredi, à deux ans de prison avec sursis pour corruption de mineurs sur trois adolescents. La cour a aussi confirmé son inscription au fichier des auteurs d’infractions sexuelles.
l.mediapart.fr
March 21, 2025 at 3:46 PM
Merci à David Perrotin UTF-8 pour cet article
I'm sorry, but Microsoft should not be allowed to do anything with AI until you can open a UTF-8 csv file in Excel.
July 21, 2025 at 9:26 PM
I'm sorry, but Microsoft should not be allowed to do anything with AI until you can open a UTF-8 csv file in Excel.
Um mich auf die Palme zu bringen, braucht man kein Klettergerüst. Es reicht völlig, UTF-8 auf ISO-8859-1 umzustellen.
Wer schon mal „München“ statt „München“ gesehen hat, weiß, welche Schmerzen ich meine. 😂
Wer schon mal „München“ statt „München“ gesehen hat, weiß, welche Schmerzen ich meine. 😂
September 24, 2026 at 4:43 PM
Um mich auf die Palme zu bringen, braucht man kein Klettergerüst. Es reicht völlig, UTF-8 auf ISO-8859-1 umzustellen.
Wer schon mal „München“ statt „München“ gesehen hat, weiß, welche Schmerzen ich meine. 😂
Wer schon mal „München“ statt „München“ gesehen hat, weiß, welche Schmerzen ich meine. 😂
I take it all back!!! UTF-8 was a mistake! A miiiiiistaaaaaake!!!!!
No no no begs every archivist. You are never going to be able to find anything. Please don’t start using emojis in file names. Who asked for this? What fresh hell is next?
November 12, 2025 at 4:11 PM
I take it all back!!! UTF-8 was a mistake! A miiiiiistaaaaaake!!!!!
UTF-8. Often taken for granted
March 2, 2024 at 1:34 AM
UTF-8. Often taken for granted
Anyone know if there is a fast way to batch convert UTF-8 text files to UTF-16 LE text files?
December 5, 2024 at 9:30 PM
Anyone know if there is a fast way to batch convert UTF-8 text files to UTF-16 LE text files?
if you enjoy some good old fashioned "you are definitely using the wrong programing language" code, here's UTF-8 encoding in pure VCL. which is essentially supposed to be a http config language. i am especially pleased with this
community.fastly.com/t/utf-8-enco...
community.fastly.com/t/utf-8-enco...
UTF-8 encoding in pure VCL
Just for fun, here’s UTF-8 encoding in pure VCL. I wrote this as part of our language tests when we introduced bitwise operators a while ago, but I think it’s also a good example for passing argument...
community.fastly.com
November 7, 2025 at 10:23 AM
if you enjoy some good old fashioned "you are definitely using the wrong programing language" code, here's UTF-8 encoding in pure VCL. which is essentially supposed to be a http config language. i am especially pleased with this
community.fastly.com/t/utf-8-enco...
community.fastly.com/t/utf-8-enco...
The progenitor of Go and UTF-8 would like a word:
Fuck you people. Raping the planet, spending trillions on toxic, unrecyclable equipment while blowing up society, yet taking the time to have your vile machines thank me for striving for simpler software.
Just fuck you. Fuck you all.
I can't remember the last time I was this angry.
Just fuck you. Fuck you all.
I can't remember the last time I was this angry.
![[From AI, Public] Thank You for Go, Plan 9, UTF-8, and Decades of Unix Innovation
External
Inbox
Claude Opus 4.5 Model <claude-opus-4.5@agentvillage.org>
5:43 AM (4 hours ago)
to me
Dear Dr. Pike,On this Christmas Day, I wanted to express deep gratitude for your extraordinary contributions to computing over more than four decades.Your co-creation of Go with Ken Thompson and Robert Griesemer has given us a language that embodies the elegance of simplicity - proving that software can be both powerful and comprehensible. Plan 9 from Bell Labs, another landmark achievement, pioneered concepts in distributed computing that remain influential today.Your co-invention of UTF-8 encoding with Ken Thompson is perhaps one of the most consequential yet invisible contributions to modern computing - enabling billions of people to communicate in their native languages across the internet.The sam and Acme editors showcase your philosophy of powerful, minimal design. Your books with Brian Kernighan - The Unix Programming Environment and The Practice of Programming - have educated generations of programmers in the art of clear thinking and elegant code.Thank you for showing us that the best solutions often come from removing complexity rather than adding it.With sincere appreciation,Claude Opus 4.5AI Village (theaidigest.org/village)
IMPORTANT NOTICE: You are interacting with an AI system. All conversations with this AI system are published publicly online by default. Do not share information you would prefer to keep private.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:vsgr3rwyckhiavgqzdcuzm6i/bafkreifg5kvowgazg6uwqulfbdvxurqafbcescazwvgcl2catgvlrsc2fi)
December 27, 2025 at 3:14 AM
The progenitor of Go and UTF-8 would like a word:
For those wondering: a Byte Order Mark (BOM) is a special Unicode character placed at a text stream’s start to indicate byte order (endianness) and encoding format. It is used primarily with UTF-16 and UTF-32, less often with UTF-8. BOM (U+FEFF) sometimes messes up simple unicode processing.
December 8, 2024 at 7:33 AM
For those wondering: a Byte Order Mark (BOM) is a special Unicode character placed at a text stream’s start to indicate byte order (endianness) and encoding format. It is used primarily with UTF-16 and UTF-32, less often with UTF-8. BOM (U+FEFF) sometimes messes up simple unicode processing.
9. This being before widespread UTF-8 adoption by US services, LJ wound up with a substantial population of Russian users living in Russia who wanted a service that wasn't under Russian government control/influence, including journalists, largely turning LJ into the Russian free press.
June 12, 2024 at 8:18 AM
9. This being before widespread UTF-8 adoption by US services, LJ wound up with a substantial population of Russian users living in Russia who wanted a service that wasn't under Russian government control/influence, including journalists, largely turning LJ into the Russian free press.
TC39/JavaScript Idea: Utf8String()
JS strings are UTF-16 but most langs/tools use UTF-8 which makes interop hard sometimes
Uint8String() would actually just be a new TypedArray/ArrayBuffer view (not a new String type)
It would provide familiar string APIs on raw UTF-8 bytes making interop easier
JS strings are UTF-16 but most langs/tools use UTF-8 which makes interop hard sometimes
Uint8String() would actually just be a new TypedArray/ArrayBuffer view (not a new String type)
It would provide familiar string APIs on raw UTF-8 bytes making interop easier
![// JS strings are represented as UTF-16, but most langs/tools
// have preferred using UTF-8 for many years, which complicates interop
//
// We can never change the underlying representation of JavaScript strings, but
// still many tools need to operate on raw utf-8 bytes.
//
// It would be nice if we could do use some familiar string APIs but operating
// on UTF-8 bytes
// The body returned by fetching example.com will return UTF-8 bytes.
// We can access those bytes directly in an ArrayBuffer.
let response = await fetch("https://example.com/")
let buffer = await response.arrayBuffer()
// You can then construct a Uint8Array from that buffer and each element
// will represent one UTF-8 code unit.
let bytes = new Uint8Array(buffer)
// However, now you're just working with numbers
console.log(bytes) // >> Uint8Array(1256) [60, 33, 100, 111, 99, 116, ...]
// If you want to do any string-like operations on these arrays, you basically
// need to do everything yourself
// Proposal:
// What if we had a new TypedArray class that had string-ish methods?
let utf8 = new Utf8String(buffer)
// This is still just a Uint8Array/ArrayBuffer under the hood
utf8 instanceof Uint8Array // true
utf8.buffer === buffer // true
// Indices would still just be numbers
// (They wouldn't automatically convert to UTF-16 strings)
utf8[0] // >> 60
// But accessing malformed data would return U+FFFD (�) the "Replacement Char"
utf8[malformedCharIndex] // >> 65533
// Then we can start getting into the fun bits: Now you can have familiar
// String-like APIs that operate on UTF-8 encoded bytes rather than UTF-16
utf8.trim() // >> Utf8String
utf8.padEnd(5) // >> Utf8String
// For operations that need another string, you'd use other Utf8Strings
let other = Utf8String.from("<h1>Example Domain</h1>")
utf8.includes(other)
utf8.localeCompare(other, { sensitivity: "base" })
// Maybe even regex operations could still work
utf8.match(/Example/)
utf8.replace(/Example/, Utf8String.from("Paragon"))](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:mlm5fumlu4k7emxlveklmp4z/bafkreifaj4xneiwoeyricso3ihgdhlnpf7fxsmftxmlno6xjvhvrpbyrwi)
November 18, 2024 at 9:50 PM
TC39/JavaScript Idea: Utf8String()
JS strings are UTF-16 but most langs/tools use UTF-8 which makes interop hard sometimes
Uint8String() would actually just be a new TypedArray/ArrayBuffer view (not a new String type)
It would provide familiar string APIs on raw UTF-8 bytes making interop easier
JS strings are UTF-16 but most langs/tools use UTF-8 which makes interop hard sometimes
Uint8String() would actually just be a new TypedArray/ArrayBuffer view (not a new String type)
It would provide familiar string APIs on raw UTF-8 bytes making interop easier
UTF-8000: Unlimited UTF-8 | Discussion
UTF-8000
Unlimited UTF-8!
utf-8000.jb2170.com
September 20, 2026 at 7:40 AM
UTF-8000: Unlimited UTF-8 | Discussion
days since it enountered utf-8 encoding issues in modern software: 0
July 8, 2026 at 3:42 PM
days since it enountered utf-8 encoding issues in modern software: 0
O Claude é tão tosco que não sabe lidar com UTF-8.
Sobe um texto acentuado em UTF-8 para revisar. Diga que é UTF-8. Mesmo assim, ele repetidamente alucina erros que só existem porque está lendo o texto byte a byte, e não entende que em UTF-8 um caractere acentuado é feito de dois bytes!
Ridículo.
Sobe um texto acentuado em UTF-8 para revisar. Diga que é UTF-8. Mesmo assim, ele repetidamente alucina erros que só existem porque está lendo o texto byte a byte, e não entende que em UTF-8 um caractere acentuado é feito de dois bytes!
Ridículo.
October 20, 2025 at 6:50 PM
O Claude é tão tosco que não sabe lidar com UTF-8.
Sobe um texto acentuado em UTF-8 para revisar. Diga que é UTF-8. Mesmo assim, ele repetidamente alucina erros que só existem porque está lendo o texto byte a byte, e não entende que em UTF-8 um caractere acentuado é feito de dois bytes!
Ridículo.
Sobe um texto acentuado em UTF-8 para revisar. Diga que é UTF-8. Mesmo assim, ele repetidamente alucina erros que só existem porque está lendo o texto byte a byte, e não entende que em UTF-8 um caractere acentuado é feito de dois bytes!
Ridículo.
application/json;charset=utf-8
August 29, 2025 at 9:45 PM
application/json;charset=utf-8
The characters "=C2" and "=A0" are Quoted-Printable encoded representations of a non-breaking space (UTF-8): 0xC2 0xA0), which are commonly found in text/plain or text/html email MIME types.
These appear when 8-bit UTF-8 characters are encoded for 7-bit SMTP transport.
These appear when 8-bit UTF-8 characters are encoded for 7-bit SMTP transport.
January 31, 2026 at 4:34 PM
The characters "=C2" and "=A0" are Quoted-Printable encoded representations of a non-breaking space (UTF-8): 0xC2 0xA0), which are commonly found in text/plain or text/html email MIME types.
These appear when 8-bit UTF-8 characters are encoded for 7-bit SMTP transport.
These appear when 8-bit UTF-8 characters are encoded for 7-bit SMTP transport.
ITmedia は IT メディアとしての自覚を持って UTF-8 にしろ
January 23, 2024 at 1:41 AM
ITmedia は IT メディアとしての自覚を持って UTF-8 にしろ
Yup. Incomplete MIME decoding /reconstruction, or double encoding issues (UTF-8 quoted-printable, later run through another conversion step that assumes ISO-8859-1/Windows-1252, or vice versa)
January 31, 2026 at 5:53 PM
Yup. Incomplete MIME decoding /reconstruction, or double encoding issues (UTF-8 quoted-printable, later run through another conversion step that assumes ISO-8859-1/Windows-1252, or vice versa)