#74 Add basic functionality for INTERNAL apparatus to XSLT

future
accepted
Tom Elliott
None
9(high)
2015-05-19
2014-06-26
BODARD Gabriel
No

If someone would be willing to create a basic template for generating a below-the-text apparatus division from common features such as reg/orig, sic/corr, app/rdg in the edition div. This should be (a) much simpler than the current $app-style="ddbdp" template in there, and (b) use an $app-style such as "internal" aut sim.

Any volunteers to work on this?

Discussion

  • BODARD Gabriel
    BODARD Gabriel
    2014-07-22

    A mini version of this now exists (only takes account of choice/reg/corr, not app/lem/reg or anything else interesting) with the parameter $apparatus-style='iospe'. Something better could (and should) be done, so this ticket remains open and seeking a volunteer...

     
  • Tom Elliott
    Tom Elliott
    2014-07-31

    I'm taking ownership of this ticket in order to organize an implementation sprint in october 2014.

     
  • Tom Elliott
    Tom Elliott
    2014-07-31

    • status: unread --> accepted
    • assigned_to: Tom Elliott
     
  • Tom Elliott
    Tom Elliott
    2014-10-16

    Now shooting for implementation sprint in November 2014.

     
  • Tom Elliott
    Tom Elliott
    2014-11-03

    • assigned_to: Tom Elliott --> Pietro Maria Liuzzo
     
  • Tom Elliott
    Tom Elliott
    2014-11-03

    Reassigned to Pietro for first pass at implementation, per agreement in sprint meeting 3 November 2014.

     
  • a version of the changes to address this issue according to the discussed architecture is under development and includes
    - break down in small templates of each case
    - a new value "defaultmax" for internal-app-style parameter
    - test cases of functionality for both changes according to leiden-style and changes according to apparatus parameter

     
    • status: accepted --> needs-feedback
     
  • Meeting for feedback and further development proposed for 20/1/15

     
  • BODARD Gabriel
    BODARD Gabriel
    2015-03-17

    • Priority: 5(medium) --> 9(high)
     
  • If you take this sample text randomly picked from IGCyr and modified to contain a several of the features we want to support in internal apparatus, and try to transform it with the example-xslt, the following results will be given.

      <div type="edition" xml:lang="grc" xml:space="preserve">
      <div type="textpart" subtype="column">              <ab>
                        <lb n="1" rend="left-to-right"/><w part="I">τ<corr>ι</corr>μο</w><gap reason="lost" unit="character" extent="unknown"/><!--Correction Without Specification-->
                        <lb n="2" rend="right-to-left"/><gap reason="lost" unit="character" extent="unknown"/><w part="F">εν</w> <g type="tripunct"></g> τοι <w lemma="πρόγονος">πρ<lb n="3" break="no" rend="left-to-right"/>ογονο<unclear>ι</unclear></w> <gap reason="lost" unit="character" extent="unknown"/><w>α<supplied reason="lost"></supplied>θ<supplied reason="lost">έν</supplied>τ<choice><corr>ο</corr><sic>α</sic></choice>υ</w> <!--Erroneous Substitution-->
                        <lb n="4" rend="right-to-left"/><choice>
     <reg>τιμὴν</reg>
     <orig>τειμην</orig>
    </choice><!--regularization--><gap reason="lost" unit="character" extent="unknown"/><w part="F">ι</w> <g type="tripunct"></g> τοι <persName type="attested"><name nymRef="Πρόκλος">Πρό<lb n="5" break="no" rend="left-to-right"/><choice>
     <unclear>Γ</unclear>
     <unclear>Ε</unclear>
     <unclear>Ζ</unclear>
     <unclear>Ξ</unclear>
     <unclear>Π</unclear>
     <unclear>Σ</unclear>
     <unclear>Τ</unclear>
    </choice><unclear>ϙ</unclear>λō</name></persName> <g type="dipunct">:</g> <w part="I">θυγ<supplied reason="lost">ατ</supplied></w><gap reason="lost" unit="character" extent="unknown"/><!--Ambiguous Characters With Alternatives Offered --></ab></div>
                   <div type="textpart" subtype="column"><ab>     <lb n="6"/>  <subst>
     <add place="inline">τέσσαρας</add>
     <del rend="corrected">τεσσαρες</del>
    </subst> <!--Ancient Corrections (Where Both Old And New Text Can Be Read)-->
    
    <lb n="7"/> public<add place="overstrike">a</add>e  <!--Ancient Corrections (Old Text Lost)-->
    <lb n="8"/> <add place="above">αβ</add> <!--Addition By Ancient Hand -->
    <lb n="9"/> <expan>πρ<hi rend="superscript">οσ</hi>
     <ex>γίνεται</ex>
    </expan>
    <!--Raised/Lowered Characters-->
    <lb n="10"/> <app type="editorial">
     <lem source="#BL_3.8"><supplied reason="lost">
       <expan>προγ<ex>εγραμμένη</ex>
       </expan>
      </supplied>
     </lem>
     <rdg><supplied reason="lost">ς <expan>
        <ex>ἐτῶν</ex>
       </expan> ιϛ</supplied>
     </rdg>
    </app> <!--editorial--> 
       <lb n="11"/> <app type="alternative">
     <lem>
      <expan>Λευκ<ex>ο</ex>γ<ex>ίου</ex>
      </expan>
     </lem>
     <rdg>Λευκῶ<add place="above">ν</add>
     </rdg>
    </app> <!--alternative-->
    </ab></div>
                </div>
    

    internal-app-style = 'default'
    NOTHING AT ALL

    internal-app-style = 'iospe'
    3: orig. Α.Θ..ΤΑΥ; 6: corr. ex ; 9: οσ s.l.

    internal-app-style = 'minex'
    l.3 sic, orig. α | l.4 reg., orig. τειμην | l.10 #BL_3.8; ὡς ἐτῶν ιϛ | l.11 Λευκῶν

    internal-app-style = 'fullex'
    l.1 ι corr. | l.3 sic, orig. α | l.4 reg., orig. τειμην | l.5 Γ aut Ε aut Ζ aut Ξ aut Π aut Σ aut Τ | l.6 del τεσσαρες | l.7 a del | l.8 αβ add above | l.9 superscript | l.10 #BL_3.8; ὡς ἐτῶν ιϛ | l.11 Λευκῶν

    The problems which I still have are:

    • for some reasons I obtain nothing with xsl:apply-templates select="t:rdg" I do not understand why. I have put value-of for the time being, but l.10 should be ὡ[ς (ἐτῶν) ιϛ], I think
    • why are the variant unclear in the choice like that in the text?
    • what should I do with @source in lem?
     
  • Tom Elliott
    Tom Elliott
    2015-05-19

    • status: needs-feedback --> accepted
    • assigned_to: Pietro Maria Liuzzo --> Tom Elliott
     
  • Tom Elliott
    Tom Elliott
    2015-05-19

    I am taking ownership of this ticket with the intention of scheduling a meeting soon to read on all critical parties (DLL, DCLP, etc.) with view to getting this resolved.