<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 14 (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: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: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='color:#1F497D'>Here’s an update on this. I’m going to make a slightly different recommendation.<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'>We’re going to leave the element names the same ( e.g., “cx,” “cy” ), but we need to change their descriptions [ e.g., “(Extent Width)” ] as in some cases they’re flat out wrong. Additionally, having made some of the changes ( length along {x,y}-axis ), it reads funny, so I think we should stick with width and height, but use them consistently.<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’m going to change 202, 211 and 248 this evening and will provide the changed text. If anyone objects to this updated approach, please let me know.<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'>Thanks,<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'>shawn<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 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"'> Shawn Villaron <br><b>Sent:</b> Thursday, January 21, 2010 12:23 PM<br><b>To:</b> SC 34 WG4<br><b>Subject:</b> Update on FPDAM Part 4 GB-0007<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Good afternoon,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As I’m going through the instances where we use “extent,” “length,” “height,” “width,” etc., I’m finding a few oddities in the prose that will require a little more time to investigate or at least guidance from WG4. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For example, GB-0007 specifically calls out change 248. When I reviewed the text for this change, I noticed that that we’ve switched “height” and “width” in the prose for the cx ( “count of x” ) example. It appears that we’ve made a similar mistake in the prose for the cy example, too. Clearly these are simple editorial changes we should make.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Stepping back, I believe that the ideal wording would be to refer to “extents” as “lengths along the {x,y}-axis” as opposed to heights, widths and lengths. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>That said, I don’t believe these minor changes impact interoperability or an implementers ability to implement the standard. I find that readers reasonably skilled in graphics ( the scope of this issue ) understand that within the scope of extents, cx is always the count along the x-axis and cy is always the count along the y-axis. The notions of height, width and length are more for the unskilled reader. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If WG4 believes we need to change the text, I’d suggest that we limit the changes to the prose and not change the names of the elements [ e.g., don’t change “cy (Extent Width)” to “cy ( Extent Length along the y-axis )” ]. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Let’s get guidance during today’s teleconference.<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>shawn<o:p></o:p></p></div></body></html>