Skip to content

autobib: include "." after doi, to clearly separate from notes. - #573

Open
fare wants to merge 9 commits into
racket:masterfrom
fare-patches:doi-dot
Open

fare wants to merge 9 commits into
racket:masterfrom
fare-patches:doi-dot

Conversation

@fare

@fare fare commented Sep 13, 2026

Copy link
Copy Markdown
Contributor
  • autobib.rkt: include "." after doi, to clearly separate from notes.
  • autobib.tex: use \Needspace instead of \parbox, much improving support for long "note" fields.

This much improves the output for the heavily annotated bibliography of my book LtUO.

@fare

fare commented Sep 13, 2026

Copy link
Copy Markdown
Contributor Author

PS: I'm tempted to have a clanker improve the parsing of bibtex to support (a) emphasis, in notes, (b) {} in titles to prevent lowercasification when using LaTeX.

Also, maybe to improve autobib so multi-paragraph notes are a thing, and maybe crossing page boundaries within a bibliography entry.

These two would also much improve LtUO.

PPS: I'm still thinking about (a), but at least the basics of (b) was apparently done by #571.

@fare

fare commented Sep 14, 2026

Copy link
Copy Markdown
Contributor Author

Weird: the CI failed on Racket 9.3.0.8, but at home it just worked on v9.3.0.8-2026-09-14-06fd59e02c [cs].

PS: I had forgotten to update a test.

@mflatt

mflatt commented Sep 19, 2026

Copy link
Copy Markdown
Member

The change to add . after a DOI would cause papers written with Scribble+autobib to render differently than Latex+bibtex (in the "acmart" style). Would it work to add . only when there's a note? Or maybe it should be configurable?

@fare

fare commented Sep 19, 2026

Copy link
Copy Markdown
Contributor Author

Yes, adding a "." only if there's a note makes a lot sense, especially for backwards compatibility. Thanks for the suggestion.

PS: also rebasing to the latest master.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resyntax analyzed 1 file in this pull request and found no issues.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resyntax analyzed 1 file in this pull request and found no issues.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resyntax analyzed 1 file in this pull request and found no issues.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resyntax analyzed 1 file in this pull request and found no issues.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resyntax analyzed 1 file in this pull request and found no issues.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resyntax analyzed 1 file in this pull request and found no issues.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resyntax analyzed 2 files in this pull request and found no issues.

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.

2 participants