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: [OASIS Issue Tracker] (OFFICE-3847) Simplify Line Height handling


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

Svante Schubert commented on OFFICE-3847:
-----------------------------------------

Regina pointed out that based on ODF 1.3 we already worked on fo:line-height in [issue 3997|https://issues.oasis-open.org/browse/OFFICE-3997].ÂThe title of 3997: "Be more precise about differences to XSL_FO for attribute fo:line-height".

She was so kind as to add a proposal.

On the left side, the former ODF 1.3 and resolution of issue 3997 version is being shown.

On the right side,Âon three pages my previous suggestions (in yellow) are being overworked by her suggestions (in blue).

Please find all attached in an ODT file called draft20210201-RH.odt.Â

We (Regina, Michael and I) had a short call about her proposal, made slight rewordings and realized it would be nice to have some pictures (telling more than 1000 words) and a vocabulary/dictionary, which explains wordings such as 'line area', 'overlapping' and other terms which should have once a precise definition to have the same understanding.

> 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
>
>         Attachments: FontSizeCompare.odt, FontSizeCompare.pdf, draft20210201-RH.odt
>
>
> 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
(v8.3.3#803004)


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