-
Notifications
You must be signed in to change notification settings - Fork 84
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
add @scope
to <language>
by factoring a new class from @scope
of att.handFeatures
#2631
base: dev
Are you sure you want to change the base?
Conversation
from att.impreciseScope to att.scope, per suggestion @martindholmes and agreement on TEI-CORRESP-SIG list.
…esp sig list discussion
@sydb After I merged in PR #2630 , I came back here to rerun the test on this PR. They failed again, but at first it was pretty simple: just needed to update specs + ST to reference att.scope instead of the original att.impreciseScope. I went through and just fixed that quickly, and after that we can build the Guidelines with this branch, but <bibl xml:id="bib4handnoteyi" xml:lang="en">
<author>Libelt, Karol</author>.
<title level="m" xml:lang="pl">Wykłady Humboldta na uniwersytecie Berlińskim: notaty prelekcyj tych po uczniu Jego Karolu Libelcie</title>,
<publisher xml:lang="de">Deutsches Textarchiv</publisher>,
<date>2024-04-02</date>.
<idno type="URN">urn:nbn:de:kobv:b4-30960-7</idno>,
<ptr target="https://www.deutschestextarchiv.de/book/download_xml/libelt_hs6623ii_1828"/>
<date type="accessed" when="2024-12-04"/>
</bibl> |
Of course...and I bet we can fix that by updating this branch from dev now... |
Huzzah! passes tests now... @sydb Think you this is ready for review? |
Basic idea was to address #2516 by removing the definition of
@scope
from att.handFeatures, modifying it slightly, and putting it into a new class "att.impreciseScope", then making both<language>
and att.handFeatures members of that new class.This was a BLOCKED draft PR because it would not build until #2630 had merged. (Or changes are made here to account for the lack of #2630. :-) #2630 has been merged, so this PR is good to go.