Bug 137186 - FILESAVE RTF Table breaks to second page too early
Summary: FILESAVE RTF Table breaks to second page too early
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.3.1 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:rtf
Depends on:
Blocks: RTF-Tables
  Show dependency treegraph
 
Reported: 2020-10-01 13:39 UTC by Buovjaga
Modified: 2024-02-01 03:15 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
The original DOCX file and its Writer-saved RTF version in current Writer (245.98 KB, image/png)
2022-01-31 00:13 UTC, Gabor Kelemen (allotropia)
Details
The original DOCX file and its Writer-saved RTF version in Word 2013 (165.63 KB, image/png)
2022-01-31 00:22 UTC, Gabor Kelemen (allotropia)
Details
The example file saved to RTF with current Writer (305.97 KB, application/msword)
2022-01-31 00:23 UTC, Gabor Kelemen (allotropia)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Buovjaga 2020-10-01 13:39:19 UTC
1. Open attachment 104763 [details] from bug 82734
2. Save as RTF and reload

The table "Servers | Instance Size" now breaks to the second page immediately after its heading.

Not sure how to investigate previous state, because everything is dependent on element positions changing.

Arch Linux 64-bit
Version: 7.1.0.0.alpha0+
Build ID: 09c24681a3414092fde50ec0f617c9f7c79e8a61
CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: kf5
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 30 September 2020
Comment 1 Dieter 2020-11-07 05:33:23 UTC
I confirm it with

Version: 7.0.3.1 (x64)
Build ID: d7547858d014d4cf69878db179d326fc3483e082
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: threaded
Comment 2 Gabor Kelemen (allotropia) 2022-01-31 00:13:00 UTC
Created attachment 177921 [details]
The original DOCX file and its Writer-saved RTF version in current Writer

This looks correct in:

Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: eb69767d7c1bb8e6e780fd9503f08c9d7f5ecb45
CPU threads: 13; OS: Windows 10.0 Build 19042; UI render: default; VCL: win
Locale: hu-HU (hu_HU); UI: en-US
Calc: threaded

since:
https://git.libreoffice.org/core/+/0a32371cc2f93fad7954e0fe9c48976aae6c5b9f

author	Justin Luth <justin.luth@collabora.com>	Wed Mar 10 14:41:57 2021 +0200
committer	Justin Luth <justin_luth@sil.org>	Thu Mar 18 16:40:02 2021 +0100

tdf#108518 partial revert tdf#64222 sw: better DOCX im/export
Comment 3 Gabor Kelemen (allotropia) 2022-01-31 00:22:43 UTC
Created attachment 177922 [details]
The original DOCX file and its Writer-saved RTF version in Word 2013

The Writer-saved RTF looks quite bad in Word, several settings are exported on the list items that were not present in the DOCX.
Let's refocus this report.
Comment 4 Gabor Kelemen (allotropia) 2022-01-31 00:23:16 UTC
Created attachment 177923 [details]
The example file saved to RTF with current Writer
Comment 5 QA Administrators 2024-02-01 03:15:34 UTC
Dear Buovjaga,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug