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: [office] Open Office XML Format TC Meeting Minutes September 15th,2003



Doug Alberg <doug.alberg@boeing.com>, Boeing
Simon Davis <simond@naa.gov.au>, National Archive of Australia
Gary Edwards <garyedwards@yahoo.com>
David Faure <faure@kde.org>
Paul Grosso <pgrosso@arbortext.com>, Arbortext
Tom Magliery <Tom.Magliery@corel.com>, Corel
Uche Ogbuji <uche.ogbuji@fourthought.com>
Daniel Vogelheim <daniel.vogelheim@sun.com>, Sun

Acceptance of Minutes of the September 8 meeting
- The attending TC members unanimously accepted the minutes.

Action Items
- Phil Boutros: create proposal for unifying change tracking in text and 
table documents
- in progress
- Paul Langille: additional chart format comparisons
- in progress
- Paul Langille,Daniel Vogelheim: proposal for business charts
- in progress

Discussion of Work Package 5.3 Style Properties

Discussion of Text/Paragraph Properties

An open issue from last week's meeting was to determine the meaning of 
the current alignment attribute and the start/end values that are 
specified for this attribute. Due to a misunderstanding this was not 
completed, and now it's Daniel's action item to determine this.

Discussion of Section Properties

The TC discussed section properties. Addition of margin attributes to 
sections has already been discussed and agreed upon previously.

The TC also discussed the meaning and use for sections in the OASIS 
format compared to Microsoft Word. There are some differences, but no 
use case was found in which a document couldn't be represented. No 
proposals to change the format were made.

Discussion of Graphics Properties

The TC started discussing graphics properties. Daniel requested that a 
new attribute style:flow-with-text be added, which specifies that 
graphics positioned at a distance from their anchor follow the text 
flow. Example: A graphics is to be positioned 10cm below its anchor. It 
is followed by only 8cm of text before the next page break. With 
style:flow-with-text='false' the graphics would then be positioned 2cm 
below the text area (somewhere in the footer); with 
style:flow-with-text='true' it would positioned 2cm into the text flow 
of the following page. The TC accepted the proposal.

The TC also discussed behaviour of graphics which are positioned 
horizontally outside of the visible area; in particular, whether 
graphics positioned outside the visible area should be moved into the 
visible area by renderers. The TC agreed that, if such behaviour is 
desired, it should be an application specific document setting, rather 
than a graphics attribute.

A question on graphics formats came up. The TC has already agreed 
earlier that the specification will recommend support for PNG, JPEG and 
SVG graphics.

The representation of the same graphics in multiple instances was 
discussed. This can be achieved by linking to the same graphics. This 
cannot currently be represented when using base64 encoded graphics. No 
conclusion/proposal on this issue was reached.

David requested that graphics should have a draw:keep-aspect-ratio 
attribute, which informs applications that graphics resizing should not 
change the graphic's aspect ratio. The TC unanimously agreed to include 
this attribute in the specification.

New Action Items

Daniel: Determine meaning of the paragraph alignment values.


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