cjk-unshrink:0.1.0

[neruthes]

I am submitting

• a new package
• an update for a package

Description: Unshrink full-width punctuation marks. A workaround for typst#7643.

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
• 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

[saecki]

Thanks for this package!

[saecki]

People don't generally read the source code of a package, and it's not that straight forward to access. It would make sense to include the content of demo_doc as an example file that you link in the readme.

[neruthes]

Added a dedicated demo.pdf in git-tracked directory and the GitHub file URL in README. Is this the best practice?

[saecki]

I wouldn't include PDF examples, since they can't be viewed directly without downloading them. I was thinking more of a demo.typ file that you link in the readme, and maybe some images so people can directly see what this package does in the readme.
There are two options:

1. You include the documentation files in this PR, link to them locally, e.g. [demo.typ](docs/demo.typ), and add them to the exclude list in the typst.toml manifest. See: https://github.com/typst/packages/blob/main/docs/tips.md#what-to-commit-what-to-exclude
2. You add a link to a file in your own repository. Make sure to either create a perma-link or link to a specific tag/branch, to ensure the linked files always match the correct package version.

[neruthes]

I added PDF in my repo with a permalink and removed it from the PR. Is that good?