On Tue, Feb 15, 2022 at 06:35:46PM +0100, Stella Ashburne wrote: [...] > You are right. I would fix them if I had the knowledge and competency. Back to the libthai thing. Perhaps it is unfixable nowadays: what shall a browser do? Look at this harmless page [1]. Somewhere down there is the Thai translation of the likewise harmless English word "water". Your browser wouldn't be capable to represent that correctly without the rendering capability provided by libthai, I guess. (What I cant say is whether your browser is using the OS provided libthai, via pango, or whether it has ingested an own version of pango with its own version of libthai. This is left as an exercise for the reader). In short: computers have grown up a lot since the good ol' days of ASCII. Sometimes it's difficult to keep up. Heck, I remember the times where there was a Germanized version of ASCII (yeah, 7 bit, curly and square brackets, and I think backslash, solidus and a couple of other innocent signs were sacrificed for the umlauts). Needless to say, mixing C code with comments in German was... strange. Then, the upper bit came, and we got Latin-1; but still you couldn't have German and, say, Greek or Russian in the same text. Now I can just say "γεια σου". That easy. Yes, Unicode is a beast. But it reflects the chaotic and lively mess we humans are! I don't want my ISO-8859-x back thankyouverymuch (but: a friend of mine, who knows a lot, heartily disagrees with me: I might be wrong, after all). Cheers [1] https://en.wiktionary.org/wiki/water/translations -- t
Attachment:
signature.asc
Description: PGP signature