[UI/UX] (keyboard shortcuts) Correct localization guidance #5514
Conversation
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 2647470: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
This PR updates the keyboard shortcuts localization documentation to clarify that the localization JSON file only provides alternative keyboard shortcuts and strings for one additional locale, rather than supporting multiple locales.
Key changes:
- Updated guidance text to reflect single additional locale support instead of multiple locales
- Modified JSON examples to show a single locale configuration
- Clarified the relationship between the shortcuts JSON file and localization resource file
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "value": "Afficher le volet de tâche pour add-in" | ||
| } | ||
| "resources":{ | ||
| "default": { |
There was a problem hiding this comment.
The localization resource file example shows "default" as the locale property, but the text in line 341 states it should configure "alternative keyboard shortcuts for one additional locale" with an "ll-cc" property (like "es-es"). The property should be "es-es" instead of "default" to match the guidance and show an actual locale-specific configuration.
| "default": { | |
| "es-es": { |
|
Learn Build status updates of commit 2e8a60e: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
The localization JSON file only provides alternative keyboard shortcuts and strings for one additional locale.