Lunduke
News • Science & Tech
The Unlikely Story of UTF-8: The Text Encoding of the Web
Plan 9, Placemats, New Jersey Diners, and last minute ideas
June 22, 2023
post photo preview

If you are reading this on a computer -- of any kind -- odds are good that the words on the screen are all encoded using something called "UTF-8".

UTF-8 (or "Unicode Transformation Format - 8 bit") is, put simply, a format for encoding and storing text -- one which allows for far more text characters than the older "ASCII" encoding (which could only show a total of 95 printable characters).

And UTF-8 is, quite simply, everywhere.

Nearly every major computer operating system heavily uses UTF-8 for handling text... likewise it is the standard for websites, with close to 100% of all webpages explicitly using UTF-8 for the text on the page.

test
The source for Wikipedia.  Like most of the web, using UTF-8.

An argument could be made that UTF-8 is one of the most successful and widely adopted standards in all of computer history.

But this almost wasn't the case.

In fact, UTF-8 was created -- at the very last possible moment -- and it was first implemented in a computer system that most people don't even know existed.

X/Open's search for better text encoding

In the early 1990s, text encoding was... an issue.

While solutions for extended character sets (beyond simple ASCII characters) existed, they were less than ideal.  To put it mildly.  The most popular solution, known as UTF-1 (aka "ISO 10646"), suffered from serious performance issues... and often caused significant problems with software which used plain "ASCII" text (including UNIX file system paths).

Having a character encoding on UNIX systems that could cause problems with UNIX file systems?  Not good.

Obviously a new type of text encoding was needed.

So, in 1992, X/Open (originally known as the "Open Group for UNIX Systems", a consortium of UNIX vendors, including: Sun, HP, AT&T, IBM, and several others) set about the task of selecting a proper text encoding standard to be used across all of the UNIX world.

The proposal that gained the most traction was known as FSS/UTF (aka "File System Safe Universal Character Set Transformation Format").  Roills off the toungue, right?

This proposal was both faster than the old text encoding standard... and, as the name suggests, it was "File System Safe".  Which was a big win.

Enter: The Plan 9 Nerds

Which brings us to September 2nd, 1992.  Sometime in the early evening.

The X/Open group was meeting, in Austin, Texas, to formally decide on the file encoding standard.

Looking to get some feedback on the proposal, some members of X/Open made a call to two legendary programmers -- Ken Thompson and Rob Pike -- who were working on the Plan 9 Operating System project at Bell Labs in New Jersey.


A little background...

Ken Thompson was one of the creators of MULTICS, UNIX, the B programming language (the predecessor to C), among many other accomplishments.

Rob Pike, also a UNIX programmer, was the co-creator of Blit, writer of multiple UNIX and programming books, and the creator of the first UNIX windowing system.

To call these two "absolute legends" in the world of computing would be, perhaps, a bit of an understatement.  The two were currently working together on a research operating system, at Bell Labs, called Plan 9.  An attempt to fix some of the perceived shortcomings of UNIX... by the creators of UNIX, itself.


What happened next... after Ken Thompson and Rob Pike received that phone call?  Luckily, we have a detailed accounting... written by Rob Pike, himself.

"We had used the original UTF from ISO 10646 to make Plan 9 support 16-bit characters, but we hated it.  We were close to shipping the system when, late one afternoon, I received a call from some folks, I think at IBM - I remember them being in Austin - who were in an X/Open committee meeting.  They wanted Ken and me to vet their FSS/UTF design."

Asking two legendary engineers for their input?  You can probably guess what happened next...

"Ken and I suddenly realized there was an opportunity to use our experience to design a really good standard and get the X/Open guys to push it out.  We suggested this and the deal was, if we could do it fast, OK."

That's right.  Ken and Rob had some ideas.  And the X/Open folks agreedd to listen to those ideas... if they could get them something fast.

And, by fast, they really meant "immediately... like... right now."  Because the X/Open team were, quite literally, all gathered in Austin to decide on this... right then.

"Yeah.  I could eat."

Ken and Rob did what any good programmers would do when placed on an almost impossibly tight deadline -- and needed to come up with an amazing idea that could change the course of computing for decades to come... they went out to grab some grub.

"So we went to dinner, Ken figured out the bit-packing, and when we came back to the lab after dinner we called the X/Open guys and explained our scheme.  We mailed them an outline of our spec, and they replied saying that it was better than theirs (I don't believe I ever actually saw their proposal; I know I don't remember it) and how fast could we implement it?  I think this was a Wednesday night and we promised a complete running system by Monday, which I think was when their big vote was."

Remember.  This was 1992.

Which means, while laptops and such certainly existed, most people (even legendary programmers) did not have any sort of mobile, portable computers.  Certainly not the kind you could take out to a restaurant.

