<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 12 (filtered medium)"><style><!--
/* Font Definitions */
@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: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.EmailStyle18
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Dear members of WG 6<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'>I have now prepared a complete draft of a faux change-tracked version of IS 26300 with COR1, COR2 and AMD1 all applied. See attached PDF.<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'>While preparing this draft I discovered just one major issue and one minor issue. The major issue concerns a correction that was made by COR1 then partially, but not completely, reversed by AMD1. This relates to Clause 15.31.3, fourth paragraph and schema fragment. COR1 changed the name of an attribute in the fourth paragraph from ‘</span><span style='font-family:"Courier New";color:#1F497D'>chart:interval-minor-division</span><span style='color:#1F497D'>’ to ‘</span><span style='font-family:"Courier New";color:#1F497D'>chart:interval-minor</span><span style='color:#1F497D'>’, for consistency with the schema fragment. AMD1 changed the name in the schema fragment from ‘</span><span style='font-family:"Courier New";color:#1F497D'>chart:interval-minor</span><span style='color:#1F497D'>’ to ‘</span><span style='font-family:"Courier New";color:#1F497D'>chart:interval-minor-division</span><span style='color:#1F497D'>’ to align with ODF v1.1, but failed to reverse the change made by COR1. This will have to be rectified by a new COR.<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'>The minor issue is a wrong font in the final paragraph of new Appendix F, where an attribute name should be in monospaced font.<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'>I shall be most grateful for any cross-checking that experts can do to ensure that this draft doesn’t contain any transcription errors.<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'>Francis Cave<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Convenor<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><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> sc34wg6-bounces@vse.cz [mailto:sc34wg6-bounces@vse.cz] <b>On Behalf Of </b>Francis Cave<br><b>Sent:</b> 26 November 2012 23:26<br><b>To:</b> SC 34/WG 6 mailing list<br><b>Subject:</b> An informal draft change-tracked text of IS 26300 + COR1, COR2 and AMD1, with list of possible new issues encountered<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dear members of WG 6<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As previously announced, I attach a draft of an informal document containing a faux change-tracked version of IS 26300 with COR1 and COR2 applied. I propose to continue in the same way to apply the revisions from AMD1. Please note that this draft, in PDF format, contains comments to assist with navigating between the changes. Deletions are in red and struck through, insertions are in blue and underscored. Be warned that the insertions mean that the pagination no longer corresponds with the original text.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>While preparing this draft, the following issues with the revised text have been noticed. In each case I have indicated my personal view on whether or not we should give any priority to resolving the issue. In most cases I don’t feel that correction is a priority, but especially in the case of Clause 9.5.3 I believe there to be a case for further correction.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>1. COR1, Correction to Clause 9.3.3, page 304, line 38, final sentence:<o:p></o:p></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“The xlink references that folder.”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The all-lowercase term “xlink” is not consistent with the term used elsewhere in the specification. Elsewhere the all-lowercase form is only used as a namespace prefix in XML fragments. Both “XLink” and “[XLink]” are used in the current text except in XML fragments, without any obvious distinction. Probably they should all be “[XLink]”, referring the reader to the XLink reference in the bibliography in Appendix B. However, I doubt that there is any ambiguity in the current text, so correction is not a priority.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>2. 26300:2006, Clauses 9.5.3 through 9.5.6, pages 333-344<o:p></o:p></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>COR1 corrects a number of minor spelling and grammatical errors, but a number of similar errors are overlooked, and one correction made by COR1 does not succeed in clarifying the meaning of the text, although a second attempt in AMD1 to correct the same error, but in another location, is more successful. Here are the details.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><i>2.1 Clause 9.5.3, page 333, line 16:<o:p></o:p></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“are describing” should be “describes”; “and or” should be “or”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>COR 1 makes this kind of correction in several places but this one was overlooked. I doubt that there is any ambiguity in the current text, so correction is not a priority.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><i>2.2 Clause 9.5.3, page 333, line 30:<o:p></o:p></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“If “$” is preceding a integer value, the value is a indexing a <span style='font-family:"Courier New"'>draw:modifiers</span> attribute. The corresponding modifier value is used as parameter value then.”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>What does this mean? It appears in three places in Clause 9.5.3, on pages 333, 334 and 336, and once in Clause 9.5.6, on page 341..<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>COR1 attempts to correct it in two places, on pages 336 and 341, to the following:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“If “$” is preceding a integer value, the value is an indexing a <span style='font-family:"Courier New"'>draw:modifiers</span> attribute. The corresponding modifier value is used as parameter value then. ”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>AMD1 attempts to correct it on page 333 to the following: <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“If “$” is preceding a integer value, the value is indexing a <span style='font-family:"Courier New"'>draw:modifiers</span> attribute. The corresponding modifier value is used as parameter value then. ”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Both these corrections still contain the minor grammatical error “a integer” and the less minor grammatical errors in the final sentence. The instance on page 334 remains uncorrected. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I believe that AMD1 gets closest to being clear enough. In which case the following text would probably be more correct:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“If “$” precedes an integer value, the value indexes a <span style='font-family:"Courier New"'>draw:modifiers</span> attribute. The corresponding modifier value is then used as the parameter value.”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In my opinion, the fact that the original unclear text occurs four times in the specification, and has been poorly corrected in two places by COR1, corrected slightly less poorly in one place by AMD1, and not at all in the fourth case, means that the text is now inconsistent and this should be corrected. Other minor grammatical errors can be corrected at the same time.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><i>2.3 Clause 9.5.3, page 333, line 35:<o:p></o:p></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“<b>Example</b> for a custom-shape that uses the draw:enhanced-path to describe a pie-chart whose top right quarter segment is taken out:”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This should be:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“<b>Example</b> of a custom-shape that uses the <span style='font-family:"Courier New"'>draw:enhanced-path</span> attribute to describe a pie-chart whose top right quarter segment is taken out:”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I doubt that there is any ambiguity in the current text, so correction is not a priority.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><i>2.4 Clause 9.5.3, page 334, line 32:<o:p></o:p></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>COR1 corrects the error in line 36, but fails to correct “a ellipse” in line 32. I doubt that there is any ambiguity in the current text, so correction is not a priority.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><i>2.5 Clause 9.5.3, page 336, line 5:<o:p></o:p></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“A example of the draw:text-areas attribute that defines two text areas, …”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This should be:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“An example of the <span style='font-family:"Courier New"'>draw:text-areas</span> attribute that defines two text areas, …”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I doubt that there is any ambiguity in the current text, so correction is not a priority.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><i>2.6 Clause 9.5.3, page 336, line 25:<o:p></o:p></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“A example of the draw:glue-points attribute that defines two glue points, including modifier and<o:p></o:p></p><p class=MsoNormal>equation usage, would be: draw:glue-points=”0 ?Formula1 100 $1” “<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This should be:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“An example of the <span style='font-family:"Courier New"'>draw:glue-points</span> attribute that defines two glue points, including modifier and<o:p></o:p></p><p class=MsoNormal>equation usage, would be: <span style='font-family:"Courier New"'>draw:glue-points=”0 ?Formula1 100 $1”</span> “<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I doubt that there is any ambiguity in the current text, so correction is not a priority.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><i>2.7 Clause 9.5.5, page 340, line 14:<o:p></o:p></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>COR1 corrects “A example” to “An example” at the start of the sentence, but fails to correct the wrong font in the attribute example in the same line. It should be:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>“An example for the <span style='font-family:"Courier New"'>draw:formula</span> attribute would be: <span style='font-family:"Courier New"'>draw:formula=”width+10-$0”</span>. If the value of the first modifier value is “100” and the width of the <span style='font-family:"Courier New"'>svg:viewbox</span> is “10000”, then the result of the above formula would be 10000 + 10 – 100 = 9910”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I doubt that there is any ambiguity in the current text, so correction is not a priority.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><i>2.8 Clause 9.5.6, page 341, lines 38-40, page 342, lines 2-7 and 10-11:<o:p></o:p></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The text in the Description column contains attribute names in the wrong font in all but two rows, and in two cases (Contents “right” and “bottom”) the word “attribute” is missing. I doubt that there is any ambiguity in the current text, so correction is not a priority.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><i>2.9 Clause 9.5.6, page 342, lines 18 and 29:<o:p></o:p></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Two cases of wrong font in attribute examples, at the end of each of these two paragraphs. I doubt that there is any ambiguity in the current text, so correction is not a priority.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>3. COR1, Clause 14.7.9, page 508, line 22<o:p></o:p></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I think that “country” should actually be “<span style='font-family:"Courier New"'>number:country</span>”. I doubt that there is any ambiguity in the current text, so correction is not a priority.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>4. COR1: Clause 15.4.7, page 565, line 12 and Clause 15.4.8, page 565, line 24<o:p></o:p></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The removal of references to “[CSS3Text]” has left a number of “See also”s which should all have been corrected to “See”. I doubt that there is any ambiguity in the current text, so correction is not a priority.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>5. COR2, Clause 7.7.1, “Copy Outline Levels”, page 163, line 15<o:p></o:p></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The correction contains a wrong font error. In the first bullet point “false” should be “<span style='font-family:"Courier New"'>false</span>” (in fixed pitch). I doubt that there is any ambiguity in the current text, so correction is not a priority.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>6. COR2, Clause 8.1.3, “Cell Current Currency”, page 188, line 4<o:p></o:p></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The correction contains a wrong font error. One instance of “office:value” should be “<span style='font-family:"Courier New"'>office:value</span>” (in fixed pitch). I doubt that there is any ambiguity in the current text, so correction is not a priority.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>7. COR2, Clause 9.4.6, page 323, line 3<o:p></o:p></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The previous correction includes Clause references for each of the cross-referenced attributes. Should there not be Clause references for the first two cross-referenced attributes?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>8. Clause 15.22.8, page 650, line 23<o:p></o:p></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The phrase “with a end angle” should be “with an end angle”. I doubt that there is any ambiguity in the current text, so correction is not a priority.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Francis Cave<o:p></o:p></p><p class=MsoNormal>Convenor<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>