The "useWord97LineBreakRules" element is defined in terms of mimicking a legacy application’s behavior. The standard contains insufficient detail on how to replicate this behavior.

Proposed change: Define the intended behavior.

2.15.3.64 [p1482]

te

Proposed Disposition of DIS 29500 Comment GB-0237 (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.64, pages 1,482­1,483), 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 text will replace the existing text in Part 4, §2.15.3.64, page 1,482, lines 7­20 through page 1,483, lines 1­5: 2.15.3.64 useWord97LineBreakRules (Emulate Word 97 East Asian Line Breaking) This element specifies that applications should perform specific calculations (detailed below) when determining inter-character spacing under certain conditions. These calculations would not normally be considered correct. Typically, the behaviors specified by the following elements are applied unconditionally: The autoSpaceDE (§2.3.1.2) and autoSpaceDN (§2.3.13) elements The topLinePunct (§2.3.1.43) element The compatibility element described in this subclause, when present with a val attribute value of true (or equivalent), specifies that applications should ignore the settings listed above in the following scenarios: 1. If an ideographic character and a non-ideographic/numeric character are logically adjacent (ignoring all content which is not within a t element), but separated by a field boundary, i.e.: The first character is within a fldSimple element, but the second is not. The characters are separated by a fldChar element with a fldCharType attribute value of end Then any appropriate inter-character spacing should be omitted. [Note: Inter-character spacing should still be calculated correctly within the field result. end note] 2. If a full-width punctuation character appears at the start of a paragraph which also specifies numbering via the numPr element (§2.3.1.19), the compression specified by the topLinePunct element is ignored. [Example: Consider a paragraph which contains a field ending in an ideograph and another paragraph, with numbering, which contains a full-width punctuation character in the first character position: <w:p> <w:r> <w:fldChar w:fldCharType="begin" /> </w:r> ... <w:r> <w:t></w:t> </w:r> <w:r> <w:fldChar w:fldCharType="end" /> </w:r> <w:r> <w:t>1</w:t> </w:r> </w:p> <w:p> <w:pPr> <w:numPr> ... </w:numPr> </w:pPr> <w:r> <w:t></w:t> </w:r> </w:p> Typically, if both the autoSpaceDN and topLinePunct are true , additional spacing is added after the ideograph in the first paragraph and punctuation kerning is applied in the second paragraph (with gridlines added for visual reference): If this compatibility setting is turned on: <w:compat> <w:useWord97LineBreakRules /> </w:compat> Then applications should not add any inter-character spacing at the end of the field and should turn off punctuation kerning in the second paragraph: end example] Similar Comments: CL-0003 , CL-0104 , CO-0112 , CZ-0022 , DK-0019 , FR-0069 , GR-0040 , IN-0037 , IR-0027 , KR-0015 , PT-0054 , US-0068

Tag and Go

No Comments

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)