Created attachment 152690 [details]
Steps to reproduce:
1. Open attached document
2. Place cursor on first line
-> Cursor and Line height should have the same height as the text, instead, it's the double.
Build ID: 7a0164f0d82d91e2ac481d74cdacfe9a7ad6080f
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
[Bug found by office-interoperability-tools]
Regression introduced by:
author Jozsef Szakacs <email@example.com> 2019-03-13 12:32:20 +0100
committer László Németh <firstname.lastname@example.org> 2019-05-29 14:31:03 +0200
commit bdfb3edb981ff04f1f3f6dc1ef335e37a0980245 (patch)
parent bdc74dc279946abfdcca409edc96e985699eb368 (diff)
tdf#120412 DOCX filter: fix missing superscript
Bisected with: bibisect-linux64-6.3
Adding Cc: to Jozsef Szakacs
@Xisco: whole text is formatted as subscript in the document. It's possible, that this is not a regression?
Created attachment 152693 [details]
Screenshot of the document in LO 6.0 and 6.4master
It was "normal" text but now it's all subscript for me on a current-ish local master build.
(In reply to László Németh from comment #2)
> @Xisco: whole text is formatted as subscript in the document. It's possible,
> that this is not a regression?
I would say this is not a regression, but it just exposes an existing difference. Microsoft seems to compress the unused "normal" space since there are not any non-lowered characters. Seems like a low priority layout bug to me.
After updating to 6.4 all my docx documents are formated in subscript. Even page numbers etc. Downgrading to 6.3 solves the issue, the same documents are formated properly again.
If there is another issue to track this, let me know please, I tried to search but couldn't find anything sensible. Here the issue was at least mentioned.
OS: Ubuntu 18.04
The same like in description in
Build ID: 4a899a5f8a72ea29a6919316afe3627de9f33e95
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
*** Bug 149201 has been marked as a duplicate of this bug. ***