Bug 166155 - FILEOPEN DOCX smart justify: Arial not justified identically to MS Word 2019
Summary: FILEOPEN DOCX smart justify: Arial not justified identically to MS Word 2019
Status: ASSIGNED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
24.2.0.0 alpha0+
Hardware: All All
: low minor
Assignee: László Németh
URL:
Whiteboard:
Keywords: bibisected, bisected
Depends on:
Blocks: DOCX-Smart-Justify
  Show dependency tree / graph
 
Reported: 2025-04-12 18:44 UTC by Justin L
Modified: 2025-04-14 14:50 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
tdf98567-1.docx_import-5.png: overlay where RED=Word2019 and black=24.8.6 (29.41 KB, image/png)
2025-04-12 18:44 UTC, Justin L 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Justin L 2025-04-12 18:44:16 UTC 
Created attachment 200326 [details]
tdf98567-1.docx_import-5.png: overlay where RED=Word2019 and black=24.8.6

I ran across this justified document that is using the common Arial font. However, our justification (as of 25.8 master) doesn't match the output I got from MS Word 2019.

There are several places in this document where we no longer match up. This page 5 has two examples. Also see page 8 and perhaps 3.

Steps to reproduce:
-open _Letter of Engagement for David GriffithsTEST 17Feb_4396733.DOCX (attachment 123453 [details] from bug 98567)

Notice on page 5 that the last paragraph does not end in a line containing only "ascertained."
Also notice that point 5.5's second line does not start with "not".

In my PDF comparison, both MS Word 2019 and LO bibisect were running on the same windows machine, so both used the identical Arial font version.

Marking as low priority, since this is mainly just submitted for information and not really as a concerned bug report.