This is the “lineWrapLikeWord6″ element. The text given says “This element specifies that applications shall emulate the behavior of a previously existing word processing application (Microsoft Word 6.0) when determining the whitespace compression of the final character on each line in the document. This emulation typically results in characters ending a line that may be compressed on the right being compressed on the right irrespective to whether the compression will allow another character to be included on the given line or not.
Unsufficient detail is given for an application to replicate the desired behavior. It is not enough to say what this emulation “typically results in”

Define the intended behavior.
We appreciate that this element is intended for backwards compatibility and is optional. However, if a vendor does want to fully implement the standard, for example, in order to read and display all OOXML documents, then this definition is insufficient.
On the other hand, if we think that no other vendor will fully implement this specification, then this brings into question its suitability for an International Standard.

- Part 4, Section 2.15.3.31

te

Proposed Disposition of DIS 29500 Comment CL-0096 (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 6.0). In addition, we will remove it from its current location in the specification (Part 4, §2.15.3.31, page 1,426­1,427), 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 existing text in Part 4, §2.15.3.31, pages 1,426­1,427, will be revised as follows: 2.15.3.31 lineWrapLikeWord6 (Ignore Compression of Full-Width Punctuation Ending a Line) This element specifies that applications should ignore the character compression settings specified by the characterSpacingControl element (§2.15.1.18) when determining if one more character fits within the text margins on each line of the document. This setting typically results in a character being pushed to the following line, ignoring the fact that the character compression settings would have allowed it to fit within the text boundaries. Typically, an application would check the character compression settings, and apply any character-level whitespace compression before attempting to fit the last character on the line. This element, when present with a val attribute value of true (or equivalent), specifies that applications shall ignore that compression and fit the character as if it should be displayed at its full width, regardless of whether the compression settings are applied. [Example: Consider a paragraph which ends with the following two characters (with each character's bounding box outlined for illustrative purposes: If the document's character compression settings were not set to doNotCompress and text extent fell at the location identified by this red line: The last character would have compression applied to its blank half, and would fit on the line. If this compatibility setting is turned on: <w:compat> <w:lineWrapLikeWord6 /> </w:compat> Then applications should compress the character, but should treat the character as full width when determining if it fits on the line; in this case, the second character would be displayed on the following line. end example] Similar Comments: CO-0105 , CZ-0016 , DK-0012 , FR-0063 , GB-0230 , GH-0005 , GR-0032 , IN-0029 , IR-0019 , KR-0008 , PT-0046 , US-0060

Tag and Go

1 Comment

  1. hAl September 25, 2007 @ 6:54 pm

    Dupe of PT 43

Sorry, the comment form is closed at this time.

  • Argentina (1)
  • Australia (30)
  • Austria (1)
  • Belgium (1)
  • Brazil (64)
  • Bulgaria (3)
  • Canada (79)
  • Chile (217)
  • China (1)
  • Colombia (237)
  • Czech Republic (75)
  • Denmark (168)
  • Ecma (76)
  • Ecuador (1)
  • Finland (15)
  • France (592)
  • Germany (162)
  • Ghana (12)
  • Greece (113)
  • India (82)
  • Iran (58)
  • Ireland (12)
  • Israel (33)
  • Italy (2)
  • Japan (82)
  • Jordan (1)
  • Kenya (81)
  • Malaysia (23)
  • Malta (5)
  • Mexico (7)
  • New Zealand (54)
  • Norway (12)
  • Peru (10)
  • Philippines (7)
  • Poland (4)
  • Portugal (118)
  • Singapore (2)
  • South Africa (17)
  • South Korea (25)
  • Spain (1)
  • Switzerland (19)
  • Thailand (1)
  • Tunisia (3)
  • Turkey (1)
  • UK (635)
  • Uruguay (18)
  • USA (288)
  • Venezuela (73)