Publish the package and its documentation, and move to the papers organization
Add the Zensical documentation of the Python package (docs/package, built by the docs workflow), merge the standard publish workflow with the setuptools-scm tag check, add the SPDX header rule to ruff, restructure the README, and point every repository and registry address at the Gitea organization papers. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B8cL4zN4XpaQF5cBtASzfq
This commit is contained in:
37 files changed
+1005
-83
No files matched your search
+1
-1
@@ -3,7 +3,7 @@
|
||||
This page answers questions about paperspec, a set of file formats that give every sentence and table cell of a scientific paper a permanent address.
|
||||
Newcomers, implementers of a reader, writer, converter or checker, and experts who know JATS (Journal Article Tag Suite), TEI (Text Encoding Initiative) or W3C Web Annotations can all use it.
|
||||
Each answer gives the plain statement first, then the precise one, then the chapter that defines it.
|
||||
The repository is <https://git.scient.ing/infra/paperspec>, and the formats are at version 0.1.0.
|
||||
The repository is <https://git.scient.ing/papers/paperspec>, and the formats are at version 0.1.0.
|
||||
|
||||
## Can I read these files without special software?
|
||||
|
||||
|
||||
Reference in new issue
Block a user