[WiP] BibTeX emulation #1955
Open
[WiP] BibTeX emulation #1955
Conversation
This file contains 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
…ve unneded sort attribut
…thanks to Tom Wiesing
|
It's great to see some progress on this PR after several years, and this looks great in principle. |
|
Exciting PR! We mentioned in the call today that this PR may be a very good occasion for adding a test exercising |
…y objects more self contained and to parse and store the object
…acros; other simplifications
…os can be substituted; thus Bibliography objects work with pure strings and BibString can be eliminated
…ng to preserve sources
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is an alternative refactoring of @tkw1536 's rather brilliant proposal in #1231 for emulating BibTeX within LaTeXML. It is much reorganized and (hopefully) simplified, and more integrated into LaTeXML's system of utilities, error handling, organization and coding style.
I've undoubtedly broken a few features that had been working, so more testing and development is needed (and probably add a few test cases) for completion, error recovery, corner cases. There are also a couple of areas I'd still like to refactor (Runtime). And preservation of semantics for tei/jats.