Skip to content

Fix link to IETF BCP 47 standard - #358

Closed
Christian Gambale (AkitoTheGambler) wants to merge 1 commit into
MicrosoftDocs:mainfrom
AkitoTheGambler:patch-1
Closed

Christian Gambale (AkitoTheGambler) wants to merge 1 commit into
MicrosoftDocs:mainfrom
AkitoTheGambler:patch-1

Conversation

@AkitoTheGambler

Copy link
Copy Markdown

Updated the link to IETF BCP 47 for accuracy.

Updated the link to IETF BCP 47 for accuracy.
Copilot AI lite review requested due to automatic review settings September 10, 2026 09:00
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit a251753:

💡 Validation status: suggestions

File Status Preview URL Details
globalization/locale/standard-locale-names.md 💡Suggestion View Details

globalization/locale/standard-locale-names.md

  • Line 5, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'v-mikau' is not a valid Microsoft alias.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The updated link should follow the repo’s established RFC/BCP linking convention (RFC Editor canonical URLs) for consistency and long-term stability.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR updates the documentation reference for the IETF BCP 47 standard in the locale naming guidance.

Changes:

  • Updates the BCP 47 hyperlink target in the “Standard locale names” documentation.
File summaries
File Description
globalization/locale/standard-locale-names.md Adjusts the BCP 47 reference link in the introductory description.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

# Standard locale names

[IETF BCP 47](https://www.ietf.org/rfc/bcp/bcp47.txt) is the standard that defines the most-commonly used format for specifying a locale. This format is used by Windows and many other environments, including C#, Java, Javascript, ICU, HTML <lang>, etc.
[IETF BCP 47](https://tools.ietf.org/html/bcp47) is the standard that defines the most-commonly used format for specifying a locale. This format is used by Windows and many other environments, including C#, Java, Javascript, ICU, HTML <lang>, etc.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Christian Gambale (@AkitoTheGambler) - Thanks for catching the broken link. I created #359 to use a slightly different link, and applied the change to additional files.
I'll close this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants