-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate document to YAML with explicit chapter/paragraph/list numbering #8
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some downsides:
- We can't easily generate docx files anymore
- YAML format is a bit harder to read and write than the old Markdown files
We should re-enable CI (preferably using GH actions) before merging this.
paragraphs: | ||
- id: "1" | ||
content: | ||
- text: "\\textbf{Stowarzyszenie Krakowski Klub Chombo}, zwane dalej \\textbf{Stowarzyszeniem}, działa na podstawie ustawy Prawo o stowarzyszeniach (Dz. U. 1989 Nr 20 poz. 104 wraz z późniejszymi zmianami) oraz niniejszego Statutu." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm thinking, is it necessary to have distinction text
/list
? In YAML, these are already two distinct data structures, so maybe we can drop these tags and make the format less verbose?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, we can – I automatically went for a tagged union so that we add another cases but no other cases came up. xd ptal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tbh now that I'm looking at this, it's hard to spot lists in this 👀 At this point, I'm fine with either version.
|
@Iipin what's the current status of this? |
@m4tx ready for rereview, PTAL |
diffPDF
found no differences between the new document and the old one.Nice potential follow-ups:
\subsection
s), it'd be nice if we could express them in a better way,Adjust the workflows,Get rid of the pandoc,