No description of the specific behaviour is given for “autospaceLikeWord95″ 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.6

te

Proposed Disposition of DIS 29500 Comment IR-0025 (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 95). In addition, we will remove it from its current location in the specification (Part 4, §2.15.3.6, pages 1,378­1,379), 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.6, pages 1,378­1,379, will be replaced with the following: 2.15.3.6 autoSpaceLikeWord95 (Incorrectly Adjust Text Spacing for Specific Unicode Ranges) This element specifies adjustments (detailed below) which should be applied to the spacing between adjoining regions of non-ideographic and ideographic text when the autoSpaceDE (§2.3.1.2) and autoSpaceDN (§2.3.13) elements have a value of true (or equivalent). This algorithm typically results in the following: An increase in the inter-character spacing added between non-ideographic and/or number characters and certain full-width characters No inter-character spacing between non-ideographic and/or number characters and certain half-width characters Typically, applications apply additional spacing between ideographic and non-ideographic characters/numeric characters when the autoSpaceDE / autoSpaceDN properties are applied. This element, when present with a val attribute value of true (or equivalent), specifies that applications shall apply the following adjustments to this logic: Characters in the following Unicode ranges should be treated as ideographic, even though those characters are full-width forms of non-ideographic text: U+FF10­U+FF19, U+FF21­U+FF3A, and U+FF41­U+FF5A. [Note: This results in the unnecessary addition of space. end note] Characters in the following Unicode ranges should be treated as non-ideographic, even though those characters are ideographic: U+FF66­U+FF9F. [Note: This results in the omission of the intended additional space. end note] [Example: Consider a WordprocessingML document with two paragraphs containing a mix of East Asian and Latin characters: <w:p> <w:r> <w:t>ab</w:t> </w:r> <w:r> <w:t></w:t> </w:r> <w:r> <w:t></w:t> </w:r> <w:r> <w:t>cd</w:t> </w:r> </w:p> <w:p> <w:r> <w:t>ab</w:t> </w:r> <w:r> <w:t></w:t> </w:r> <w:r> <w:t></w:t> </w:r> <w:r> <w:t>cd</w:t> </w:r> </w:p> The first paragraph contains characters with Unicode value U+FF66 (). The second paragraph contains characters with Unicode value U+FF12 (). If autoSpaceDE is true , spacing is added in the first paragraph (between the ideographs and the non-ideographic characters), but not in the second (all four characters are not ideographs): If this compatibility setting is turned on: <w:compat> <w:autoSpaceLikeWord95 /> </w:compat> Then, although it appears incorrect, applications should not add space in the first paragraph and should apply it in the second: end example] Similar Comments: CL-0002 , CL-0102 , CO-0103 , CZ-0014 , DK-0010 , FR-0061 , GB-0228 , GH-0003 , GR-0038 , IN-0035 , JP-0052 , KR-0013 , PH-0007 , PT-0052 , US-0066

Tag and Go

1 Comment

  1. hAl September 25, 2007 @ 4:13 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)