So what, pray tell, did they write their new text encoding design on?

A placemat from a New Jersey diner.

This is not the placemat that UTF-8 was designed on.

Seriously.

"UTF-8 was designed, in front of my eyes, on a placemat in a New Jersey diner."

The boys, Ken and Rob, now had just a few days to get all of this done -- before the big vote on the new text encoding standard.  And they sure as heck didn't waste any time.

They got back from dinner, placemat in hand, and got to work.

"So that night Ken wrote packing and unpacking code and I started tearing into the C and graphics libraries.  The next day all the code was done and we started converting the text files on the system itself.  By Friday some time Plan 9 was running, and only running, what would be called UTF-8.  We called X/Open and the rest, as they say, is slightly rewritten history."

They converted an entire operating system over to a brand new -- just designed on a placemat -- text encoding format... in less than two days.

Here's the rough time-line:

  • Wednesday (Sep 2) evening: Dinner at a New Jersey Diner.  Ken Sketches out the idea on a placemat.
  • Wednesday night: Coding begins.
  • Thursday: Coding complete.
  • Friday: Entire Plan 9 operating system is now using "UTF-8".
  • Monday (Sep 7): X/Open group votes to use the Ken/Rob encoding design.

On Tuesday, September 8th, 1992 (at 3:22am), mere hours after the official vote to accept their text encoding design, Ken Thompson sends out the following email regarding Plan 9 now using UTF-8:

"The code has been tested to some degree and should be pretty good shape.  We have converted Plan 9 to use this encoding and are about to issue a distribution to an initial set of university users."

That's right.

Ken and Rob got a call asking for feeback on a Wednesday.  By the next Tuesday (at 3am) they were ready to ship a version of their Plan 9 OS with all the changes, and their designs had been voted on by the largest UNIX companies in the world.

Like I said.

A recent picture of the two legends, themselves.

These guys are legends.

What about that placemat?

Considering the vast impact of UTF-8 on the world of computing... whatever happened to that original "design document" (aka "the placemat")?  It would certainly be of historic significance.

"I very clearly remember Ken writing on the placemat and wished we had kept it!"

Let this be a lesson to all of the programmers out there:

Keep all of you doodles, notes, and sketches you make for your projects... you never know when one of those projects will become critical to the entire world... making your quick sketch worthy of being in a museum.

Especially if it's on a placemat.  From a diner.  In New Jersey.


Copyright © 2023 by Bryan Lunduke.  All rights reserved.  The contents of this article are licensed under the terms of The Lunduke Content Usage License.

community logo
Join the Lunduke Community
To read more articles like this, sign up and join my community today
11
What else you may like…
Videos
Podcasts
Posts
Articles
CreepyLink.com: URL Shortener That Makes Links Look Suspicious
00:05:38
January 17, 2026
Modern Linux Using Only 200MB of RAM?

The Vendefoul Wolf Linux Distro has a new release based on Devuan, XLibre, & IceWM. And it uses only 217 MB of RAM. The way it should be.

$89 Lifetime Lunduke Journal Subscriptions all January:
https://lunduke.substack.com/p/89-lifetime-lunduke-journal-subscriptions-c1b

More from The Lunduke Journal:
https://lunduke.com/

00:09:45
January 16, 2026
GNOME 50 Alpha: "Entirely Removes X11"

The GNOME Foundation's war on X11 continues, with the Alpha release of GNOME 50. Announced by the same GNOME contributor who defaced XLibre project pages (calling them "Nazis" ).

$89 Lifetime Lunduke Journal Subscriptions all January:
https://lunduke.substack.com/p/89-lifetime-lunduke-journal-subscriptions-c1b

More from The Lunduke Journal:
https://lunduke.com/

00:18:35
November 22, 2023
The futility of Ad-Blockers

Ads are filling the entirety of the Web -- websites, podcasts, YouTube videos, etc. -- at an increasing rate. Prices for those ad placements are plummeting. Consumers are desperate to use ad-blockers to make the web palatable. Google (and others) are desperate to break and block ad-blockers. All of which results in... more ads and lower pay for creators.

It's a fascinatingly annoying cycle. And there's only one viable way out of it.

Looking for the Podcast RSS feed or other links? Check here:
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

The futility of Ad-Blockers
November 21, 2023
openSUSE says "No Lunduke allowed!"

Those in power with openSUSE make it clear they will not allow me anywhere near anything related to the openSUSE project. Ever. For any reason.

Well, that settles that, then! Guess I won't be contributing to openSUSE! 🤣

Looking for the Podcast RSS feed or other links?
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

openSUSE says "No Lunduke allowed!"
September 13, 2023
"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

This episode is free for all to enjoy and share.

