Skip to content
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

optipng: add changelog #50579

Merged
merged 1 commit into from
May 29, 2024
Merged

Conversation

RunningDroid
Copy link
Contributor

Testing the changes

  • I tested the changes in this PR: YES

xchangelog handles it fine, the file itself starts with non-printing characters* for some reason though:
2024-05-28T22:53:50,555115731-04:00

*: byte sequence is EF BB BF

@classabbyamp
Copy link
Member

classabbyamp commented May 29, 2024

that's a UTF8 byte-order mark https://en.wikipedia.org/wiki/Byte_order_mark

UTF-8 always has the same byte order, so its only use in UTF-8 is to signal at the start that the text stream is encoded in UTF-8, or that it was converted to UTF-8 from a stream that contained an optional BOM.

@classabbyamp classabbyamp merged commit f7d27ea into void-linux:master May 29, 2024
8 checks passed
@RunningDroid
Copy link
Contributor Author

Thanks, I had checked that page but stopped reading after it started talking about FE FF.

@RunningDroid RunningDroid deleted the optipng_changelog branch June 3, 2024 23:14
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.

None yet

2 participants