<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=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
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="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Thanks very much for your feedback Caroline. See in-line for my responses.<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'>Rex<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'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Arms, Caroline [mailto:caar@loc.gov] <br><b>Sent:</b> Tuesday, June 9, 2015 4:06 PM<br><b>To:</b> 'Rex Jaeschke'; SC 34 WG4<br><b>Cc:</b> TC45<br><b>Subject:</b> RE: PLEASE PROOF: Final Drafts of 29500-1:2015 and 29500-4:2015 Posted to the SC 34/WG4 Site for Proofing. Feedback due by 2015-07-10<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>Rex,<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'>Here are checks of six of my ten DRs. I’m afraid I did find 2 or 3 problems.<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'> To be continued. Caroline<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoPlainText><b>DR 14-004<o:p></o:p></b></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>CT_Font does appear to be defined at line 3797. But the link in<o:p></o:p></p><p class=MsoPlainText>18.8.22 still doesn't work.<o:p></o:p></p><p class=MsoPlainText><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoPlainText><span style='color:#1F497D'>Rex> Agreed; will fix.<o:p></o:p></span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>If you look at the definition for CT_Fonts in A.2 (line 3484) its element CT_Font doesn't link to anything either. Same bad link in CT_Dxf. Does that indicate that a problem remains?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><span style='color:#1F497D'>Rex> Agreed; will fix.<o:p></o:p></span></p><p class=MsoPlainText><b><span style='color:#1F497D'><o:p> </o:p></span></b></p><p class=MsoPlainText><b>DR 13-004<o:p></o:p></b></p><p class=MsoPlainText> superseded by<o:p></o:p></p><p class=MsoPlainText><b>DR 13-009</b> (edits are in N270)<o:p></o:p></p><p class=MsoPlainText> All looks OK (in Parts 1 and 4), assuming that the diagrams in deleted clauses in L.7.3.4 are really deleted. I believe they are but it will be worth checking.<o:p></o:p></p><p class=MsoPlainText><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoPlainText><span style='color:#1F497D'>Rex> I’ll check this when I adopt the changed.<o:p></o:p></span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><b>DR 12-0012</b> OK<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><b>DR 09-0040</b> (complex font stuff!!!)<o:p></o:p></p><p class=MsoPlainText>in 17.3.2.26, the added example is incorporated correctly, but I note that it mentions the two-step algorithm, before the algorithm has been introduced. I would add "below" following "algorithm" in its first occurrence in the Example.<o:p></o:p></p><p class=MsoPlainText><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoPlainText><span style='color:#1F497D'>Rex> Agreed; will fix.<o:p></o:p></span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Table entry on page 303 for cs (Complex Script Font) is missing the insertion of <w:cs /> in the sample markup<o:p></o:p></p><p class=MsoPlainText><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoPlainText><span style='color:#1F497D'>Rex> Agreed; will fix.<o:p></o:p></span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Same problem on 304 for<o:p></o:p></p><p class=MsoPlainText>cstheme (Complex Script Theme Font) is missing the insertion of<o:p></o:p></p><p class=MsoPlainText><w:cs /> in the sample markup<o:p></o:p></p><p class=MsoPlainText><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoPlainText><span style='color:#1F497D'>Rex> Agreed; will fix.<o:p></o:p></span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Everything else OK.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><b>DR 12-0005<o:p></o:p></b></p><p class=MsoPlainText>Replacement diagrams in 17.7.2 and 17.7.3 are not showing up properly in the PDF.<o:p></o:p></p><p class=MsoPlainText><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoPlainText><span style='color:#1F497D'>Rex> Agreed; will fix.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoPlainText><b>DR 12-0003</b> OK<o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='color:#1F497D'>Caroline Arms<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Library of Congress Contractor<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Co-compiler of Sustainability of Digital Formats resource <a href="http://www.digitalpreservation.gov/formats/">http://www.digitalpreservation.gov/formats/</a><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'>** Views expressed are personal and not necessarily those of the institution **<o:p></o:p></span></p></div><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 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'> Rex Jaeschke [<a href="mailto:rex@RexJaeschke.com">mailto:rex@RexJaeschke.com</a>] <br><b>Sent:</b> Wednesday, June 03, 2015 11:58 AM<br><b>To:</b> SC 34 WG4<br><b>Cc:</b> TC45<br><b>Subject:</b> PLEASE PROOF: Final Drafts of 29500-1:2015 and 29500-4:2015 Posted to the SC 34/WG4 Site for Proofing. Feedback due by 2015-07-10<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Some months ago, balloting ended on CORs for Parts 1 and 4 of 29500. Both ballots passed.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have applied the edits in each COR to the corresponding standard from 2012 to create a 2015 edition. As this new edition contains no new material beyond what was adopted in the ballots, no further balloting is necessary; this is an editorial task.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>However, before I submit the final versions to ISO for publication, I’m giving WG4 (and Ecma TC45) members a chance to review the final drafts to make sure I applied all the edits correctly. In the case of Part 1, there are some 250 sets of edits. I don’t expect members to check all of them, but if each member randomly chose 10 of them and checked those, we’ll likely get good coverage.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The changes are tracked, and both DOCX and PDF versions are included for each Part. Don’t be concerned if you see some bright blue edits, as they will be “fixed” when I finally adopt the tracked changes.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Part 4 contains some manual pointers into Part 1, but these have not yet been updated. I will do that once Part 1’s tracked changes have been adopted, and that Part is frozen.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have posted to Livelink the 49-MB and 13-MB zip files as documents 2015-0309 and 2015-0310, respectively. Only registered members can access these.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Rex Jaeschke, 29500 Project Editor<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>