Be sure to subscribe here at Lunduke.Locals.com to get all shows & articles (including interviews with other amazing nerds).

"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044
January 17, 2026

The 100x Architect: Why the "Vibe Coding" Argument is a Dangerous Coping Mechanism

I hear it constantly from my fellow nerds: “I’m not worried. Non-coders ‘vibe coding’ AI slop will never be a threat to my job.”

You’re 100% right. Vibe-coded slop isn't the threat. The threat is top-talent developers who also master GenAI tools.

While the skeptics are busy mocking juniors for generating buggy Todo apps, they are missing the real shift: the veterans with 40 years of patterns in their heads who are using GenAI as a 10x multiplier.

The math is simple: 10x1 is 10. 10x10 is 100.

If you are a talented dev (a 10), and you refuse to use the multiplier, you aren't "staying pure"—you’re just being out-scaled by the people who have your skills AND scale themselves with GenAI.

A Field Report from the 100x Front:

In two recent projects—one for a paying client and one for a friend—I built in a few hours by myself what would have traditionally taken a small team a couple of weeks...

20 hours ago

The Big Tech "Charity" Hustle.

A Eulogy For Omarchy - Sunday Laptop Rebuild Stream

Last Tuesday, I tried to put Omarchy on my daily driver laptop. After six days of fighting with it, I'm quitting.

This is the THIRD TIME I've tried to make Omarchy a thing for me, and all three times, I've had nothing but struggle. So, now, we're going back to Manjaro. But before I do, I'll spend a little time experimenting with other distros, live on camera, unscripted. Just for the gawkers.

[EDIT] Apologies: I got a little LIPPY because of how much Omarchy pissed me off. Just to warn you.

placeholder
January 16, 2026
Lunduke Journal Week In Review - Jan 16th, 2025

Whew! It’s been another wild week for Tech News!

Here’s a crazy stat for ya:

We are currently 16 days into 2026, and The Lunduke Journal has already recorded 19 shows (17 of which have been published on every platform, and 2 others to be published this weekend everywhere… but are already available via the MP4 download page). And that’s with taking New Year’s Day off (and getting the flu this week).

It’s a heck of a lot of Tech News, to be sure.

Lunduke’s Top Stories for the Week

If you only have time to watch a few of shows, I recommend these 3 as being the most interesting (or important… or just… strange) from the last week:

In other words: A pretty gosh-darned crazy week for Linux.

(Those links are to Lunduke.Substack.com, but you can watch all of those shows on any other platform. As always.)

Other Tidbits of Awesomeness

A few other notes on this, most excellent, Friday!

And, with that, I leave you with a screenshot of the MP4 listing of the shows so far in 2026. Bonkers.

 

-Lunduke

Read full Article
January 14, 2026
Lunduke's Lifetime Subscriber Wall 3 is almost full!

Holy moly.

This afternoon I sat down to update the 3rd Lunduke Journal Lifetime Subscriber wall — adding in all of you who sent in requests over the last week or so.

And, boy howdy, were there a lot of you! So many, in fact, that the 3rd Lifetime Wall only has room for around 6 or 7 more names (depending on the name lengths)! That’s crazy!

If you want to make it onto “The Lunduke Journal Lifetime Subscriber” Wall number 3… send me an email (bryan at lunduke.com) with the way you would like your name to be displayed.

Or, if you’re not already a Lifetime Subscriber, remedy that for $89. (Which, you know, is a pretty gosh darned good value.) … Then send me that email requesting to be added to the wall.

Once Wall 3 is full, we’ll start in on Wall number 4 (that’s nuts). At the current rate, I expect Wall 4 to debut this week.

And, as always, thank you for your support. Whatever kind of subscription you have, it is deeply appreciated. Monthly, Yearly, or Lifetime. All are amazing. You make The Lunduke Journal possible.

You rule.

-Lunduke

 
Read full Article
January 13, 2026
Lunduke Out Sick Tomorrow

I’ve got the flu (or something else yucky) and need to take the day off tomorrow.

But I don’t really have a normal “boss” to email. Heck, all of you are sort of like my collective boss.

So I’m emailing you:

Boss, *cough cough* Lunduke is out sick tomorrow.

Which means no new shows on Wednesday. Hoping to rest up and be back with new shows on Thursday.

If you’ve missed any shows over the last few weeks, now’s a good chance to catch up.

And feel free to grab one of those fancy-shmancy $89 Lifetime Subscriptions while you’re at it. That won’t make my flu go away any faster… but it definitely won’t hurt.

Unrelated note: Buying stock in Nyquil might not be a bad idea. I think I’m about to increase their profits.

-Lunduke

Read full Article
See More
Available on mobile and TV devices
google store google store app store app store
google store google store app tv store app tv store amazon store amazon store roku store roku store
Powered by Locals