đź’ˇ Feedback
Open
Multi-Language Object
Currently, if I want to research something I mostly use English so my notes are written in English, but when I want to translate the notes (to share them with others or publish them) I would need to duplicate them and manage the properties values and future edits of both notes manually.
Which made me think, why not have the option to add a translation inside the object itself (which means properties and their value could be translated too).
This feature might strengthen the experience of users who speak more than two languages, the RTL feature (if planned), and the publish to web feature (if planned).
1 Comment
Sign in to comment

That´s an interesting one!
Also interesting use case.
I was thinking the same thing for quite some time, if for different reasons: my work (and knowledge) contexts constantly switch between different languages. And I think this is quite a common/trivial condition in the new, post-global world.
So, some way of accommodating for multi-language use (bi-/trilingual situations) would really help in practical terms and many RL contexts. đź«°
– Not sure this can only/solely be tackled by Multi-Language Object. But could as well be a 2nd-language layer to all objects, or – given new circumstances and affordances – be built/molded into Capacities via some AI-(sub-)functions… 🤔