Bug 123387 - FILEOPEN: RTF table font size wrong in first column
Summary: FILEOPEN: RTF table font size wrong in first column
Status: RESOLVED DUPLICATE of bug 123393
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, filter:rtf, regression
Depends on:
Blocks:
 
Reported: 2019-02-12 07:54 UTC by Ari Latvala
Modified: 2019-02-12 16:10 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
RTF file showing problem on table 5 (1.35 MB, application/rtf)
2019-02-12 07:54 UTC, Ari Latvala
Details
comparison MSO 2010 and LibreOffice 6.3 Master (163.71 KB, image/png)
2019-02-12 12:23 UTC, Xisco Faulí
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ari Latvala 2019-02-12 07:54:33 UTC
Created attachment 149189 [details]
RTF file showing problem on table 5

Text should be Arial 7 points on the table 5, now first column has point size 10. 

Maybe somehow related to these?
* Bug 98321 - FILEOPEN: RTF checkbox font type wrong and size too big
* Bug 108093 - FILEOPEN: RTF table horizontal position wrong because frame not imported
Comment 1 Xisco Faulí 2019-02-12 12:23:40 UTC
Created attachment 149222 [details]
comparison MSO 2010 and LibreOffice 6.3 Master
Comment 2 Xisco Faulí 2019-02-12 12:24:56 UTC
Reproduced in

Version: 6.3.0.0.alpha0+
Build ID: c7ad7849d54fd3dad67e7779102f65b8b2f04881
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded

but not in

Version: 5.4.0.0.alpha1+
Build ID: 9feb7f7039a3b59974cbf266922177e961a52dd1
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group
Comment 3 Xisco Faulí 2019-02-12 16:10:19 UTC
Regression introduced by https://cgit.freedesktop.org/libreoffice/core/commit/?id=aaa6a5202a447fb4e86d5f016d8e79fbc34a3ed7 which is the same as in bug 123393

*** This bug has been marked as a duplicate of bug 123393 ***