Bug 151062 - Formula editor in ooimpress is not working correctly
Formula editor in ooimpress is not working correctly
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
rawhide
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Caolan McNamara
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-03-14 10:05 EST by Paul F. Johnson
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-03-14 11:10:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenOffice.org 21118 None None None Never

  None (edit)
Description Paul F. Johnson 2005-03-14 10:05:10 EST
Description of problem:
If you try to insert a formula on a non-white background, the text is very
small, black and is not inserted into the correct position)

Version-Release number of selected component (if applicable):
1.9.83-1

How reproducible:
Very

Steps to Reproduce:
1. Start ooimpress and create a new presentation. Choose the blue background
with orange lines style
2. Select any of the bullet point options. Type some text
3. Insert a formula
  
Actual results:
The text is black (not the colour of the rest of the text), very small
(incorrect font size) and not in the position where the cursor was when the text
was inserted)

Expected results:
The formulae should marry up to the font and font colour in use

Additional info:
This also applies to 1.9.80
Comment 1 Caolan McNamara 2005-03-14 11:10:34 EST
Sadly impress never worked this way. The default formula font is hard-coded to
the default writer font size.
http://qa.openoffice.org/issues/show_bug.cgi?id=21118 is an upstream suggestion
to implement the size of the formula based on the current style.

Note You need to log in before you can comment on or make changes to this bug.