News for hackers. Stuff that matters.
Re:I'm Not a Fan of Strlcpy(3) by anamexis on Monday July 15, 2024 @10:58AM (#40968442)
Advocating a new global constructed language to accomodate C's shortcomings seems like the wrong direction to be thinking.
Re:I'm Not a Fan of Strlcpy(3) by smaudet on Monday July 15, 2024 @11:03AM (#40968490)
Less a global constructed language, more a "better" encoding. Base64 works really well for arbitrary binary-in-text encoding, for instance.
Re:I'm Not a Fan of Strlcpy(3) by estebank on Monday July 15, 2024 @01:21PM (#40969745)
Unicode is that better encoding. The "small and efficient per locale encoding" that you proposed was the status quo, and was an endless source of mojibake. There is a reason we moved away from that.
Re:I'm Not a Fan of Strlcpy(3) by smaudet on Monday July 15, 2024 @02:38PM (#40970320)
I think there is a misunderstanding, which I tried to address but evidentally failed.

UTF-8 is fine for a display encoding. However, not every string encoding need be a display encoding, which the parent post seems to not be considering.

You could also have multiple display encodings, if it makes sense to (a tool only intended for use in a certain part of the world for instance), however that is not what I mean.