WP59: Contextualize "Export" string to differentiate it from other occurrences in WP Core #37660
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.
Description
This change aims to differentiate the Site export menuitem from other occurrences of the string in WP Core, because in Core it's not used in the same context. So it several languages, having the same string for both occurrences may lead to inappropriate translations.
See this report from zh_TW locale: https://wordpress.org/support/topic/wordpress-5-9-beta-4-i18n-issue-string-export/
The same goes at least for fr_FR.
Types of changes
Bug fix (non-breaking change which fixes an issue)
Checklist:
*.native.js
files for terms that need renaming or removal).