The standard uses several different length units-for example font size is specified using half pt (see ST_HpsMeasure Part 4/2.18.48/p. 1742), DrawingML uses EMU unit (see ST_Coordinate data type Part 4/5.1.12.16/p. 3694) and 100th of point (see ST_TextPoint data type Part 4/5.1.12.75/p. 3861). On other place twips unit (see ST_TwipsMeasure Part 4/2.18.105/p. 1836) is used. Although usage of such different units might have some benefits like suitable scale or elimination of rounding errors it would be very useful if any length value can be specified using any common length unit.

Modify all length data types to support also values with specified measure unit. At least the following units should be supported: cm, mm, in, pc and pt. These units must be recognized during document loading but they do not have to be preserved during editing session. When saving a default unit for given length data type might be used.

te

Proposed Disposition of DIS 29500 Comment CZ-0045 (Modified: 2008-01-11) This is a good suggestion for consideration by those involved in the future maintenance of this standard. As an example of how further control over the unit of measure could be implemented, consider the following possible extension to the font-size element (Part 4, §2.3.2.6): <w:p> <w:r> <w:rPr> <w:sz w:unit="points" w:val="32" /> </w:rPr> <w:t>Sample text.</w:t> </w:r> </w:p> As another example, consider the following possible extension to the page-size element (Part 4, §2.6.13): <w:sectPr> <w:pgSz w:unit="inches" w:w="8.5" w:h="11" /> … </w:sectPr> These could also be accomplished as follows: <w:p> <w:r> <w:rPr> <w:sz w:val="32pt" /> </w:rPr> <w:t>Sample text.</w:t> </w:r> </w:p> <w:sectPr> <w:pgSz w:w="8.5in" w:h="11in" /> … </w:sectPr> Each of these approaches has merits and disadvantages. As such, we believe that the suggestion to add an additional attribute for specifying the units of measurement must be very carefully considered, as the wrong approach could add complexity for both producers and consumers. For this reason, we do not believe this should occur in the current version of the standard. A proper study of this would be undertaken as a maintenance activity, where the proper amount of time and discussion could be devoted to this subject ­ for example, the issues regarding defaults, supported units, and other details can be appropriately researched and decided.