Issue 43926 - Rationalise the layout of aportrophe characters
Summary: Rationalise the layout of aportrophe characters
Status: ACCEPTED
Alias: None
Product: Math
Classification: Application
Component: code (show other issues)
Version: OOo 1.1.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-02 17:27 UTC by imi84
Modified: 2013-08-07 14:54 UTC (History)
2 users (show)

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

Attachments
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 imi84 2005-03-02 17:27:28 UTC 
Check this picture:
http://people.inf.elte.hu/pentek_i/doksik/Linux/bugs/OOo/df.png
In mathematics we often use apostrophe characters to distuinguish objects, like
f and f' maybe apostrophe should be treated as if it would be an upper index, so
the lower index would be just below the apostrophe sign.
Comment 1 thomas.lange 2005-03-03 08:42:45 UTC 
.
Comment 2 thomas.lange 2005-04-05 08:35:56 UTC 
Target set to OOo 2.0.1.
As agreed with MRU it may also be changed to Target set to OOo 2.0.2.
Comment 3 andreas.martens 2005-05-25 09:11:35 UTC 
Considering the effort, the priority, the risk and our resource planning I've to
retarget this issue to OOo Later.
Comment 4 andreas.martens 2005-10-28 08:26:03 UTC 
Work-Around supposed by Özgür (thanks!), usage of "stack" like:

size 12 {f = f size 8 {stack {' # n }}}
Comment 5 allaw 2008-04-22 03:01:40 UTC 
the last suggestion is not a workaround is not an adequate solution. I thing it
is an escape from trying to improve math editor. Try to do the following and you
will see that the subscript letter is getting farther from the f letter.
size 12 {f = f size 8 {stack {''' # n }}}
So you have to add more commands to align the letters to the left. Even after
doing alignment the n letter is still far from the f letter.
Comment 6 lapsap7+ooo 2011-06-13 10:55:10 UTC 
I think this bug could be marked as duplicate of issue 52620, esp because content in that issue is richer that in this one.

However, status of this issue is STARTED while status of that one is NEW.  No idea if this really matters to mark duplicity.