Bug 129920 - FILEOPEN DOCX Raised subscript characters top part not visible
Summary: FILEOPEN DOCX Raised subscript characters top part not visible
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
: 146901 (view as bug list)
Depends on:
Blocks: DOCX-Character
  Show dependency treegraph
 
Reported: 2020-01-10 11:02 UTC by NISZ LibreOffice Team
Modified: 2024-05-04 09:43 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file from Word (24.86 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2020-01-10 11:03 UTC, NISZ LibreOffice Team
Details
Screenshot of the original document side by side in Word and Writer (94.34 KB, image/png)
2020-01-10 11:03 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NISZ LibreOffice Team 2020-01-10 11:02:06 UTC
Description:
This is a followup to bug #122037
In the bugdoc there is a paragraph with characters formatted as subscipt and having elevated their position by 5 pt.
Writer opens this as superscript and raised by 50%. Most importantly the character size is not reduced as it should be with subscript/supersript. This along with the fixed line spacing causes the characters “1)” to be not readable.
Turning off the elevated position setting in Word makes the characters to be imported as subscipt and with smaller size, making them look like in Word.
Turning off the subscipt setting in Word makes the characters to not have smaller size and their top not being visible.

Steps to Reproduce:
1. Open attached document in Word and Writer and compare their settings.


Actual Results:
The characters “1)” are not readable, their top part missing.

Expected Results:
Characters should be readable.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 NISZ LibreOffice Team 2020-01-10 11:03:04 UTC
Created attachment 157055 [details]
Example file from Word
Comment 2 NISZ LibreOffice Team 2020-01-10 11:03:33 UTC
Created attachment 157056 [details]
Screenshot of the original document side by side in Word and Writer
Comment 3 Dieter 2020-01-10 11:19:29 UTC
I confirm it with

Version: 6.5.0.0.alpha0+ (x64)
Build ID: e26d89371f0e4f41476c9a99be01d98dedb76776
CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; 
Locale: de-DE (de_DE); UI-Language: en-GB
Calc: threaded
Comment 4 Dieter 2021-11-23 15:36:19 UTC
Still present in

Version: 7.2.3.2 (x64) / LibreOffice Community
Build ID: d166454616c1632304285822f9c83ce2e660fd92
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL
Comment 5 m_a_riosv 2022-01-21 21:37:57 UTC
*** Bug 146901 has been marked as a duplicate of this bug. ***
Comment 6 QA Administrators 2024-01-22 03:11:56 UTC Comment hidden (obsolete)
Comment 7 Dieter 2024-05-04 09:43:34 UTC
Still present in

Version: 24.2.3.2 (X86_64) / LibreOffice Community
Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL threaded