GithubHelp home page GithubHelp logo

ivanadob / mondsee Goto Github PK

View Code? Open in Web Editor NEW
0.0 0.0 1.0 4.2 MB

The script and library of Mondsee in the Carolingian period

Home Page: https://ivanadob.github.io/mondsee/

License: Other

XSLT 86.90% TeX 4.87% HTML 2.33% CSS 1.54% Shell 0.09% JavaScript 2.75% Python 1.52%
fragmentarium fragments manuscripts medieval mondsee scriptorium tei xslt

mondsee's People

Contributors

csae8092 avatar ivanadob avatar

Watchers

 avatar  avatar

Forkers

csae8092

mondsee's Issues

LaTeX

remove: \end{document} after each section.
the space tabs at the headline for each fragment are sometimes to narrow. The dating is often too long, perhaps place it at the end.
Need of punctuation.

merge listbibl and listtitle into singel valid TEI file

maybe something like below, which would leverage oxygen's autocomplete function to link sources with secondary literatur

<TEI xmlns="http://www.tei-c.org/ns/1.0">
  <teiHeader>
      <fileDesc>
         <titleStmt>
            <title>Title</title>
         </titleStmt>
         <publicationStmt>
            <p>Publication Information</p>
         </publicationStmt>
         <sourceDesc>
            <p>Information about the source</p>
         </sourceDesc>
      </fileDesc>
  </teiHeader>
  <text>
      <body>
         <listBibl xml:id="secondary-lit">
            <bibl xml:id="barre-henri-1962">
               <title type="full">Barré, Henri. Les homéliaires Carolingiens de l’école d’Auxerre. Studi e testi 225. Rome, 1962.</title>
               <title type="short">Barré 1962</title>
               <idno type="gbv"></idno>
            </bibl>
            <bibl xml:id="barre-henri-1961">
               <title type="full">Barré, Henri. Les homéliaires Carolingiens de l’école d’Auxerre. Studi e testi 225. Rome, 1962.</title>
               <title type="short">Barré 1962</title>
               <idno type="gbv"></idno>
            </bibl>
            <bibl xml:id="ccsl">
               <title type="full">Corpus christianorum. Series latina, Turnholti 1953-</title>
               <title type="short">CCSL</title>
            </bibl>
         </listBibl>
<!-- #### sources ####        -->
         <listBibl xml:id="sources">
            <bibl>
               <author ref="#caesarius_arelatensis">Caesarius Arelatensis</author>
               <title>Sermo 199</title>
               <incipit></incipit>
               <note></note>
               <listRelation>
                  <relation ref="#ccslc">
                     <desc>
                        <bibl><abbr>CCSL</abbr> 104,  pp. 803-807.</bibl>
                     </desc>
                  </relation>
               </listRelation>
            </bibl>
         </listBibl>
      </body>
  </text>
</TEI>

Possible problem by presentation of info for 1+ fragments in one host volume

If there are several fragments within one host volume, in the LaTeX file it owuld be better to get the info relating to Binding etc. only once (not to be redundant).
But if we aim at TEI MsDecs for each fragment, then we need the info in every fragment description.
Perhaps work on the LaTeX xslt separately, if we at all want one catalogue (and not pdf files for each separate fragment).

Linking facsimiles

Link facsimiles using IIIf manifests (instead of // or in addition to // adding manually the URLs in the facsimile element).

Corrections to tei-to-latex.xsl

  • Desired order to follow the Austrian Richtlinien for MS descriptions
    B Beschreibstoff, Zustand und Zusammensetzung der ursprünglichen Handschrift
    S Schriftraum, (Beispiel: min 230 X 250. Zwei Spalten zu 31-37 Zeilen. Blindlinierung. Schrift.
    A Ausstatung (Rote Überschriften)
    E Entstehung
    P Provenienz (Makulaturtyp NOT to include if in situ - this info in Shelfmark field)
    L Literatur
    Inhalt

  • Shelfmark: if in situ: Cod. # (Makulaturtyp)

  • in the subtitle add: material (Perg. or Pap.), Umfang

xslt layout

Add layout transofrmation. Get the values from the attributes and add text automatically, to reduce text written in the xml.

  • lineHeight
  • ruled lines
  • columns

Updates required for the xslt

In order to get the tei xml complained to Fragmentarium schema and way of reference:

  1. TEI header should include xml:base with the ID of the fragment (for the description) - this should be taken from the URL already available in the Google spreadsheet (cell 7) probably using substring-after ...
  2. the same URL ID reference must come in the sourceDesc -> msDesc xml:id="F-2076-731" xml:lang="eng" Here F-2076 is the ID of the fragment, 731 is the ID of the description (which are probably numerus currens, hard to get the right one ...

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.