@hongminhee洪 民憙 (Hong Minhee)

>most server implementations (Mastodon, Misskey, etc.) don't properly handle this content as of April 2025

How multilingual content should be handled, in your opinion? Specification doesn't provide any guidance on that matter.

>I'm considering several approaches:

I'd use (2) as primary representation and (3) as fallback.

(1) is fine too (FEP-e232 links could be used instead of inReplyTo, if top-level posts are preferable).

(4) should be avoided, because such content will be rendered as a long post with no clear boundaries between translations. I don't think <hr> is a good solution, and it's not widely supported (m).

@silverpill

How multilingual content should be handled, in your opinion? Specification doesn't provide any guidance on that matter.

It would be great if the existing implementations have language tabs for multilingual posts!

FEP-e232 links could be used instead of inReplyTo, if top-level posts are preferable

FEP-e232 sounds a good idea! I'm considering that approach too.

(4) should be avoided, because such content will be rendered as a long post with no clear boundaries between translations. I don't think <hr> is a good solution, and it's not widely supported (m).

I'm also considering using <details> as well. I'm not sure how many existing implementations support it though. 🤔

2

❤️

2 people reacted.

Product-1st Front-end Engineer, based in Singapore. Currently on a career break since July '22. Working on a Mastodon web client phanpy.social @phanpy

Why follow me: I have interests in , , , , , & . I usually post about my side projects, tech events, weird discoveries, and sometimes local news.

tfr

Developer of ActivityPub-based micro-blogging and content subscription platform Mitra. Working on Fediverse standards: https://codeberg.org/silverpill/feps