@hongminhee洪 民憙 (Hong Minhee) (4) seems good. It'll be no different than having mixed-language content. E.g. the ruby tags can be extended as such:
```
<ruby lang="ja">日本語<rp>(</rp><rt lang="ko">일본어</rt><rp>)</rp></ruby>
```
But, I think some folks might want to separate them with (1), so that people can subscribe to one account but filter by language ("Change subscribed language" in individual profile pages on Mastodon).
@cheeaunChee Aun 🤔 That ruby annotation approach is interesting! It's a creative solution for inline translations.
I agree though—it's frustrating that despite ActivityPub having built-in support for multilingual content through contentMap, major implementations like Mastodon don't properly display this content. If they did, we wouldn't need these workarounds.
The language filtering feature in Mastodon profiles that you mentioned is useful, but it only works well with separate posts. It's a trade-off between user experience (reading only preferred languages) and maintaining content relationship (keeping translations connected).
I'm thinking of implementing multiple approaches to give our users flexibility while we wait for better contentMap support across the fediverse. The ideal solution would be for more ActivityPub servers to properly implement the multilingual features already in the spec!
If you have a fediverse account, you can quote this note from your own instance. Search https://hackers.pub/ap/notes/01964208-04f9-7c7f-b904-0d4a54b019f5 on your instance and quote it. (Note that quoting is not supported in Mastodon.)