<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Palatino Linotype";
panose-1:2 4 5 2 5 5 5 3 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Palatino Linotype","serif";
color:#1F497D;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The backwards c with a hook pictured at the bottom of p. 188 of DCRM(B) and treated as a contraction (for con) is listed as a tironian notae in Brown, M.P. A guide to western historical scripts, from antiquity to 1600, 1990 (p. 136).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>When I discussed this rule change with Svato Schutzner, our rare book cataloger emeritus here at the Library of Congress, he was horrified. Because of this, I always note if the transcribed "&" is actually representing a tironian sign.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Anna R. Bryan<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Senior Cataloger<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Rare Materials Section<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>US Anglo Division<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Library of Congress<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Washington, DC 20540<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I speak only for myself.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> dcrm-l-bounces@lib.byu.edu [mailto:dcrm-l-bounces@lib.byu.edu] <b>On Behalf Of </b>Deborah J. Leslie<br><b>Sent:</b> Friday, August 19, 2011 12:08 PM<br><b>To:</b> DCRM Revision Group List<br><b>Subject:</b> Re: [DCRM-L] Question about Tironian notes in DCRM(B)<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-family:"Palatino Linotype","serif";color:#1F497D'>There were a number of difficulties with that instruction for printed books, which I suspected stemmed from a confusion of ampersand and tironian signs. Not available to us at the time, there is a cool wikipedia article on the ampersand, which confirms my conclusion:<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The ampersand should not be confused with the <a href="http://en.wikipedia.org/wiki/Tironian_notes" title="Tironian notes">Tironian "et"</a> (“⁊”), which is a symbol similar to the numeral <i>7</i>. Both symbols have their roots in the classical antiquity, and both signs were used up through the Middle Ages as a representation for the Latin word "et" ("and"). However, while the ampersand was in origin a common ligature in the everyday script, the Tironian "et" was part of a highly specialised stenographic <a href="http://en.wikipedia.org/wiki/Shorthand" title=Shorthand>shorthand</a>.<sup><a href="http://en.wikipedia.org/wiki/Ampersand#cite_note-7">[8]</a> </sup><a href="http://en.wikipedia.org/wiki/Ampersand">http://en.wikipedia.org/wiki/Ampersand</a> <o:p></o:p></p><p class=MsoNormal><span style='font-family:"Palatino Linotype","serif";color:#1F497D'>If we can verify the information in the wikipedia paragraph, i.e., that one can only properly call the 7-shaped symbol a tironian et when it was used with other Tironian signs in a document, we may want to reconsider 0G8.2 when we revise DCRM(B). I don't think I've ever seen actual Tironian signs (i.e., the systematic shorthand) in a printed book. Have any of you?<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Palatino Linotype","serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#0070C0'>Deborah J. Leslie, M.A., M.L.S. | Head of Cataloging, Folger Shakespeare Library | 201 East Capitol St., S.E. | Washington, D.C. 20003<br><a href="mailto:djleslie@folger.edu"><span style='color:#0070C0'>djleslie@folger.edu</span></a></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#0070C0'>| 202.675-0369 | <a href="http://www.folger.edu/"><span style='color:#0070C0'>http://www.folger.edu</span></a> <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Palatino Linotype","serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> dcrm-l-bounces@lib.byu.edu [mailto:dcrm-l-bounces@lib.byu.edu] <b>On Behalf Of </b>Manon Theroux<br><b>Sent:</b> Thursday, 18 August, 2011 19:44<br><b>To:</b> DCRM Revision Group List<br><b>Subject:</b> Re: [DCRM-L] Question about tironian notes in DCRM(B)<o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Hi, Jenny-<br><br>This page has links to the discussion papers from the DCRM Conference, held 10-13 March, 2003, at Yale University:<br><a href="http://www.rbms.info/committees/bibliographic_standards/dcrm/dcrmtext.html">http://www.rbms.info/committees/bibliographic_standards/dcrm/dcrmtext.html</a><br><br>If you scroll down to the Conference section, look under Working Group 2, and click to open "Transcription Issues 1" (a discussion paper written by Deborah J. Leslie & Benjamin Griffin), you'll find the following on p. 18:<br><br>===<br>4.1. Tironian sign. The Gothic font’s “tironian sign” should be transcribed as an ampersand, since it is the black-letter analogue for what appears as an ampersand in roman type. Both are derived from MS. contractions of Latin “et”. (This was the decision arrived at by the Bibliographic Standards Committee at the ALA annual meeting in 1999).<br>===<br><br>Unfortunately, I don't find anything about the Tironian sign in the BSC minutes from 1999. The closest thing I could find there was: "Treat an ampersand as an ampersand."<br><br>-Manon<o:p></o:p></p><div><p class=MsoNormal>On Wed, Aug 17, 2011 at 7:26 PM, <<a href="mailto:jnelson@law.berkeley.edu">jnelson@law.berkeley.edu</a>> wrote:<o:p></o:p></p><p>Dear DCRM-Listers,<br>I was asked the below question by someone from the Latin for Catalogers workshop. Since it is a little out of my purview and expertise, I thought I would put it to this group.<br>Best regards,<br>Jenny<br><br>Question:<br><br>"...In DCRB, catalogers were instructed to transcribe the Tironian sign for "et" as "[et]" if they were unable to reproduce it. DCRMB 0G8.2 says to transcribe a Tironian sign as an ampersand without brackets. When DCRMB was published, I didn't understand the reason for this change, and I still don't. To me it seems better to transcribe a Trionian sign as '[et]' because it is from a special shorthand system and the ampersand was created from the ligature of the word 'et' ... do you have any insight into this rule change?"<o:p></o:p></p><p> <o:p></o:p></p><pre style='margin-bottom:12.0pt'>-- <br>Jennifer K. Nelson<br>Reference Librarian<br>The Robbins Collection<br>UC Berkeley School of Law (Boalt Hall)<br>Berkeley, CA 94720<br><a href="mailto:jnelson@law.berkeley.edu" target="_blank">jnelson@law.berkeley.edu</a><o:p></o:p></pre><pre style='margin-bottom:12.0pt'>Tel: <a href="tel:510.643.9709" target="_blank">510.643.9709</a><br>Fax: <a href="tel:510.642.8325" target="_blank">510.642.8325</a><br><a href="http://www.law.berkeley.edu/library/robbins/" target="_blank">www.law.berkeley.edu/library/robbins/</a><o:p></o:p></pre><pre style='margin-bottom:12.0pt'><o:p> </o:p></pre></div><p class=MsoNormal><o:p> </o:p></p></div></body></html>