Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

1751 Clarify BOM handling #1765

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

1751 Clarify BOM handling #1765

wants to merge 1 commit into from

Conversation

michaelhkay
Copy link
Contributor

Fix #1751

Clarifies BOM handling (and byte order generally) in bin:encode-string and bin:decode-string.

Also adds a note to bin:octal for the prevention of possible misunderstanding.

@michaelhkay michaelhkay added Enhancement A change or improvement to an existing feature Tests Needed Tests need to be written or merged EXPath An issue related to the EXPath extension functions labels Feb 5, 2025
@ndw ndw self-requested a review February 5, 2025 12:08
@ndw ndw added the Propose Merge without Discussion Change is editorial or minor label Feb 5, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Reviewers

@ndw ndw ndw approved these changes

Assignees
No one assigned
Labels
Enhancement A change or improvement to an existing feature EXPath An issue related to the EXPath extension functions Propose Merge without Discussion Change is editorial or minor Tests Needed Tests need to be written or merged
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

bin:encode-string - should the result have a BOM?
2 participants
@michaelhkay @ndw