Bug 134772 - FILEOPEN: DOCX : Add drop cap,format display is not correct
Summary: FILEOPEN: DOCX : Add drop cap,format display is not correct
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.2 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: DOCX-Paragraph Paragraph-Drop-Caps
  Show dependency treegraph
 
Reported: 2020-07-13 08:25 UTC by NSO LibreOffice Team
Modified: 2024-09-20 03:17 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Example file (12.36 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2020-07-13 08:25 UTC, NSO LibreOffice Team
Details
Comparison MSO 2010 and LibreOffice 7.1 master (61.90 KB, image/png)
2020-07-13 10:40 UTC, Xisco Faulí
Details
Example file (160.26 KB, image/png)
2020-07-14 01:49 UTC, NSO LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NSO LibreOffice Team 2020-07-13 08:25:08 UTC
Created attachment 162956 [details]
Example file

Description:
Open MSO and create a large character at the beginning of a paragraph ,save it as docx, and then close the document, Open with Lo, and the sinking character format is not displayed correctly 

Steps to Reproduce:
1.Create a new word document, and create a sinking character at the beginning of a paragraph
2.save it as docx, and then close the document
3.Open with Lo, the sinking character format is not displayed correctly 


Actual Results:
Open with Lo, the sinking character format is not displayed correctly 

Expected Results:
Open with Lo, should be compatible with the sinking character format 

Reproducible: 
Always

Additional Info:
Version Infomation
Version: 7.1.0.0.alpha0+ (x64)
Build ID: 4c14c88cc681abab787a461a1bea502a777f37e6
CPU threads: 12; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: zh-CN (zh_CN); UI: en-US
Calc: threaded
Comment 1 Xisco Faulí 2020-07-13 10:40:40 UTC
Created attachment 162960 [details]
Comparison MSO 2010 and LibreOffice 7.1 master
Comment 2 Xisco Faulí 2020-07-13 10:41:33 UTC
What do you mean by 'it's not displayed correctly' ? Please be more precise when reporting issues. Also add a comparison screenshot if possible
Comment 3 NSO LibreOffice Team 2020-07-14 01:49:12 UTC
Created attachment 162993 [details]
Example file

Hi,  Xisco Faulí

Please check this attachment
Comment 4 Xisco Faulí 2020-07-14 11:21:54 UTC
So the problem is that the drop cap uses 3 lines top drop and while Word puts 3 lines to the rights, Writer only puts 1


Reproduced in

Version: 7.1.0.0.alpha0+
Build ID: fa844c15233f108a0e9b0b2e8c9757c1aa088a4b
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 5 Xisco Faulí 2020-07-14 11:24:25 UTC
Also reproduced in

Version: 6.1.0.0.alpha1+
Build ID: 3a801799536e6870f2fb111b1cc00b9575a35a39
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: group

In previous versions, the document crashes at import time
Comment 6 QA Administrators 2022-07-15 03:44:50 UTC Comment hidden (obsolete)
Comment 7 Gabor Kelemen (allotropia) 2022-09-20 07:38:13 UTC
Still happens in 

Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 349e3af0c5dd5ed495ed61aab526f63c16f0e215
CPU threads: 14; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (hu_HU); UI: en-US
Calc: threaded

The original file has the "Lines to drop" set to 3 and this is imported correctly - but interpreted differently.
In Word the drop cap can be displayed next to lines which are made from multiple paragraphs, as in this case.
In Writer the drop cap is a paragraph level property and can only be displayed if the paragraph is multiple lines long.
If the paragraph is just one line there is no drop cap displayed with Latin script, but with Asian script it is displayed as on attachment 162993 [details] - 1 line text with 2 line high empty space.
Comment 8 QA Administrators 2024-09-20 03:17:21 UTC
Dear NSO LibreOffice Team,

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