OASIS Open Document Format for Office Applications (OpenDocument) TC

As per my action item to kick of the work on specifying style property defaults, 
  have produced the attached document. It includes tables listing all the style 
property attributes that appear in various property sets that are set down in 
the ODF schema. Only for the paragraph-properties have I started to fill in some 
defaults.

I would like to get some feedback on whether you think this is the right way to 
progress on gathering all the defaults which could then be integrated into the 
spec - either in this tabular format, or in an ODF/XML representation (or both).

One possible mode of operation would be for each implementor to go through the 
list and fill in what they think should be the default and if there is 
disagreement on specific properties, we try to come to a consensus.

One possible problem may be, that the property-sets may appear in various 
combinations in the context of styles from different families. When we discussed 
this in the call, we decided to try to leave the family context out of the 
picture for the defaults if possible - thus, this is how we start. Furthermore, 
different types of applications may have different ideas about defaults. Again, 
we decided to start with one set, assuming that the differences for particular 
application types would be small enough that they can be represented through 
default-style elements written by the application in question...

Cheers,
Lars


-- 
Sun Microsystems                Lars Oppermann 

On 02/11/2007, Lars Oppermann 

Dave Pawson wrote:
> On 02/11/2007, Lars Oppermann 

On 02/11/2007, Lars Oppermann 

Dave Pawson wrote:
> Are the language elements not an illogical mix?
> font-name and font-name-asian might be illogical in one document?
> 
> style:shadow and text:shadow?
> 
> fo:margin and fo:margin-top etc?
> 
> padding and padding-right (basically the shortform attributes and the
> longer forms)
> 
> Doubtful if it will impact defaults, but writing mode tblr then
> setting some asiatic
> script that required tbrl etc?

Those are interesting points...

The script specific settings are not mutually exclusive. They allow to 
select a font based on the script type, so the same paragrapg can use a 
different font for Chinese (asian script type) text than it uses for 
Arabic (complex script type). The overall feasibility of default fonts 
however is something that I am not sure about.

There is no text:shadow, so I assume you mean fo:text-shadow, which is 
in fact something different than style:shadow. The former controls a 
shadow effect for characters, while the latter controls the shadow of an 
object (which may contain characters with another shadow effect), e.g. a 
page or a frame. The default for both of these should be to have no shadow.

The short forms probably should not get a default. Their default would 
rather be reflected by the defaults of their individual components.

I am not sure about the writing directions, but I think our defaults are 
OK as long as they are consistent. In general, whenever there is 
potential for conflicting attributes we must make a choice and write 
that down in the spec. From an interoperability point of view, an 
application is free to disagree with out choice as long as it says so in 
the files it produces.

Bests,
Lars

On Friday 02 November 2007, Lars Oppermann wrote:
> > What about irregular combinations of attributes? I.e. two attributes
> > that cannot
> > be used together? How might this be addressed?
> > What about other interdependencies?
> 
> I don't think that this is a problem, given the goals stated above. Furthermore, 
> I am not aware of such a combination - which doesn't mean that they don't exist. 
> I'd be thankful for an example here.

The best example IMHO is fo:line-height, fo:line-height-at-least and fo:line-spacing.
Those three attributes are mutually exclusive, since they map to three different ways
of calculating the line spacing.

But the answer is simple: in all word processors I know, fo:line-height is the default, with a value of "normal" (100%).
The other attributes are therefore simply not set by default.

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).

On Friday 02 November 2007, Lars Oppermann wrote:
> As per my action item to kick of the work on specifying style property defaults, 
>   have produced the attached document. It includes tables listing all the style 
> property attributes that appear in various property sets that are set down in 
> the ODF schema. Only for the paragraph-properties have I started to fill in some 
> defaults.

Here are the default properties from KOffice-1.6 (from knowledge and from code reading) :

Character properties
----------------------

fo:background-color = transparent

fo:color   = special case: by default nothing is saved, which means "use the default text color
from the user settings - could be e.g. yellow on screen depending on the kde color scheme, 
and the default color is resolved to black when printing". This seemed like a nice feature at the
time, to obey the color scheme (e.g. people who like to read text in a light color over a dark background
can do this in kword); however it breaks the idea of WYSIWYG so I'm not sure koffice-2.0 will keep it.

fo:language = language set by the user in KDE
fo:country = country part of the language set by the user in KDE

fo:font-family = default font set by the user in KDE :)
fo:font-style = also part of the kde font settings
fo:font-weight = normal
fo:font-style = normal
fo:font-variant = normal
fo:text-transform = none
fo:text-shadow = none
fo:hyphenate = false

style:text-underline-type = none
style:text-underline-style = none (although the internal value is "solid", but that gets converted to none if type is none)
style:text-underline-mode = continuous        [this one is missing in OO's output?]
style:text-line-through-type = none
style:text-line-through-style = none
style:text-position = 0%

Paragraph properties
-------------------------
fo:text-align = start
fo:line-height = 100% (also known as "normal")
style:writing-mode = lr-tb
fo:margin-left = 0
fo:margin-right = 0
fo:text-indent = 0
fo:margin-top = 0
fo:margin-bottom = 0
style:tab-stops = (empty list)
style:join-border = true
fo:border = none
fo:break-before = auto
fo:break-after = auto
fo:keep-together = auto
fo:keep-with-next = auto
fo:background-color = see above fo:color explanation; defaults to "obey color scheme", resolved to white when printing.

Page layout properties
-------------------
fo:page-width and fo:page-height = the page format is A4 or Letter depending on the user settings in KDE
style:print-orientation = portrait
fo:margin-right/left/top/bottom = 20mm