You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current postprocessing XSLT functions well to migrate "orphaned" solitary <rdg> elements to the next following <app> element, and to migrate orphaned deleted passages aligned against empty (markup-only) rdgs, also to the next following <app>. We have a few more improvements we can process but handling it all in the same stylesheet causes difficulties with writing templates that don't collide / disrupt each other. So it will be better to do more pre-processing in a second stage XSLT. In this, we should try to handle:
Deletions (or longTokens) aligned only with other deletions (or longTokens)
Here's an example from C-13. It may be rare, but it seems like a predictable pattern. This is the first time I've seen a case where we should move a special passage to an immediately preceding app. It may sometimes happen with longToken passages or delstart....delend passages. Because Thomas AND fMS are involved in two separate <rdgGrp> elements, this problem wouldn't be picked up as a loner <rdgGrp>, and leaving it alone (as two deleted passages runs the risk of being invisible in the Variorum viewer unless moved.
<app>
<rdgGrpn="['']">
<rdgwit="fThomas"><pb xml:id="F1818_v1_163" n="151"/> </rdg>
<rdgwit="fMS"><sga-add eID="c56-0084__main__d5e18134"/> </rdg>
</rdgGrp>
<rdgGrpn="['and then']">
<rdgwit="f1831"><longToken>And then</longToken> </rdg>
</rdgGrp>
<rdgGrpn="['besides,']">
<rdgwit="f1818"><pb xml:id="F1818_v1_163" n="151"/>Besides, </rdg>
<rdgwit="f1823">Besides, </rdg>
</rdgGrp>
</app>
<app>
<rdgGrpn="['<delstart/>besides<delend/>', '<addedthomas-start/>and<addedthomas-end/>', ',']">
<rdgwit="fThomas"><del rend="strikethrough">Besides</del><add place="margin">And</add> , </rdg>
</rdgGrp>
<rdgGrpn="['–', '<delstart/>the com<delend/>', 'mon', 'people', 'would', 'believe', 'it', 'to', 'be', 'a', 'real', 'devil', 'and', 'who', 'could', 'attempt', 'besides']">
<rdgwit="fMS">– <del rend="strikethrough" xml:id="c56-0084__main__d5e18152">the com</del><lb n="c56-0085__main__1"/>mon people would believe it to <lb n="c56-0085__main__2"/>be a real devil and who could attempt <lb n="c56-0085__left_margin__1"/>Besides </rdg>
</rdgGrp>
</app>
Stranded deleted passages
where the contents of the deletion are mostly represented in the next following-sibling::app.
<app>
<rdgGrpn="['<delstart/>our father looks so sorrowful:', ' this dreadful event seems to have revived in his mind his grief on the death of mamma.', ' poor elizabeth also is quite inconsolable."<delend/>', '<addedthomas-start/>the sense of our misfortune is yet unalleviated; the silence of our father is uninterrupted, and there is something more distressing than tears in his unaltered sadness—while poor elizabeth, seeking solitude and for ever weeping, already begins to feel the effects of incessant grief—for her colour is gone, and her eyes are hollow and lustreless<addedthomas-end/>']">
<rdgwit="fThomas"><del rend="strikethrough">Our father looks so sorrowful: this dreadful event seems to have revived in his mind his grief on the death of Mamma. Poor Elizabeth also is quite inconsolable.”</del><add>the sense of our misfortune is yet unalleviated; the silence of our father is uninterrupted, and there is something more distressing than tears in his unaltered sadness—while poor Elizabeth, seeking solitude and for ever weeping, already begins to feel the effects of incessant grief—for her colour is gone, and her eyes are hollow &amp; lustreless</add> </rdg>
</rdgGrp>
<rdgGrpn="['our']">
<rdgwit="f1818">Our </rdg>
<rdgwit="f1823">Our </rdg>
<rdgwit="fMS"><sga-add eID="c56-0086__main__d5e18427"/><sga-add place="superlinear" sID="c56-0086__main__d5e18433"/>our </rdg>
</rdgGrp>
</app>
<app>
<rdgGrpn="['', 'father looks so sorrowful', 'and', 'it']">
<rdgwit="fMS"><sga-add eID="c56-0086__main__d5e18433"/><longToken>father looks so sorrowful</longToken> and it </rdg>
</rdgGrp>
<rdgGrpn="['father looks so sorrowful:', 'this', 'dreadful', 'event']">
<rdgwit="f1818"><longToken>father looks so sorrowful:</longToken> this dreadful event </rdg>
<rdgwit="f1823"><longToken>father looks so sorrowful:</longToken> this dreadful event </rdg>
</rdgGrp>
</app>
The text was updated successfully, but these errors were encountered:
The current postprocessing XSLT functions well to migrate "orphaned" solitary
<rdg>
elements to the next following<app>
element, and to migrate orphaned deleted passages aligned against empty (markup-only) rdgs, also to the next following<app>
. We have a few more improvements we can process but handling it all in the same stylesheet causes difficulties with writing templates that don't collide / disrupt each other. So it will be better to do more pre-processing in a second stage XSLT. In this, we should try to handle:Deletions (or longTokens) aligned only with other deletions (or longTokens)
Here's an example from C-13. It may be rare, but it seems like a predictable pattern. This is the first time I've seen a case where we should move a special passage to an immediately preceding app. It may sometimes happen with longToken passages or delstart....delend passages. Because Thomas AND fMS are involved in two separate
<rdgGrp>
elements, this problem wouldn't be picked up as a loner<rdgGrp>
, and leaving it alone (as two deleted passages runs the risk of being invisible in the Variorum viewer unless moved.where the contents of the deletion are mostly represented in the next
following-sibling::app
.The text was updated successfully, but these errors were encountered: