Advice on lang files and i18n

[wohaopa]

I think when you write a mod like this you have to jump through files and write description string and you have to think about keys and things like that. Can we use a preprocessor to do it directly.
For example: use a special comment construct to write the description string directly where it is needed instead of key as we are using now.

// #tr demo.key
// #en_US Demo
// #zh_CN 演示
// # more language
anything code

Just like the addition in this PR

[eigenraven]

I think having all languages in code is a bad idea, if you support say ~10 languages this will make code almost unreadable. However having an annotation processor or similar to update translation keys in resources as new keys are detected seems useful, an AP could even have a list of minecraft methods that take in translation keys and also support defining custom ones via annotations for convenience, so you wouldn't need special tags in comments at all.

[wohaopa]

I think having all languages in code is a bad idea, if you support say ~10 languages this will make code almost unreadable. However having an annotation processor or similar to update translation keys in resources as new keys are detected seems useful, an AP could even have a list of minecraft methods that take in translation keys and also support defining custom ones via annotations for convenience, so you wouldn't need special tags in comments at all.

You misunderstood me. I mean, it can make it easy for coders to write one or two languages they are familiar with, just like GT's language system. The new key does not need to be manually written back to the language file, it will be automatically sorted out and written back.

[wohaopa]

Compared with AP, it does not need to introduce new annotations and import new classes.