Skip to content
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

Merge upstream changes #10

Open
wants to merge 283 commits into
base: master
Choose a base branch
from
Open

Merge upstream changes #10

wants to merge 283 commits into from

Conversation

bbloomf
Copy link
Collaborator

@bbloomf bbloomf commented Oct 11, 2021

No description provided.

igneus added 30 commits July 12, 2020 17:35
against liturgie.cz and the calendar printed at the beginning of a local
breviary (2005 edition, volume 3)
Markdown doesn't support lettered lists, but we want the letters
preserved, so a little cheat is used
+ prevent item numbers in the Table of liturgical days from being
tinkered with by Markdown renderers, even at the price of losing the
list formatting

ci skip
Formatting footnotes as blocks of pre-formatted text may not be the best
idea semantically, but at least they are clearly separated from the
surrounding text

ci skip
it seems to be updated either never or unce upon a looong time
igneus and others added 30 commits June 23, 2022 19:11
to match the standard one used in the rest of data files
as falsely promised by the API documentation for a long time
example was originally in an older version of the document
but reports all up to the end of input

fix #16
+ use be_an instead of be_a wherever appropriate (pure code cosmetics,
no semantic difference)
This seems to be the most authoritative document defining the rule
concerning numbering of Ordinary time Sundays.
with instance of a different class
as it prevents the specs from running on Ruby < 2.5
and we're not ditching support of rubies down to 2.0 just for niceties
in the specs
ref #101
Place the code block so that the paragraph immediately preceding
(incipit of which is now used as example name) is the one containing the
actual technical details.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants