Implemented flags to accept invalid or reserved chunk names #209
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 4 commits
September 16, 2025 14:15
ReallyNiceGuy
force-pushed
the
enable_invalid_chunk_ids
branch
from
5ec6b11 to
9bf24a1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Chunk names can only contain the characters A-Z and a-z, and the 3rd character can never be lower case, as this marks the chunk as reserved for further use in the PNG standard.
But there are some non-compliant files that need to be read, and sometimes, written, which break these rules.
Let's implement flags on the encoder and decoder settings to ignore these checks, but they are enabled by default.