Add support for I18N #28
Open
Conversation
This file contains 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
* Set C# version to latest * Update Microsoft.Windows.Compatibility to 8.0.5 (to avoid security issues) * Include System.Net.Http * Temporarily disable DPI aware
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.
This PR implements I18N function using
.resxfiles and the native methods, and closes #8 and #27.Stringsresource item to translate strings in the source code (invisible in Designer view)Todos:
Simplify translation process (e.g. put all strings in a single resource file)seems like a bad idea...After this PR merged, translation to other languages can be done by:
<Form>.<Language Code>.resxfor corresponding forms. Such asUpdater.zh-CN.resxStrings.<Language Code>.resxfor strings not covered above.Resources.<Language Code>.resxunderProperties/directory for resource texts.