The text says: "The interpretation of property is reversed if the parent table is right to left using the bidiVisual element."
Then in the formal description of the "val" attribute on page 345, we find: "The possible values for this attribute are always specified relative to the page, and do not change semantic from right-to-left and left-to-right documents."
This looks as a contradiction, or at least mightily confusing.

Clarify the meaning.

jc (Table Row Alignment), on page 344
Section 2.4.22

te

Proposed Disposition of DIS 29500 Comment IL-0029 (Modified: 2008-01-02) Agreed; the use of a single-alignment simple type created unintentional confusion in Part 4, §2.4.22 (and other places). The following changes will be made (note that this disposition overlaps with the concerns around naming of directionally-dependent values): 1. Part 4, §2.4.21, page 344, attribute table: Part 4, §2.4.22, page 345, attribute table: Part 4, §2.4.23, page 346, attribute table: Attributes Description val (Alignment Type) Specifies the justification which should be applied to the parent table object within a document . The possible values (see below) for this attribute are always specified relative to the page, and do not change semantic from right-to-left and left-to-right documents. [Example: Consider the following WordprocessingML fragment for a paragraph table in a document: <w: pPr tblPr > <w:jc w:val=" right center " /> </w: pPr tblPr > This paragraph table is now right justified centered on the page , regardless of the paragraph or section settings . end example] The possible values for this attribute are defined by the ST_Jc Table simple type (§2.18.50 a ). 2. Part 4, §2.18, add a new simple type definition: ST_JcTable (Table Alignment Type) This simple type specifies all types of alignment that are available to be applied to tables in a WordprocessingML document. [Example: Consider a table row that is right aligned. This requirement would be specified as follows in the WordprocessingML markup: <w:trPr> <w:jc w:val="end" /> </w:trPr> The val attribute's value of end specifies that the table will be right-aligned on the page (assuming the table is aligned left-to-right. end example] This simple type’s contents are a restriction of the XML Schema string datatype. The following are possible enumeration values for this type: Enumeration Value Description center (Align Center) Specifies that the table shall be centered on the line between both of the text margins in the document. (See §2.4.1) end (Align to Trailing Edge) Specifies that the table shall be aligned to the trailing edge of the text flow ­ the right text margin (for a left-to-right table); or the left text margin (for a right-to-left table) in the document. (See §2.4.1) start (Align To Starting Edge) Specifies that the table shall be aligned to the leading edge of the text flow ­ the left text margin (for a left-to-right table); or the right text margin (for a right-to-left table) in the document. (See §2.4.1) Referenced By jc@val (§2.4.21); jc@val (§2.4.22); jc@val (§2.4.23) The following XML Schema fragment defines the contents of this simple type: <simpleType name="ST_JcTable"> <restriction base="xsd:string"> <enumeration value="center"/> <enumeration value="end"/> <enumeration value="left"/> <enumeration value="right"/> <enumeration value="start"/> </restriction> </simpleType> 3. To wml.xsd, the following changes will be made: A new simple type (ST_JcTable): <simpleType name="ST_JcTable"> <restriction base="xsd:string"> <enumeration value="center"/> <enumeration value="end"/> <enumeration value="left"/> <enumeration value="right"/> <enumeration value="start"/> </restriction> </simpleType> A new complex type (CT_JcTable): <complexType name="CT_JcTable"> <attribute name="val" type="ST_JcTable" use="required"> <annotation> <documentation>Table Alignment Type</xsd:documentation> </annotation> </attribute> </complexType> To CT_TrPrBase, CT_TblPr, CT_TrPrExBase: <xsd:element name="jc" type="CT_Jc Table " minOccurs="0" maxOccurs="1"/> In addition, we will remove the directionally biased enumeration values from their current location in the specification (Part 4, §2.18.50, pages 1,744­1,746), and place them 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. Additional Enumeration Values for ST_JcTable (Table Alignment Type) The following deprecated values can also be used within the context of the ST_JcTable simple type: Enumeration Value Description left (Align Left) Specifies that the table shall be aligned on the left text margin (for a left-to-right table); or the right text margin (for a right-to-left table) in the document. (See §2.4.1) right (Align Right) Specifies that the table shall be aligned on the Enumeration Value Description right text margin (for a left-to-right table); or the left text margin (for a right-to-left table) in the document. (See §2.4.1)

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)