Skip to content

Patch 3#352

Open
Ashtontameirao wants to merge 4 commits into
MicrosoftDocs:mainfrom
Ashtontameirao:patch-3
Open

Patch 3#352
Ashtontameirao wants to merge 4 commits into
MicrosoftDocs:mainfrom
Ashtontameirao:patch-3

Conversation

@Ashtontameirao

Copy link
Copy Markdown
Contributor

Updated Future Support for Microsoft.

Added new scripts marked with asterisks indicating future support and updated font details for various languages.
Expanded the section on future Windows versions to include goals for font coverage and added details about new scripts and associated fonts.
Updated the date for script and font support documentation and clarified the description for Sharada support.
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit a85cd44:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
❌Error Details

  • [Error: CannotMergeCommit] Cannot merge commit a85cd44ecb7d4fbe59a4188835dad98d3f180710 in branch patch-3 of repository https://github.com/Ashtontameirao/globalization into branch main (commit 5c595863c2d925b4c416129e43d668880c2c292b). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

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

Learn Build status updates of commit b9d7a43:

✅ Validation status: passed

File Status Preview URL Details
globalization/fonts-layout/font-support.md ✅Succeeded View

For more details, please refer to the build report.

@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.

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.

1 participant