Fun video about #Unicode #UTF8. I knew about the historical context and fundamental implementation ideas already, but I didn’t know about the Hangul combinations block trick mentioned in the end… clever stuff.

https://www.youtube.com/watch?v=vpSkBV5vydg

fn sub(foo: &String) {
    println!("We got this string: [{}]", foo);
}

fn main() {
    // "Hello", 0x00, 0x00, "!"
    let buf: [u8; 8] = [0x48, 0x65, 0x6C, 0x6C, 0x6F, 0x00, 0x00, 0x21];

    // Create a string from the byte array above, interpret as UTF-8, ignore decoding errors.
    let lossy_unicode = String::from_utf8_lossy(&buf).to_string();

    sub(&lossy_unicode);
}

Create a string from a byte array, but the result isn’t a string, it’s a cow 🐮, so you need another to_string() to convert your “string” into a string.

• https://doc.rust-lang.org/std/string/struct.String.html#method.from_utf8_lossy
  
• https://doc.rust-lang.org/std/borrow/enum.Cow.html
  

I still have a lot to learn.

(into_owned() instead of to_string() also works and makes more sense to me, it’s just that the compiler suggested to_string() first, which led to this funny example.)

@lyse@lyse.isobeef.org Sorry, I don’t think I ever had charset=utf8. I just noticed that a few days ago. OpenBSD’s httpd might not support including a parameter with the mime type, unfortunately. I’m going to look into it.

Övergång till UTF-8 ⌘ https://hack.org/mc/blog/utf8.html

Fun fact: OpenBSDs vi does not support utf8. That’s probably the first time I haven’t just used the default system vi.

Fun fact: OpenBSDs vi does not support utf8. That’s probably the first time I haven’t just used the default system vi.

@kas@enotty.dk And to make it even worse, most clients interpret the data as win1252. But does any twtxt client autoconvert to utf8 in case another charset is send? I think it probably okay for every client to assume it’s utf8.

@kas@enotty.dk And to make it even worse, most clients interpret the data as win1252. But does any twtxt client autoconvert to utf8 in case another charset is send? I think it probably okay for every client to assume it’s utf8.

@tx@0x1A4.1337.cx Nice! But i don’t get a UTF8 feed, for example https://twtxt.1337.cx/tazgezwitscher

@tx@0x1A4.1337.cx Nice! But i don’t get a UTF8 feed, for example https://twtxt.1337.cx/tazgezwitscher