Bug 148472 - Render of Bold Italic Strikeout font differs with MS Word for specific docx file (with null values)
Summary: Render of Bold Italic Strikeout font differs with MS Word for specific docx f...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
Depends on:
Blocks: DOCX-Character
  Show dependency treegraph
 
Reported: 2022-04-08 18:35 UTC by Pavel Lobashov
Modified: 2025-01-06 03:13 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
NullBoldItalicStrike (4.49 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2022-04-08 18:35 UTC, Pavel Lobashov
Details
screenshot (49.24 KB, image/png)
2022-04-08 18:36 UTC, Pavel Lobashov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Lobashov 2022-04-08 18:35:27 UTC
Created attachment 179415 [details]
NullBoldItalicStrike

Steps to reproduce:

1. Open attached file in LibreOffice 7.3.2.2
2. Open attached file in MS Word 2021
3. Compare

Result:

In MS Word Some text has Bold Italic Strikeout properties to set
In LibreOffice, it's just default values without Bold Italic Strikeout

See screenshot with that comparison

My Eniroment:
Kubuntu 20.04
LibreOffice flatpak 7.3.2.2

MS Windows 10 
MS Office 2021
Comment 1 Pavel Lobashov 2022-04-08 18:36:01 UTC
Created attachment 179416 [details]
screenshot
Comment 2 Buovjaga 2023-01-06 13:24:06 UTC
Confirmed.

Unzipping the document and looking at word/document.xml, I see

<w:b w:val = "null"/>
<w:i w:val = "null"/>
<w:strike w:val = "null"/>

Same result in 6.3, 5.2, 3.5

Arch Linux 64-bit, X11
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d6c54b3d4ee757958f9040a84dfbde0ab25f59bf
CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded Jumbo
Built on 6 January 2023
Comment 3 QA Administrators 2025-01-06 03:13:39 UTC
Dear Pavel Lobashov,

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