Seeing this as a bumper sticker on a car is very on point.

I have been test driving a lot of cars recently since my last vehicle was considered a total loss by insurance (thankfully no one was injured when an idiot fell asleep at the wheel and crashed into me after veering from the Express lane).

My second language is Japanese, and I noticed Unicode display errors when linking a to a Toyota CarPlay system! Curious, that a car manufacturer, that originates in Japan, can't display Japanese!? But presumably their "infotainment system" is targeted for North America (it only lets users select English Spanish and French as languages).

In contrast, when driving a KIA recently, it displayed the Japanese characters correctly via CarPlay (though I did notice it also allowed users to select Korean as a display language; implying that while they didn't offer a Japanese localization, they also hadn't bothered to remove UTF-8/Unicode which they presumably already required for Hangul character encoding support. That is more how I would expect things to be in 2025, but Toyota proved me wrong!).

UTF-8 is over 30 years old now (1992 origin story recollected here: https://doc.cat-v.org/bell_labs/utf-8_history) but it's dumb founding to me how companies worth hundreds of billions of dollars, still fail to implement it correctly, even when it comes to representing the native language of their own corporation's culture!

@tze I have roughly the same joke in website form: https://luser.github.io/i-heart-unicode/ (it's using font shenanigans, though.)

@tze reminds me of my absolute favourite Unicode-related tweet: