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
AI Submissions to Linux Hits New Record, 10% of All Patches

571 submissions to The Linux Kernel, this last week, were coded by Al.
That's over 10% of all code submissions to the kernel. And growing. Fast.

Get on The Wall with a Massively Discounted Lifetime Sub:
https://lunduke.substack.com/p/50-off-yearly-and-massively-discounted

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

00:18:08
Slackware Tests Replacing Xorg with XLibre

The oldest actively maintained Linux distro now includes XLibre in their official builds, and is testing removing Xorg entirely.

Get on The Wall with a Massively Discounted Lifetime Sub:
https://lunduke.substack.com/p/50-off-yearly-and-massively-discounted

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

00:21:35
Rust-Based Malware Hits 1.4% of Arch User Repository

The data stealing code compromised over 1,500 packages in the Arch Linux User Repository, making use of Rust, Systemd, NodeJS, & Bun.

Grab a Discounted Lifetime Sub & Get on The Wall:
https://lunduke.substack.com/p/50-off-yearly-and-massively-discounted

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

00:12:27
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
Heads up: "Win2k" & "TempleOS" Lunduke Journal Lifetime Subscriber Walls are almost full!

Also: If you have already emailed me with your request to be added to one of these three Walls, but haven't received a response, email me again ASAP. I had an email issue this last week and I want to make sure nobody gets missed.

Here are how many more names can fit on each of the three currently open Walls (best estimate, variable depending on name lengths):

  • Mac System 1 : 12 spots left
  • Windows 2000 : 4 spots left
  • TempleOS : 7 spots left

If you already have a Lifetime Subscription to The Lunduke Journal, just email me to let me know which Wall you'd like to be on and how you'd like your name displayed (nickname, full name, etc.).

Lunduke Journal contact info is here:
https://lunduke.com/

If you don't have a Lifetime Sub yet... get on that!

Lifetime Subscriptions are massively discounted through the end of June. Take advantage of that:
https://lunduke.substack.com/p/50-off-yearly-and-massively-discounted

-Lunduke

post photo preview

Local Works - But Not Well Enough

I keep occasionally dipping my toes into the local AI for coding pool. It gets better and better - but TLDR; - nowhere near good enough for me right now.

This last time was best yet. I have Codex at my finger tips and after discussing the ins and outs of local on Apple silicon Macs we selected the following:

Pi as the agentic coding harness. Think “Claude Code” - open source and minimal. I like it for when I’m using llm’s via api. Works just as well for local llms.

My machine is an M5 Air with 32gig RAM. I tried to find a solution that would use both the NPU and GPU, alas, that solution hasn’t come online yet. I went wit MLX as that’s Apple’s optimized platform.

mlx-community/Qwen3-Coder-30B-A3B-Instruct-4bit

Qwen Coder is one of the best local coding llm’s but 4bit just takes out too much of the intelligence.

Fun thing, with Codex’s abilities of late, after we discussed through the options and what was best I could say “install all the ...

3 hours ago

Red Alert!!!

post photo preview
Lunduke's Week in Tech : June 7 - June 13, 2026

It has been, yet another, weird and wild week in the world of Tech and Open Source.

Filled with awesome and inspiring stories (Linux logos on Race cars!)… mixed with bizarre, Woke politics and concerning technical news.

And, as usual, all but one of the big stories this week were completely ignored by the other of the Tech News outlets.

Here are the major stories from the last week, with direct links to X and Substack. You can also watch / listen on a bunch of other platforms (Rumble, RSS Audio Podcast, etc.), listed on Lunduke.com.

  • Rust-Based Malware Hits 1.4% of Arch User Repository (X, Substack)

  • Godot Game Engine Promotes Extreme, Pro-Trans "Pronoun Palace" Game (X, Substack)

  • GNOME in Damage Control Mode After Revelations from Ex Board Member (X, Substack)

  • Proton Mail Apologizes for Sponsoring "Far Right French YouTuber" (X, Substack)

  • Ex Board Member Reveals Corruption & Dysfunction at GNOME Foundation (X, Substack)

  • AI Generated Patches to Linux Kernel Hits New Record High (X, Substack)

  • Linux Logos on Racecars (X, Substack)

  • XLibre Turns One Year Old (X, Substack)

