AutoSpaceLikeWord95 Class
Emulate Word 95 Full-Width Character Spacing.When the object is serialized out as xml, its qualified name is w:autoSpaceLikeWord95.
Inheritance Hierarchy
System.Object
DocumentFormat.OpenXml.OpenXmlElement
DocumentFormat.OpenXml.OpenXmlLeafElement
DocumentFormat.OpenXml.Wordprocessing.OnOffType
DocumentFormat.OpenXml.Wordprocessing.AutoSpaceLikeWord95
Namespace: DocumentFormat.OpenXml.Wordprocessing
Assembly: DocumentFormat.OpenXml (in DocumentFormat.OpenXml.dll)
Syntax
'Declaration
Public Class AutoSpaceLikeWord95 _
Inherits OnOffType
'Usage
Dim instance As AutoSpaceLikeWord95
public class AutoSpaceLikeWord95 : OnOffType
Remarks
[ISO/IEC 29500-1 1st Edition]
9.7.3.4 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 (Part 1, §17.3.1.2) and autoSpaceDN (Part 1, §17.3.1.3) 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>2</w:t> </w:r> <w:r> <w:t>2</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 (2). 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]
Parent Elements |
---|
compat (Part 1, §17.15.1.21) |
This element’s content model is defined by the common boolean property definition in Part 1, §17.17.4.
© ISO/IEC29500: 2008.
Thread Safety
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.