Skip to content

hadronic-rirekisho:0.1.0#5257

Open
yoshphys wants to merge 6 commits into
typst:mainfrom
yoshphys:add-hadronic-rirekisho
Open

hadronic-rirekisho:0.1.0#5257
yoshphys wants to merge 6 commits into
typst:mainfrom
yoshphys:add-hadronic-rirekisho

Conversation

@yoshphys

@yoshphys yoshphys commented Jul 5, 2026

Copy link
Copy Markdown

I am submitting

  • a new package

Description: A Typst template for the traditional Japanese rirekisho (履歴書) resume format — the standardized form used when applying for jobs in Japan. It provides ruled tables for personal info, education/work history, qualifications, motivation, and a signature section, plus era-aware (和暦/西暦) date formatting and a kintou (均等割付) helper for even letter-spacing, mirroring conventions used in real paper rirekisho forms.

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: "rirekisho" alone is the literal Japanese word for a resume/CV, which is too canonical under the naming rules. "hadronic" pairs it with a unique, non-descriptive term: the template composes several independent blocks (basic info, education/work history, qualifications, ...) into one document, echoing how a hadron is a composite particle built from quarks. The bundled example is also historical physicist Yukawa Hideki, who proposed the pion (a hadron) exchange theory.
  • added a typst.toml file with all required keys
  • added a README.md with documentation for my package
  • have chosen a license (MIT-0) and added a LICENSE file
  • tested my package locally on my system and it worked
  • excluded PDFs or README images, if any, but not the LICENSE
  • ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use

yoshphys added 4 commits July 5, 2026 15:55
A Typst template for the traditional Japanese rirekisho (履歴書) resume format.
"rirekisho" alone is the canonical/generic name for what the package
does, disallowed by the naming rules. Pairs it with a unique,
non-descriptive term instead.
@yoshphys yoshphys temporarily deployed to Package Check July 5, 2026 07:38 — with GitHub Actions Inactive
@typst-package-check typst-package-check Bot added the new A new package submission. label Jul 5, 2026
Rename public top-level bindings to kebab-case, tag the file-tree code
block in the README so it isn't parsed as Typst source, and point
`repository` at the renamed typst-hadronic-rirekisho repo.
@yoshphys yoshphys temporarily deployed to Package Check July 5, 2026 07:49 — with GitHub Actions Inactive
@elegaanz elegaanz self-assigned this Jul 6, 2026

## ファイル構成

```text

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This is not really relevant on Typst Universe, as users won't see the contents of the package. I would suggest to remove this section, or at least move it to the end of the README. It can also go in a CONTRIBUTORS.md file dedicated to contribution guidelines and tips, that will only exist in your own repository.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Linking to this file in your README would allow users to access a preview of what the package does easily. In the current situation, this file is quite hard to discover. Can you add that please?

Addresses PR review feedback: the file-tree listing isn't relevant to
Universe users, and the example output was hard to discover.
@yoshphys yoshphys temporarily deployed to Package Check July 6, 2026 17:39 — with GitHub Actions Inactive
@yoshphys

yoshphys commented Jul 6, 2026

Copy link
Copy Markdown
Author

Thanks for the review!

  • Moved the "ファイル構成" (file-tree) section to the bottom of the README, since it's internal repo structure that isn't relevant to Universe users.
  • Added a link to example/example.typ and example/example.pdf right after the usage instructions, so the example output is easy to find.

Pushed in 120949b.

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