-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: Localized item display names #11
Comments
Hi, this library is great!, but I have some questions about it:
|
As a developer, I understand that we always want a slim jar instead of fat one and want to reduce the extra stuff that a server admin has to install on their servers as much as possible. Making something optional really optional is always the best decision :) I think there are basically two cases for this feature:
My recommedation would be: If the server admin has put the LanguageUtil jar into their plugin folder, then TownyResources will use LanguageUtils to get the display names of materials. Otherwise, TownyResources will just directly get the display names. If this feature were implemented this way, then those who want this feature could simply install LanguageUtils and those who don't could simlpy use the TownyResource the way as before. |
Ok I think I get it, thanks for the info!. We'll go with your recommendation, makes sense! |
Hi there!
I'm here again to come up with a suggestion ;)
As the title. Currently the resource information on the town/nation's screen is only in English:
I am not a native speaker and unfortunately not all players in my server can read the English names of all materials.
So the localized resource display names would really help those players :D
I am also a plugin developer and fortunately the easiest solution is to use a plugin called "LanguageUtils" to do the translation automatically. Here is the repo: https://github.com/NyaaCat/LanguageUtils and here is the usage example: https://github.com/MascusJeoraly/LangUtilsExample
The text was updated successfully, but these errors were encountered: