Are your translations in standard .po files? A good model for this would be how the #Drupal open source project does it.
Check out https://localize.drupal.org
Not a direct comparison because different apps, but you’re right, everybody could benefit.
The translations in damus are a great resource, maybe we could put them in some format that everyone on nostr could use nostr:npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf ?
Discussion
Damus is using Apple’s recently deprecated locale-specific .strings and .stringsdict file formats. I have a PR open that converts Nos.social from .strings to Apple’s new multilingual .xcstrings file format (effectively JSON) which was possible because Crowdin supports that format, but I haven’t done it for Damus yet because Transifex doesn’t support it yet. In any case, if this were to be done, some platform agnostic format should be used.
Im fine if we just convert any of these formats to csv or json. I want something simple that I can load into notedeck/android
Let me think about how to do this. Translations are no longer simple once you start dealing with plural rules. You’re using Rust, right? Is there a good Rust localization library?
.po files support plural.
https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html