<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Digital Du Chemin</title>
	<atom:link href="http://blogs.haverford.edu/digitalduchemin/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.haverford.edu/digitalduchemin</link>
	<description>Just another News.haverford.edu weblog</description>
	<lastBuildDate>Wed, 19 Oct 2011 15:58:05 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Literary Texts and TEI:  Discussion</title>
		<link>http://blogs.haverford.edu/digitalduchemin/2011/10/19/literary-texts-and-tei-discussion/</link>
		<comments>http://blogs.haverford.edu/digitalduchemin/2011/10/19/literary-texts-and-tei-discussion/#comments</comments>
		<pubDate>Wed, 19 Oct 2011 15:53:48 +0000</pubDate>
		<dc:creator>rfreedman</dc:creator>
				<category><![CDATA[2011 Discussions]]></category>

		<guid isPermaLink="false">http://blogs.haverford.edu/blogs/digitalduchemin/?p=137</guid>
		<description><![CDATA[Define research questions that will govern mark up, encoding, and search/display.  What would we want to see/compare: A. Text as determined by modern editor (that is, corresponding to the base text presented in the musical edition) B. Text as &#8220;presented&#8221; in chansonnier, that is, already interpreted via certain types of division, repetition, prolongation. C. Text [...]]]></description>
				<content:encoded><![CDATA[<p>Define research questions that will govern mark up, encoding, and search/display.  What would we want to see/compare:</p>
<p>A. Text as determined by modern editor (that is, corresponding to the base text presented in the musical edition)</p>
<p>B. Text as &#8220;presented&#8221; in chansonnier, that is, already interpreted via certain types of division, repetition, prolongation.</p>
<p>C. Text as it appeared in some sixteenth-century literary (non musical) source, which might or might not correspond to the &#8220;musical&#8221; treatment</p>
<p>D. Views that could highlight <em>differences</em>, such:</p>
<p>E. Ways in which the &#8220;musical&#8221; poem departs from printed ones (like variants, or extra verses)</p>
<p>F. Ways in which the musical poem departs among the individual voice parts (orthography or punctuation, or wording)</p>
<p>G. Views that could highlight <em>similarities</em>, such as:</p>
<p style="padding-left: 30px">1. Poems that cite each other, perhaps in connection with music that does likewise</p>
<p style="padding-left: 30px">2. Patterns of circulation for the text, in all its forms:</p>
<p>H. Within a anthology of other settings</p>
<p>I. Citation or quotation (in another musical setting)</p>
<p>J. Rival settings</p>
<p>K. Additional verses</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.haverford.edu/digitalduchemin/2011/10/19/literary-texts-and-tei-discussion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title></title>
		<link>http://blogs.haverford.edu/digitalduchemin/2011/10/04/128/</link>
		<comments>http://blogs.haverford.edu/digitalduchemin/2011/10/04/128/#comments</comments>
		<pubDate>Tue, 04 Oct 2011 14:29:42 +0000</pubDate>
		<dc:creator>rfreedman</dc:creator>
				<category><![CDATA[Key Challenges for 2011 to 2013]]></category>

		<guid isPermaLink="false">http://blogs.haverford.edu/blogs/digitalduchemin/?p=128</guid>
		<description><![CDATA[1. &#8220;Layers&#8221; of editorial control and participants. Different users will want to use the sites in different ways.  It’s important for us to recognize that there will be different levels of expertise, and different interests—from students (intermediate as well as advanced) to scholars (in literary studies, digital humanities, as well as musicologists) to performers.  Some [...]]]></description>
				<content:encoded><![CDATA[<p><strong>1. </strong><strong>&#8220;Layers&#8221; of editorial control and participants. </strong></p>
<p>Different users will want to use the sites in different ways.  It’s important for us to recognize that there will be different levels of expertise, and different interests—from students (intermediate as well as advanced) to scholars (in literary studies, digital humanities, as well as musicologists) to performers.  Some will simply want finished editions.  Others will want to get involved in the reconstructions.  Still others want might want to look at variant readings or undertake studies of style and influence.</p>
<p style="padding-left: 30px">So here is a <strong>model of the ‘levels’ of permission and authority</strong>:</p>
<p style="padding-left: 30px">Owners (who maintain the site, and hold the copyright)<br />
Editors (who are responsible for the big policies and questions)<br />
Contributors (who send in essays or reconstructions)<br />
Correspondents (who can ask questions or make comments on particular pieces)<br />
Viewers (anyone)</p>
<p><strong>2. </strong><strong>Nouvelles sur nouvelles.</strong></p>
<p>We want to move beyond a static archive and instead towards an <em>interactive</em> model of collaborative inquiry.  We thus need ways to announce new content, or new conversations.  We also need to find ways for users to follow this news, and for them to find each other.  The “news” function is important for sustaining interest in the site during the inevitable gaps and silences between launch of new material.  We thus need announcements that report on what we are doing, and what is coming up.  (For instance, announcement about a grant, about the Med-Ren meeting, about the Ecole thematique, etc).</p>
<p>We could also use this public space as a way of encouraging users (individual scholars, or perhaps a professor and students) to edit some pieces or propose a reconstruction.  We could, for instance, make a suggestion about something to discuss, or a challenging piece for reconstruction.  We could make announcements about a group of students who are seeking someone else for collaboration.</p>
<p><strong>3.  Documentation is a key part of all digital humanities projects. </strong></p>
<p>We need to provide a written record of the steps we have taken (even discussions like this one!).  We also need document our editorial and encoding methods.  These records are a crucial part of what we have promised granting agencies. They will be an important part of securing future funding.  It will also be crucial for us to have clear methods we attempt to collaborate—whether with scholars who want to contribute something to our projects or to those like the ELVIS project who want to make use of our data.</p>
<p style="padding-left: 30px">Thus we are likely to need two ‘spaces’&#8211;one private, the other public:</p>
<p style="padding-left: 60px">a.  The <strong>decisions taken by the advisory board and technical team.</strong></p>
<p style="padding-left: 60px">b. A clear set of <strong>editorial standards.</strong></p>
<p><strong>4.  Verwandlungsmusik. </strong></p>
<p>Our end users are unlikely to be able to use <strong>MEI</strong>, or even learn it.  We will in any case still need to produce engraved PDFs for performers, and still need to use <strong>Sibelius</strong> and <strong>Finale</strong> to distribute and gather reconstructions from contributors.  We also have members of the <strong>CMME</strong> community to work with.  Can we hire consultants to produce tools for transformation from one format to the other?</p>
<p>The MEI team is making <em>excellent</em> progress on tools for encoding and displaying music.  They expect to launch a viewer/encoder in May of 2012.  It is very important for us to document our standards so that our files will be easily converted into MEI standard.</p>
<p>How, exactly, will we treat variants and reconstructions in our Sibelius editions or our CMME encodings?  What happens to this information when we export data as Music XML and then MEI?  What happens when we export a CMME file with ‘variants’ as MusicXML or MEI?  What happens when we “add” a voice with Sibelius, then try to incorporate it into a CMME file for display?  What happens to musica ficta and other editorial accidentals in he transformation process?</p>
<p><strong>5.  Citation/juxtaposition. </strong></p>
<p>As part of our workshop for reconstructions, we want to &#8220;point&#8221; between and among related pieces.  We also want to make connections between the elements in our Thesaurus (like a cadential figure) and corresponding passages in pieces we have reconstructed.</p>
<p>Can the MEI team suggest specific ways to do any of this?  Can we document the practice?  Eventually these could be rendered in some dynamic way on screen.  For now we would be satisfied with pointers to fixed images of the Thesaurus figures, which would be organized in some systematic way.</p>
<p style="padding-left: 30px">Note that the <strong>Shakespeare Quartos Archive</strong> allows users to juxtapose different readings or editions. and allows them to annotate what they find.  There is also a way to <em>save</em> the annotations!</p>
<p style="padding-left: 30px">See the Shakespeare Quartos Archive for some great tools and tutorials on how to use them.  They allow users to ‘collect’ passages and put them side by side.  Also registered users can <em>keep</em> their annotations:</p>
<p style="padding-left: 30px"><a href="http://www.quartos.org/">www.quartos.org/</a></p>
<p style="padding-left: 30px"><a href="http://www.quartos.org/lib/Diff/compare.html">www.quartos.org/lib/Diff/compare.html</a></p>
<p><strong>6. Developing the Community.</strong></p>
<p>During the Barcelona Med-Ren meeting I started to keep a list of scholars interested in the AVRP and Du Chemin.</p>
<p style="padding-left: 30px">Jessie Rodin [Josquin Project.]</p>
<p style="padding-left: 30px">Luca Bruno [Naples.  Great presentation on Santa Maria and Villanesche]</p>
<p style="padding-left: 30px">Philippe Canguilhem  [Toulouse.  Interesting work on Lusitano and improvisation-composition]</p>
<p style="padding-left: 30px">Ann Smith [Basel Schola Cantorum]</p>
<p style="padding-left: 30px">Robert Kendrick (Chicago—he is already using Du Chemin with his students)</p>
<p style="padding-left: 30px">Wolfgang Fuhrmann (Vienna.  Expressed interest in missing voice part from Petrucci motets]</p>
<p style="padding-left: 30px">Julie Cumming [Montreal.  Elvis project]</p>
<p style="padding-left: 30px">Peter Schubert [Montreal.  Elvis project]</p>
<p style="padding-left: 30px">Andrea Lindmayr-Brandl</p>
<p style="padding-left: 30px">Vladimir Prado [Vienna. Working on Digital editions of de Monte]</p>
<p style="padding-left: 30px">Thomas Schmidt-Beste [Bangor.  Working on new grant to catalog manuscripts and prints]</p>
<p>We also have our <strong>Advisory Board</strong> members.  I am not sure how many of them want to stay actively involved:</p>
<p style="padding-left: 30px">Jennifer Bloxam</p>
<p style="padding-left: 30px">Patrick Macey</p>
<p style="padding-left: 30px">Jennifer Thomas</p>
<p style="padding-left: 30px">Honey Meconi</p>
<p style="padding-left: 30px">Cynthia Cyrus</p>
<p style="padding-left: 30px">Carla Zecher (Newberry)</p>
<p style="padding-left: 30px">Erin Mayhood (UVA Library and MEI)</p>
<p>And a few others who had already expressed interest in Du Chemin and AVRP during the early months of 2011.</p>
<p style="padding-left: 30px">Stefano Mengozzi</p>
<p style="padding-left: 30px">Vassiliki Koutsobina</p>
<p style="padding-left: 30px">Jeanice Brooks</p>
<p style="padding-left: 30px">David Crook</p>
<p style="padding-left: 30px">Erika Honisch</p>
<p><strong>Technical Consultants:</strong></p>
<p style="padding-left: 30px">Craig Sapp (Stanford)</p>
<p style="padding-left: 30px">Andrew Hankinson (McGill)</p>
<p style="padding-left: 30px">Raffaele Vigliante (London)</p>
<p style="padding-left: 30px">Ichiro Fujinaga (McGill)</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.haverford.edu/digitalduchemin/2011/10/04/128/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Editorial Guidelines&#8211;clarifications</title>
		<link>http://blogs.haverford.edu/digitalduchemin/2010/05/30/editorial-guidelines-clarifications/</link>
		<comments>http://blogs.haverford.edu/digitalduchemin/2010/05/30/editorial-guidelines-clarifications/#comments</comments>
		<pubDate>Sun, 30 May 2010 08:13:29 +0000</pubDate>
		<dc:creator>rfreedman</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Edit Guidelines--Texts]]></category>

		<guid isPermaLink="false">http://blogs.haverford.edu/blogs/digitalduchemin/?p=89</guid>
		<description><![CDATA[Freedman Responses to Chater questions. May 28 2010 General 1. I have replaced the titles with the incipits as found in the contents table. However, this brings the problem that the spelling is often at variance with the spelling found in the music. In these cases I have followed the music and noted the discrepancies [...]]]></description>
				<content:encoded><![CDATA[<h2><strong>Freedman Responses to Chater questions. </strong></h2>
<h2><strong>May 28 2010</strong></h2>
<h1><strong> </strong></h1>
<p><span style="text-decoration: underline">General</span></p>
<p>1. I have replaced the titles with the incipits as found in the contents table. However, this brings the problem that the spelling is often at variance with the spelling found in the music. In these cases I have followed the music and noted the discrepancies below.</p>
<p><strong>RF:  This is tricky, since we said that we would follow the table of contents in the naming of the pieces.  What is the policy for the Basse de données on the CESR web site?  And in our table of contents pages for the Du Chemin system?</strong></p>
<p>2. Richard has stated a preference for 2<sup>nd</sup> time text to be placed on the lower line. I’ve no objection, but it’s a lot of work, as I have done them all on the first line! What do other editions do? The trouble is, the format has to be “settled” before you do this; otherwise, each time the system division changes location, you are going to have to reformat.</p>
<p>I will keep them as they are for the moment and leave it to you and Vincent to decide. The only problem is that when you go on to the next system the line has to revert the upper line. This is tricky as the system change keeps changing accord as the format changes. So for the moment I have left it as it is and Vincent can change it after the final format has been established. But maybe this should be reconsidered?  See my further remarks below, at II,21.</p>
<p><strong>RF:   This is a very small detail of layout, although I agree that it would be best for things to be consistent.  I would suggest that _just_ the last syllable of the second line be moved lower, so that the singer will see it in relation to the second verse.  The _remainder_ of the text in that voice part (that is, after the second ending) can revert back to the normal position for single verses.  This is in any case what Du Chemin&#8217;s typesetters do.</strong></p>
<p>3. It is often difficult to decide if 2 syllables separated by a gap make up one or two words. The typesetter does not use hyphens but leaves a gap between 2 syllables belonging to the same word.</p>
<p>Individual cases discussed below. My knowledge of old French is not sufficient for me to be completely sure. Maybe consult a dictionary of sixteenth-century French if one can be found?</p>
<p><strong>RF:  I think the editor will need to use some judgment here, just as Du Chemin&#8217;s singers needed to.  What does the Fiala project do in such cases?   I agree that reference to a dictionary of old French might help.  What is our shared resource for Fiala and Freedman?  The big dictionary I know is Huguet, <span style="text-decoration: underline">Dictionnaire de la langue française du seizieme siecle</span> (Champion, 1933ff).  But perhaps there is something newer, like the Chicago Artfl Project, and its <a href="http://http://artfl-project.uchicago.edu/node/17"></a><a href="http://http://artfl-project.uchicago.edu/node/17">Dictionnaire d&#8217;autrefois.</a><br />
</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.haverford.edu/digitalduchemin/2010/05/30/editorial-guidelines-clarifications/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Second livre:  Questions and Responses</title>
		<link>http://blogs.haverford.edu/digitalduchemin/2010/05/30/second-livre-questions-and-responses/</link>
		<comments>http://blogs.haverford.edu/digitalduchemin/2010/05/30/second-livre-questions-and-responses/#comments</comments>
		<pubDate>Sun, 30 May 2010 07:48:36 +0000</pubDate>
		<dc:creator>rfreedman</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Edit Guidelines--Texts]]></category>

		<guid isPermaLink="false">http://blogs.haverford.edu/blogs/digitalduchemin/?p=83</guid>
		<description><![CDATA[Freedman Responses to Chater questions. May 28 2010 II,1 Je me veulx tant. Souffrir m’est doulz et mon mal j’estime heur. For the scansion, the final e of “estime” should be elided with “heur” (h is not aspirated).  Do you like my solution? RF:  I assume you mean in mm 22-23 and 28-9, you are [...]]]></description>
				<content:encoded><![CDATA[<h1><strong>Freedman Responses to Chater questions. </strong></h1>
<h1><strong>May 28 2010</strong></h1>
<p><strong> </strong></p>
<h2>II,1 Je me veulx tant.</h2>
<p>Souffrir m’est doulz et mon mal j’estime heur. For the scansion, the final e of “estime” should be elided with “heur” (h is not aspirated).  Do you like my solution?</p>
<p><strong>RF:  I assume you mean in mm 22-23 and 28-9, you are delaying both me and heur to the last note.  I agree that this seems a more regular 4+6 syllable line.</strong></p>
<h2>II,2 Vous me changez</h2>
<p>Last word. I made “serf-vice” into one word. In the print there is a small gap after the “f”, so I made it two words. But elsewhere the printer often leaves a small gap and no hyphen between 2 syllables belonging to the same word. I think it is obviously to be considered one word.</p>
<p><strong>RF:  Yes, seems reasonable, although I wonder if there is some kind of word play with earlier line on &#8220;service&#8221; (no f in this case).  That would rule against the hyphen. </strong></p>
<h2>II,5 Un fin Mary, bar 27ff.</h2>
<p>Here “à” is used for third person singular present tense of “avoir”. If we automatically put an accent on “à” as preposition, should we not leave it off if it means “has”? I have changed it to “a”.</p>
<p><strong>RF:  We have said we&#8217;d add accents to avoid ambiguity, and also to expand abbreviations, both without further comment.  I agree that it would be &#8220;a&#8221; (no accent).  Just put the change in the report, I think. </strong></p>
<h2>II,5 Un fin Mary</h2>
<p>“Ha ha mon mary”, bars 39ff and 49ff: On reflection, I don’t think this qualifies as patter or nonsense, so I have punctuated it as a normal repetition, supplying commas between each “Ha”: “Ha, Ha mon mary…” (Without repeats, “Ha mon mary”)</p>
<p><strong>RF:  I have come to the conclusion that we must treat patter in the same way we do all other repetition.  Otherwise we will be forced to decide what is patter and what is not.  I think the only situation in one would not add comma for repetition might be when the repetition was _internal_ to the verse structure (that is, two &#8216;Ha&#8217;s&#8221; as part of a ten-syllable line.  Here, at any rate, is what we say in the Editorial Guidelines about repetitions:</strong></p>
<p><strong> </strong></p>
<ul>
<li>Punctuation for text repetitions (either indicated in the source or based on editorial suggestions) follows this rule:  the first statement of a line or part of a line is separated from the repetition by a comma.  Subsequent repetitions are also separated from each other by a comma.  There is no additional comma between the repetition and the continuation of the line to which it belongs.  The original punctuation (whether comma, colon, or period) appears at the end of the text of that line.</li>
</ul>
<p><strong> </strong></p>
<h2>II,10 Or my doint.</h2>
<p>The spelling of the title in the table has “doinbt” while the S, Ct and T have “doint”.</p>
<p>For the opening line, the B begins: “Or dieu mi Donne”, probably a misprint. I have replaced it and put a footnote.</p>
<p>Bar 9. I hesitate between “m’envoys and “m’en voys”. (I am not sure what it means: “I part”? “I am sent away?”). On the Ricercar site it is “m’en voys” but I have my doubts. In the books, B and T have a system breaks between “en” and “voys”, S and CT spell as one word (no gap between syllables). I have revised it as “m’envoys”. Do we know what was 16<sup>th</sup>-century usage?</p>
<p><strong>RF:  Our tables follow Du Chemin&#8217;s tables.  Our editions follow his texts.  This is a riddle, I know, but not sure how we can fix it, since the former are part of our electronic system.    Yes, emend the Bassus text, but I would say in this case put it in [  ] and make a note.  We say we fix orthography silently, but not whole words.   I would think that the presence of the abbreviation suggests one word, as does the general musical gesture, which ties the whole set together acoustically anyway.    Note:  Huguet explains &#8216;envoyer&#8217; as a verb used to send a request for assistance.  That&#8217;s the sense of this usage, since the speaker applies to all loyal ones, from his condition of sadness.</strong></p>
<h2>II,11 Ho le meschant</h2>
<p>“Nonsense” syllables issues :</p>
<p>Opening repetitions of “meschant” and “villain”: “meschant meschant” and “villain villain”: no comma added.</p>
<p>I am punctuating the text repetitions within the line “Et ne vault plus en bon latin” as “Et ne vault plus en bon latin, Et ne vault plus en bon latin, en bon en bon latin” &#8212; note commas after “latin” but no comma between the 2 appearances of “en bon”. Source has no punctuation separating repeats of line or bits of text within line.</p>
<p><strong>RF:  This is really one of those places where we smack our heads against our own rules.  The stuttering effect of the repetitions I think is _meant_ to exaggerate the difference between this manner of speach and &#8216;good latin&#8217;.  But we have said in our &#8216;rules&#8217; that we add commas for all internal repetitions, even when Du Chemin does not.  It is quite variable in the sources, and David Fiala tells me that his colleagues in the BVH project simply shrugged at the question of commas, since they are highly arbitrary in any case.  Where meaning breaks down, as it does here, I think we can say that our system breaks down, too!</strong></p>
<h2>II,12 Au feu</h2>
<p>T, opening line: I have tried to improve the text underlay.</p>
<p><strong>RF:  It is an odd line.  How good a composer was Martin?!</strong></p>
<h2>II,13 Cupido.</h2>
<p>Title in index has “appetiz” but all 4 voices in music have “appetitz”</p>
<p><strong>RF:  As above, we are stuck.</strong></p>
<h2>II,15 Dieu doinbt.</h2>
<p>Contents table gives spelling “Dieu doinbt le bonjour” with “b” in “doinbt” and “bonjour” looking like one word. In the voice parts, it is “doint” in all 4, and in all 4 there is a clear space between “bon” and “jour”. However, this does not necessarily mean we should interpret it as 2 words. So in the transcription I have added a hyphen: “bon-jour” to harmonise with the contents table.</p>
<p><strong>RF:  OK.</strong></p>
<h2>II,16 Allons.</h2>
<p>Bar 1, 2<sup>nd</sup> time text, first word: = “Cependant” or “Ce pendant”? In the source it looks like “Ce pendant” in all 4 voices (gap after “Ce”, no gap in “pendant”), so I have left it as two words.</p>
<p>CT, bars 6-8: underlay?? (no repeat mark for “plaisanment”).</p>
<p><strong>RF:  What does David F say?  Yes, I see only one repeat marks for plaisanment, so you can add the repetition in [ roman ].</strong></p>
<h2>II,17  Ce friant oeil</h2>
<p>Title is “Ce friant œil” in contents table but “oeil” (oe not contracted) in parts.</p>
<p>Bar 6 “coeurs”: 2 of the voices have a contraction, 2 don’t. I have left it uncontracted.</p>
<p>Optional underlay suggestions, bar 10, T. Ok.</p>
<p><strong>RF:  The title is just a question of typography, no?  I would leave it uncontracted throughout.</strong></p>
<h2>II,18 Je souffre passion</h2>
<p>Bar 7-8, 44, S and T: is this better underlay?</p>
<p>bars 6 and 44, af-fe-ction. From now on I will split all words ending in “-ction” like this.</p>
<p><strong>RF:  ct together is our new policy.  The underlay in 7-8 and 44 is another case of which rule broken first:  no syllables on small notes, or keep the melisma for the end?  Delaying &#8216;con-for&#8217; has the plus of allowing simultaneous declamation with CT and B, which perhaps add rhetorical nuance to what&#8217;s being said (a wish for self- assurance that is reflected in the &#8216;wishful&#8217; coordination).  Depends how you want to read it.</strong></p>
<h2>II,20 Qui souhaitez</h2>
<p>“Souhaitez” spelt with one “t” in table, two in vocal parts.</p>
<p>Bar 12ff, “ex-em-ple” or “e-xem-ple”. Etymology suggests it should be “ex-em-ple” on the analogy with “des-es-poir” (“ex” being a prefix: Latin “ex” + “emere”).</p>
<p>Bass, bar 25ff, comma after “au” in phrase “c’est au Soleil”. This is clearly a mistake and doesn’t conform to 16<sup>th</sup>-cent. usage. In any case, according to our majority rule, the comma disappears as it is not in the other voices.</p>
<p>23ff, CT: “Voller au ciel”. It makes sense if one assumes that the typesetter accidentally omitted a phrase:</p>
<p><strong>RF:  More chaos with the database, since I think it is two different ways here too.  OK on word division.  Right reasoning with the comma. </strong></p>
<p>What was meant to appear:</p>
<p>Voller au ciel, ij Voller au ciel</p>
<p>What actually appears:</p>
<p>ij Voller au ciel</p>
<p>I have assumed that ij refers to an omitted phrase “Voller au Ciel,”, not “audacieusement” (the word before), which does not fit.</p>
<p>According to my reckoning, the omitted phrase should appear in brackets, then there should be a phrase in italics (for the ij phrase), then one in roman. See also footnote. Do you agree?</p>
<p><strong>RF:</strong> <strong>Yes, I think the typesetter went to lunch at this point.  Clearly the first instance is [roman].  And the last is just Roman, with no brackets.  The middle one must be editorial, since it&#8217;s not an expansion of anything the typesetter put there.  So [roman] too.  But if it slips through as italics, I don&#8217;t mind.</strong><strong> </strong></p>
<h2>II,21 Qu’est il</h2>
<p>15. Placement of “second time” text. Cf II,26, bar 17,same problem. Also II,17, bar 12 – and probably other places that we don’t know until the final formatting has been done.</p>
<p>Bar 16.3 ff, Superius: I have changed word underlay. I think it is better now.</p>
<p>Bar 32.3. Footnote concerning misplaced repeat sign. Isn’t this the sort of typesetter error that we should mention in the critical commentary (along with wrong length notes/rests etc.)? By the way, this is the only case I have so far found of a misplaced repeat sign.</p>
<p><strong>RF:  I would just move &#8216;voir&#8217; down at m 14 for the second time text.  The rest of the line is OK.  With Sibelius this is easy.  Delete one &#8216;voir&#8217;  then insert a Lyric2 and re-enter.  Right, don&#8217;t emend 16.3 S.    Yes, now I see your point about the repeat sign.  Sometimes they are not misplaced, but simply the voices have different amounts of text for the second ending.  Here the guy just misread the link point, perhaps because the tied SB threw him off (cannot easily return to the middle of a note!)</strong></p>
<h2>II,22 Margot</h2>
<p>Bar 35.3. There’s no doubt the unprepared 4<sup>th</sup> (T and B) is uncanonical. Is there some expressive justification for it? I don’t think so. I am fairly sure that it was unintended. Are we just going to leave it without suggesting an alternative?</p>
<p>To explain the issue a little more clearly, I have rewritten the commentary (see footnotes and commentaries).</p>
<p><strong>RF:  Well, it&#8217;s a fairly crude poem, even by the standards of the day.  I would note the motivic connection between T m 35 and CT m 39, a correspondence that points out the word play at work between the two passages.  So on this grounds we might keep the lousy counterpoint.  No wonder the piece is anonymous.</strong></p>
<h2>II,23 La terre, l’eau</h2>
<p>Table has “La terre l’eau” without comma. Voice parts all have comma.</p>
<p>Bar 37, canonical voice, E: = E flat ficta or real E flats? I have changed it to ficta: it should definitely be E flat, given the E flat in the bass. Also, it is a canon without exact replication of major and minor intervals, so probably the flat cannot be taken as “Gospel”, so needs to be shown as ficta.</p>
<p><strong>RF:  OK on table, as we must check the Coeurdevey database.  I agree that it must be sung as E-flat.  Some canons, I suppose could be sung in transposition, and the singer would remember about the &#8216;fa&#8217; simply as part of that.  But not in this piece, with it&#8217;s odd reversals and inversions.</strong></p>
<h2>II,24. Sur la verdure</h2>
<p>I wasn’t sure of punctuation, because of the square brackets. I wanted to put the full stop somewhere, but where?</p>
<p>In the end I chose:</p>
<p>(for CT and T)</p>
<p>Quant vis qu&#8217;aul-tre d&#8217;el-le es-toit jou-ys-sant, [Quant vis qu'aul-tre d'el-le es-toit jou-ys-sant]. Sur la ver-du-re.</p>
<p>(for S and B)</p>
<p>Quant vis qu&#8217;aul-tre d&#8217;el-le es-toit jou-ys-sant, [d'el-le es-toit jou-ys-sant]. [my preference.]</p>
<p>[comma before repetition, point OUTSIDE square bracket : seems the most logical]</p>
<p><strong>RF:  Yes, this is good.</strong></p>
<p><strong> </strong></p>
<p><strong>Thanks for all these keenly observed details!</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.haverford.edu/digitalduchemin/2010/05/30/second-livre-questions-and-responses/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Literary Texts&#8211;Editorial Principles</title>
		<link>http://blogs.haverford.edu/digitalduchemin/2010/04/18/literary-texts-editorial-principles/</link>
		<comments>http://blogs.haverford.edu/digitalduchemin/2010/04/18/literary-texts-editorial-principles/#comments</comments>
		<pubDate>Sun, 18 Apr 2010 21:17:24 +0000</pubDate>
		<dc:creator>rfreedman</dc:creator>
				<category><![CDATA[Literary Texts–Editorial Principles]]></category>

		<guid isPermaLink="false">http://blogs.haverford.edu/blogs/digitalduchemin/?p=59</guid>
		<description><![CDATA[Auteur:  David Fialia (April 2010) Principes éditoriaux 1. Généralités Les textes sont exclusivement édités à partir d’une unique source musicale, même — et surtout — quand des concordances sont disponibles, comme pour les textes de poètes aussi connus que Marot ou Ronsard. La transcription doit demeurer au plus près de la source, selon les principes suivants : • [...]]]></description>
				<content:encoded><![CDATA[<p><strong>Auteur:  David Fialia (April 2010)</strong></p>
<p><strong>Principes éditoriaux</strong></p>
<p>1. Généralités</p>
<p>Les textes sont exclusivement édités à partir d’une unique source musicale, même — et surtout — quand des concordances sont disponibles, comme pour les textes de poètes aussi connus que Marot ou Ronsard.</p>
<p>La transcription doit demeurer au plus près de la source, selon les principes suivants :</p>
<p>• aucune modernisation d’orthographe ou de ponctuation, en dehors (1) du rétablissement de la distinction i/j et u/v ; (2) du remplacement de l’esperluette « &amp; » par « et » ; (3) de la résolution des abréviations (N.B. : « ñre » = « nostre », et non « notre »).</p>
<p>• conservation exacte des accents, des majuscules et de la ponctuation (N.B. : « , &amp; », transcrit par « , et », et non « et »).</p>
<p>2. Difficultés particulières</p>
<p>L’établissement d’une édition poétique à partir de sources musicales présente des difficultés spécifiques, dont la résolution est particulièrement formatrice pour des étudiants. Les deux principales difficultés sont :</p>
<p><em>a. Rétablissement de la versification</em></p>
<p>La principale difficulté inhérente à l’édition d’un poème à partir d’une source musicale est la (re)mise en forme versifiée du texte, qui est évidemment présenté de façon continue sous les portées musicales. La transcription littéraire doit donc remettre en page le poème sous sa forme versifiée, avec retour à la ligne pour chaque vers. Ce travail exige donc en fait une analyse de la versification. Ainsi, toute transcription doit être accompagnée de l’indication des rimes et de la forme métrique dans les rubriques prévues à cet effet en regard du texte.</p>
<p>Dans la plupart des sources musicales (dont, par exemple, les imprimés de Du Chemin), le texte qui figure sous la musique inclut des majuscules au début de chaque vers, ce qui permet de rétablir assez facilement la versification. Toutefois, la mise en musique du texte peut comprendre (souvent) des mots répétés et (très souvent) des reprises (musicales), sans parler du fait que toutes les voix ne chantent pas forcément tout le texte. Le transcripteur se doit d’identifier ces différents problèmes et de rétablir le poème « initial » (notamment : sans mots répétés, sauf très rares exceptions). Enfin, il existe des cas particuliers, irréguliers ou difficiles, voire insolubles, qui exigent des explications : ces difficultés doivent être présentées et discutées dans la rubrique « Commentaire », en marge de l’édition du texte.</p>
<p><em>b. Variantes entre les parties musicales</em></p>
<p>Comme l’édition est établie, dans la plupart des cas, à partir des quatre voix ou parties musicales qui constituent la norme de la polyphonie du XVIe siècle (<em>superius, altus, tenor, bassus</em>), l’éditeur doit prendre en compte les quatre textes imprimés sous chaque voix, et donc opérer des choix entre d’éventuelles variantes. Ces variantes sont le plus souvent minimes, relevant de détails de ponctuation («  : » et « , » selon les voix) ou d’orthographe (« cœur » et « cueur » selon les voix). Dans ce cas, le transcripteur est invité à opter pour la leçon la plus fréquente, sans autre commentaire. En cas de variantes plus importantes ou d’hésitation sérieuse, une note doit être ajoutée dans la rubrique « Commentaire ».</p>
<p><strong>Comité éditorial</strong></p>
<p>David Fiala</p>
<p>Richard Freedman</p>
<p>Annie Cœurdevey</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.haverford.edu/digitalduchemin/2010/04/18/literary-texts-editorial-principles/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Literary Texts&#8211;General Statements for the Project</title>
		<link>http://blogs.haverford.edu/digitalduchemin/2010/03/26/editorial-guidelines-poetic-texts/</link>
		<comments>http://blogs.haverford.edu/digitalduchemin/2010/03/26/editorial-guidelines-poetic-texts/#comments</comments>
		<pubDate>Fri, 26 Mar 2010 20:06:16 +0000</pubDate>
		<dc:creator>rfreedman</dc:creator>
				<category><![CDATA[Literary Texts–General Statements for the Project]]></category>

		<guid isPermaLink="false">http://blogs.haverford.edu/blogs/digitalduchemin/?p=42</guid>
		<description><![CDATA[Voici le &#8220;presentation&#8221; de bases de donnés Ricercare pour les textes litteraires (Auteur:  David Fialia): Présentation bases de données Ricercar : textes Du Chemin Projet de titre, à terme ? : Corpus poétique de la chanson française de la Renaissance ? (CPCFR / CorPoChaFR) Présentation Ce site est la première version d’essai d’un portail collaboratif d’édition des textes de [...]]]></description>
				<content:encoded><![CDATA[<p>Voici le &#8220;presentation&#8221; de bases de donnés Ricercare pour les textes litteraires (Auteur:  <strong>David Fialia</strong>):</p>
<p>Présentation bases de données Ricercar : textes Du Chemin</p>
<p><span style="color: #ff0000">Projet de titre, à terme ? :</span></p>
<p><span style="color: #ff0000">Corpus poétique de la chanson française de la Renaissance ? (CPCFR / CorPoChaFR)</span></p>
<p>Présentation</p>
<p>Ce site est la première version d’essai d’un portail collaboratif d’édition des textes de chansons françaises de la Renaissance, qui vise à compléter progressivement le Catalogue de la Chanson française d’Annie Cœurdevey en proposant l’édition complète des textes poétiques français conservés dans les sources musicales du XVIe siècle. Ce corpus littéraire de plusieurs milliers de poèmes, dont l’immense majorité ne figure dans aucune publication littéraire de l’époque, reste très méconnu. Son édition et son étude est susceptible d’intéresser non seulement les musicologues, mais également les historiens de la littérature, de la langue ou de la culture.</p>
<p>Ce site est un portail de publication qui permet de consulter librement un riche ensemble de textes poétiques rares ou inédits. Mais sa spécificité réside plus encore dans sa nature collaborative. Pour mener à bien dans un délai raisonnable une édition complète du vaste corpus poétique de la chanson française de la Renaissance, il offre un outil qui permet à toute personne interessée de soumettre, après accord du comité éditorial, un ensemble de transcriptions en ligne, dont l’édition est ensuite validée et rendue publique par les éditeurs du site. Cette invitation à collaborer s’adresse notamment aux enseignants de littérature, d’histoire ou de musicologie, auxquels ce programme suggère un projet pédagogique simple et formateur : faire réaliser par des étudiants la transcription littéraire en ligne de volumes choisis en accord avec le comité éditorial. Pour ce type de projets, l’équipe Ricercar propose des accès sécurisés au site d’édition et le soutien logistique de son importante collection de sources musicales en fichiers images (pdf). Pour contacter le comité éditorial, suivre ce lien [mailto : <a class="autohyperlink" href="mailto:david.fiala@univ-tours.fr" title="mailto:david.fiala@univ-tours.fr">david.fiala@univ-tours.fr</a>].</p>
<p>Cette première version du site présente l’édition des textes de près de quatre cents chansons parues dans les seize livres de Chansons nouvelles publiés par l’imprimeur Nicolas Du Chemin entre 1549 et 1568. En association avec le projet des « Livres de chansons de Nicolas Duchemin » (R. Freedman), qui a permis l’accès en ligne à toutes les sources musicales nécessaires, la transcription de ces textes a été réalisée directement sur le site par les étudiants du séminaire de Master 1 « Histoire de la musique » du CESR, lors du premier semestre 2009-2010. Ce travail a permis de finaliser l’interface de soumission et de validation éditoriale en ligne, et notamment les procédures de connexion par des comptes individuels qui garantissent la sécurité des travaux soumis.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.haverford.edu/digitalduchemin/2010/03/26/editorial-guidelines-poetic-texts/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Tasks/Devoirs</title>
		<link>http://blogs.haverford.edu/digitalduchemin/2010/03/26/tasksdevoirs/</link>
		<comments>http://blogs.haverford.edu/digitalduchemin/2010/03/26/tasksdevoirs/#comments</comments>
		<pubDate>Fri, 26 Mar 2010 20:05:13 +0000</pubDate>
		<dc:creator>rfreedman</dc:creator>
				<category><![CDATA[Tasks/Devoirs]]></category>

		<guid isPermaLink="false">http://blogs.haverford.edu/blogs/digitalduchemin/2010/03/26/tasksdevoirs/</guid>
		<description><![CDATA[Some Challenges for the Next Phase of our work: How to manage the flow of work? Each file now passes through several stages on its way to publication.   We need a clear system for knowing what needs to be done next with each file.  With so many &#8216;lieutenants&#8217; in charge of the materials (from Chater [...]]]></description>
				<content:encoded><![CDATA[<h2>Some Challenges for the Next Phase of our work:</h2>
<p><strong>How to manage the flow of work?</strong> Each file now passes through several stages on its way to publication.   We need a clear system for knowing what needs to be done next with each file.  With so many &#8216;lieutenants&#8217; in charge of the materials (from Chater to Freedman to Besson and then to Busson), we need a place to keep a list of what has been validated, and what has not. This is especially tricky, since we mainly correspond by email, and have no single place to look at where things stand.   Could a table on our editors blog do this?</p>
<p><strong>What might users want to know about the site? </strong> What kinds of projects or work might be suitable for them to share with still others?  Classroom assignments?  Transcriptions?  Reconstructions?  How should we manage this as part of the <em>public blog</em> for the project?  See the examples started here on the <a href="http://blogs.haverford.edu/chansonniers/">Public Du Chemin Blog.</a></p>
<p><strong>How might our projects be better integrated or coordinated with each other? </strong> We are already building some connections among the Coeurdevey/Freedman/Fiala projects (database, Du Chemin editions-facsimiles, Du Chemin literary texts).  What sorts of standards will allow these projects to work more smoothly with each other?  Would further work with the <a href="http://dublincore.org/">Dublin-Core standard</a> help us link these (and other) resources more effectively, allowing users to find related materials by author, text, printer/scribe, date, etc?</p>
<p><strong>How will users save, bookmark, and export what they find in these resources?</strong> Will users be able to <em>cite</em> a particular page or transcription using a unique and stable URL?    Will they be able to <em>save</em> the results of searches (or export them) in some way?  Might tools like <a href="http://www.collex.org/?page_id=2">Collex</a> serve as a way for users to assemble their own &#8220;bookshelves&#8221; of digital documents and references, citing our resources as part of their research and publication?   See <a href="http://www.nines.org/">Nines.org</a> And how will they inform us of what they are doing with these resources?</p>
<p><strong>What digital tools might allow us to produce new kinds of editions and critical reports? </strong>The <a href="http://www.tei-c.org/index.xml">Text Encoding Initiative</a> has in recent years emerged as a powerful standard for digital editions.  Now a new initiative aims to produce the same kind of standard for music:  <a href="http://www.music-encoding.org">Music Encoding Initiative (MEI</a>).  Might a tool like this be a way to create digital music editions?  Digital critical reports of musical variants?  See this example of an edition with variants: <a href="http://www.haverford.edu/music/faculty/freedman/DuChemin/(10) Si la promesseRF-variants.pdf">Si la promesse</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.haverford.edu/digitalduchemin/2010/03/26/tasksdevoirs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Editorial Guidelines&#8211;Music</title>
		<link>http://blogs.haverford.edu/digitalduchemin/2010/03/26/editorial-guidelines-music/</link>
		<comments>http://blogs.haverford.edu/digitalduchemin/2010/03/26/editorial-guidelines-music/#comments</comments>
		<pubDate>Fri, 26 Mar 2010 20:04:53 +0000</pubDate>
		<dc:creator>rfreedman</dc:creator>
				<category><![CDATA[Editorial Guidelines–Music]]></category>

		<guid isPermaLink="false">http://blogs.haverford.edu/blogs/digitalduchemin/2010/03/26/editorial-guidelines-music/</guid>
		<description><![CDATA[Some provisional principles for the musical transcriptions.  Author:  Richard Freedman Musical Transcriptions. The base text in all cases is from the Chansons nouvelles series of Du Chemin.  By far the majority of the works issued in this series were first editions; many appear uniquely in this set.   [Note:  the Music Encoding Initiative (www.mei.org) will eventually [...]]]></description>
				<content:encoded><![CDATA[<p>Some provisional principles for the musical transcriptions.  <strong>Author:  Richard Freedman</strong></p>
<p><strong>Musical Transcriptions.</strong> The base text in all cases is from the <span style="text-decoration: underline">Chansons nouvelles</span> series of Du Chemin.  By far the majority of the works issued in this series were first editions; many appear uniquely in this set.   [Note:  the Music Encoding Initiative (<a href="http://www.mei.org/">www.mei.org</a>) will eventually make it possible to combine features of the single-text approach with those of a critical edition, at least for those compositions appearing in other sources of the sixteenth century.]</p>
<ul>
<li>In the musical transcriptions we have <span style="text-decoration: underline">retained the original note values</span>, and of course both added bar lines and arranged the individual parts in score format.  One <em>tempus</em> in the original notation thus corresponds to one measure in the modern transcription.</li>
<li><span style="text-decoration: underline">Modern clefs</span> are used in the transcriptions; <span style="text-decoration: underline">original clefs</span> can be seen via the <em>incipits</em>.  The incipits include original notation up to and including the first note of the given part.</li>
<li><span style="text-decoration: underline">Flat and sharp signs</span> appearing on the staff itself are found in the original sources.  Those appearing above the staff in the modern transcription are implied by contrapuntal contexts—in order to avoid forbidden intervals with other signed alterations, or in order to create complete cadences.</li>
<li><span style="text-decoration: underline">Ligatures</span> have been marked above the notes they connect, and serve to confirm text underlay by preventing a change of syllable.</li>
<li><span style="text-decoration: underline">Coloration</span> in the original notation (indicating a shift from duple to triple mensuration at a given level) has been transcribed without special indication.</li>
<li><span style="text-decoration: underline">Repeat signs</span> in the original parts have been retained in the modern transcriptions.  First and second endings have been regularized among the voice parts.</li>
<li><span style="text-decoration: underline">Emendations</span> to correct obvious errors or missing notes are recorded in the <span style="text-decoration: underline">critical commentary</span> for each piece.</li>
<li>Most of the chansons are unique to the Du Chemin <em>Chansons nouvelles</em> series.  For compositions appearing in other sources of the 16th century, we note concordances and variants (if any) in the <span style="text-decoration: underline">critical commentary</span> for each piece.</li>
</ul>
<p><strong>Text Underlay.</strong> Text underlay follows a number of basic principles:</p>
<ul>
<li> In all cases we use Du Chemin’s books as a guide.   His typesetters had a careful eye for the alignment of text and musical notation as it is known in some music-theoretical writings of the mid sixteenth century.</li>
<li>Phrases proceed syllabically, saving extra notes for the penultimate syllable of the line.</li>
<li>The last note of each phrase normally receives the last syllable of the poetic line.</li>
<li><span style="text-decoration: underline">Repetitions of words</span>, or parts of poetic lines, are sometimes indicated in the original sources (either through written out repetitions or by <em>ii</em>.  These appear in <span style="text-decoration: underline">roman type</span> in the modern editions.  Repetitions in <span style="text-decoration: underline">italic type</span> are modern editorial interventions undertaken according to ideals set out in theoretical writings of the period.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://blogs.haverford.edu/digitalduchemin/2010/03/26/editorial-guidelines-music/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Links and Resources</title>
		<link>http://blogs.haverford.edu/digitalduchemin/2009/03/15/links/</link>
		<comments>http://blogs.haverford.edu/digitalduchemin/2009/03/15/links/#comments</comments>
		<pubDate>Sun, 15 Mar 2009 21:12:33 +0000</pubDate>
		<dc:creator>rfreedman</dc:creator>
				<category><![CDATA[2010 Discussions]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Links]]></category>

		<guid isPermaLink="false">http://blogs.haverford.edu/blogs/digitalduchemin/?p=39</guid>
		<description><![CDATA[CESR Du Chemin Project CESR Programme Ricercar CESR Bibliothèques virtuelles humanistes National Endowment for the Humanities Office of Digital Humanities Dublin Core Metadata Text Encoding Initiative Music Encoding Initiatve (MEI-C.org) University of Chicago Artfl Project:  Dictionnaire d&#8217;autrefois Jenni Bloxam’s St. Donation Mass Project: Jennifer Thomas’s Motet Database DIAMM  [Facsimile and Catalog Project] CMME  [Digital Music [...]]]></description>
				<content:encoded><![CDATA[<p><a href="http://ricercar.cesr.univ-tours.fr/3-programmes/EMN/duchemin/">CESR  Du Chemin Project</a></p>
<p><a href="http://ricercar.cesr.univ-tours.fr/3-programmes/EMN/duchemin/"></a><a href="http://ricercar.cesr.univ-tours.fr/index.htm">CESR Programme Ricercar</a></p>
<p><a href="http://www.bvh.univ-tours.fr/">CESR Bibliothèques virtuelles humanistes</a></p>
<p><a href="http://www.neh.gov/odh/">National Endowment for the Humanities<br />
Office of Digital Humanities</a></p>
<p><a href="http://dublincore.org/">Dublin Core Metadata</a></p>
<p><a href="http://http://www.tei-c.org/index.xml">Text Encoding Initiative</a></p>
<p><a href="http://www.mei-c.org">Music Encoding Initiatve (MEI-C.org)</a></p>
<p><a href="http://http://artfl-project.uchicago.edu/node/17">University of Chicago Artfl Project:  Dictionnaire d&#8217;autrefois</a></p>
<p><a href="http://webdev.williams.edu/obrecht/era.php">Jenni Bloxam’s St. Donation Mass Project:</a></p>
<p><a href="http://www.arts.ufl.edu/motet/default.asp">Jennifer Thomas’s Motet Database</a></p>
<p><a href="http://www.diamm.ac.uk/index.html">DIAMM  [Facsimile and Catalog Project]</a></p>
<p><a href="http://www.cmme.org/">CMME  [Digital Music Editions]</a></p>
<p><a href="http://www.undoulxregard.org/chansonniers/index.html">Loire Valley Chansonniers </a>(Concordance and Facsimile to Mellon Chansonnier, with Laborde, Copenhagen, Dijon, and Wolfenbuttel):</p>
<p><a href="http://chansonniers.pwch.dk/">Copenhagen Chansonnier Project</a></p>
<p><a href="http://lcweb2.loc.gov/diglib/ihas/loc.natlib.ihas.200152631/default.html">Laborde Chansonnier Facsimile</a></p>
<p><a href="http://diglib.hab.de/mss/287-extrav/start.htm">Wolfenbuttel Chansonnier Facsimile</a></p>
<p><a href="http://beinecke.library.yale.edu/dl_crosscollex/SetsSearchExecXC.asp?srchtype=ITEM">Mellon Chansonnier Facsimile</a></p>
<p><a href="http://www.kb.nl/galerie/gruuthuse/book.html">Dutch National Library Medieval Songbook Project</a></p>
<p><a href="http://www.princeton.edu/~rwegman/mass.htm">Rob Wegman—Renaissance Mass Project</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.haverford.edu/digitalduchemin/2009/03/15/links/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>And now, a working version . . .</title>
		<link>http://blogs.haverford.edu/digitalduchemin/2009/03/03/and-now-a-working-version/</link>
		<comments>http://blogs.haverford.edu/digitalduchemin/2009/03/03/and-now-a-working-version/#comments</comments>
		<pubDate>Tue, 03 Mar 2009 16:55:45 +0000</pubDate>
		<dc:creator>rfreedman</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.haverford.edu/blogs/digitalduchemin/?p=33</guid>
		<description><![CDATA[Our Colleagues at the CESR have made some excellent progress towards a working model of the site.  Follow the link below and see what you think of the basic functions, layout.  Of course there will be changes, but this should give a sense of how things work. So far, you can search (but only the [...]]]></description>
				<content:encoded><![CDATA[<p>Our Colleagues at the CESR have made some excellent progress towards a working model of the site.  Follow the link below and see what you think of the basic functions, layout.  Of course there will be changes, but this should give a sense of how things work.</p>
<p>So far, you can search (but only the Premier livre has full images and transcriptions), scroll through books, toggle among the voice parts, download PDFs, and download transcriptions.</p>
<p><a href="http://ricercar.cesr.univ-tours.fr/3-programmes/EMN/duchemin/">Test Version of the Du Chemin Site</a></p>
<p>If you would like to PLAY the transcriptions using Sibelius Scorch player, you will need to install the Scorch player using the link below.</p>
<p><a href="http://www.sibelius.com/cgi-bin/download/get.pl?com=sh&amp;prod=scorch">Instructions for Scorch Download</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.haverford.edu/digitalduchemin/2009/03/03/and-now-a-working-version/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
