I noticed that when my local Mastodon instance updated to v4, translations no longer worked.
It looks like they added class="notranslate" to the root of the app and then added class="… translate" to individual toots. We support the former (to match Google) but not the latter (I didn't know that even worked?)
So this is a feature request to implement the latter where we do dig down into notranslate elements, searching for translate elements and only submit those. I think it needs a bit of a refactor of how we filter nodes because this concept of including a subtree of an excluded tree is not really possible right now.
I noticed that when my local Mastodon instance updated to v4, translations no longer worked.
It looks like they added
class="notranslate"to the root of the app and then addedclass="… translate"to individual toots. We support the former (to match Google) but not the latter (I didn't know that even worked?)So this is a feature request to implement the latter where we do dig down into notranslate elements, searching for translate elements and only submit those. I think it needs a bit of a refactor of how we filter nodes because this concept of including a subtree of an excluded tree is not really possible right now.