Huge thank you to all of The Lunduke Journal’s subscribers. You make all of this possible.

-Lunduke

Read full Article
post photo preview
TempleOS arrives on The Lunduke Journal Lifetime Wall

“When are you going to add a TempleOS Lifetime Wall??!”

I’ve lost track of the number of times I’ve received that request over the last few weeks. Well. What the heck! Why not?

There are now three Lunduke Journal Lifetime Subscriber Walls (displayed both on Lunduke.com and the end of all new shows) with space available:

  • Macintosh System 1

  • Windows 2000

  • TempleOS

 

A few quick notes:

  1. The Windows 2000 Wall, which was introduced only 2 days ago, is already about half way full. At the current rate, that one will likely be full by the end of the week. Still plenty of space on the Mac System 1 Wall.

  2. The discount on Lifetime Subscriptions ($125… discounted from the normal $300) runs through the end of June.

  3. One Lifetime Subscription = Name Listed on One Wall. These Walls are crazy popular and fill up super fast, so I have to put that limit in place.

  4. Want your name on more than one Lifetime Wall? Grab a second Lifetime Subscription (use the discounted rate) and you can have your name added to one of the Walls with space still available.

Massive high five to everyone who has supported The Lunduke Journal and made these retro-computer Lifetime Walls so much fun to do!

-Lunduke

Read full Article
post photo preview
Behold! The "Win 2K" & "Mac System 1" Lifetime Sub Walls!

Woah! The 8th Lifetime Subscriber Wall of The Lunduke Journal (aka “The Windows 1.0 Wall”) is already full! After only one week! That’s nuts!

So I’m opening up two new, retro computer walls!

  • Wall 9 - “The Macintosh System 1 Wall”

  • Wall 10 - “The Windows 2000 Wall”

 

Show your support for The Lunduke Journal, and be immortalized in a retro computer screenshot. Win-win!

If the past is any indicator, these will fill up crazy fast. First come, first served.

Plus: For the entire month of June, Lifetime Subscriptions are discounted down to $125 (regularly $300).

  1. Scroll down and grab a new Lifetime Subscription (at that bonkers discount).

  2. Choose which of the two new Walls you’d like to be on (Mac System 1 or Windows 2000). Totally optional.

How to Grab a Discounted Lifetime Subscription:

There are 3 different ways to pick up a Lunduke Journal Lifetime sub. All of them work great and include the same perks. Choose whichever works best for you!

Get a Lifetime Subscription via Locals:

  1. Go to Lunduke.Locals.com/support.

  2. Select “Give Once“.

  3. Enter “125“ into the amount field.

  4. After checking out, Lunduke will toss you an email once your account is set to full lifetime status. (This usually happens within a few hours.)

Get a Lifetime Subscription via Substack:

  1. Go to Lunduke.Substack.com/subscribe.

  2. Select the “Lifetime Subscription” option.

  3. After checking out, Lunduke will toss you an email once your account is set to full lifetime status. (This usually happens within a few hours.)

If you would also like full, Lifetime access to Lunduke.Locals.com (which is included):

  1. Make a free account on Lunduke.Locals.com.

  2. Email “bryan at lunduke.com” with the email address you use on both Substack and Locals (can be different email addresses).

  3. Lunduke will toss you an email once your account is set to full lifetime status on Locals.

Get a Lifetime Subscription with Bitcoin:

Bonus: Save an extra $10 with the Bitcoin option, as Bitcoin processing has fewer fees associated with it.

bc1qyjakve8fywm8pz2v99v57yhjj0vzr2vjze6fcq

  • Email “bryan at lunduke.com” with the following information: What time you made the transaction, how much was sent (in Bitcoin), and the email address you use (or plan to use) on Locals.com or Substack.com.

-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