Closed yhr0x43 closed 3 years ago
Yes, I have test this in the dev environment, can confirm all texts works so far. For translateTextForPlayer, there could be something like a sendMessage util function that combines translation and sending which takes one ServerPlayerEntity as argument, but I think just use what I have here is totally acceptable.
I just see that the tps command can benefit from using the translated support of Text builder. I will see what I can do with that.
tps localization finished. All current messages are tested working in the development environment. This is ready for review.
Both U.S. English and Chinese work when tested on a release fabric server. But for any other language it just sends the translation key out, is that intended? I have attached the result of running /tps with my client language set to en_us, zh_cn, en_gb
But for any other language it just sends the translation key out, is that intended? It's supposed to default back to en_US, looks like that's a bug I'll have to fix in the framework.
Other than that it looks good to me, maybe @ItsIlya can review it as well.
Referring to #92, translations support.