No description of the specific behaviour is given for “mwSmallCaps” element, although it is supposed to reproduce behaviour of a prior version of Microsoft Word.
The definition of the behaviour should be given.
Part 4, Section 2.15.3.32
te
Proposed Disposition of DIS 29500 Comment IR-0020 (Modified: 2008-01-13) Agreed; we will fully define the information necessary to implement this property (specified below). This description provides all of the information needed to mimic a behavior observed in a previously existing word processing application (Word 5.x for the Macintosh). In addition, we will remove it from its current location in the specification (Part 4, §2.15.5.32, pages 1,4271,428), and place it into a new annex for deprecated features. Following the precedent set by other ISO standards (such as SQL’s ISO 9075:2003 Part 1 and C++’s ISO/IEC 14882:1998), we will make use of a new Annex that contains normative descriptions of all deprecated features. The intent of this Annex is to enable a transitional period during which existing binary documents being migrated to DIS 29500 can make use of those deprecated features to preserve their fidelity, while noting that new documents should not use them. Accordingly, the Conformance clause will also be changed to state that newly created documents (those not created by migrating existing binary documents) should not use deprecated features. All deprecated features will be removed from their current locations in the standard, but will be fully defined in this new Annex. To provide a full description, the following changes will be made to Part 4, §2.15.3.32, page 1,427, lines 921 through page 1,428, lines 111: 2.15.3.32 mwSmallCaps (Use Specific Small Caps Algorithm) This element specifies that applications should use a specific algorithm to determine the font size of small caps (the formatting resulting from the use of the smallCaps element (§2.3.2.31). This emulation typically results in small caps which are smaller than typical small caps at most font sizes. Typically, applications can utilize any algorithm that results in small caps formatting. This element, when present with a val attribute value of true (or equivalent), specifies that applications should determine the font size for small caps using the following algorithm: If 7 , then the font size for small caps is 7 points. Otherwise, sequentially iterate through until +1 , at which point the font size for small caps is points. where is an array defined as follows: 7,9,10,12,14,18,24,36,48,60,72,80, 1 , 2 , … , where = 80 + 10 . is an integer calculated as follows: The font size of the run to which small caps formatting is applied (in points). [Example: Consider a WordprocessingML document with small caps on its text contents. If this compatibility setting is turned on: <w:compat> <w:mwSmallCaps /> </w:compat> And the font size for a single run is 16 points, and performing the algorithm above would result in 14 points as the calculated font size for small caps. end example] Similar Comments: CL-0097 , CO-0106 , CZ-0017 , DK-0013 , FR-0064 , GB-0231 , GR-0033 , IN-0030 , KR-0009 , PT-0047 , US-0061

Dupe of PT 43