@jpfox @adele I am seriously considering providing a #gettext / #i18n based patch

Thrilled to announce that issue #550 in Chinese Layout Requirements (clreq) has been fixed! Emphasis dots now stay properly centre-aligned with the text even after letter-spacing is increased.

https://github.com/w3c/clreq/issues/550

#i18n #WebStandards

@hongminhee @liaizon @Edent @north @Profpatsch (3/3)
4. I think that the next step towards #GloballyInclusiveHandles is to find brave pioneers who want to use these handles, even though they will find it difficult.
5. I think that the step after that is to find or modify #Fediverse software to work with these handles, so it is useful for the pioneers. Which software is a good starting point?
6. I think that those pioneers aren't near me in Canada. They might be at @COSCUP , speaking Chinese or Korean or Japanese. Someone should propose a COSCUP session on Globally Inclusive Handles.
#i18n #GloballyInclusiveFediverse #Fediverse #Multilingual #GloballyInclusive
@hongminhee @liaizon @Edent @north @Profpatsch (2/3)
1. Everyone supports #GloballyInclusive handles in principle. Strongly.
2. There are big holes in the #ActivityPub architecture around handles. See <https://lists.w3.org/Archives/Public/public-swicg/2026May/0001.html> for a taste. Probably specifications need to be improved if non-Latin handles are to work well.
3. I got strong encouragement to join #W3C Social Web Incubator Community Group https://www.w3.org/community/socialcg/ and show up for the design discussion and spec writing. I have done so. I subscribed to the public-swicg email list. You folks might want to consider joining also: it's free, and works with any time zone.
#i18n #GloballyInclusiveFediverse #Fediverse #Multilingual #SWICG
Taskforce Proposal: Internationalized "handles" from emelia on 2026-05-01 ([email protected] from May 2026)

@hongminhee @liaizon @Edent @north @Profpatsch (1/3)

Report back from #FediForum last week. Held a good session on #GloballyInclusive handles. Just a few attendees, but one knew the technical issues deeply and was well connected to ActivityPub design. Session notes will likely appear at https://fediforum.org/topics/#topic-internationalization in a few weeks. For now, here is a summary:

#i18n #GloballyInclusiveFediverse #Fediverse #Multilingual

FediForum | Topics

FediForum
A source of example domain names: IANA has some non-Latin top-level domains marked "test": https://www.iana.org/domains/root/db . Combine with the word "example". It makes: 範例.測試 (#漢語), 示例.测试(#汉语), 예시.테스트 (#한국어), 例.テスト (#日本語), उदाहरण.परीक्षा (#हिंदी).
Native speakers, please help me: do those names look a) correct, b) appropriate for a technical presentation?
#i18n #GloballyInclusive #Fediverse @COSCUP #translation
Root Zone Database

I want some generic human names to use as examples in a talk. For English, I would use Jane, John, Alice, Bob, Pat, Kim, etc. What are similar common, generic names in 繁體字 , 简化字 , 한글 , 和文 , อักษรไทย , देवनागरी , and other non-Latin scripts? #i18n #GloballyInclusive #Fediverse @COSCUP
I want some example domain names to use in a talk. For English, I would use `example.com`. What are similar example domain names in 繁體字 , 简化字 , 한글 , 和文 , อักษรไทย , देवनागरी , etc? #i18n #GloballyInclusive #Fediverse @COSCUP

Global Growth Without Friction. Keep keys and placeholders intact while you localize.

Built for high-volume localization workflows without brittle copy/paste steps.

Explore the workflow: www.json-translate.com
#Localization #i18n #DeveloperTools

Congrats @Profpatsch on your #Flohmarkt demo at #FediForum2026. Thank you for mentioning #GloballyInclusive handles. #GloballyInclusiveFediverse #i18n