What if Nostr apps would have an open source resource library for all app strings?

Nostr would be instantly available on most if not all languages.

No need to do duplicate work for each new client and app.

Unified terminology in translations would help in adaption.

New strings would need to be translated only once.

There are open source translation tools like Weblate etc. but where are the libraries?

After all, mute is still mute, open is still open etc. The basic app strings are always the same 😁

Reply to this note

Please Login to reply.

Discussion

Well languages are sometimes really complicated. Sometimes "cancel" fits in a given action, but in other languages the word stop or interrupt might be the better choice. Grammar has alot of rules...

But a open approach to translation services using nostr to provide translation packets is really interesting in my opinion. Ive been thinking about it too. Lets tag it: #nostrdesign

It doesn’t need to be one option only for source files.

Could be multiple alternatives to choose from in the original word based on the use case. That’s the dev’s choice or they could request a new string (translation).

Translations reflect that then based on the meta-description.

E.g. mute (as in silence) might be for a mic action, hide (as in don’t show) for user account or note etc.

Ah okay. Who stores it btw? Ive this app called translator (fdroid), if we fork it and include internet connectivity we might connect and upload translation samples sorted on different categories.

I guess it could be a git repo?

neat idea

What if I don’t want to name my posts notes? /hides

Just use your customestring then or make an alt.name string for the resource pool.