Fix translations for the main project#48
Merged
jjw24 merged 1 commit intoFlow-Launcher:devfrom May 14, 2020
Merged
Conversation
fixes translation of UI fields that are not plugin-specific
jjw24
approved these changes
May 14, 2020
Member
|
Good pick up, thank you |
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
2 participants
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.
The translation files from
Flow.Launcher/Languagesare currently not included in the build output and are therefore not available at runtime.Changing the language from settings only affects the plugin-specific fields in the
Plugintab, because the plugin projects are copying their language files correctly.