Open Document Format for Office Applications (OpenDocument) v1.1 Errata 01
OASIS Approved Errata
22 July 2013
Specification
URIs
This version:
http://docs.oasis-open.org/office/v1.1/errata01/os/OpenDocument-v1.1-errata01-os.odt (Authoritative)
http://docs.oasis-open.org/office/v1.1/errata01/os/OpenDocument-v1.1-errata01-os.html
http://docs.oasis-open.org/office/v1.1/errata01/os/OpenDocument-v1.1-errata01-os.pdf
Previous version:
N/A
Latest version:
http://docs.oasis-open.org/office/v1.1/errata01/OpenDocument-v1.1-errata01.odt (Authoritative)
http://docs.oasis-open.org/office/v1.1/errata01/OpenDocument-v1.1-errata01.html
http://docs.oasis-open.org/office/v1.1/errata01/OpenDocument-v1.1-errata01.pdf
Technical Committee:
OASIS Open Document Format for Office Applications (OpenDocument) TC
Chair:
Rob Weir (robert_weir@us.ibm.com), IBM
Editors:
Dennis E. Hamilton (dennis.hamilton@acm.org), Individual
Patrick Durusau (patrick@durusau.net), Individual
Additional artifacts:
This prose specification is one component of a Work Product which also includes:
Related work:
This specification provides errata for:
Abstract:
This specification lists errata for Open Document Format for Office Applications (OpenDocument) v1.1.
Status:
This document was last revised or approved by the OASIS Open Document Format for Office Applications (OpenDocument) TC on the above date. The level of approval is also listed above. Check the ÒLatest versionÓ location noted above for possible later revisions of this document.
Technical Committee members should send comments on this Work Product to the Technical CommitteeÕs email list. Others should send comments to the Technical Committee by using the "Send A Comment" button on the Technical CommitteeÕs web page at http://www.oasis-open.org/committees/office/.
For information on whether any patents have been disclosed
that may be essential to implementing this Work Product, and any offers of
patent licensing terms, please refer to the Intellectual Property Rights
section of the Technical Committee web page (http://www.oasis-open.org/committees/office/ipr.php).
Citation format:
When referencing this Work Product the following
citation format should be used:
[OpenDocument-v1.1-errata01]
Open Document Format for Office Applications
(OpenDocument) v1.1 Errata 01. 22 July 2013. OASIS Approved Errata. http://docs.oasis-open.org/office/v1.1/errata01/os/OpenDocument-v1.1-errata01-os.html.
Notices
Copyright © OASIS Open 2013. All Rights Reserved.
All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.
OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.
The name "OASIS" is a trademark of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/policies-guidelines/trademark for above guidance.
Table of Contents
1 Introduction.............................................................................................................................. 5
1.1 Terminology...................................................................................................................... 5
1.2 Normative References....................................................................................................... 5
1.3 Non-Normative References................................................................................................ 6
1.4 Errata Tabulation Format.................................................................................................. 7
1.5 Notation Conventions........................................................................................................ 7
1.5.1 Section/Subsection Entries........................................................................................ 7
1.5.2 Issue Identifications.................................................................................................... 7
1.5.3 Issue Sources.............................................................................................................. 7
1.5.4 Amd? Status............................................................................................................... 8
2 Errata Items.............................................................................................................................. 9
3 Conformance.......................................................................................................................... 37
Appendix A Acknowledgments.................................................................................................... 38
Appendix B Issues Not Applicable to ODF 1.1............................................................................. 40
Appendix C IS 26300:2006/Amd1 Reconciliation....................................................................... 41
[All text of this document is informative.]
This document provides the first Errata document for Open
Document Format for Office Applications (OpenDocument) v1.1 [ODF 1.1].
The errata items have three sources:
– Errata
items developed for the earlier [ODF 1.0] that
also apply to the text of [ODF 1.1]
– Additional
errata based on comments submitted to or originated in the OASIS Open Document Format
for Office Applications (OpenDocument) TC
– Errata
identified for achieving technical alignment of [ODF 1.1] and
International Standard for OpenDocument [IS
26300:2006] as
amended for mutual alignment [AMD1]
These errata do not apply to the International
Standard. To facilitate technical-alignment
review, these errata entries identify whether an equivalent errata item has
already been included in changes that align the International Standard with ODF
1.1.
Some ODF 1.0 Errata items do not apply to ODF
1.1. Those are accounted for in ().
Some ODF 1.1 Errata 01 items have arisen since the
International Standard corrigenda and amendment were produced. Those items are identified in the Errata
items (section ) and
also summarized in a form applicable to the amended International Standard ().
Within the ODF 1.1 specification and the extracts presented in errata items, the terms "shall", "shall not", "should", "should not", and ÒmayÓ are interpreted as described in Annex H of [ISO/IEC Directives] if they appear in bold letters [ODF 1.1]. Occurrences have their effect in the ODF 1.1 specification. They do not apply to the interpretation of this document.
This is an informative specification. There is no introduction of normative conditions and conformance clauses by reference or in any other manner.
[ISO/IEC
Directives]
ISO/IEC
Directives, Part 2: Rules for the structure and drafting of
International Standards. Fifth edition, 2004. International Organization for Standardization and
International Electrotechnical Commission.
Sixth edition with unchanged Annex H available at http://www.iso.org/directives
[ODF 1.0]
Open Document Format for Office Applications (OpenDocument) v1.0. 01 May
2005. OASIS Standard. Available at http://docs.oasis-open.org/office/v1.0/OpenDocument-v1.0-os.pdf
[1.0-1]
Open Document Format for Office Applications (OpenDocument) 1.0 Errata 01.
24 November 2008. OASIS Approved
Errata. All formats available at http://docs.oasis-open.org/office/v1.0/errata/os/
[1.0-2]
Open Document Format for Office Applications (OpenDocument) 1.0 Errata 02.
20 September 2010. OASIS Approved
Errata. All formats available at http://docs.oasis-open.org/office/v1.0/errata/os/
[ODF 1e2]
Open Document Format for Office Applications (OpenDocument) 1.0 (Second
Edition).
19 July 2006. OASIS Committee
Specification 01. Available at https://www.oasis-open.org/committees/document.php?document_id=19274 (PDF)
and https://www.oasis-open.org/committees/document.php?document_id=19275 (ODT)
[ODF 1.1]
Open Document Format for Office Applications (OpenDocument) v1.1. 01
February 2007. OASIS standard. All formats available at http://docs.oasis-open.org/office/v1.1/OS/
[IS 26300:2006]
Information Technology – Open Document Format for Office Applications
(OpenDocument) v1.0. Available
at http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html
(entry for Standard ISO/IEC 26300:2006)
[COR1]
Information Technology – Open Document Format for Office Applications
(OpenDocument) v1.0, Technical Corrigendum 1. 2010-12-15. Available at http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html (entry
for Standard ISO/IEC 26300:2006/Cor.1:2010)
[COR2]
Information Technology – Open Document Format for Office Applications
(OpenDocument) v1.0, Technical Corrigendum 2. 2011-12-01. Available at http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html (entry
for Standard ISO/IEC 26300:2006/Cor.2:2011)
[AMD1]
Information Technology – Open Document Format for Office Applications
(OpenDocument) v1.0 – Amendment 1: Open Document Format for Office
Applications (OpenDocument) v1.1.
2012-03-15. Available at http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html (entry
for Standard ISO/IEC 26300:2006/Amd.1:2012)
Section/ |
Instruction |
Issue |
Source |
Amd? |
2.1.1 |
〚Instructions and other notations that are not the texts
themselves are included in these brackets.〛
|
COR2 |
- |
|
2.1.2/ |
Style changes are shown in magenta, double-underlined. The text is shown in the desired resulting style. |
N0942:50 |
1.0-1 |
N |
When instructions apply to a numbered section outside of any subsection, the section number is used alone. For example, Ò2.1.1Ó refers to ODF 1.1 section 2.1.1 Document Root Element Content Models.
When the instructions apply in a named subsection, the subsection name follows the numbered section identification. For example, Ò2.1.2/VersionÓ refers to the Version subsection of section 2.1.2 Document Root Attributes.
Issue identifications beginning with N, such as N0942:50 and N1078:10, refer to numbered issues in defect reports on [IS 26300:2006] received from ISO/IEC JTC1/SC34. Further details on those defect items and their disposition in [ODF 1.0] are found in ODF 1.0 Errata 02 [1.0-2].
Issues identified by numerals, nnnn, such as 3798,
refer to an issue identified OFFICE-nnnn (e.g., OFFICE-3798) in the issue database of the OASIS Open Document Format for Office Applications (OpenDocument)
TC.
Whenever an issue
identification has a link, there is (also) discussion of the issue in the issue
database. The link is to the
corresponding issue entry (e.g., ÒN1078:10Ó linked to associated issue
OFFICE-1802, Ò3798Ó linked to associated issue OFFICE-3798).
All errata items originate
in ODF 1.0 Errata and/or ODF 1.1-specific issues captured in the OpenDocument
TC issue database. The Source
indicates additional information that is pertinent to the alignment of ODF 1.1
and IS 26300:2006:
– 1.0-1 indicates an ODF 1.0 Errata 01 item [1.0-1]
– COR1 indicates an ODF 1.0 Errata 01 item that was also applied in
IS 26300:2006 [COR1]
– 1.0-2 indicates an ODF 1.0 Errata 02 item [1.0-2]
– COR2 indicates an ODF 1.0 Errata 02 item that was also applied in
IS 26300:2006 [COR2]
– TC indicates an ODF 1.1 item that originated in the OpenDocument
TC
– WG6 indicates an ODF 1.1 item that originated in ISO/IEC JTC1/SC34
WG6 as part of creating the [AMD1] alignment for ODF 1.1.
This column indicates
whether or not there is an issue that is or is not reflected in [AMD1]:
1.
Entry
Ò-Ó signifies that [AMD1] coverage was unnecessary.
This is usually an item that was covered with [COR1] or [COR2].
2.
Entry
ÒYÓ signifies that [AMD1] also covered the errata item.
3.
Entry
ÒNÓ signifies that [AMD1] did not cover the errata item and any coverage depends on
subsequent work by ISO/IEC JTC1/SC34 WG6.
These items are also accounted for in .
Section/ |
Instruction |
Issue |
Source |
Amd? |
1.3 |
〚Change, in the Prefix column of Table 1〛 |
COR2 |
- |
|
1.6 |
〚Change the entire section〛 |
COR2 |
- |
|
2.1.1 |
〚Change the first paragraph of the section〛 |
N0942:41 |
1.0-01 |
Y |
2.1.2/ |
〚Change the first paragraph of the subsection〛 |
COR2 |
- |
|
2.3.1/ |
〚Change
the fifth and sixth paragraphs of the subsection〛 |
WG6 |
Y |
|
3.1.15 |
〚Change,
in the last paragraph〛
|
COR2 |
- |
|
3.1.18 |
〚Change,
in the schema〛 〚
É 〛 <optional>
<attribute name="meta:frame-count">
<ref name="nonNegativeInteger"/>
</attribute> </optional> <optional>
<attribute name="meta:sentence-count">
<ref name="nonNegativeInteger"/>
</attribute> </optional> <optional>
<attribute name="meta:syllable-count">
<ref name="nonNegativeInteger"/>
</attribute> </optional> <optional>
<attribute name="meta:non-whitespace-character-count">
<ref name="nonNegativeInteger"/>
</attribute> </optional> |
TC |
N |
|
4.4.1/ |
〚Change,
at the end of the last paragraph〛 〚
É 〛To avoid saving the password directly into the XML file, only a
hash value of the password is stored. The hashing is implementation-dependent. |
COR2 |
- |
|
4.7 |
〚In
some forms of the ODF 1.1 specification, there may need to be some or all of
these changes to have the correct form of the last sentence. Change, in the last sentence of the
section〛 See section 2.3.1: |
WG6 |
Y |
|
5.1.1 |
〚Change,
in the last line preceding the start of the ÒSpace Character Subsection〛
|
TC |
- |
|
5.1.4 |
〚Change,
in the beginning of the list〛 – Name – Title – 〚 É 〛 |
|
WG6 |
Y |
6.3 |
〚Change
the first paragraph〛 OpenDocument
|
COR2 |
- |
|
6.7.2 |
〚Change
the first paragraph〛 The text:fixed attribute specifies whether or not the
value of a field element is fixed. – true: value of the field element
where this attribrute appears is preserved. – false:
value of the field element where this attribute appears may be changed. |
COR2 |
- |
|
6.7.5 |
〚Change
the text of the first list item〛
|
N0942:40 |
COR1 |
- |
6.7.5 |
〚Change
the text of the second list item〛 – formula This value
allows the display of the formula rather than the value of the field. |
N0942:40 |
COR1 |
- |
7.3.1/ |
〚Change
at the end of the only paragraph〛 〚
É 〛 |
COR2 |
- |
|
7.3.1/ |
〚Change
the only paragraph〛 The text:index-scope attribute |
COR2 |
- |
|
7.3.2 |
〚Change
the end of first paragraph〛 〚
É 〛for any outline level. |
COR2 |
- |
|
7.4.1/ |
〚Change
the only paragraph〛
The defined values of the text:use-caption attribute are: – true: illustration captions are
used for an index. – false:
illustration names are used for an index. |
COR2 |
- |
|
7.7.1/ |
〚Change
the entire text〛
The text:copy-outline-levels
attribute specifies whether index entries are indented according to the
outline level of their source. The
defined values for the text:copy-outline-levels attribute are: –
false: no indentation is added. – true:
index entries are indented according to the outline level of their source. |
1.0-02 |
N |
|
7.8.2 |
〚Insert
a new paragraph after the only one〛 〚 É 〛an XLink, which points to the resource containing the list of terms. The
format of an index mark file is implementation-dependent. |
COR2 |
- |
|
7.12 |
〚Change
the first sentence〛 There are seven |
COR2 |
- |
|
8.1.1/ |
〚Change,
at the end of the first paragraph〛 〚
É 〛If a table is protected, all of the table's cell elements |
COR2 |
- |
|
8.1.1/ |
〚Change,
at the end of the second paragraph〛 〚
É 〛only a hash value of the password is stored within the table:protection-key attribute. The hashing is implementation-dependent. |
COR2 |
- |
|
8.1.2/ |
〚Change,
in the first paragraph〛 〚 É 〛Cells
contained in the row that don't have a table:style-name |
WG6 |
Y |
|
8.1.2/ |
〚Change,
in the only paragraph〛 The table:visibility attribute specifies – visible: the row is visible – collapse: the row is not visible – filter: the row is not visible as
the result of applying a filter (see section 8.7) The
default is visible. |
COR2 |
- |
|
8.1.3/ |
〚Change,
in the last paragraph, following the schema fragment〛 See section
8.5.3 for more information on cell content validation and the <table: |
WG6 |
Y |
|
8.1.3/ |
〚Change,
in the first sentence〛 The |
COR2 |
- |
|
8.1.3/ |
〚Change,
in the first paragraph〛 The office:value attribute
specifies the current numeric value of a cell. This attribute is |
COR2 |
- |
|
8.1.3/ |
〚Change,
in the first paragraph〛 The |
1.0-2 |
N |
|
8.1.3/ Cell Current Date Value |
〚Change,
in the first paragraph〛 〚
É 〛This attribute is present only
|
COR2 |
- |
|
8.1.3/ |
〚Change,
in the first paragraph〛 〚
É 〛This attribute is present only
|
COR2 |
- |
|
8.1.3/ |
〚Change,
in the first paragraph〛 〚
É 〛This attribute is present only
|
COR2 |
- |
|
8.1.3/ |
〚Change,
in the first paragraph〛 〚
É 〛This attribute |
COR2 |
- |
|
8.1.3/ |
〚Change,
in the first paragraph〛 The table:protect 〚Change,
in the last paragraph〛 〚
É 〛 the |
COR2 |
- |
|
8.2.1/ |
〚Change,
in the first paragraph〛 〚 É 〛cells
that don't have a table:style-name |
WG6 |
Y |
|
8.3.4 |
〚Change,
in the first paragraph〛 The <table:shapes> element contains all |
COR2 |
- |
|
8.4.3 |
〚Change,
in the first paragraph〛 The <table:detective> element contains information about what relationships between the
current cell and other cells are revealed in the presentation of the table. |
COR2 |
- |
|
8.4.4 |
〚Change,
in the first paragraph〛 The <table:operation> element specifies both the type of detective operation that leads to the
discovery of relationships between cells (table:name
attribute) and the order in which those operations are applied (table:index attribute). Once
relationships between cells have been discovered, those cells are highlighted
to show those relationships. |
COR2 |
- |
|
8.4.4/ |
〚Change,
in the only paragraph〛 The table:name attribute
specifies the name of a The defined values for the table:name attribute are: – remove-dependents: removes highlighting from cells that use the value of
the current cell in their formula – remove-precedents: removes
highlighting from cells whose values are use in the formula of the current
cell. – trace-dependents: highlights
cells that use the value of the current cell in their formula. – trace-errors: highlights cells
that cause an error while calculating the result of the current cell's
formula. – trace-precedents: highlights
cells whose values are use in the formula of the current cell. The
nature of the highlighting imposed or removed from cells as the result of
detective operations is implementation dependent. |
COR2 |
- |
|
8.5.1 |
〚Change,
at the end of the only paragraph〛 〚
É 〛a hash value of the password is stored. The hashing is implementation-dependent. |
COR2 |
- |
|
8.5.2/ Search Criteria Must
Apply to Whole Cell |
〚Change
the only paragraph〛 The table:search-criteria-must-apply-to-whole-cell
attribute specifies whether a search pattern from
the table:value
attribute matches the entire content of a cell – false: a search pattern can match
any substring at any position in a cell. – true: a search pattern must match
the entire content of a cell. The table:search-criteria-must-apply-to-whole-cell attribute is only used with the <table:filter-condition>
element when its table:data-type attribute has the value text and its table:operator attribute has one
of the values: – match (i.e. matches) – !match (i.e. does not match) – = (i.e. equal to) – !=
(i.e. not equal to). |
COR2 |
- |
|
8.5.2/ |
〚
Insert after the only paragraph〛 〚 É 〛enabled
for character string comparisons and when searching. The
syntax and semantics of the regular expressions are implementation-dependent. |
COR2 |
- |
|
8.5.3/ |
〚
Change the entire text〛 The table:condition attribute specifies the condition that must evaluate to ÒtrueÓ for all cells the validation rule is applied to. The value of this attribute should be a namespace prefix, followed by an implementation-dependent Boolean expression.
|
COR2 |
- |
|
8.6.10/ |
〚
Insert after the only paragraph〛 〚 É 〛stdevp, sum, var and varp. These
functions are implementation-dependent. |
COR2 |
- |
|
8.7.1/ |
〚
Change in the top row of the Example table〛 〚 É 〛 G | |
COR2 |
- |
|
8.8 |
〚
Change in the only paragraph〛 Data pilot
tables |
COR2 |
- |
|
8.8.4/ |
〚
Insert after the only paragraph〛 〚 É 〛that
no function is applied at all. These
functions are implementation-dependent. |
COR2 |
- |
|
8.8.4/ |
〚
Change in the last sentence of the text〛 〚 É 〛The
value -1 means that no hierarchy
should be applied at all. |
COR2 |
- |
|
8.8.7/ |
〚 Insert
after the only paragraph〛 〚 É 〛sum, var and varp. These
functions are implementation-dependent. |
COR2 |
- |
|
8.9/ |
〚
Insert after the only paragraph〛 〚 É 〛sum, var and varp. These
functions are implementation-dependent. |
COR2 |
- |
|
8.11.7 |
〚Change
the text〛 The <table:change-deletion> element specifies |
N0942:61 |
COR1 |
- |
8.11.8/ Position |
〚Change
the text〛 The table:position
attribute specifies the position where the deletion was made in the
table. Depending on the deletion
type, |
N0942:62 |
COR1 |
- |
8.11.14/ Formulas and Values |
〚Change,
in the first line〛 The change
track table cell |
N0942:63 |
COR1 |
- |
9.1.3 |
〚Change,
in the sentence immediately after the schema fragment〛 The <draw:layer> element |
WG6 |
Y |
|
9.1.4/ Master Page |
〚Change,
in the first list item〛 – Defines properties such as the size and borders
of the drawing page |
N0942:64 |
COR1 |
- |
9.1.5 |
〚Change,
near the bottom of the example〛 <presentation:notes>
<draw:text ...>This is a note</draw:text>
</presentation:notes> </draw:page> </office:body> |
N0942:65 |
COR1 |
- |
9.2.5 |
〚Change,
in the sentence immediately after the schema fragment〛 The attributes
that may be associated with the <draw:regular-polygon> element are: |
WG6 |
Y |
|
9.2.5/ Sharpness |
〚Change,
in the last sentence〛 In general, if
r is the radius of the polygon, and s is the sharpness, the
inner corners are located on an ellipse whose |
N0942:65 |
COR1 |
- |
9.2.6/ Path Data |
〚Change,
in the last sentence〛 Some
implementations may only support |
N0942:42 |
COR1 |
- |
9.2.7/ Radius |
〚Change,
in the last sentence〛 If this
optional attribute is |
N0942:43 |
COR1 |
- |
9.2.9 |
〚Change,
in the first paragraph〛 The <draw:connector>
element represents a Start
and/or end points can be assigned to glue points (see section 9.2.19) or
absolute positions. |
COR2 |
- |
|
9.2.11 |
〚Change,
in the first paragraph〛 The <draw:measure> element represents a shape that
is used to measure distances in drawings. The
layout of the measure shape is implementation-dependent. |
COR2 |
- |
|
9.2.12/ Control |
〚Change,
in the first line〛 The 〚 É 〛 |
N0942:44 |
COR1 |
- |
9.2.15/ |
〚Change,
in the entire text〛 The draw:caption-id
attribute establishes a relationship between a drawing object
See appendix
E for guidelines |
TC |
N |
|
9.2.18 |
〚Change,
in the first sentence〛 The following
defined attributes are common for all shapes that support |
N0942:45 |
COR1 |
- |
9.2.18 |
〚Change,
in the last sentence〛 The following
defined attributes are common for all shapes that support |
N0942:46 |
COR1 |
- |
9.2.19/ Position |
〚Change,
in the first sentence〛 The svg:x and svg:y
attributes specify 〚 É 〛 |
N0942:47 |
COR1 |
- |
9.2.19/ Align |
〚Change,
in the first sentence〛 The attribute draw:align |
N0942:48 |
COR1 |
- |
9.2.19/ Escape Direction |
〚Change,
in the second sentence〛 The value horizontal means that |
N0942:49 |
COR1 |
- |
9.2.20 |
〚Change
the last sentence of the section〛
|
TC |
N |
|
9.3 |
〚Change,
in the first sentence〛 A frame is a
rectangular container 〚 É 〛 |
N0942:50 |
COR1 |
- |
9.3 |
〚Change,
in the third list item after the schema fragment, by inserting a section and
subsection reference〛 – Presentation class – see section 9.6.1 Class |
WG6 |
Y |
|
9.3/ Relative Sizes |
〚Change,
in the fifth paragraph〛 The value scale-min
equals the value scale, except that the 〚 É 〛 |
COR2 |
- |
|
9.3/ Relative Sizes |
〚Change,
at the end of the last paragraph〛 〚 É 〛real
width and heights in the svg:width and svg:height or |
N0942:53 |
COR1 |
- |
9.3/ Copy Frames |
〚Change,
in the last paragraph〛 〚 É 〛This
does not a |
N0942:54 N0942:55 |
COR1 |
- |
9.3.1/ Minimum Height and Width |
〚Change,
in the only paragraph〛 The fo:min-height
and fo:min-width attributes specify a minimum height and 〚 É 〛 |
N0942:56 N0942:57 |
COR1 |
- |
9.3.3 |
〚Change,in
the last item of the first list and the paragraph just before the schema
fragment〛 – Objects that do not have an XML
representation. These objects only have a binary representation. The <draw:object> element represents objects that have an
XML representation. 〚 É 〛 |
N0942:58 N0942:59 |
COR1 |
- |
9.3.3/ |
〚Change,in
the first list item〛 – The xlink:href attribute links to the object
representation, as follows: −
For
objects that have an XML representation, the link references the sub package
of the object. |
N0942:60 |
COR1 |
- |
9.3.9 |
〚NOTE:
In ODF 1.0 (and COR1), there was a section 9.3.9 that is not present in ODF
1.1 and is also removed in AMD1.
The ODF 1.1 section 9.3.9 corresponds to section 9.3.10 in COR1.] Frames may
behave like hyperlinks. Such
hyperlinks are represented by the <draw:a> element, where |
N0942:1 |
COR1 |
- |
9.3.9/ |
〚Change,in
the last paragraph〛 〚 É 〛
If the value of |
N0942:2 N0942:3 |
COR1 |
- |
9.3.10/ |
〚NOTE:
In ODF 1.0 (andCOR1), there was a section 9.3.9 that is not present in ODF
1.1 and is also removed in AMD1.
The ODF 1.1 section 9.3.10 corresponds to section 9.3.11 in COR1. Change,in
the first list item〛 – Link, including an IRI and link target frame. |
N0942:4 |
COR1 |
- |
9.4 |
〚Insert,
as the first paragraph of the section〛 3D
shapes are used to define geometry inside coordinate systems. All ODF
coordinate systems are right-handed. Geometry is represented by a tree of
scenes. Each scene may contain zero or more 3D shapes, with scene being a
special case of shape. The root scene defines the world coordinate system.
Each 3D shape may define a local coordinate system relative to its parent 3D
scene. |
COR2 |
- |
|
9.4.1/ |
〚Change,in
the last list item〛 – rotatez (<rotate-angle> ), which specifies a rotation by <rotate-angle> degrees along
the z |
N0942:5 |
COR1 |
- |
9.4.5 |
〚Change,in
the first paragraph〛 The <dr3d:extrude> element represents a
three-dimensional extruded object
based on |
COR2 |
- |
|
9.4.6 |
〚Change,in
the first paragraph〛 The <dr3d:rotate> element represents a
three-dimensional rotation shape based on |
COR2 |
- |
|
9.5 |
〚Change,at
the end of the first paragraph〛 〚 É 〛that
provide a simple way to modify the |
N0942:6 |
COR1 |
- |
9.5.2/ |
〚Addition,
after the only paragraph〛 The draw:extrusion-first-light-harsh attribute specifies if the primary light is harsh. When the
attribute value is true, the
light is harsh. The light is an undiffused point source. When the attribute
value is false, the light is not harsh. The means
by which the light is softened is implementation-dependent. |
COR2 |
- |
|
9.5.2/ |
〚Addition,
after the only paragraph〛 The draw:extrusion-second-light-harsh attribute specifies if the secondary light is harsh. When the
attribute value is true, the
light is harsh. The light is an undiffused point source. When the attribute
value is false, the light is not harsh. The means
by which the light is softened is implementation-dependent. |
COR2 |
- |
|
9.5.3/ |
〚Change
in the first paragraph〛 〚
É 〛other instructions together with |
WG6 |
N |
|
9.5.3/ |
〚Change
in the list of parameter enhancements
Ò?Ó and Ò$Ó〛 – If
Ò$Ó |
WG6 |
N |
|
9.5.3/ |
〚Change,
at the beginning of the Description Entry for Command A〛 (x1,y1) and
(x2,y2) |
WG6 |
N |
|
9.5.3/ |
〚Change,
at the end of the Description Entry for Command A〛 〚 É 〛the
end-angle that is specified by point (x |
N0942:7 |
COR1 |
- |
9.5.3/ |
〚Change,
in the Description Entry for Command B〛 The same as
the ÒAÓ command, except that an
implied moveto to the starting point is done. |
N0942:8 |
COR1 |
- |
9.5.3/ |
〚Change,
in the Description Entry for Command V〛 The same as
the ÒAÓ command, except that an
implied moveto to the starting point is done and the arc is drawn clockwise. |
N0942:9 |
COR1 |
- |
9.5.3/ |
〚Change,
in the first paragraph〛 The draw:text-areas
attribute specifies an optional list
of text areas. The text areas are |
WG6 |
N |
|
9.5.3/ |
〚Change,
in the second list item〛 – If
Ò$Ó |
N0942:10 |
COR1 |
- |
9.5.3/ |
〚Change,
in the last paragraph〛 An example of the 〚 É 〛 |
N0942:11 |
COR1 |
- |
9.5.3/ |
〚Change,
in the first paragraph〛 The draw:glue-points
attribute specifies a list of object defined glue points. |
WG6 |
N |
|
9.5.3/ |
〚Change,
in the second list item〛 – If
Ò$Ó |
N0942:12 |
COR1 |
- |
9.5.3/ |
〚Change,
in the last paragraph〛 An example of the draw:glue-points
attribute that defines two glue points, including modifier and equation
usage, would be: draw:glue-points= |
N0942:13 |
COR1 |
- |
9.5.3/ |
〚Change,
in the last list item〛 – rectangle:
the middle of each side of the shape bound rectangle specifies an object specific glue point |
N0942:14 |
COR1 |
- |
9.5.3/ |
〚Change,
in the last sentence〛 The position
in the list is the same as the |
N0942:15 |
COR1 |
- |
9.5.5/ |
〚Change,
in the last sentence〛 Due to the
fact that modifier values may be changed
〚 É 〛 |
N0942:16 |
COR1 |
- |
9.5.5/ |
〚Change,
in the first paragraph〛 〚 É 〛A
formula can make use of other formulas or modifier values by function |
N0942:17 |
COR1 |
- |
9.5.5/ |
〚Change,
in the table heading row〛 I |
N0942:18 |
COR1 |
- |
9.5.5/ |
〚Change,
in the Description entry for Identifier ÒtopÓ〛 The top
position of the svg:viewBox
attribute has to be used. |
N0942:19 |
COR1 |
- |
9.5.5/ |
〚Change,
in the Description entry for Identifier ÒrightÓ〛 The right
position of the svg:viewBox
attribute has to be used. |
N0942:20 |
COR1 |
- |
9.5.5/ |
〚Change,
in the Description entry for Identifier ÒbottomÓ〛 The bottom
position of the svg:viewBox
attribute has to be used. |
N0942:21 |
COR1 |
- |
9.5.5/ |
〚Change,
in the last paragraph〛 An example for the draw:formula
attribute 〚 É 〛 |
N0942:22 |
COR1 |
- |
9.5.6/ |
〚Change,
in the second list item〛 – If
Ò$Ó |
N0942:23 |
COR1 |
- |
9.7.2/ |
〚Change,
in the tenth list item〛 – lines: the shape is faded in or |
N0942:24 |
COR1 |
- |
9.8.1 |
〚Change,
at the end of the first paragraph〛 〚 É 〛animate
a single shape |
N0942:25 |
COR1 |
- |
9.8.2/ |
〚Change,
in the first sentence〛 For
presentation documents, the |
N0942:26 |
COR1 |
- |
9.9/ |
〚Change,
in the eighth list item〛 – execute:
another application is launched when
this event is triggered. 〚 É 〛 |
N0942:27 |
COR1 |
- |
9.10 |
〚Change,
in the first sentence〛 This section
describes text fields that are specific to the text of drawing shapes that
are contained in presentations. |
N0942:28 |
COR1 |
- |
9.11.4/ |
〚Change,
in the first sentence〛 The presentation:source attribute specifies whether the current date/time or the fixed
content of the |
N0942:29 |
COR1 |
- |
10.3.1 |
〚Change,
in the only paragraph〛 〚 É 〛This
element can contain fixed text or it can |
TC |
N |
|
11.6 |
〚In
the Value of script:event-name Attribute column of the table, correct
the entry for Òform:startrealodÓ, adjusting the alphabetical index entry
accordingly〛
|
WG6 |
Y |
|
11.7.3 |
〚Change,
at the end of the first paragraph〛 (See section
6.7.1 for more information on value
and value type attributes.) |
N0942:82 |
COR1 |
- |
12.4 |
〚At
the end of the last list item where the referenced section number is missing
or an error is indicated, insert a cross reference by number to section 9.9
Presentation Events〛 〚 É 〛Presentation
events are described in section 9.9. |
N0942:83 |
COR1 |
- |
12.4.1/ |
〚 In
the Value of script:event-name Attribute column of the table, correct the
entry for Óon-mouseoutÓ, adjusting the alphabetical index entry accordingly〛
|
WG6 |
Y |
|
14.5.1 |
〚Change,
at the end of the first paragraph〛 〚 É 〛They
have a text:style-name attribute that references these styles. |
WG6 |
Y |
|
14.5.1 |
〚Add
period at the end of the second paragraph〛 〚 É 〛created
in the corresponding cells. |
WG6 |
Y |
|
14.5.1 |
〚In
schema fragment lines 11519-11523 the <optional> element should include
the <attribute> element, not the reverse.〛 11519 <optional> 11520 <attribute
name="text:paragraph-style-name"> 11521 <ref
name="styleNameRef"/> 11522 </attribute> 11523 </optional> |
WG6 |
Y |
|
14.7.9/ |
〚Change,
at the end of the first paragraph〛 〚 É 〛The
country |
N0942:84 |
COR1 |
- |
14.10.3/ |
〚In
the table, change the ÒUNICODE Character NameÓ entry for UNICODE Character
Code U+2794〛 HEAVY WIDE-HEADED RIGHTWARDS ARROW |
WG6 |
Y |
|
15.4.7 |
〚Change,
in the last line of the only paragraph〛
|
N0942:38 |
COR1 |
- |
15.4.8 |
〚Change,
in the next to last sentence of the only paragraph〛
|
N0942:38 |
COR1 |
- |
15.4.19 |
〚Change
the first sentence of the second paragraph〛 |
WG6 |
- |
|
15.4.29 |
〚Change,
in the last line of the only paragraph〛
|
N0942:38 |
COR1 |
- |
15.4.30 |
〚Change,
in the last line of the only paragraph〛
|
N0942:38 |
COR1 |
- |
15.4.33 |
〚Change,
in the last line of the only paragraph〛
|
N0942:38 |
COR1 |
- |
15.4.34 |
〚Change,
in the last line of the only paragraph〛
|
N0942:38 |
COR1 |
- |
15.4.38 |
〚Change
the entire text〛
The style:text-combine attribute
specifies whether to combine characters so that they are displayed within two
lines. The defined values for the
style:text-combine attribute are: – letters: Display text in
Kumimoji. Up to five (5) characters are combined within two lines and are
displayed with a reduced size in a single wide-cell character. Additional
characters are displayed as normal text. – lines: Displays text in Warichu.
All characters with the style:text-combine attribute that immediately follow each other are
displayed within two lines of approximately the same length. A line break may
occur between any two characters to meet this constraint. – none: characters should not be combined. |
COR2 |
- |
|
15.5.20 |
〚Change
in the first paragraph〛 〚 É 〛If
the attributes are |
WG6 |
- |
|
15.5.29 |
〚Change
in the referencing of [XSL]〛 See ¤7.14.9 |
N0942:31 |
COR1 |
- |
15.5.38 |
〚Change
in the title of the section〛 15.5.38
Snap To Layout
Grid |
N0942:67 |
COR1 |
- |
15.5.38 |
〚Change
in the first sentence〛 The style:snap-to-layout-grid
attribute |
WG6 |
N |
|
15.10.1 |
〚Change
the second paragraph〛 The style:row-height property specifies a fixed row
height, while the style:min-row-height property
specifies a |
N0942:97 |
COR1 |
- |
15.11.9 |
〚Change
in the only paragraph〛 〚
É 〛properties of the border lines of the cell |
N0942:98 |
COR1 |
- |
15.11.11 |
〚Change
in the first referencing of [XSL]〛 See ¤7.15.13 of [XSL] for details. |
N0942:32 |
COR1 |
- |
15.12/ |
〚Change
in the only paragraph〛 The style:font-name attribute specifies 〚 É 〛 |
N0942:96 |
COR1 |
- |
15.14.12 |
〚Change
in the first paragraph〛 〚
É 〛This attribute is only interpreted if the value of the current style:repeat attribute is |
COR2 |
- |
|
15.19 |
〚Change
in the only paragraph〛 〚 É 〛contained in all kinds of
applications. The layout of the connector is implementation-dependent. |
COR2 |
- |
|
15.20 |
〚Change
in the only paragraph〛 〚 É 〛contained in all kinds of
applications. The layout of the measure drawing objects is
implementation-dependent. |
COR2 |
- |
|
15.22.5 |
〚Change
in the first paragraph〛 The |
COR2 |
- |
|
15.22.8 |
〚Change
in the first paragraph〛 The
attribute dr3d:end-angle specifies the rotation
angle for 3D |
COR2 |
- |
|
15.22.9 |
〚Change
in the only paragraph〛 The dr3d:close-front property specifies whether a front
plane |
COR2 |
- |
|
15.22.10 |
〚Change
in the only paragraph〛 The dr3d:close-back property describes if a back plane |
COR2 |
- |
|
15.24.4 |
〚Change
in the only paragraph〛 The attribute dr3d: – blend: blends the texture color with the object color. – modulate: modulates the object color with the texture color. – replace: replaces the object color with the texture color. |
COR2 |
- |
|
15.27.21 |
〚Change
in the list entries〛 ¥
right: Text may wrap
around the right |
N0942:92 |
COR1 |
- |
15.27.31 |
〚Change
in the first paragraph after the schema fragment〛 〚
É 〛Without wrapping, the images overlie |
N0942:90 |
COR1 |
- |
15.27.31 |
〚Change
in the second paragraph after the schema fragment〛 〚
É 〛This corresponds to the option |
N0942:94 |
COR1 |
- |
15.28.3 |
〚Change
in the only paragraph〛 The draw:frame-margin-horizontal
and draw:frame-margin-vertical
attributes〚 É 〛 |
N0942:88 |
COR1 |
- |
15.28.4 |
〚Change
the only paragraph〛 The
attributes described in 15.28.5 and 15.28.6 |
N0942:93 |
COR1 |
- |
15.28.6 |
〚Change
the first sentence〛 For embedded
OLE objects, the draw:ole-draw-aspect
attribute 〚 É 〛 |
WG6 |
- |
|
15.30.4 |
〚Change
the only paragraph〛 The width
and height of each symbol can be set using the attribute chart:symbol-width and chart:symbol-height |
N0942:87 |
COR1 |
- |
15.30.9 |
〚Change
the last sentence〛 The line
interpolation is determined by the chart:interpolation |
N0942:86 |
COR1 |
- |
15.31.2 |
〚Change
the first sentence〛 To determine
whether or not an axis object is visible, use the chart: |
N0942:85 |
COR1 |
- |
15.31.3 |
〚Change
in the first two paragraphs〛 〚 É 〛However,
the chart: The optional
chart: |
N0942:81 |
COR1 |
- |
15.31.4 |
〚Change
the text〛 The tick
mark properties are used to specify the existence of tick marks at an axis.
The major marks are drawn with respect to the major interval that may be
specified by the chart: |
COR1 |
- |
|
15.36 |
〚Change
in the first paragraph〛 〚 É 〛They are contained in a <style:style-drawing-page-properties> element. |
N0942:77 |
COR1 |
- |
15.36 |
〚Change
end of list immediately before 15.36.1〛 – Display Date and Time – Transition Type or Family – Transition Subtype – Transition Direction – Fade Color |
N0942:75 |
COR1 |
- |
15.36.8 |
〚Change
in the first paragraph〛 The attribute presentation: |
N0942:76 |
COR1 |
- |
15.36.10 |
〚Change
the text〛 Sound effects can be added to your presentation pages using
the element presentation:sound. |
N0942:72 |
COR1 |
- |
16.1 |
〚In
the list item for custom data types,change in the first paragraph of the
entry for Òlength.Ó Zoom the text
to clearly see the difference in the quotation marks.〛 – length A (positive, zero, or
negative) physical length, consisting of magnitude and unit, in conformance
with ¤5.9.11 of [XSL]. Supported
units are |
N0942:74 |
COR1 |
- |
16.1 |
〚In
the list item for custom data types,change the entry for ÒvalueType.Ó 〛 – valueType A
list of |
N0942:74 |
COR1 |
- |
17.6 |
〚Change
in the last paragraph〛
|
N0942:74 |
COR1 |
- |
17.7.3/ |
〚Change
in the text〛 〚 É 〛For a full list of mime types
see http://www.isi.edu/in-notes/iana/assignments/media-types/media-typeshttp://www.iana.org/assignments/media-types/. |
N0942:36 |
COR1 |
- |
17.7.4 |
〚Change
the first sentence after the schema fragment〛 The <manifest:encryption-data>
element contains the following elements: |
COR2 |
- |
|
17.7.6/ |
〚Change
in the text〛 The manifest:key-derivation-name attribute specifies the
name of the algorithm used to derive the encryption
key |
N0942:69 |
COR1 |
- |
Appendix B |
〚In the References entry for [ZIP],
change the URL〛
|
1.0-02 TC |
N |
|
Appendix D |
〚In the table entry for Section 12.2,
change the Title〛 Number Format |
N0942:71 |
COR1 |
- |
Appendix D |
〚In the table entry for Section 15.16,
change the Title〛 Text and Text Alignment
Properties |
N0942:71 |
COR1 |
- |
Appendix E.4 |
〚Change the only paragraph〛 Please see the additional, detailed Accessibility
Guidelines http://docs.oasis-open.org/office/office-accessibility/v1.0/. |
WG6 |
N |
|
Appendix F/ |
〚In the last sentence of the last
paragraph〛 〚
É 〛number:calendar
attribute specified in section 14.7.11. |
WG6 |
N |
This informative document has no conformance clauses.
The OASIS Open Document Format
for Office Applications (OpenDocument) TC gratefully acknowledges the
contribution and partnership of the ISO/IEC JTC1 SC34 WG6 working group on ODF
Maintenance for its participation in
the creation of technical alignment between OASIS ODF 1.1 and the International
Standard.
Participants
At the OpenDocument TC the following individuals have participated in the creation of this specification and are gratefully acknowledged.
Chieko Asakawa, IBM
Thorsten Behrens, Novell
Camilla Boemann, KDE e.V.
Suresh Chande, Nokia Corporation
Robin Cover, OASIS
Jerome Dumonteil, Ars Aperta
Patrick Durusau, Individual Member
Cherie Ekholm, Microsoft Corporation
Jean Gouarne, Ars Aperta
Andreas J. Guelzow, Individual Member
Zhun Guo, Individual Member
Dennis E. Hamilton, Individual Member
Bart Hanssens, Fedict
Donald Harbison, IBM
John Haug, Microsoft Corporation
Regina Henschel, The Document Foundation
Mingfei Jia, IBM
Peter Junge, Beijing Sursen Electronic Technology Co., Ltd.
Kazmer Koleszar, MultiRacio Ltd.
Peter Korn, Oracle Corporation
Jirka Kosek, Individual Member
Robin LaFontaine, Individual Member
David LeBlanc, Microsoft Corporation
Fong Lin, Novell
Yue Ma, IBM
Doug Mahugh, Microsoft Corporation
Gervase Markham, Mozilla Corporation
James Mason, ISO/IEC JTC1/SC34
Tristan Mitchell, Individual Member
Eric Patterson, Microsoft Corporation
Steven Pemberton, Stichting Centrum voor Wiskunde & Informatica
Chris Rae, Microsoft Corporation
PŽter Rakyta, MultiRacio Ltd.
Asokan Ramanathan, IBM
Andre Rebentisch, Ars Aperta
Douglas Schepers, Individual Member
Svante Schubert, Individual Member
Charles Schulz, Ars Aperta
Richard Schwerdtfeger, IBM
Wei Gui Shi, IBM
Yan Shi, Beijing Sursen Electronic Technology Co., Ltd.
Jomar Silva, OpenDocument Format Alliance
Keld Simonsen, ISO/IEC JTC1/SC34
Michael Stahl, Red Hat
Louis Suarez-Potts, Individual Member
Hironobu Takagi, IBM
Malte Timmermann, Oracle Corporation
John Tolbert, The Boeing Company
Jos van den Oever, KED e.V.
Alex Wang, Beijing Sursen Electronic Technology Co., Ltd.
Robert Weir, IBM
David A. Wheeler, Individual Member
Olvier-Rainer Wittmann, IBM
Kohei Yoshida, Novell
Helen Yue, IBM
Thorsten Zachmann, Nokia Corporation
Some items in previous errata and corrigenda for ODF 1.0 are not reflected in ODF 1.1 Errata 01. The omissions are because they do not apply to the ODF 1.1 text or they have been disposed of in some other manner.
This informative Appendix provides an accounting for those so it can be understood why those items and related issues are not transposed to ODF 1.1. This material can also be used to verify that all previous issues and defect reports have been accounted for and none have been overlooked.
Section/ |
Explanation |
Issue |
Source |
Amd? |
15.27.22 |
In the schema
fragment, the change of -treshold to -threshold has already been made in ODF 1.1. |
N0942:91 |
COR1 |
- |
15.31.3 |
COR1 makes the
following changes: 〚Change
the last paragraph (preceding the last schema fragment)〛 chart:interval-major,
chart:interval-minor However, the
ODF 1.0 schema defines only chart:interval-minor. For ODF 1.1, the inconsistency is
resolved by defining chart:interval-minor-divisor
in the schema and leaving the original text intact. ODF 1.2 also uses chart:interval-minor-divisor alone. |
N0942:80 |
COR1 |
- |
Appendix B |
COR1 makes a
change to the URL for [DOMEvents].
That reference does not occur in ODF 1.1. Instead, there are new references,
[DOMEvents2] and [DOMEvents3] to which the COR1 change does not apply. IS 26300:2006/AMD1 makes an
appropriate adjustment as part of ODF 1.1 alignment. |
N0942:39 |
COR1 |
- |
There are errata instructions in this ODF 1.1 Errata 01 that are not reflected in IS 26300:2006/Amd1. This Appendix identifies each of them and where they apply.
The explanation includes instructions for making aligning changes to an IS 26300:2006 with COR1, COR2, and AMD1 applied. In some cases the correction is for a deviation introduced in COR1 or COR2.
Section/ |
Explanation |
Issue |
Source |
Amd? |
3.1.18 |
〚Change,
in the schema, starting at line 791〛 〚
É 〛 <optional>
<attribute name="meta:frame-count">
<ref name="nonNegativeInteger"/>
</attribute> </optional> <optional>
<attribute name="meta:sentence-count">
<ref name="nonNegativeInteger"/>
</attribute> </optional> <optional>
<attribute name="meta:syllable-count">
<ref name="nonNegativeInteger"/>
</attribute> </optional> <optional>
<attribute name="meta:non-whitespace-character-count">
<ref name="nonNegativeInteger"/>
</attribute> </optional> |
TC |
N |
|
7.7.1/ |
The correction
for this section in ODF 1.0 Errata 02 was transposed to IS 26300:2006/COR2
incorrectly. This change repairs
IS 26300:2006/COR2 〚In the
list defined values, correct the first item〛 – false: no indentation is added |
1.0-2 |
N |
|
8.1.3/ |
The correction
for this section in ODF 1.0 Errata 02 was transposed to IS 26300:2006/COR2
incorrectly. This change repairs
IS 26300:2006/COR2 〚Change,
in the first paragraph〛 The office:currency attribute specifies the currency system in which the value of the office:value attribute is expressed. 〚 É 〛 |
1.0-2 |
N |
|
9.2.15/ |
〚Change,
in the entire text〛 The draw:caption-id
attribute establishes a relationship between a drawing object
See appendix
E for guidelines |
TC |
N |
|
9.2.20 |
ODF 1.1 Errata
01 alignment is achieved by applying this correction to a change introduced
in IS 26300:2006/AMD1. 〚Change
the last sentence of the section〛
|
TC |
N |
|
9.3.3/ |
The second
part of this errata item (replacing xlink by link) applies to text introduced
by IS 26300:2006/COR1 〚Change,in
the first list item〛 – The xlink:href attribute links to the object
representation −
For
objects that have an XML representation, the link references the sub package
of the object. For objects that
have an XML representation, the representation of the object is equivalent to
a separate document representing that object, except it is stored in a folder
in the document package. The |
N0942:60 |
COR1 |
- |
9.5.3/ |
〚Change
in the first paragraph〛 〚
É 〛other instructions together with |
WG6 |
N |
|
9.5.3/ |
This change
applies to a passage as it already appears in ODF 1.1 and as it appears after
IS 26300:2006/AMD1. 〚Change
in the list of parameter enhancements
Ò?Ó and Ò$Ó〛 – If
Ò$Ó |
WG6 |
N |
|
9.5.3/ |
〚Change,
at the beginning of the Description Entry for Command A〛 (x1,y1) and
(x2,y2) |
WG6 |
N |
|
9.5.3/ |
〚Change,
in the first paragraph〛 The draw:text-areas
attribute specifies an optional list
of text areas. The text areas are |
WG6 |
N |
|
9.5.3/ |
This change
modifies the text as modified by COR1.
〚Change,
in the second list item〛 – If
Ò$Ó |
N0942:10 |
COR1 |
- |
9.5.3/ |
〚Change,
in the first paragraph〛 The draw:glue-points
attribute specifies a list of object defined glue points. |
WG6 |
N |
|
9.5.3/ |
This change
modifies the text as modified by COR1.
〚Change,
in the second list item〛 – If
Ò$Ó |
N0942:12 |
COR1 |
- |
9.5.3/ |
The correction
to ÒAnÓ is from COR1. 〚Change,
in the last paragraph〛 An example of the draw:glue-points
attribute that defines two glue points, including modifier and equation
usage, would be: draw:glue-points= |
N0942:13 |
COR1 |
- |
9.5.6/ |
This change
modifies the text as modified by COR1. 〚Change,
in the second list item〛 – If
Ò$Ó |
N0942:23 |
COR1 |
- |
10.3.1 |
〚Change,
in the only paragraph〛 〚 É 〛This
element can contain fixed text or it can |
TC |
N |
|
15.5.38 |
Change in
the first sentence〛 The style:snap-to-layout-grid
attribute |
WG6 |
N |
|
15.31.3 |
〚This
correction rescinds an IS 26300 deviation introduced via IS 26300:2006/COR1.
〚Change
in the last paragraph (preceding the last schema fragment)〛 〚
É 〛chart:interval-major, chart:interval-minor-divisor
– set major and minor interval for ticks or markings on the axis. The chart:interval-major defines the interval value. The
minor interval is determined by dividing the chart:interval-major
value by the chart:interval-minor-divisor. |
TC |
N |
|
Appendix B |
〚In the References entry for [ZIP],
change the URL〛
|
1.0-2 TC |
N |
|
Appendix E.4 |
〚Change the only paragraph〛 Please see the additional, detailed Accessibility
Guidelines http://docs.oasis-open.org/office/office-accessibility/v1.0/. |
WG6 |
N |
|
Appendix F/ |
〚In the last sentence of the last
paragraph〛 〚
É 〛number:calendar
attribute specified in section 14.7.11. |
WG6 |
N |