The current i18n system works but could be updated/improved. Some thoughts:
- Paper is rigorously deprecating all string-based messaging/formatting. Sooner or later, we have to switch to Adventure chat.
- Adventure's MiniMessage serialization format may be a good candidate for i18n, as it allows for simple formatting in configs and is extendable.
- There is some translation/i18n support in Paper/Adventure. We may be able to integrate with that. https://docs.papermc.io/paper/dev/component-api/i18n
- Current translation quality varies widely, and we don't support many common languages. AI translations can give a very good baseline nowadays - in conjunction with community-driven https://crowdin.com/.
The current i18n system works but could be updated/improved. Some thoughts: