Date: prev next · Thread: first prev next last
2018 Archives by date, by thread · List index



hi Regina,


On 01.09.2018 19:01, Regina Henschel wrote:
Hi all,

the ODF specification has only for value "normal" a rule for the precedence between the attributes fo:line-height [3] and style:line-height-at-least [1] and style:line-spacing [2]. So I want to extend the description. Unfortunately LibreOffice behaves so, that the attribute order determines the final style (examine attached file). But in XML the order of attributes is irrelevant. So what behavior would you like to be specified?
i agree that having results depending on attribute order is in need of improvement, but i'm not sure what exactly the result should be in that case.

maybe the "fo:line-height" should win, because it's an "exact" value, while "style:line-height-at-least" specifies only a lower bound?

The attributes "style:line-height-at-least" and "style:line-spacing" are not supported for ODF by MS Office. I don't know, whether something similar exists in OOXML.

okay then preferring "fo:line-height" would interop better with MS Office too...



--
Michael Stahl
Senior Software-Entwickler LibreOffice
–––
CIB software GmbH
Geschäftsstelle Hamburg
Flachsland 10
22083 Hamburg
–––
T +49 (40) / 28 48 42 -296
F +49 (40) / 28 48 42 -100
Michael.Stahl@cib.de
www.cib.de
–––
Sitz: München
Registergericht München, HRB 123286
Geschäftsführer: Dipl.-Ing. Ulrich Brandner


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.