Impressively, they already fixed it, while I was asleep.
In supposing it's old, I am assuming that (1) libxbcommon is in fact that old, which is the case for many x libraries, but maybe not this one, and (2) the BOM idea is as old as UTF-8.
@mcc interesting, and prompted me to wonder if I covered that in my char encoding article. To my delight it seems I did, by writing-
.. defer to Wikipedia for the details, but for this article, here is the key quote:
"BOM use is optional. Its presence interferes with the use of UTF-8 by software that does not expect non-ASCII bytes at the start of a file but that could otherwise handle the text stream."
@mcc
Oof.
Don't know if it makes it better, but I found a bug in our system yesterday that is probably ~20 years old. Only happens at the point of implementation for an uncommon configuration. I can only guess that no one has mentioned it is that if our implementation consultants ran into it, they just fixed the record in the back end and got on with their lives.
If libxkbcommon attempts to close my bug as a WONTFIX/works-as-intended I am going, this is not a joke, I am going to attempt to track down Ken Thompson and see if I can get him to take my side in this GitHub thread. Yes, he's actually relevant
@ok_devalias I think it's more like an 80s coming-of-age movie. "I'm going to go on a road trip… to find Ken Thompson! And ask him to settle this argument"
@mcc (Alright, that was too random. In my defense, I've had a loooot of sugar this evening. The thinking was: way older than drinking/voting age, but aaaalmost old enough to start the mid-life crisis phase)
Add comment