Bug 68416 - EDITING: Superscripts and Subscripts Unicode Chart U2070 are displayed with most fonts
Summary: EDITING: Superscripts and Subscripts Unicode Chart U2070 are displayed with m...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.1.2 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-22 08:40 UTC by jakj
Modified: 2016-07-15 07:42 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Sample ODT-Document with different fonts embedded (18.68 KB, application/vnd.oasis.opendocument.text)
2013-08-22 08:40 UTC, jakj
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jakj 2013-08-22 08:40:44 UTC
Created attachment 84436 [details]
Sample ODT-Document with different fonts embedded

Problem description: 
With many fonts the superscript an subscript-Unicode-Symbols are wrongly displayed as normal Numbers.

Steps to reproduce:
1. In a Writer Document insert: H\u2086OO and try different fonts (ttf-mscoreronts-installer and the Fonts subdirectory of an Windows XP installation are present), each in one line

Current behavior:
The following Fonts result are displayed as H2O instead of H₂O:
H₂O 	Arial
H₂O 	Arial Tahoma
H₂O 	Bitstream Vera Sans
H₂O 	Courier New
H₂O 	Droid Sans
H₂O 	Garamond
H₂O 	Liberation Mono
H₂O 	Liberation Sans
H₂O 	Liberation Serif
H₂O 	Nimbus Sans L
H₂O 	Segoe
H₂O 	StiX
H₂O 	Times New Roman

Expected behavior:
The fonts mentioned above should also result in H₂O as correctly in:
H₂O 	Arial Unicode MS
H₂O 	Calibri
H₂O 	DejaVu Sans
H₂O 	Free Sans
H₂O 	Free Serif
H₂O 	Gentium
H₂O 	Georgia
H₂O 	Linux Libertine
H₂O 	Lucinda Sans Unicode
H₂O 	Ubuntu
H₂O 	Unifont

The Error is kept after PDf/A-Export

              
Operating System: Ubuntu
Version: 4.1.0.1 rc
Comment 1 Jean-Baptiste Faure 2013-09-21 21:21:59 UTC
Not reproducible for me on Ubuntu 13.04 with LO 4.1.3.0.0+. When opening your file I see the same thing on each line.

Please, could you try again with LO 4.1.2 RC2 which is available from the following webpage: http://www.libreoffice.org/download/pre-releases/
I you reproduce the problem again, please attach a screen-copy or a pdf export.

Best regards. JBF
Comment 2 QA Administrators 2014-05-17 00:34:05 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 3 QA Administrators 2014-06-01 20:30:04 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO