Skip to content

Mention IsomorphicString and update ByteString guidance appropriately #151

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.

Sign up for GitHub

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

Jump to bottom
Open
aphillips opened this issue Feb 14, 2025 · 0 comments · May be fixed by #158
Open

Mention IsomorphicString and update ByteString guidance appropriately #151

aphillips opened this issue Feb 14, 2025 · 0 comments · May be fixed by #158
Assignees
@aphillips
Labels
Agenda+ Best Practice bug

Comments

@aphillips
Copy link
Contributor

In w3ctag/design-principles#454 there is a discussion with @annevk about the current guidance related to ByteString. We should update our guidance to be clearer and more thorough about the usage of byte-array/byte-string types in protocols and point to isomorphic string handling explicitly. See his/my comments of 2025-02-13/14
@aphillips aphillips self-assigned this Feb 14, 2025
@aphillips aphillips mentioned this issue Apr 9, 2025
Open
aphillips added a commit to aphillips/bp-i18n-specdev that referenced this issue Apr 18, 2025
@aphillips
Address isomorphic string and ByteString guidance
4fb6dbb 
Fixes w3c#151

Adds a new subsection about byte-oriented formats.
Adds guidance about ByteString and isomorphic strings.
Moves the guidance about not defining legancy encoding to the encoding
section.
@aphillips aphillips linked a pull request Apr 18, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aphillips aphillips

Labels
Agenda+ Best Practice bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Address isomorphic string and ByteString guidance aphillips/bp-i18n-specdev
1 participant
@aphillips