Add XML Translation Api#91
Open
HayashiUme wants to merge 1 commit into
Open
Conversation
Author
|
To improve code cleanliness, I force push to the Pr |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add Translation API
This PR adds a complete multi-language translation system to MiraAPI, allowing mods to register translation files and
use
.Translate()extension method anywhere.Translation Flow
<string name="teleporter.name">传送者</string>public string RoleName => "teleporter.name";"Example Bool") doesn't match anystructured key, the system searches English dictionary values and maps back to the structured key for translation
Translation Files
Resources/Translations/English.xmlandSChinese.xmlfor both MiraAPI and MiraAPI.ExampleApplication.persistentDataPath/mira_languages/{ModGuid}/on startup, overwritten each updateRegistration API
Tip
TranslationManager.Register() must be called in the plugin constructor rather than Load(), because attribute option constructors fire during the PluginLoad event before the mod's own Load() completes, causing .Translate() to miss the mod's own translations.