Commit c2d25aa3 authored by Elisa Nury's avatar Elisa Nury
Browse files

Change full text search box and minor corrections

parent eebfddb4
<?xml version="1.0" encoding="UTF-8"?>
<tei:TEI xmlns="http://www.tei-c.org/ns/1.0" xmlns:tei="http://www.tei-c.org/ns/1.0">
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<fileDesc>
<titleStmt>
......@@ -26,7 +26,7 @@
</fileDesc>
<encodingDesc>
<classDecl>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../grammateus_taxonomy.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:tei="http://www.tei-c.org/ns/1.0" href="../grammateus_taxonomy.xml"/>
</classDecl>
<p>This file is encoded to comply with TEI Guidelines P5, Version 4.0.0.
<ref>https://tei-c.org/guidelines/p5/</ref>
......@@ -145,7 +145,7 @@
salutation is usually [<term xml:lang="grc">ἔρρωσο</term>] [<ref type="internal" target="802.xml">802</ref>
256 BCE, Alexandria], while in the Roman period [<term xml:lang="grc">ἐρρῶσθαί σε εὔχομαι</term>] is
favoured [<ref target="http://papyri.info/ddbdp/p.mert;1;23" type="external">28779</ref> II CE, Oxyrhynchus]. A
feature of the business letters in the Zenon archive is a date is often included
feature of the business letters in the Zenon archive is a date often included
at the end of the letter, usually after the closing formula [<ref type="internal" target="755.xml">755</ref> 257 BCE]; but this is not generally the case
in most examples of the sub-type. The format is similar in style to the private
letter: predominantly <term xml:lang="lat">transuersa charta</term> in the Ptolemaic
......@@ -229,7 +229,7 @@
legible e.g. [<ref target="http://www.papyri.info/ddbdp/p.tebt;1;17" type="external">3653</ref>
114 BCE, Tebtunis]; although the fragmentary [<ref type="external" target="http://papyri.info/ddbdp/p.oxy;51;3615">15350</ref> III CE, Oxyrhynchus] emanates from the office of
<term xml:lang="grc">ἐπιτηρητὴς ἡγεμονικῶν ἐπιστολῶν καὶ ἄλ̣λ̣ων</term>, <q>the
superintendant of the letters of the prefect and others</q>, and is hardly legible.
superintendant of the letters of the prefect and others</q>, it is hardly legible.
Chancery documents display regular, non-ligatured lettering that can be quite
stylized [<ref type="internal" target="23140.xml">23140</ref> 209 CE, Alexandria]. Chancery scribes follow a distinct model,
with the opening address separated from the text and the greeting
......@@ -265,7 +265,6 @@
<ptr target="gramm:paramone2004"/>
<citedRange>9, introduction</citedRange>
</bibl>.
<!--[<ref target="http://www.papyri.info/biblio/18001">P. Paramone 9</ref>, introduction]-->
These documents often refer to themselves as <term xml:lang="grc">ἐπιστολή</term> or
<term xml:lang="grc">γράμματα</term> [<ref type="internal" target="8207.xml">8207</ref> 248 BCE; <ref type="internal" target="8212.xml">8212</ref> 245 BCE, both Oxyrhynchus]. They vary in
format from <term xml:lang="lat">transuersa charta</term> [<ref type="internal" target="1939.xml">1939</ref>, <ref type="internal" target="8207.xml">8207</ref>, <ref type="external" target="http://papyri.info/ddbdp/p.hib;1;168">8281</ref> 245 BCE, Oxyrhynchus] to
......@@ -346,7 +345,7 @@
<ref type="internal" target="15120.xml">15120</ref> 204 CE, Arsinoite nome;
cf. <bibl>
<author>Ferretti et al.</author>
<ptr target="gramm:schubert2020"/>
<ptr target="gramm:ferretti2020"/>
</bibl>. </p>
<p>The text of a receipt is laid out as a single block, often with the date
separated from the rest of the writing [<ref type="external" target="http://papyri.info/ddbdp/p.fay;;88">10931</ref> 204 CE, Arsinoite
......@@ -382,4 +381,4 @@
<div type="bibliography"/>
</body>
</text>
</tei:TEI>
\ No newline at end of file
</TEI>
\ No newline at end of file
......@@ -74,7 +74,7 @@
<li>The <b>Provenance</b> is the Nome when available, or a more precise place name depending on the precision of the HGV metadata. <br/>
<u>Technical note:</u> the Nome is usually encoded with a <span class="code">&lt;provenance&gt;</span> element. However, not all papyri have this precise encoding. When there is no <span class="code">&lt;provenance&gt;</span> element, the Nome may also be extracted from <span class="code">&lt;origPlace&gt;</span>, if it is present in parenthesis. If the Nome cannot be safely deduced, then the content of <span class="code">&lt;origPlace&gt;</span> is used. <!--TODO (add link to code)-->
</li>
<li>The <b>Date</b> can be filtered by selecting a range of centuries, within the corpus bounds (Prolemaic and Roman period). The search is loose, meaning that the date range of a document must overlap with the selected range. Papyri that have an incomplete range, i.e. only one terminus post or ante quem, are given a range of 100 years before/after their terminus. <br/>
<li>The <b>Date</b> can be filtered by selecting a range of centuries, within the corpus bounds (Ptolemaic and Roman period). The search is loose, meaning that the date range of a document must overlap with the selected range. Papyri that have an incomplete range, i.e. only one terminus post or ante quem, are given a range of 50 years before/after their terminus. <br/>
When there are multiple datations for one papyrus, we consider only the first one. For a precise datation, please check HGV. <!--TODO (add link to code)-->
</li>
</ul>
......
......@@ -53,7 +53,34 @@ body {
min-height: 100vh;
flex-direction: column;
}
/* Search box */
.input-search {
border-bottom: 1px solid white;
}
/*.input-search:focus-within {*/
/* border-bottom: 1px solid var(--search-color); */
/* color: var(--search-color);*/
/*}*/
.logo-search {
background-color: var(--main-bg-color);
color: white;
border:0;
padding-left: 0.5rem;
padding-right: 0.5rem;
}
.text-search {
background-color: var(--main-bg-color);
border: 0;
border-radius: 0;
}
.text-search:focus {
background-color: var(--main-bg-color);
color: white;
border: 0;
box-shadow: none;
}
/*----------*/
/* content container */
#content {
margin-bottom: 0px; /*57px*/
......@@ -447,7 +474,11 @@ a.img-btn > i:hover {
.signature {
background-color: var(--papyrus-signature-color);
}
/* multiple sections */
/* three sections */
span.main-text ~ .main-text.salutation.date {
background: linear-gradient(to right, var(--papyrus-main-color), var(--papyrus-salutation-color), var(--papyrus-date-color));
}
/* two sections */
.date.descr-contents:first-of-type {
background: linear-gradient(to right, var(--papyrus-date-color), var(--papyrus-descr-cont-color));
}
......@@ -499,6 +530,8 @@ span.subscription ~ .subscription.date {
span.main-text ~ .main-text.salutation {
background: linear-gradient(to right, var(--papyrus-main-color), var(--papyrus-salutation-color));
}
/* subscription inside date (TM 15112)? does not seem possible in css */
/* TODO: special case - date embedded in subscription (TM14355)? */
......
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id$ -->
<xsl:stylesheet xmlns:EDF="http://epidoc.sourceforge.net/ns/functions" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:t="http://www.tei-c.org/ns/1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema" exclude-result-prefixes="#all" version="2.0">
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:t="http://www.tei-c.org/ns/1.0" xmlns:EDF="http://epidoc.sourceforge.net/ns/functions" xmlns:xs="http://www.w3.org/2001/XMLSchema" exclude-result-prefixes="#all" version="2.0">
<!-- Actual display and increment calculation found in teilb.xsl -->
<xsl:import href="teilb.xsl"/>
......@@ -41,7 +41,7 @@
*or lines with a lettter (e.g 33a)
*or lines with a slash (e.g. 32/33), as they are not a unique line but a combination, and not recommended and likely to disappear (TM12078)
-lines which are in the margins. -->
<xsl:number count="t:lb[not(ancestor::t:reg or ancestor::t:corr or ancestor::t:rdg or ancestor::t:del[parent::t:subst] or following-sibling::*[1][self::t:space][following-sibling::*[1][self::t:lb]] or following-sibling::*[1][self::t:figure][not(following-sibling::*)] or following-sibling::*[1][self::t:figure][following-sibling::*[1][self::t:lb]] or following-sibling::*[1][self::t:gap[@extent = 'unknown' and @unit = 'line']] or following-sibling::*[1][self::t:gap[@unit = 'line' and @reason = 'illegible']] or following-sibling::*[1][self::t:gap[@unit = 'line' and @reason = 'lost' and @precision = 'low']] or following-sibling::*[1][self::t:note] or following-sibling::*[1][self::t:g[@type = 'x']] or following-sibling::*[1][self::t:milestone[@rend = 'box' and @unit = 'undefined']] or matches(@n, '[A-Za-z/]') or ancestor::t:div[@n = 'ms'] )]" level="any"/>
<xsl:number count="t:lb[not( ancestor::t:reg or ancestor::t:corr or ancestor::t:rdg or ancestor::t:del[parent::t:subst] or following-sibling::node()[1][self::t:space][following-sibling::node()[1][self::t:lb]] or following-sibling::*[1][self::t:figure][not(following-sibling::*)] or following-sibling::*[1][self::t:figure][following-sibling::*[1][self::t:lb]] or following-sibling::*[1][self::t:gap[@extent = 'unknown' and @unit = 'line']] or following-sibling::*[1][self::t:gap[@unit = 'line' and @reason = 'illegible']] or following-sibling::*[1][self::t:gap[@unit = 'line' and @reason = 'lost' and @precision = 'low']] or following-sibling::*[1][self::t:note] or following-sibling::*[1][self::t:g[@type = 'x']] or following-sibling::*[1][self::t:milestone[@rend = 'box' and @unit = 'undefined']] or matches(@n, '[A-Za-z/]') or ancestor::t:div[@n = 'ms'] )]" level="any"/>
</xsl:if>
</xsl:variable>
......
......@@ -48,13 +48,13 @@
<a class="nav-item nav-link" href="bibliography.html">Bibliography</a>
</div>
<form action="./browse.html" method="get" class="form-inline my-2 my-lg-0">
<div class="input-group">
<input type="text" name="keyword" class="form-control" placeholder="Search the website" aria-label="Search" aria-describedby="basic-addon1"/>
<div class="input-group-append">
<button class="btn btn-danger" type="submit" id="basic-addon1">
<div class="input-group input-search">
<div class="input-group-prepend">
<span class="input-group-text logo-search" id="addon-search">
<i class="fas fa-search"/>
</button>
</span>
</div>
<input type="text" name="keyword" aria-label="Search the website" aria-describedby="addon-search" class="form-control text-search" placeholder=""/>
</div>
</form>
</div>
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment