corrected typo in teicat review

i-d-e · Sep 5, 2023 · bba6fb4 · bba6fb4
1 parent 0e7ada9
commit bba6fb4
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 6 deletions.
diff --git a/issues/issue15/teicat/teicat-tei.xml b/issues/issue15/teicat/teicat-tei.xml
@@ -1590,8 +1590,8 @@
             <head>General presentation of the TEI-CAT</head>
             <div xml:id="div1.1">
                <head>Intellectual and practical scope</head>
-               <p xml:id="p1">Regardless of their purpose and method, scholars preparing critical editions (whether “Lachmannian”, “Bedierist” or focused on the study of textual tradition) often have to register, summarize and account for textual variations across several manuscripts and citations. To date, two approaches have been prevalent. The first one involves entering variations in a collation table, either in a notebook or a spreadsheet, and manually redacting the critical text and the critical apparatuses with a word processor or in a TeX file. The second approach involves using specialized software<note xml:id="ftn1">Among others: <ref target="https://web.archive.org/web/20221008175234/http:/www.tustep.uni-tuebingen.de/">TUSTEP</ref> (<ref type="crossref" target="#karls1966">Karls 1966–2020</ref>), <ref target="https://www.oeaw.ac.at/kvk/cte/">Classical Text Editor</ref> (CTE, <ref type="crossref" target="#hagel1997">Hagel 1997–2021</ref>) and <ref target="https://web.archive.org/web/20221110133752/https:/cental.uclouvain.be/chrysocollate/">ChrysoCollate</ref> (<ref type="crossref" target="#moureau2021">Moureau 2021</ref>).</note> that provides a unified interface and various auxiliary tools in order to support the editing process from transcribing to exporting the definitive files.</p>
-               <p xml:id="p2">Such all-in-one applications have undeniable advantages. However, apart from TUSTEP (<ref type="crossref" target="#karls1966">Karls 1966–2020</ref>), which includes a general-purpose text editor and a full scripting language,<note xml:id="ftn2">See <ref target="https://web.archive.org/web/20211212154719/https://ride.i-d-e.de/issues/issue-11/tustep/">Christian Griesinger’s review in RIDE 11</ref>.</note> most applications comprise a predefined set of features that the user can hardly extend and that complicate exchanging data with other software — at best, users can export their work for further processing with another software, whose output cannot be reimported and reworked without losing information.<note xml:id="ftn3">CTE works around this limitation by letting the user insert arbitrary TEI-XML tags in the text. However, to be exportable to TEI-XML, the apparatus has to be redacted in a machine-readable way, which is generally incompatible with the requirements of a print edition: for instance, following the manual, expressions indicating nested variant locations such as <emph>deus dixit] dominus (christus B) dicit ABC</emph> will not be recognized. The practical consequence is that users must choose between print and TEI output.</note> For instance, Pinche (<ref type="crossref" target="#pinche2021">2021</ref>) relies on the annotation of places, personal names and punctuation marks in the edited text in a detailed and structured way. Other examples involve linguistic tagging or describing the shape of letters and abbreviations. This limitation requires performing such tasks after establishing the critical text, which is not always optimal. A workflow based on a TEI-XML encoded file (as described in <ref type="crossref" target="#andrews2009">Andrews 2009, 34–74</ref>) is highly suited to addressing such needs.</p>
+               <p xml:id="p1">Regardless of their purpose and method, scholars preparing critical editions (whether “Lachmannian”, “Bedierist” or focused on the study of textual tradition) often have to register, summarize and account for textual variations across several manuscripts and citations. To date, two approaches have been prevalent. The first one involves entering variations in a collation table, either in a notebook or a spreadsheet, and manually redacting the critical text and the critical apparatuses with a word processor or in a TeX file. The second approach involves using specialized software<note xml:id="ftn1">Among others: <ref target="https://web.archive.org/web/20221008175234/http:/www.tustep.uni-tuebingen.de/">TUSTEP</ref> (<ref type="crossref" target="#karls1966">Universität Tübingen 1966–2020</ref>), <ref target="https://www.oeaw.ac.at/kvk/cte/">Classical Text Editor</ref> (CTE, <ref type="crossref" target="#hagel1997">Hagel 1997–2021</ref>) and <ref target="https://web.archive.org/web/20221110133752/https:/cental.uclouvain.be/chrysocollate/">ChrysoCollate</ref> (<ref type="crossref" target="#moureau2021">Moureau 2021</ref>).</note> that provides a unified interface and various auxiliary tools in order to support the editing process from transcribing to exporting the definitive files.</p>
+               <p xml:id="p2">Such all-in-one applications have undeniable advantages. However, apart from TUSTEP (<ref type="crossref" target="#karls1966">Universität Tübingen 1966–2020</ref>), which includes a general-purpose text editor and a full scripting language,<note xml:id="ftn2">See <ref target="https://web.archive.org/web/20211212154719/https://ride.i-d-e.de/issues/issue-11/tustep/">Christian Griesinger’s review in RIDE 11</ref>.</note> most applications comprise a predefined set of features that the user can hardly extend and that complicate exchanging data with other software — at best, users can export their work for further processing with another software, whose output cannot be reimported and reworked without losing information.<note xml:id="ftn3">CTE works around this limitation by letting the user insert arbitrary TEI-XML tags in the text. However, to be exportable to TEI-XML, the apparatus has to be redacted in a machine-readable way, which is generally incompatible with the requirements of a print edition: for instance, following the manual, expressions indicating nested variant locations such as <emph>deus dixit] dominus (christus B) dicit ABC</emph> will not be recognized. The practical consequence is that users must choose between print and TEI output.</note> For instance, Pinche (<ref type="crossref" target="#pinche2021">2021</ref>) relies on the annotation of places, personal names and punctuation marks in the edited text in a detailed and structured way. Other examples involve linguistic tagging or describing the shape of letters and abbreviations. This limitation requires performing such tasks after establishing the critical text, which is not always optimal. A workflow based on a TEI-XML encoded file (as described in <ref type="crossref" target="#andrews2009">Andrews 2009, 34–74</ref>) is highly suited to addressing such needs.</p>
                <p xml:id="p3">When using the <ref target="https://web.archive.org/web/20221110133927/https:/tei-c.org/release/doc/tei-p5-doc/en/html/index.html">TEI (Text Encoding Initiative) encoding standard</ref> (<ref type="crossref" target="#teiconsortium2021">TEI Consortium 2021</ref>)<note xml:id="ftn4">Especially the modules devoted to the <ref target="https://tei-c.org/release/doc/tei-p5-doc/en/html/MS.html">manuscript description</ref>, the <ref target="https://tei-c.org/release/doc/tei-p5-doc/en/html/PH.html">representation of primary sources</ref> and the <ref target="https://tei-c.org/release/doc/tei-p5-doc/en/html/TC.html">critical apparatus</ref>.</note>, which addresses a wide range of needs and provides extension and specialization mechanisms, scholars are virtually unlimited in determining the data structure of their edition file. This is the case because XML-TEI files only contain structured information. As such, they are not meant to be consulted directly by readers but processed by an external programme to produce, for instance, word processor files (to be sent to a publisher), electronic editions (displayed in a web browser), or even work files (e.&#xA0;g. tables containing all variant readings). XSLT (<ref type="crossref" target="#kay2017">Kay 2017</ref>), a language designed to perform transformations on XML files with the help of stylesheets, is often used to that end (for an example, see <ref type="crossref" target="#vaughan2021">Vaughan 2021</ref>). Separating the recording of variants and the redaction of apparatus entries, which is delegated to further processing (in contrast, notably, to CTE, <ref type="crossref" target="#hagel1997">Hagel 1997–2021</ref>), also ensures a homogeneous syntax in the critical apparatus (see <ref type="crossref" target="#code1">code example 1</ref>) and permits its adaptation to the publisher’s requirements by modifying the transformation stylesheet. On the one hand, this requires time and programming skills, but on the other it enables recording a lot of information in a single XML file, only part of which will be used and preserved in every output.<figure xml:id="code1">
                      <eg xml:space="preserve">&lt;TEI xmlns="http://www.tei-c.org/ns/1.0"&gt;<lb/>&lt;teiHeader&gt;<lb/>    [...]<lb/>    &lt;bibl source="https://www.augustinus.it/latino/cdd/cdd_17.htm"/&gt;<lb/>    [...]<lb/>&lt;/teiHeader&gt;<lb/>  &lt;text&gt;<lb/>    [...]<lb/>    &lt;body&gt;<lb/>      &lt;p xml:lang="la"&gt;Et quia in prophetia vox eius agnoscitur:<lb/>        &lt;seg xml:id="cit1"&gt;Non &lt;app&gt;<lb/>        &lt;lem wit="#A" cert="high"&gt;derelinques&lt;/lem&gt;<lb/>        &lt;rdg wit="#B #C" type="grammatical"&gt;derelinquas&lt;/rdg&gt;<lb/>        &lt;/app&gt; animam meam in inferno&lt;/seg&gt;,<lb/>        &lt;seg xml:id="cit2"&gt;&lt;app&gt;<lb/>        &lt;lem wit="#A #C" cert="high"&gt;eumdem&lt;/lem&gt;<lb/>        &lt;rdg wit="#B" cause="haplography"&gt;eum&lt;/rdg&gt;<lb/>        &lt;/app&gt; deduxit ad inferos et reduxit&lt;/seg&gt;.&lt;/p&gt;<lb/>    &lt;/body&gt;<lb/>    &lt;standOff type="references"&gt;<lb/>      &lt;spanGrp type="biblicalReferences"&gt;<lb/>        &lt;span target="#cit1"&gt;<lb/>          &lt;ref type="literal" cRef="Ps 15:10"/&gt;<lb/>          &lt;ref type="allusive" cRef="Ac 2:27"/&gt;<lb/>        &lt;/span&gt;<lb/>        &lt;span target="#cit2"&gt;<lb/>          &lt;ref type="allusive" cRef="Ac 2:31"/&gt;<lb/>        &lt;/span&gt;<lb/>      &lt;/spanGrp&gt;<lb/>    &lt;/standOff&gt;<lb/>  &lt;/text&gt;<lb/>&lt;/TEI&gt;</eg>
                      <head type="legend">Edition file with some annotations and the identification of biblical references. Note that the references have been separated from the edited text to avoid overloading.</head>
@@ -1706,7 +1706,7 @@
                <bibl xml:id="dumont2021">Dumont, Bastien. 2021. <emph>Tests for the TEI-CAT</emph> (version 1.1). <ref target="https://doi.org/10.5281/zenodo.5270343">https://doi.org/10.5281/zenodo.5270343</ref>.</bibl>
                <bibl xml:id="dunning2020">Dunning, Andrew. 2020. “Reledmac. Typesetting Technology-Independent Critical Editions with LaTeX.” <emph>RIDE</emph> 11. <ref target="https://doi.org/10.18716/ride.a.11.1">https://doi.org/10.18716/ride.a.11.1</ref>.</bibl>
                <bibl xml:id="hagel1997">Hagel, Stephan. 1997–2021. <emph>Classical Text Editor</emph> (version 10.4). Windows. Austrian Academy of Sciences, Corpus Scriptorum Ecclesiasticorum Latinorum. <ref target="https://web.archive.org/web/20221104100713/https://cte.oeaw.ac.at/">https://web.archive.org/web/20221104100713/https://cte.oeaw.ac.at/</ref>.</bibl>
-               <bibl xml:id="karls1966">Karls, Eberhard. 1966–2020. <emph>Tübinger System von Textverarbeitungs-Programmen</emph>. Linux, Mac OS, Raspbian, Windows. Universität Tübingen, Zentrum für Datenverarbeitung. <ref target="https://web.archive.org/web/20221008175234/http://www.tustep.uni-tuebingen.de/">https://web.archive.org/web/20221008175234/http://www.tustep.uni-tuebingen.de/</ref>.</bibl>
+               <bibl xml:id="karls1966">Eberhard Karls Universität Tübingen. 1966–2020. <emph>Tübinger System von Textverarbeitungs-Programmen</emph>. Linux, Mac OS, Raspbian, Windows. Universität Tübingen, Zentrum für Datenverarbeitung. <ref target="https://web.archive.org/web/20221008175234/http://www.tustep.uni-tuebingen.de/">https://web.archive.org/web/20221008175234/http://www.tustep.uni-tuebingen.de/</ref>.</bibl>
                <bibl xml:id="kay2017">Kay, Michael, ed. 2017. “XSL Transformations (XSLT) Version 3.0.” W3C. June 8, 2017. <ref target="https://www.w3.org/TR/xslt-30/">https://www.w3.org/TR/xslt-30/</ref>.</bibl>
                <bibl xml:id="moureau2021">Moureau, Sébastien. 2021. <emph>ChrysoCollate</emph> (version 1.0). Browser-based. Université catholique de Louvain. <ref target="https://web.archive.org/web/20221111120045/https://cental.uclouvain.be/chrysocollate/">https://web.archive.org/web/20221111120045/https://cental.uclouvain.be/chrysocollate/</ref>.</bibl>
                <bibl xml:id="pierazzo2019">Pierazzo, Elena. 2019. “What Future for Digital Scholarly Editions? From Haute Couture to Prêt-à-Porter.” <emph>International Journal of Digital Humanities</emph> 1: 209–20. <ref target="https://doi.org/10.1007/s42803-019-00019-3">https://doi.org/10.1007/s42803-019-00019-3</ref>.</bibl>

diff --git a/issues/issue15/teicat/teicat.pdf b/issues/issue15/teicat/teicat.pdf