Schema: allow prelude/interlude/postlude to contain BlockStatement
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- xml
- Domain
- documentation
Research direction
The issue names the RELAX NG definitions of Prelude, Interlude and Postlude, which currently use BlockText+. Find those definitions in the schema source and check where BlockStatement is defined and used elsewhere in the grammar. Before changing anything, confirm with a maintainer that allowing statements here is wanted, since the thread has no replies. Done means the schema accepts a statement inside each of the three elements and existing sample documents still validate.
Written by the indexing model from the issue text.
Description
Current schema is
Prelude =
element prelude {BlockText+}
Interlude =
element interlude {BlockText+}
Postlude =
element postlude {BlockText+}
but would be nice if those BlockText+ were changed to BlockStatement+.
- Dominant language
- XSLT
- Stars
- 466
- Forks
- 251
- Avg merge
- 4m
- Merged PRs (30d)
- 13
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PreTeXtBook/pretext
-
The print preview leaves writing space short by the margins of hidden headers, footers and solutionsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PreTeXtBook/pretext#3329 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
PreTeXtBook/pretext#3305 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PreTeXtBook/pretext#3297 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
PreTeXtBook/pretext#3285 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PreTeXtBook/pretext#3283 ·
Maintainers usually reply within 1 day
All issues in PreTeXtBook/pretext
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 75/100
cran-task-views/Spatial#130 ·
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw-windows-node#2287 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
daniel-ospina/tortoise#13343 ·
Maintainers usually reply within 1 day
-
[Docs]: Clarify theme variables location and usage in CONTRIBUTING.mdPossibly taken @srishtimishra520-beep claimed this today. Openkind/docs
Difficulty 1/5 Under an hour Newbie friendliness 88/100
meshery/meshery.io#3220 · 1 comment ·
Maintainers usually reply within 1 day
-
current task
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Sunday-School-Software/Sunday-School-Scheduler#87 ·
Maintainers usually reply within 1 day