The file is originally made in MS Office Word 20xx.
Steps to Reproduce:
1. Open example file. You see 2 empty line 48 pt height and 5 empty lines 12pt height.
2. Save it to DOC.
3. Reopen the file.
4. Now you see 3 empty line 48pt height and 4 empty lines 12pt height.
5. Repeat steps 2-4. Each time you reopen the file you will see 1+ line 48pt and 1- line 12pt until there's only 1 line 12pt.
Lines change font height.
Lines shouldn't change font height.
User Profile Reset: No
User-Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Maxthon/5.0 Chrome/55.0.2883.75 Safari/537.36
Created attachment 135545 [details]
The problem is not yet in 3.6, but in that version there is only 1 empty line with 48 pt height and 6 lines with 12 pt.
Still, could be valuable to bibisect.
Arch Linux 64-bit, KDE Plasma 5
Build ID: 507247697dc6c4a41fe17a29d522511f97040738
CPU threads: 8; OS: Linux 4.12; UI render: default; VCL: kde4;
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on August 29th 2017
Arch Linux 64-bit
Version 188.8.131.52 (Build ID: e183d5b)
(In reply to Buovjaga from comment #2)
> The problem is not yet in 3.6, but in that version there is only 1 empty
> line with 48 pt height and 6 lines with 12 pt.
Which is how Word shows the file, so that is the correct state.
Narrowing the range: good in 184.108.40.206, bad in 220.127.116.11.
Bibisected to the following commit using repo bibisect-44max. Adding Cc: to Caolán McNamara, please take a look sometimes.
I assume it's an import issue, since the 1:6 ratio of lines becomes 2:5 upon first open, then 3:4 on the second (after save), etc.
author Caolán McNamara <firstname.lastname@example.org> 2014-09-23 19:35:50 (GMT)
committer Caolán McNamara <email@example.com> 2014-09-24 09:04:48 (GMT)
"WW8PLCFMan::AdjustEnds deeply flawed concept wrt change tracking"
same commit as in bug 104027, besides both descriptions look similar... Closing as RESOLVED DUPLICATED
*** This bug has been marked as a duplicate of bug 104027 ***
Sorry, I meant bug 103967
*** This bug has been marked as a duplicate of bug 103967 ***