<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<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 name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:"Palatino Linotype";
panose-1:2 4 5 2 5 5 5 3 3 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.normalbold
{mso-style-name:"normal + bold";
font-weight:bold;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Palatino Linotype","serif";
color:#1F497D;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Palatino Linotype","serif";
color:#993366;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Palatino Linotype","serif";
color:#003300;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</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=Section1>
<p class=MsoNormal><span style='color:#1F497D'>New proposed change, formatted
as HTML with crossed-out and underlined text (see below for version all in
plain text, if your e-mail client doesn’t show HTML): <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Palatino Linotype","serif"'>If the
rules for capitalization require converting the letters <b><s>i/j</s></b><s> or
<b>u/v</b> to uppercase or lowercase</s> <b>I</b> or <b>V</b> to lowercase, or <b>i</b>,
<b>j</b>, <b>u</b>, or <b>v</b> to uppercase, follow the pattern of usage in
the text <u>to determine which graph to use</u>.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Plain-text version of the above,
if the crossings-out and underlinings don’t show up for you:<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>EXISTING: If the rules for
capitalization require converting the letters <b>i/j</b> or <b>u/v</b> to
uppercase or lowercase, follow the pattern of usage in the text.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>PROPOSED: If the rules for
capitalization require converting the letters <b>I</b> or <b>V</b> to
lowercase, or <b>i</b>, <b>j</b>, <b>u</b>, or <b>v</b> to uppercase, follow
the pattern of usage in the text to determine which graph to use.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'> EB.</span><span
style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<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> Wednesday, December 08, 2010 11:21 AM<br>
<b>To:</b> DCRM Revision Group List<br>
<b>Subject:</b> Re: [DCRM-L] FW: Correction Re: DPC: Wording of i/j u/v
conversionin DCRM<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";
color:#003300'>Sounds good. Can you do a better-and-after textual comparison?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";
color:#003300'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<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>Erin
Blake<br>
<b>Sent:</b> Wednesday, 08 December, 2010 09:53<br>
<b>To:</b> DCRM Revision Group List<br>
<b>Subject:</b> Re: [DCRM-L] FW: Correction Re: DPC: Wording of i/j u/v
conversioninDCRM<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Thinking about this some more
(and with apologies to Deborah, since she’s not in her office, and I can’t talk
with her in person first) I’m back to thinking the existing wording <i>isn’t</i>
fine: "If the rules for capitalization require converting the letters <b>i/j</b>
or <b>u/v</b> to uppercase or lowercase, follow the pattern of usage in the
text” is technically correct, but misleading. Yes, follow the pattern of use:
if <b>J</b> needs to be converted to lowercase, the pattern of use happens to
always be <b>J</b> > <b>j</b> so it’s very easy to determine. But it’s also
true that patterns of use show <b>A</b> > <b>a</b>, <b>B</b> > <b>b</b>,
and so on. Mentioning <b>J</b> and <b>U</b> at all, when there’s nothing
special about them, is confusing.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>“If the rules for capitalization
require converting the letters <b>I</b> or <b>V</b> to lowercase, or <b>i</b>, <b>j</b>,
<b>u</b>, or <b>v</b> to uppercase, follow the pattern of usage in the text” is
also correct, but clearer. (Especially with the comma added, as Margaret
Nichols just pointed out). <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Additional possibility: expand
the sentence to clarify that conversion of case will sometimes, but not always,
involve changing the graph. That’s the point of DCRM(B) 0G2.2, but it doesn’t
explicitly say so. In other words, change it to: “If the rules for
capitalization require converting the letters <b>I</b> or <b>V</b> to
lowercase, or <b>i</b>, <b>j</b>, <b>u</b>, or <b>v</b> to uppercase, follow
the pattern of usage in the text to determine which graph to use.”<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'> EB.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<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> Tuesday, December 07, 2010 4:18 PM<br>
<b>To:</b> DCRM Revision Group List<br>
<b>Subject:</b> [DCRM-L] FW: Correction Re: DPC: Wording of i/j u/v conversion
inDCRM<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";
color:#1F497D'>Erin and I just spoke about this. The existing wording is
actually just fine; some of the confusion in this instance appears to arise the
fact that there are two types of conversion going on: converting case (e.g., I
to i), and converting graph while converting case (i.e., V to u). <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";
color:#1F497D'>Our solution: Add the note that uppercase J or U signals a
modern distribution in 0G2, to let people know at that point that they don't
need to look for usage in the text for that particular letter. (Keep in mind
that distinction of the letter J as its own letter, and of U as its own letter,
didn't necessarily happen at the same time.) That's probably enough, but if
people want even more guidance, add to the table "Uppercase letter to be
converted" in Appendix G: J </span><span style='font-size:12.0pt;
font-family:Wingdings;color:#1F497D'>à</span><span style='font-size:12.0pt;
font-family:"Palatino Linotype","serif";color:#1F497D'> j and U </span><span
style='font-size:12.0pt;font-family:Wingdings;color:#1F497D'>à</span><span
style='font-size:12.0pt;font-family:"Palatino Linotype","serif";color:#1F497D'>
u <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Verdana","sans-serif";
color:#1F497D'>_________________________</span><span style='color:#1F497D'> <br>
</span><span style='font-size:9.0pt;color:#1F497D'>Deborah J. Leslie, M.A.,
M.L.S. <br>
RBMS past chair 2010-2011 | Head of Cataloging, Folger Shakespeare Library <br>
201 East Capitol St., S.E. | Washington, D.C. 20003 | 202.675-0369 <br>
djleslie@folger.edu | <a href="http://www.folger.edu/">http://www.folger.edu</a>
<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<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>Erin
Blake<br>
<b>Sent:</b> Tuesday, 07 December, 2010 15:48<br>
<b>To:</b> dcrm-l@lib.byu.edu<br>
<b>Subject:</b> [DCRM-L] DPC: Wording of i/j u/v conversion in DCRM<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Last DPC of the season, if we're sticking to one a week: As
some of you know, this came up at the BSC meeting at Annual, when it became
clear that there was confusion about the phrase "If the rules for
capitalization require converting the letters <span class=normalbold>i/j</span>
or <span class=normalbold>u/v</span> to uppercase or lowercase..."
because, in fact, "uppercase or lowercase" aren't reciprocal here. It
will never be the case that an uppercase <b>J</b> or <b>U</b> will be converted
to lowercase, see footnote 26 in Appendix G, which reads "An uppercase<b>
J</b> or <b>U</b> in the source signals a modern distribution, in which <b>i</b>
and<b> j</b> are functioning as separate letters, as are <b>u</b> and <b>v</b>,
requiring no special consideration while converting case." <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Proposed change: replace the standard phrase as follows...<o:p></o:p></p>
<p class=MsoNormal>Existing wording: If the rules for capitalization require
converting the letters<span class=normalbold> i/j</span> or <span
class=normalbold>u/v</span> to uppercase or lowercase.<o:p></o:p></p>
<p class=MsoNormal>New wording: If the rules for capitalization require
converting the letters<span class=normalbold> I</span> or <span
class=normalbold>V</span> to lowercase or<span class=normalbold> i</span>, <span
class=normalbold>j</span>, <span class=normalbold>u</span>, or <span
class=normalbold>v</span> to uppercase.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Discussion is open to anyone through DCRM-L for one week. BSC
members will be asked to vote on the proposed change on December 14.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal> EB.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>--------------------------------------------------<o:p></o:p></p>
<p class=MsoNormal>Erin C. Blake, Ph.D. | Curator of Art &
Special Collections | Folger Shakespeare Library | 201 E.
Capitol St. SE | Washington, DC 20003-1004 | office tel.
(202) 675-0323 | fax: (202) 675-0328 |
eblake@folger.edu | www.folger.edu<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>