Piero Bosio Social Web Site Personale

@valhalla @movim Yes, that's the workaround: Set the UI to one language, post in this language, set UI to other language, post in that language. Slightly cumbersome for people who post in multiple languages.

**@小明@範例.測試, or, Fediverse handles in every language**is the proposal I just submitted to @COSCUP . Abstract:A person's handle is their name and address on the Fediverse. But despite people on using the Fediverse in many languages from all over the world, almost all handles are limited to Latin script letters and numbers: **@somebody@example.com** . Instead, people should be able to use a handle in their own language and characters, e.g. **@小明@範例.測試** or **@김@예시.테스트**. We call this "globally inclusive Fediverse handles".This talk explains the reasons why handles are now limited…. We look at the role of specifications, and existing software…. We look at the history of internationalising other address types such as email addresses ( जिम@डाटामेल.भारत ) and domain names ( http://ยูเอทดสอบ.ไทย ). We list some rules from DNS, Unicode, and IETF…: the Fediverse can build on them. We propose a path forward….#GloballyInclusiveHandles #GloballyInclusiveFediverse #i18n Thank you @hongminhee for your encouragement!

@neatnit No, what's cool is that if *I* link them, it works everywhere. You won't be able to though. Edit: In any useful fashion.

A character encoding defines how text is stored as bytes. If you’ve seen “café” instead of “café,” that’s an encoding mismatch. This intro covers how encoding works, how #Unicode and UTF-8 relate, and why mistakes break apps and websites. It also matters beyond #developers—affecting readability, search, data exchange, #accessibility and whether people see text correctly online.🎬 Watch @xfq, @w3c's #i18n lead, explain what character encoding is: https://youtu.be/y2ay7otbFWk