Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Require `utf8string` types to be null-terminated

Open
#308 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust

Research direction

Locate the parsing implementations for HandlerBox (hdlr), ItemInfoEntry (infe), and SchemeTypeBox (schm), then inspect how their utf8string fields are currently handled. Compare that behavior with the null-termination requirement in ISO/IEC 14496-12:2020 § 4.2.1; done means the listed fields, and any other affected utf8string fields found, enforce that requirement.

Written by the indexing model from the issue text.

Description

compliance

Per ISOBMFF (ISO/IEC 14496-12:2020) § 4.2.1, fields of type utf8string are

UTF-8 string as defined in IETF RFC 3629, null-terminated.

Currently this requirement is not enforced in the parsing of:

  • HandlerBox (hdlr)
  • ItemInfoEntry (infe)
  • SchemeTypeBox (schm)

and possibly others

Dominant language
Rust
Stars
448
Forks
72
Avg merge
20d 3h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/mp4parse-rust

All issues in mozilla/mp4parse-rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.