Bug 125602 - FILEOPEN DOC: Incorrect paragraph font style due to CR formatting
Summary: FILEOPEN DOC: Incorrect paragraph font style due to CR formatting
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.4.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: DOC-Paragraph Regressions-705a8c22
  Show dependency treegraph
 
Reported: 2019-05-31 06:31 UTC by Aleksey Kozyayikin
Modified: 2025-11-01 03:12 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Example of problem (27.00 KB, application/msword)
2019-05-31 06:32 UTC, Aleksey Kozyayikin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aleksey Kozyayikin 2019-05-31 06:31:38 UTC
Description:
I created document in doc format using word application. 
I Added Paragraph, changed font style for last carriage return symbol, and added table. Then I  saved document.  Document is in attachment.
If you open this document in LibreOffice you see that font style of carriage return symbol is applied for paragraph.

Steps to Reproduce:
1.Create document in doc format using word application
2.Add Paragraph, change font style for last carriage return symbol, and add table
3.Save document
4. Open document in LibreOffice

Actual Results:
Font style for carriage return is applied for previous paragraph

Expected Results:
Font style for carriage return is not applied for previous paragraph


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Aleksey Kozyayikin 2019-05-31 06:32:09 UTC
Created attachment 151794 [details]
Example of problem
Comment 2 Durgapriyanka 2019-05-31 20:21:53 UTC
I can confirm the bug present in 

Version: 6.3.0.0.alpha0+
Build ID: b6b28931435e44aca92b8c0e1659f701e3ed1a87
CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-01-30_06:57:04
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded

I cannot reproduce the bug in 

LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
Comment 3 Dieter 2019-06-01 10:13:18 UTC
Durgaprinyka, if you are able to reproduce a bug, you are also allowed to set status to NEW

=> NEW because of comment 2
Comment 4 Xisco Faulí 2019-06-11 11:20:48 UTC
Reproduced in

Version: 5.2.0.0.alpha1+
Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e
CPU Threads: 4; OS Version: Linux 4.15; UI Render: default; 
Locale: ca-ES (ca_ES.UTF-8)

but not in


Version: 4.3.0.0.alpha1+
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
Comment 5 Xisco Faulí 2019-06-11 11:21:19 UTC Comment hidden (obsolete)
Comment 6 Xisco Faulí 2019-06-11 15:18:52 UTC
Regression introduced by:

author	Caolán McNamara <caolanm@redhat.com>	2014-09-23 19:35:50 (GMT)
committer	Caolán McNamara <caolanm@redhat.com>	2014-09-24 09:04:48 (GMT)
commit 705a8c226aee3e68db492083b7cf8b704335328b (patch)
tree c701b3a13f48f6d5a4c226bcf4f67e1e91a41049
parent 6332c643016ce4c4d254c8429a5eceae6664bf5c (diff)

Adding Cc: to Caolán McNamara
Comment 7 Timur 2021-04-06 13:57:49 UTC Comment hidden (obsolete)
Comment 8 Justin L 2021-04-07 18:35:55 UTC
(In reply to Timur from comment #7)
> This report needs source ODT before it's saved as DOC.

This report doesn't really need anything because there are at least 10 other reports also targetting Regressions-705a8c22. There isn't really anything that can be done (unless you are more genius than Caolan).
Comment 9 QA Administrators 2025-11-01 03:12:30 UTC
Dear Aleksey Kozyayikin,

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