Bug 51002 - VIEWING: In inported .pps presentation symbol for reduced Plancks constant isn't displayed correctlly. I only get a rectangle instead of it.
Summary: VIEWING: In inported .pps presentation symbol for reduced Plancks constant is...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
3.5.4 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-12 03:14 UTC by martinplavala
Modified: 2014-06-01 20:30 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
screenshot of presentation, in the red circle is the rectangle, instead of which should be h-bar. (71.59 KB, image/png)
2012-06-12 03:14 UTC, martinplavala
Details

Note You need to log in before you can comment on or make changes to this bug.
Description martinplavala 2012-06-12 03:14:58 UTC
Created attachment 62925 [details]
screenshot of presentation, in the red circle is the rectangle, instead of which should be h-bar.

Problem description: 

Steps to reproduce:
1. Create in Microsoft office presentation including formula with reduced plancks constant (h - bar it is called)
2. Open the presentation in Libre office

Current behavior:
Instead of h-bar displayed, theres a rectangle

Expected behavior:
Display h-bar, lihe here: http://en.wikipedia.org/wiki/H_with_stroke

Platform (if different from the browser): 

Archlinux with Gnome         
Browser: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0
Comment 1 bfoman (inactive) 2012-06-21 04:42:56 UTC
Could you attach any example documents to allow others to check on different
system/build?
Comment 2 martinplavala 2012-06-26 10:51:09 UTC
(In reply to comment #1)
> Could you attach any example documents to allow others to check on different
> system/build?

http://www.sendspace.com/file/9qnkqx
here it is. It should be around page 13, didnt wanted to edit ot (rather). sorry it took so long.
Comment 3 A (Andy) 2013-02-16 12:33:52 UTC
Does this issue also still persist for you with the last LO releases?
Comment 4 ign_christian 2013-06-03 12:18:13 UTC
It seems file is not in the link anymore. Could you attach in this bug page?

Comment 3 ?

After you provide above needs, please change status to: UNCONFIRMED
Comment 5 QA Administrators 2014-05-17 00:34:27 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 6 QA Administrators 2014-06-01 20:30:24 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