Define a tested BibLaTeX structural compatibility profile#587
Draft
claell wants to merge 5 commits into
Draft
Conversation
* Retain source spelling while classifying block types case-insensitively. * Cover splitter behavior and parse-write round trips with regression tests.
* Preserve source spelling in the parser default. * Provide optional lowercase normalization as middleware.
* Retain citation-key spelling through the public round trip. * Preserve custom field-key casing without implicit normalization.
* Verify richer entry types, fields, dates, annotations, and extended names. * Preserve set, xdata, and custom data-model records without a dialect flag. * Validate the synthetic standard-profile fixture with Biber 2.21.
* Distinguish structural preservation from Biber data-model semantics. * List the separately tested BibLaTeX extensions. * Reserve data-model conversion for explicit, loss-reporting transformations.
This was referenced Jul 16, 2026
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
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.
Summary
@set,@xdata, richer entry types and fields, dates, UTF-8, annotations, extended names, and custom data-model names.Closes #586. Closes #105.
Dependency and commit structure
The first three commits are the exact entry-type case-preservation work already under review in PR #570. The BibLaTeX contract tests and boundary documentation are the final two commits. The branch runs against current
main; after #570 merges, it should be rebased so those prerequisite diffs disappear from this PR.The nested Biber-comment feature from #372 / PR #585 is intentionally not included or claimed by this branch.
Validation
pytest -p no:cacheprovider -W error tests/test_biblatex_contract.py: 4 passed.tests/test_entrypoint.py.--tool --validate-datamodelaccepted the exact synthetic fixture, completed data-model validation, and emitted no warnings.Review note
Most of this PR is an explicit compatibility contract rather than new schema interpretation. Maintainer review should confirm that the parser is intended to remain schema-agnostic and that preserving custom entry/field names without a dialect flag is the correct boundary.
AI assistance
This pull request was prepared with ChatGPT Codex using GPT-5.6 Sol with high reasoning effort. Codex assisted with standards review, fixture design, dependency separation, documentation, and validation. Automated validation is not a substitute for maintainer review.