[Localization] Switch diagnostics/localization to .strings format
#60707
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
Format is as follows: - Comment: /* ... */ - Diagnostic: "<id>" = "<translation>";
|
@swift-ci please clean test |
hborla
approved these changes
Aug 22, 2022
|
Please test with following pull request: @swift-ci please test |
|
Please test with following pull request: @swift-ci please test macOS platform |
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.
.stringsformat is just a pair of aidand a correspondingmessageso it's easier to work with forboth translators and tools.
The format is as follows:
/* ... */"<diagnostic-id>" = "<diagnostic-message>";YAMLproducer and conversion tool are removed in the last commit as a unit to make it easierto re-instate them in the future if need arises.