[PR #1268] [FIX] Disable BOM in non-Windows build #2054

New Issue

claunia · 2026-01-29T17:20:03Z

claunia commented

2026-01-29 17:20:03 +00:00

Original Pull Request: https://github.com/CCExtractor/ccextractor/pull/1268

State: closed
Merged: Yes

I have read and understood the contributors guide.
I have checked that another pull request for this purpose does not exist.
I have considered, and confirmed that this submission will be valuable to others.
I accept that this submission may not be used, and the pull request closed at the will of the maintainer.
I give this submission freely, and claim no ownership to its content.
I have mentioned this change in the changelog.

My familiarity with the project is as follows (check one):

I have never used CCExtractor.
I have used CCExtractor just a couple of times.
I absolutely love CCExtractor, but have not contributed previously.
I am an active contributor to CCExtractor.

about bom In the ccextractor help :


                 -bom: Append a BOM (Byte Order Mark) to output files.
                       Note that most text processing tools in linux will not
                       like BOM.
                       This is the default in Windows builds.
                       -nobom: Do not append a BOM (Byte Order Mark) to output
                       files. Note that this may break files when using
                       Windows. This is the default in non-Windows builds.

Currently, bom is also enabled in non-Windows builds. This PR fixes this issue.

**Original Pull Request:** https://github.com/CCExtractor/ccextractor/pull/1268 **State:** closed **Merged:** Yes --- - [X] I have read and understood the [contributors guide](https://github.com/CCExtractor/ccextractor/blob/master/.github/CONTRIBUTING.md). - [X] I have checked that another pull request for this purpose does not exist. - [X] I have considered, and confirmed that this submission will be valuable to others. - [X] I accept that this submission may not be used, and the pull request closed at the will of the maintainer. - [X] I give this submission freely, and claim no ownership to its content. - [X] **I have mentioned this change in the [changelog](https://github.com/CCExtractor/ccextractor/blob/master/docs/CHANGES.TXT).** **My familiarity with the project is as follows (check one):** - [ ] I have never used CCExtractor. - [X] I have used CCExtractor just a couple of times. - [ ] I absolutely love CCExtractor, but have not contributed previously. - [ ] I am an active contributor to CCExtractor. --- about bom In the ccextractor help : ``` -bom: Append a BOM (Byte Order Mark) to output files. Note that most text processing tools in linux will not like BOM. This is the default in Windows builds. -nobom: Do not append a BOM (Byte Order Mark) to output files. Note that this may break files when using Windows. This is the default in non-Windows builds. ``` Currently, bom is also enabled in non-Windows builds. This PR fixes this issue.

claunia added the pull-request label 2026-01-29 17:20:03 +00:00

claunia closed this issue

2026-01-29 17:20:03 +00:00

claunia referenced this issue

2026-01-29 17:24:19 +00:00

[PR #2057] [MERGED] fix: prevent heap overflow in parse_PAT/parse_PMT and null deref in processmp4 #2864

claunia referenced this issue

2026-01-29 17:24:20 +00:00

[PR #2057] fix: prevent heap overflow in parse_PAT/parse_PMT and null deref in processmp4 #2868

Sign in to join this conversation.