Issue 56083 - Exponent font bug
Summary: Exponent font bug
Status: CONFIRMED
Alias: None
Product: Math
Classification: Application
Component: code (show other issues)
Version: OOO 2.0 Beta2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2005-10-16 09:16 UTC by faverdbr
Modified: 2013-08-07 14:54 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Screenshot of the bug (2.44 KB, image/png)
2005-10-16 09:16 UTC, faverdbr 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description faverdbr 2005-10-16 09:16:10 UTC 
When typing something like "A^2x+B^x", the first and second "x" don't use the
same font. In fact, when "x" is alone, the correct "math" font is used, but when
associated with another caracter or operation, regular "non-math" font is used
instead. The use of brackets don't change anything.
Same problem when trying something like : "A_2x+B_x".
The result is a printed document with formulas having non uniform fonts, and
this is anoying. As I often have to use formula editor, this bug prevents me
from switching from 1.1.5 to 2.0...
Comment 1 faverdbr 2005-10-16 09:16:55 UTC 
Created attachment 30503 [details]
Screenshot of the bug
Comment 2 Regina Henschel 2005-10-16 13:17:28 UTC 
Yes the behavior has changed from 1.1.5 to 2.0. Now you must use a blank between
the number and the variable. But I don't know if this is intended or not. I
don't like it, because you write more often combinations of number and variable
then combinations of number and unit, for which it is useful.
Comment 3 faverdbr 2005-10-17 09:02:59 UTC 
Ok, adding a blank between number and "x" seems to work but, to my opinion, it's
not a good idea as it add a space between number and caracter, that is not usual
when you write equations. I think it would be nice, if you can, to reverse to
the 1.1.5 behaviour, which used to work fine.

Regards,
Bruno Faverdin
Comment 4 thomas.lange 2007-08-02 10:47:27 UTC 
Setting target to OOo later as discussed with QA.

For a more detailed reasoning look in issue 54976 because the root problem is
the same in both issues.