Bug 129920

Summary:	FILEOPEN DOCX Raised subscript characters top part not visible
Product:	LibreOffice	Reporter:	NISZ LibreOffice Team <libreoffice>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	NEW ---
Severity:	normal	CC:	dgp-mail, kelemeng, nemeth, wolfram
Priority:	medium	Keywords:	filter:docx
Version:	7.0.0.0.alpha0+
Hardware:	All
OS:	All
See Also:	https://bugs.documentfoundation.org/show_bug.cgi?id=122037
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	108769
Attachments:	Example file from Word Screenshot of the original document side by side in Word and Writer

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)

Dear NISZ 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

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