← Prev in month ← Prev in thread
Next in thread → Next in month →

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

From
OASIS Issues Tracker <>
Date
2013-10-14T14:47:28+00:00
ID
334457664.23001381762119895.JavaMail.tomcat@customer-jira
Thread
[OASIS Issue Tracker] Created: (OFFICE-3847) Simplify Line Height handling
Simplify Line Height handling
-----------------------------

                 Key: OFFICE-3847
                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3847
             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
          Issue Type: Improvement
    Affects Versions: ODF 1.2
            Reporter: Svante Schubert 


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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
← Prev in month ← Prev in thread
Next in thread → Next in month →