Bug 201442 - Formula editor not permitting certain equations
Summary: Formula editor not permitting certain equations
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-05 13:25 UTC by Paul F. Johnson
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-08-05 19:15:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Paul F. Johnson 2006-08-05 13:25:17 UTC
Description of problem:
The formula editor seems to have a problem with from and to SIGMA (though it is
represented in the tools box)

Version-Release number of selected component (if applicable):
2.0.3-7.7

How reproducible:
Always

Steps to Reproduce:
1. Start openoffice and create a new formula
2. Type int from 0 to infinity newline
3. Type %SIGMA from 0 to infinity.
  
Actual results:
The int 0 from 0 to infinity gives the correct result
The %SIGMA from 0 to infinity doesn't. There is an icon in the toolbox to
suggest that this is available (and it is a common form in higher maths)

Expected results:
Both int and %SIGMAs should be the same

Additional info:
This has worked in the past. It definitely did under OOo 1.3

Comment 1 Caolan McNamara 2006-08-05 19:15:33 UTC
nah...

stuff like "%SIGMA" and %alpha are just the names of the symbols themselves,
there are inbuild key words like "int" and "sum" which math knows the formula
syntax of, but with a bare symbol you have to more manually layout the equation.
A little demo below...

int from 0 to infinity foo newline
sum from 0 to infinity foo newline
size*1.5 %SIGMA csub 0 csup infinity foo newline

FWIW: The idea from the "selection" tool is that when you click on one of the
examples a template is put into the text with <?> where you put your term


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