This definition is intrinsically based upon material that is not part of the OOXML submission, and that is not part of any known standard either. As such, it cannot be accepted. A proper definition must be provided for the shapeLayoutLikeWW8 feature, or the feature must be removed altogether.

Define the shapeLayoutLikeWW8 feature properly or drop it from the OOXML proposal.

page 1442, lines 13-18 Part4, Section 2.15.3.41 shapeLayoutLikeWW8 (Emulate Word 97 Text Wrapping Around Floating Objects)

te

Proposed Disposition of DIS 29500 Comment FR-0065 (Modified: 2008-01-13) Agreed; we will define fully 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 97). In addition, we will remove it from its current location in the specification (Part 4, §2.15.3.41, page 1,422­1,423), 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.41, page 1,422, lines 7­21 through page 1,423, lines 1­7: 2.15.3.41 shapeLayoutLikeWW8 (Ignore Text Wrapping around Objects at Bottom of Page) This element specifies that applications should ignore the line wrapping setting specified by a floating object, instead allowing text to be displayed beneath it under the following specific set of conditions. Typically, text wrapping around a floating object is dictated by the presence of one of the following as a child element of the object’s anchor element (§5.5.2.3): wrapNone (§5.5.2.16) element, which specifies no text wrapping wrapSquare (§5.5.2.17) element, which specifies square text wrapping wrapThrough (§5.5.2.18) element, which specifies through text wrapping wrapTight (§5.5.2.19) element, which specifies tight text wrapping wrapTopAndBottom (§5.5.2.20) element, which specifies top and bottom text wrapping This element, when present with a val attribute value of true (or equivalent), specifies that applications shall allow text to wrap beneath a floating object, ignoring the object’s true wrapping setting, when the following conditions are met: The floating object has any of the following elements present as a child of the object’s anchor element (§5.5.2.3): wrapSquare (§5.5.2.17), wrapTight (§5.5.2.19), or wrapTopAndBottom (§5.5.2.20). The floating object has a positionV element (§5.5.2.11) with a relativeFrom attribute value of line. The floating object has a negative value for the child posOffset element (§5.5.2.12) of the positionV element (§5.5.2.11). The paragraph containing the anchor element would appear directly after the previous paragraph if the wrapping settings were ignored. The paragraph containing the anchor element would be pushed to the next page if the wrapping settings were respected. [Example: Consider a WordprocessingML document containing a DrawingML object which meets the conditions outlined above: <w:p> <w:r> <w:t>Sample text. Sample text. Sample text. Sample text. Sample text. Sample text.</w:t> </w:r> <w:r> <w:drawing> <wp:anchor ... > <wp:positionV relativeFrom="line"> <wp:posOffset>-428914</wp:posOffset> </wp:positionV> <wp:wrapTopAndBottom /> ... </wp:anchor> </w:drawing> </w:r> <w:r> <w:t> Sample text. Sample text. Sample text. Sample text. Sample text. Sample text.</w:t> </w:r> ... </w:p> When the wrapping settings are respected, the shape and its paragraph do not fit on the page, so they are moved to the next page (the paragraph containing the anchor has been highlighted for illustrative purposes): If this compatibility setting is turned on: <w:compat> <w:shapeLayoutLikeWW8 /> </w:compat> Then applications should ignore the wrapping setting and allow text to wrap beneath the object. This behaviour results in the following (again, the paragraph containing the anchor has been highlighted for illustrative purposes): end example] Similar Comments: CL-0098 , CO-0107 , CZ-0018 , DK-0014 , GB-0232 , GH-0006 , GR-0034 , IN-0031 , IR-0021 , KR-0010 , PT-0048 , US-0062