Discussions and important action items from the Petrarchive bi-weekly meeting will be documented here.
...
John has question about c. 16r and Rvf 71, and c. 4r and Rvf 23.
Isabella: we have not encoded c.16r yet: at the moment we have encoded only the last 12 verses of Rvf71 (on c.16v). The first part of Rvf71 will be on c.61r (yet to be encoded). As for Rvf23, it starts on c.4r and finishes on c.5r (mistake fixed below).
Wednesday, 23 September 2015
...
- Disable "Timeline" and "Notes".
- People: add a small paragraph for each and link to personal webpages etc.
- Prototypes: we might want to use a different term but still keep them aside (or inside) the Introduction.
- Encoding issues to fix (from 16 September's meeting notes):Some poems are missing poem and/or line numbers. Here is a list:
c.002r, c002v: missing poem and line numbers from Rvf11 and Rvf 14 Ballata grande
- c.004r-v005r: missing line numbers canzone Rvf 23 (john: incomplete?)
- c005v: missing line numbers Rvf 28 canzone
- cc.015r-v: missing line numbers canzone Rvf 70
- cc.016v-18v: missing line numbers canzoni Rvf 71, 72, 73
- cc.022v-23r: missing line numbers Rvf 106 canzone
- c.024v: missing line numbers canzone Rvf 119
c.026r: missing line numbers madrigalRvf 121(and Donna,ballata)- c.069v-r: missing line numbers Rvf 356 canzone
Catchwords need to be at the bottom center of the chartae:- Catchword: Et solo = end of 16v
- Cathchword: Tal che = end of 24v
...
Allie will keep a list of encoding issues and upload it to the wiki for future encoders to use. One example of such an issue is page breaks, as in c045r. Members in general will keep an eye out for appropriate fonts to use for the website. Meanwhile, Isabella and Wayne will meet with Modigliani to discuss some of the punctuation in the diplomatic edition of the Rvf.
...
John also showed members c039r as displayed on the web, and he decided to have the parts written over erasures/cancellations displayed in gray. Allie will add an example of this to the wiki and call it "writing over a cancellation" or another such name. This is the same situation as is found on c026r.
...
Members began by discussing the visual layout of the chartae on the web. John will play around with spacing on the webpage to show the lack of horizontal space between the poems. Apparently, the large-font paragraph marker is responsible for much of the current dysfunction. They also talked about hiring a designer to create document maps.
Regarding c026r, the line lengths are very long and therefore the poems do not display properly online. Furthermore, the whole of poem 121 is written over an erasure. John suggested using substitution, deletion, or other tags for the poem. In other collections of Petrarch's poetry, the erased poem travels between the 120s and 240s in number. Images of the palimpsest, or of other manuscripts, might be added to the webpage for this charta. John will figure out how to encode the erasures. Also for poem 121, one of the rs should be small caps, but Petrarch made a mistake. The tag <choice orig="___"> might be used to show this mistake, which would be standardized as small caps. At the end of poem 122 there is a punctuation mark which is not a true punctus elevatus. Eventually the mark will be standardized as such. Interestingly, this charta only has 30 lines because the madrigal has 6 lines. The erased ballata underneath would have had 7. Petrarch is clearly imitating Malpaghini's transcriptional style in this charta.
...
The members offered suggestions for using specialer characters in the TEI documents such as the punctus elevatus. Some of the characters may be present in the MUFI character recommendation sheets, which Allie will add to the wiki. John showed Allie and Isabella how to put code in the header which will describe such characters, which can be linked in the body of the document with <g ref="#punctelevhiback" /> or another such tag. They also discussed a p-macron character not present in Unicode that Allie encountered in c069v. These characters will be compiled in the TEI template by John.
...
John will put TEI prototypes for all chartae on the wiki. Isabella will begin encoding c026r. Allie will add Wayne's word document transcriptions and edited versions of all chartae to the wiki. Wayne will begin getting Vatican permission to use Rvf images. The project will be presented as an edition, not a transcription, of the document so the Vatican is more likely to grant such permission.
...
Allie will change page titles in the wiki to add more 0s to the chartae names. John showed members that he added the madrigal and canzone as <lg type=""> terms. For the canzoni and other poems he will have to add additional subtype terms. Members also discussed the proper way to encode space in the TEI documents. They settled on the following: <space unit="lines" extent="" ana="# />, with ana standing for analysis. In here members can type #space-stop or other terms. #space-sonnet was posited as a way to encode the 7-line gaps in the text that appear, but Wayne pointed out that a madrigal or ballota could also appear in that space. Unless the space must contain the sonnet, it should be encoded in terms of empty lines. Petrarch's 31-line canvas should be kept in mind at all times. There should also be an abbreviation created for the 1-line space between poems.
Charta 069v presents some interesting problems. Due to space constraints, Petrarch wrote 3 verses of the canzone per line instead of the usual 2. It should have been a metrical sister to poem Rvf 119. Members created the term "triple hemistich" to encode the poem. Allie will encode 069v and 070r during the next 2 weeks. The members are interested to see how far they can push TEI to accommodate the visual poetics in the manuscript.
Tuesday, 16 April, 2013
The meeting was kept short due to John's absence. Members discussed space issues within the manuscript, such as the half-line space that is characteristic of the canzone. Since it is merely the conclusion of a strophe, the members agreed that it should be described in terms of the text rather than just as a space, perhaps as a "half-hemistiche" or "conclusion of strophe." They also discussed recurring abbrevations and decided to add "pmo/primo" to the list of entities. John will also have to add further <lg type=" "> entries for genre terms, including the canzone, strophe, and madrigal.
Tuesday, April 9, 2013
In light of Wayne's absence, the members focused on problems Allie and Isabella encountered while encoding c03v and c22r and v. John agreed to create a unified entity file that can be linked to the individual XML files for the chartae. New abbreviations can be added to the master file once they are identified. The members discussed how to deal with capitalized abbreviations vs. ones that occur within a line. In order to make them all searchable under one name, they decided to change the entity name and expansion but keep the abbreviations the same. They also talked about how to deal with poems that cross page boundaries. Many of these problems will have to be considered more fully once further examples are found in the manuscript.
...
Isabella will begin encoding fol. 22v, which contains a new genre of poem. Allie will also encode 3v, which contains a sonnet and a sestina. To aid in this endeavor, John will make sure the TEI headers on the wiki are updated.
Tuesday, March 19, 2013
John and Isabella agreed to meet tomorrow, and Tuesdays after the project meetings as needed, to go over the TEI encoding process. John debuted the newly fleshed-out TEI header with tags for the document name, project members, etc. He and Wayne discussed who should be listed as the project's publisher. John explained that eventually all this information will become a boilerplate which can be linked in the XML documents of the individual chartae, so members don't need to edit hundreds of files if changes are made to the general header. He also noted that he had given a Creative Commons Attribution Non-Commerical license to the project.
Members discussed the possibilities of having a multilingual, English-Italian website for the project. John explained that the <msdesc> and other tags can have both English and Italian information in them to facilitate this. John will continue to revise the TEI header as Wayne gives him more information about the document. He also discussed how unusual it was for TEI projects to have separate files for every page/charta, but members agreed that this setup fit the goals of the project. They posited how they might create a "master document" that pulls in information from the TEI boilerplate as well as the individual charta files to create one complete TEI file with all aspects of the project in it. It is important to show the compositional unit of the page, as it is not arbitrary in the Rvf. John and Wayne agreed to compile an index of poem numbers and first lines to help users navigate the project. The two also want to create a document "map" of the folios to represent visually where the chartae lie in the document and show the position of the poems on the pages. The document map should be arrangeable by genre, page order, folios, etc. To facilitate this, Wayne will begin identifying gatherings and conjunct leaves. He will also compile a vocabulary of defined spaces in the manuscript, including a term for the space under erasures,
Isabella will start encoding fol. 22r. The members agreed to add fols. 22v and 23r to the project subset. John will begin work on a new charta as well as continuing to craft the <msdesc> tag. Allie will upload image files for all the chartae onto the wiki.
Tuesday, March 5, 2013
Wayne agreed to do a micro-examination of the hands to determine all the interventions in the text. John outlined the pages of the wiki and the functions thereof. He will change the Chartae page to clarify the poems on each leaf, add a link to the online "development" version, and determine a way to pose questions about the charta on the wiki page. Members discussed possibilities for creating a unique font for the project, especially for initials and other special characters. As John explained, Unicode is concerned with the "Platonic ideal" of forms of characters, or "glyphs," and it might be best to use different fonts to change the display, or perhaps the <hi> or <rend> codes. Members then reviewed the common abbreviations that will be added to the TEI header, and John agreed to flesh out the TEI header in general. He will also add TEI boilerplate information about publication.
Isabella will work on the <msdesc> tag to expand an Italian version of the information and translate it into English and also use the <mspart> tag to incorporate anomalies of individual chartae. John will expand the charta pages and upload all the images as attachments. Wayne will change the photos' file names to reflect their position in the manuscript. Isabella will practice encoding fol. 22r because it is very similar to fol. 01v. John posited ways to encode missing poems, perhaps using <space type="sonnet">, etc., and similar methods for empty lines, length of empty spaces in centimeters, and other elements. John will add a page on the wiki with the XML template to facilitate this.
...
Wayne and John discussed how they can use encoding to act as a deep commentary on the genesis and changes made to the document over time, especially by noting changes in the hand, erasures, and additions to the text. If the encoding is consistently detailed, they should be able to auto-generate textual notes from the TEI codes. The encoding might also be used to create infographics related to the text, especially relating to the various hands used in the document. Wayne agreed to create a list of the hands used throughout the document so John can create a shortcut that can be used during encoding.
...