Skip to content

palimpsest:0.1.0 - #5751

Open
eusebe wants to merge 2 commits into
typst:mainfrom
eusebe:submit-palimpsest-0.1.0
Open

palimpsest:0.1.0#5751
eusebe wants to merge 2 commits into
typst:mainfrom
eusebe:submit-palimpsest-0.1.0

Conversation

@eusebe

@eusebe eusebe commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

I am submitting

  • a new package
  • an update for a package

Description: Palimpsest turns one annotated manuscript into everything a peer-review response needs: the clean manuscript, a tracked-changes version showing every edit, and a response letter that cites the manuscript's own real page and figure numbers.

I have read and followed the submission guidelines and, in particular, I

  • selected a name that isn't the most obvious or canonical name for what the package does
    • Explanation: A palimpsest is a manuscript page that was scraped clean and reused, where traces of the erased, earlier writing remain faintly visible beneath the new text. The name is a metaphor for what the package does (showing a manuscript's revision history still legible underneath its accepted, final text) rather than a literal, descriptive term like "review-tracker" or "manuscript-diff" would be.
  • added a typst.toml file with all required keys
  • added a README.md with documentation for my package
  • have chosen a license and added a LICENSE file or linked one in my README.md
  • tested my package locally on my system and it worked
  • excluded PDFs or README images, if any, but not the LICENSE

@eusebe
eusebe deployed to Package Check September 3, 2026 11:49 — with GitHub Actions Active
@typst-package-check typst-package-check Bot changed the title Add palimpsest 0.1.0 palimpsest:0.1.0 Sep 3, 2026
@typst-package-check typst-package-check Bot added the new A new package submission. label Sep 3, 2026
…nippet, outdated charged-ieee pin

- "academic" isn't a real category; switched to "office"/"utility".
- README's placeholder `authors: (...)` isn't valid Typst, breaking
  the package checker's parse of the fenced code block; now `("...",)`.
- charged-ieee bumped 0.1.3 -> 0.1.4 (current), no API change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new A new package submission.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants