Hi Regina,
That's right what Miklos wrote here, it was added mainly for MS
compatibility, so the expected behavior if it works similar to that. This
line height handling "bug" seems an independent issue from the character
border, which affects that use case too.
However I'm not sure that ODF specification is this detailed that you need
to specify these things too. At least I did not meet with a detailed
specification. As I remember in ODF spec the border related attrubutes are
general attributes already used for other objects like paragraphs, pages,
frames, etc. So it might be a good idea to check how paragraph border works
for example. In theory these two should be somewhat consistent and as I see
they are. Line height - border interaction seems similar for paragraphs and
when a paragraph is splitted between pages I see two separate boxes.
Best Regards,
Tamás
2018-07-30 9:24 GMT+02:00 Miklos Vajna <vmiklos@collabora.co.uk>:
Hi Regina,
On Mon, Jul 30, 2018 at 12:36:01AM +0200, Regina Henschel <
rb.henschel@t-online.de> wrote:
I have noticed the problems described below, when looking what would be
needed for interoperability with Word and what would be needed for EPUB
export.
I think it was on purpose that Tamas implemented this feature in terms
of what Word does.
Regards,
Miklos
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
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.