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

Restarting stanza numbering after a pagelike partition #335

Open
danbalogh opened this issue Nov 4, 2024 · 1 comment
Open

Restarting stanza numbering after a pagelike partition #335

danbalogh opened this issue Nov 4, 2024 · 1 comment
Assignees

Comments

@danbalogh
Copy link
Collaborator

I notice that our EGD (§2.3.3 in the gdoc) permits encoders to restart the numbering of stanzas after a pagelike partition "in order to follow the numbering scheme of a previous edition or the conventions of your specific field". I would prefer to forbid this (allowing the restarting of stanza numbering only for boxlike partitions), and I think at present the schema also enforces this, so I believe there aren't many (or any) already encoded files that restart stanza numbers after a pagelike partition.
@michaelnmmeyer , am I right to assume that allowing stanza numbering to reset after a pagelike partition would seriously interfere with the referencing scheme in #307 and require schema modifications?
@arlogriffiths , I think this option was included in the original guide at your insistence. Do you feel it is necessary, or can I edit it out of the EGD?

If the option to restart stanza numbering in such cases is really important, then one way to go ahead may be to prescribe complex stanza numbers for such cases, analogously to the system of complex line numbers. But I would rather avoid that.

@manufrancis
Copy link
Collaborator

I concur with Daniel and would avoid the restart of the numbering of stanzas after a pagelike partition

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

No branches or pull requests

4 participants