This repository was archived by the owner on Dec 16, 2022. It is now read-only.
[WIP] Re-use default text domain for strings that are common with core #364
Conversation
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
westonruter
force-pushed
the
reuse-default-translation-strings
branch
from
382c17d to
e8892e9
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
See https://wordpress.org/support/topic/use-wordpress-native-translation/
I did the first ~10 strings that are in common.
For a list of all the common strings and where I left off, see https://gist.github.com/westonruter/08ca016d4e2ada375dc2f26895d9f243#file-common-strings-txt-L10
Some of the strings in Customize Posts should be modified to align with what is in core. For example in this PR, I modified Customize Posts to use
(no title)instead of(No title)in one case.