Skip to content

Standardize paragraph about ASCII, SBCS, and MBCS #5537

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Rageking8
Copy link
Contributor

Standardize the 2 slightly differing paragraphs about ASCII, SBCS, and MBCS. The motivation was the phrasing in docs/c-runtime-library/single-byte-and-multibyte-character-sets.md:

... Japanese Kanji, include many more characters than can be represented in a single-byte coding scheme, and so ...

Although technically correct, the "than can" is prone to being misread as "that can" (I fell for it...), which in this case flips the meaning.

Copy link
Contributor

@Rageking8 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit df6a32b:

✅ Validation status: passed

File Status Preview URL Details
docs/c-runtime-library/single-byte-and-multibyte-character-sets.md ✅Succeeded
docs/text/text-and-strings-in-visual-cpp.md ✅Succeeded

For more details, please refer to the build report.

@ttorble
Copy link
Contributor

ttorble commented Jul 14, 2025

@TylerMSFT

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged Tracking label for the PR review team label Jul 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants