[OASIS Issue Tracker] (OFFICE-3847) Simplify Line Height handling

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OFFICE-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=72475#comment-72475 ] 

Regina Henschel commented on OFFICE-3847:
-----------------------------------------

Your proposal for the schema, forbids multiple attributes on the same element. I support that. But OFFICE-3997 has only a precedence rule for multiple attributes on the same element. So the resolution in OFFICE-3997 needs to be adapted.

Thus in your proposal

"The attributes fo:line-height, style:line-height-at-least, style:line-spacing specify the same formatting property, i.e., any one of these attributes on a style overrides any of these attributes on its parent style."

the rule for same element has to be added:

"The attributes fo:line-height, style:line-height-at-least, style:line-spacing specify the same formatting property, i.e., any one of these attributes on a style overrides any of these attributes on its parent style, and at most one of them shall occur in an <style:paragraph-properties> element."

And the sentence (see OFFICE-3997)

" In case a {{style:line-height-at-least}} or a {{style:line-spacing}} attribute occurs in addition in the same element, the attribute {{fo:line-height}} has precedence."

has to be deleted.

=================

Your proposal contains

"replace:
 * normal: disables the effects of style:line-height-at-least and style:line-spacing.

with:
 * normal: equivalent to 100%"

Deleting the sentence (see OFFICE-3997) "The value {{normal}} disables the effects of {{style:line-height-at-least}} and {{style:line-spacing}}." is OK, but remaining part should be kept, so that it reads

"{{normal}}: activates the default line height calculation. The calculation method is not specified, but should be similar to a percentage in the range of 100% to 120%. It may consider font metrics."

I think a more flexible value is needed, because some fonts include a suitable leading already and other fonts do not. Some application are able to use all metrics information of the font and others not. Therefore a fixed 100% is not so good. If 100% is desired by a producer, it can force 100% by using the percent variant of the attribute.

=============

Besides that, I support the idea of making the properties exclusive.

Â

Â

> Simplify Line Height handling
> -----------------------------
>
>                 Key: OFFICE-3847
>                 URL: https://issues.oasis-open.org/browse/OFFICE-3847
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Improvement
>          Components: Formatting Properties, Paragraph, Part 1 (Schema)
>    Affects Versions: ODF 1.2
>            Reporter: Svante Schubert
>            Priority: Major
>             Fix For: ODF 1.4
>
>
> Currently we have four independt ODF attributes defining our line-height in ODF. 
> http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#property-fo_line-height
> http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#property-style_line-height-at-least
> http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#property-style_line-spacing
> http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#property-style_font-independent-line-spacing 
> I would like to have feed-back from other implementors on the following:
> The first @fo:line-height is dereived from the W3C formatting object specification, 
> http://www.w3.org/TR/xsl/#line-height here we should make clear the "normal" for office documents is equal 100%, not as in browser between 110 and 130% 
> The second @style:line-height-at-least is an extension of the W3C attribute to have a better OOXML interoperability.
> The third @style:line-spacing is equal to 'leading' (not from leader, but from the metal 'lead', as during ancient print there was added a line of lead between the letters), it is specifiying the space between lines.
> The last one @style:font-independent-line-spacing is only used by implementations for presentations, to have a similar layout during the change of the font.
> AFAIK all ODF implementations are using these values exclusivly. 
> I suggest to either make them exclusively in the RelaxNG, or to specify a precedence (or collision) handling. What happens if two attributes exist at the same time?



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)