Translatability of several plugins #377
Merged
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
Plugins using `PLUGIN_SET_TRANSLATABLE_INFO()` don't need to call `main_locale_init()`.
frlan
added a commit
that referenced
this pull request
Mar 1, 2016
Translatability of several plugins
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.
Fix "translatability" of several plugins, either overall (GeanyCTags, DevHelp, GeanyMacro, Overview), only the infos, and remove redundant localization init in some plugins.
Symptoms are that translation might not work in certain cases i.e. if the plugin is loaded first (or alone), or only one from GP installed.
GeanyPy also suffers from the non-translatability, but it doesn't have
LOCALEDIRandGETTEXT_PACKAGEproperly set from it's build system so it's not as straightforward to fix. @codebrainz