Bug 100526 - [FILEOPEN] New line/paragraph missing after field in specific DOCX
Summary: [FILEOPEN] New line/paragraph missing after field in specific DOCX
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
Version:
(earliest affected)
4.3.0.4 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, filter:docx, regression
Depends on:
Blocks: DOCX-Fields
  Show dependency treegraph
 
Reported: 2016-06-21 17:01 UTC by Cor Nouws
Modified: 2024-02-11 03:13 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Image showing current situation of fields without new paragraph between in LibreOffice (10.87 KB, image/png)
2016-06-21 17:01 UTC, Cor Nouws
Details
Minimized example file (28.09 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2019-10-10 07:07 UTC, Gabor Kelemen (allotropia)
Details
Minimized example file in Word and Writer side by side (53.38 KB, image/png)
2019-10-10 07:08 UTC, Gabor Kelemen (allotropia)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Cor Nouws 2016-06-21 17:01:22 UTC
Created attachment 125813 [details]
Image showing current situation of fields without new paragraph between in LibreOffice

Open File https://bugs.documentfoundation.org/attachment.cgi?id=125792 (bug 100513)
In the right margin of page 2 and onward there is a frame with a table
The lower line there is
   "Ons kenmerk650806"
That should be
   "Ons kenmerk
    650806"

Also see pdf from Word in  https://bugs.documentfoundation.org/attachment.cgi?id=125793
Comment 1 Cor Nouws 2016-06-21 17:15:52 UTC
Mind that in the current version, the text box with fields already is better then in older versions.

Before, bold text missed and one other paragraph mark too.
Comment 2 Buovjaga 2016-06-26 11:40:23 UTC
Confirmed the situation on pg 2.

Arch Linux 64-bit, KDE Plasma 5
Version: 5.3.0.0.alpha0+
Build ID: ff25ea3d5ccf3a990767cbb1ef99037d3f84b072
CPU Threads: 8; OS Version: Linux 4.6; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8)
Built on June 26th 2016
Comment 3 Xisco Faulí 2016-10-08 15:59:33 UTC
This is a regression as the line break can't be reproduced in Version: 4.2.0.0.alpha1+
Build ID: fc8f44e82de4ebdd50ac5fbb9207cd1a59a927e3
However, the overall layout looks very bad back in that version. I'm not sure this can be bibisected...
Comment 4 QA Administrators 2017-12-10 16:40:41 UTC Comment hidden (obsolete)
Comment 5 Cor Nouws 2017-12-28 22:51:05 UTC
still a problem in 
Version: 6.1.0.0.alpha0+
Build ID: a9b202a6b7000e7af34f2a639ca207122a3968bf
CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-12-26_23:09:36
Locale: nl-NL (nl_NL.UTF-8); Calc: group threaded
Comment 6 QA Administrators 2018-12-29 03:49:40 UTC Comment hidden (obsolete)
Comment 7 Cor Nouws 2019-01-20 22:10:20 UTC
still a problem in Version: 6.3.0.0.alpha0+
Build ID: b8e450a54936560cdac00ab4c70ef80c20cfaf99
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-01-18_06:04:42
Locale: nl-NL (nl_NL.UTF-8); UI-Language: en-US
Calc: threaded
Comment 8 Gabor Kelemen (allotropia) 2019-10-10 07:07:06 UTC
Created attachment 154884 [details]
Minimized example file
Comment 9 Gabor Kelemen (allotropia) 2019-10-10 07:08:39 UTC
Created attachment 154886 [details]
Minimized example file in Word and Writer side by side

Still present in

Version: 6.4.0.0.alpha0+ (x86)
Build ID: 489eef894e7034873ad262f9dfca554022db1b09
CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-10-01_23:43:38
Locale: hu-HU (hu_HU); UI-Language: en-US
Calc: CL
Comment 10 NISZ LibreOffice Team 2019-10-10 07:22:27 UTC
Bibisected with the minimized example file using bibisect-win32-4.3 to:

https://cgit.freedesktop.org/libreoffice/core/commit/?id=3dc548476c7e88f7a67cc38daf622631a34e34dd

author	Michael Stahl <mstahl@redhat.com>	2014-03-01 22:05:51 +0100
committer	Michael Stahl <mstahl@redhat.com>	2014-03-03 13:53:22 +0100


writerfilter: salvage a field parameter parsing train wreck

Before the fields were not imported as fields only plain text: but with a paragraph break between them.

Adding CC to: Michael Stahl
Comment 11 Xisco Faulí 2021-03-31 14:04:32 UTC
Dear László Németh,
This bug has been in ASSIGNED status for more than 3 months without any
activity. Resetting it to NEW.
Please assign it back to yourself if you're still working on this.
Comment 12 QA Administrators 2024-02-11 03:13:31 UTC
Dear Cor Nouws,

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