OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Errata Draft 14


Dear TC members,

as stated in my previous mail, the OpenOffice.org developers did run
some validation tests with the new OASIS Open Office filter in the
OpenOffice.org application and the schema contained in draft 14. They
unfortunately did not only find the already posted bugs in the schema
itself, but also a few other issues that can be classified as follow:

A) elements or attributes that are contained in the OpenOffice.org DTD
but were not properly specified in the OpenOffice.org file format
specification, and for that reason, got lost in the OASIS Open Office
schema.

B) elements or attributes that are conatained in the OpenOffice.org and 
also in the OASIS Open Office schema, but are used in the OpenOffice.org 
schema in a way that is not allowed in the OASIS Open Office schema any 
longer.

C) others issues

My proposal is to include these issue into the draft we are currently
preparing. I further would like propose to delay the committee
draft voting to the first week of November, so that we may have a closer
look at it and espacially the changes we are going to make. I


Class A issues
==============
A1) The <text:sheet-name> element is missing. This element describes a
text field (as decribed in section 6) that displays the name of a sheet 
in spreadsheet documents.

A2) The <draw:page> element described in section 9.1.4 may have an 
"draw:id" that assigns an ID to it.

A3) The graphics property "dr3d:end-angle" is missing (would go into 
section 15.22). It takes a non negative integer as value and specifies 
the rotation angle for 3D lathe objects. If it's the value is the 
default (360), the lathe object is closed and completely rotated. With 
smaller values it is possible to define opened lathe objects (segments). 
The then visible sides are closed and take into account the 
dr3d:back-scale and dr3d:edge-rounding attributes. With bigger values it 
is possible to create lathe objects with more than one rotation. This 
will only have a visible effect when e.g. dr3d:back-scale is used.

For example, with a end angle of 270, the lathe object will be opened
by 90.

A4) The graphics property "draw:fit-to-contour" is missing. The property
is similar to "draw:fit-to-size" described in section 15.16.2, but
specifies that the drawing object's text is stretched to fit the contour
of the drawing shape.

A5) A boolean "draw:recreate-on-edit" attribute is mising at the
<draw:contour-polygon> and <draw:contour-path> elements decribed in
section 9.3.8. It specifies that a drawing object's contour should be
recreated aumatically if the object is edited.

A6) The boolean "dont-balance-text-colunms" section property is missing 
(would go into section 15.7). It specifies whether the text column 
content should be evently distributed over all caolumns or not.

A7) The boolean "text:enable-numbering" paragraph property is missing 
(would go into section 15.5. It controls whether a paragraph contain in 
a draing object is numbered. See also B2).


Class B issues
==============
B1) The "style:writing mode" formatting property described in section 
15.5.35 can be used as page layout and paragraph property only, but
should be usable as table and section property as well. That is,
"style:writing-mode" should also be an attribute of
"<style:table-properties>" and "<style:section-properties>".

In the OOo DTD all formatting properties were contained in the
<style:properties> element, so style:writing-mode could be used for
table and section styles.

B2) A graphic style may contain a full list style, that is
<text:list-style> may be contained in a <style:graphic-properties>
element. The reason is that graphic styles in presentation documents may
include the definition of list styles that are applied to the text of
for instance a text box. These list styles do not appear in the UI as a
style of its own, but are a simple setting of a graphic style. Since 
real styles may not reference automatic styles, it is required to
include the list style settings in the graphic style itself. A
<text:list-style> contained in a <style:graphic-properties> element must
not have a <text:name> attribute.

Whether the list style is applied to a certain paragraph that is
contained in a drawing object is controlled by the
"text:enable-numbering" property described in A7).

In the OOo DTD, the content of <style:properties> was ANY, so
<text:list-style> was allowered there. The "text:name" attribute of 
"<text:list-style>" was #IMPLIED.

B3) The <style:list-level-style-properties> element currently may
contain a "style:font-name" attribute that specifies the name of the
font to be used to format a bullet or number. In fact, there are some
more text properties that might be applied to list style levels, like a
font size. To not add additional attributes to the
<style:list-level-style-properties>, one may add the full
<style:text-properties> element to the <style:list-level-style-*>
elements in addition to <style:list-level-properties>.

In the OOo DTD, all formatting properties were contained in the
<style:properties> element, so all text formatting properties could be
used inside a list level style.



Class C issues
==============
C1) In the proposal for presentation headers and footers, it was missing
that headers and footers do not only exist for drawing pages, but also
for presentation notes pages as described in section 14.4.2. To support 
this, the <draw:page> attributes "presentation:user-header-name", 
"presentation:user-footer-name" and "presentation:user-footer-name" 
described in section have 9.1.4 to exist for the <presentation-notes> 
element (decribed in section 14.4.2) as well. In addition to this, the 
<presentation:notes> element requires a "draw:style-name" attribute that 
reference a drawing page style, because it is the drawing page style 
that controls whether heeaders and footers are actually displayed.

C2) There is an issue with the "text:outline-level" attribute in section
7.3.1. It currently is

"The |text:outline-level| attribute specifies which outline levels are
used when generating the table of contents. The value of this attribute
must be |none| or an integer greater than zero. If the
value of this attribute is none, no entries are generated from the
outline. If this attribute is omitted, all outline levels are used by
default."

In fact, the level specified by the attribute is also applied to text
content index marks and paragraph styles that are specified in the index
source. That is, one could specify that the table of content should only 
contain entries specified by index marks up to a certain level, but 
should not contain entries for the paragraphs whose styles are contained 
in the outline numbering, That's not covered by the specification. To 
cover this situation, an additional attribute "text:use-outline-level" 
is required.

The specication then could look like this:

[changed] 7.3.1[.1] Outline Level
The |text:outline-level| attribute specifies which outline levels are
used when generating the table of contents. The value of this attribute
must be an integer greater than zero. If this attribute is omitted, all
outline levels are used by default.

<define name="text-table-of-content-source-attlist" combine="interleave">
<optional>
   <attribute name="text:outline-level">
    <ref name="positiveInteger"/>
   </attribute>
  </optional>
</define>


[new] 7.3.1[.2] Use Outline
The text:use-outline-level attribute specifies whether heading are used
to generate entries for the table of content. The text:outline-level
flag determines up to which outline level headings are being included.

<define name="text-table-of-content-source-attlist" combine="interleave">
<optional>
   <attribute name="text:use-outline-level" a:defaultValue="true">
     <ref name="boolean"/>
   </attribute>
  </optional>
</define>


[changed] 7.3.1[.3] Use Index Marks
[...] The text:outline-level flag determines up to which outline level
index marks are being included.

[changed] 7.3.1[.4] Use Index Source Styles
[...] The text:outline-level flag determines up to which outline level
index source styles are being included.


Best regards

Michael




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]