<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:m="http://schemas.microsoft.com/office/2004/12/omml" 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 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Nirmala UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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 bgcolor=white lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p><span style='color:windowtext'>Dear Kuldeep and NBGP members,<o:p></o:p></span></p><p><span style='color:windowtext'>IP has suggested some minor edits to consider before final submission of the proposal, listed in their message below. <o:p></o:p></span></p><p><span style='color:windowtext'>As next steps, once these edits are incorporated, the proposal will be published at the <a href="https://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en">proposals’ webpage</a> as the final version after public comment, and then IP will undertake its evaluation.<o:p></o:p></span></p><div><div><p><span style='color:windowtext'>Regards,<br>Sarmad</span><o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p>TO: NeoBrahmi Generation Panel<br>FROM: Integration Panel<o:p></o:p></p><p>We have reviewed the updated Oriya proposal dated 20 Feb 2019 and found several issues that require a quick fix, plus a few additional suggestions for improved text. In one case identical text in DOCx and XML relies on terminology not defined in either document - this requires new text to be written by the GP that gives the necessary explanation in terms the (non-native/non-expert) reader can follow.<o:p></o:p></p><p>The required fixes apply to both the document and the XML.<o:p></o:p></p><p>There is an additional MUST FIX item each for DOCx and XML as a result of clerical error in preparing the LGR. <br><br>Additional edits are recommended to the attention of the GP.<o:p></o:p></p><p>- Integration Panel<o:p></o:p></p><p><o:p> </o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>DOCX</b>:<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>(1) MUST FIX: on p. 20 the Unicode name for 0B2F was unaccountably changed from YA to JA and now incorrectly duplicates the name for 0B1C. (Oriya has both a JA and a YA.) <o:p></o:p></p></div><div><p class=MsoNormal>This change should be backed out and the correct character name YA used for 0B2F.<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>(2) both the proposal and the XML mention the word "varga" without explaining it. This is most likely due to some copying and pasting of text from other proposals. However, non-specialist readers will not be able to understand the description of Anusvara in Oriya if it relies on terms not introduced in the proposal document. Here are the two uses in Section 3.11:<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>"that particular varga" --- which one?<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>"non-varga consonant" --- what is that?<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br><br><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>This should definitely be fixed, even if it requires a bit of new/rewritten text. The IP recommendation is to either rewrite the description without relying on the term "varga", or find a way to gloss the term in passing; alternatively, provide a fuller discussion (more appropriate for the DOCx than the XML).<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>XML</b><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>In the Section "Character Classes"<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>(1) the subsection for Halant could be edited as follows:<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <p>Halant: A Halant, also known as Virama, is used after a consonant to "strip" <br> it of its inherent vowel. The Halant form of a consonant is the form produced by adding the Halant, <br> encoded as U+0B4D (<span lang=OR style='font-family:"Nirmala UI",sans-serif'> ୍ ) </span>ORIYA SIGN VIRAMA<br> to the nominal shape. A Halant follows all but the last consonant in every Oriya <br> syllable. More details in Section 3.7, "The Implicit Vowel Killer Halant" of the [Proposal].</p><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The subsection header should be the name of the character class, not the title of the section in the proposal; other suggested edits are for consistency.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>(2) This also applies to the subsection for Visarga:<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <p>Visarga: U+0B03 ORIYA SIGN VISARGA is frequently used in Sanskrit and represents a sound <br> very close to /h/. More details in Section 3.9, "Visarga & Avagraha" of the [Proposal].</p><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The "Avagraha" is not part of the repertoire in this XML and therefore this subsection should be named only after the Visarga (even if the proposal subsection does discuss both).<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br><br><o:p></o:p></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>(3) Nasalization: Candrabindu: section in <description>.<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>First, "Nasalization" is not a character class, therefore, it ought to be made a subheader.<o:p></o:p></p></div><div><p class=MsoNormal>Change <p>Nasalization: Candrabindu ... <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>to <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <h3>Nasalization:</h3><br> <p>Candrabindu....<o:p></o:p></p></div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>(4) in the Anusvara: section, there is the use of "varga" which is not explained in the XML (and which presents a real problem for the integrated Root Zone LGR as users are normally not expected to read the [Proposal] first.)<o:p></o:p></p></div><div><p class=MsoNormal>This must be reformulated (see comment for DOCx above). The same (or similar) language should be used in both DOCx and XML, if possible, but keeping in mind the different focus: readers of the XML care more about how a character class is used in identifiers than how it features in writing text. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>This is a MUST FIX.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>(5) in the WLE rules section, perhaps add the number of each WLE rule as follows:<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <li>1. N: must be preceded only by C1</li><br> <li>1. B: must be preceded by V, C, N or M</li><br> <li>3. X: must be preceded by V, C, N or M</li><br> <li>4. D: must be preceded by V, C, N or M</li><br> <li>5. H: must be preceded by C or N</li><br> <li>6. M: must be preceded by C or N</li><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>(6) MUST FIX:<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> In the XML, the type attribute of the <var> elements for 101D and 1031 should be "out-of-repertoire-var" and not "out-of-repertoire".<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><o:p> </o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>TXT</b><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <b><i>No changes, so not tested.</i></b><o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br><br><o:p></o:p></p></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>