This repository has been archived by the owner on Dec 16, 2022. It is now read-only.
Attempt to enable translating via translate.wordpress.org #215
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
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
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.
We're currently not able to make use of translate.wordpress.org for translating the plugin. It reports:
I thought that the
Text Domainplugin meta could be empty since it is now assumed to be the slug, I thought, but I added it in 421da21 to try to fix the issue on translate.wordpress.org. However, that didn't fix it in 0.7.0. I also thought thatDomain Pathwas optional, but maybe it isn't.Anyone have any specifics for what is missing?