Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Subscript letter appears in normal size | ||||||
---|---|---|---|---|---|---|---|
Product: | Math | Reporter: | Unknown <non-migrated> | ||||
Component: | code | Assignee: | michael.ruess | ||||
Status: | CLOSED FIXED | QA Contact: | issues@sw <issues> | ||||
Severity: | Trivial | ||||||
Priority: | P3 | CC: | issues | ||||
Version: | 644 | ||||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | All | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
Unknown
2003-02-23 00:44:28 UTC
Created attachment 4851 [details]
At upper right elements' A_1n and A_2n, subscript letters appear normal-sized
Hi, I noticed this behavior can be due to a change in formula command interpretation. If this is the case, the issue will be categorized as another documentation (example in help) issue. Sorry for confusion. Seems to be a bad conflict with the new defined (previously undefined) behaviour what an identifier/number should look like. Probably only one can be available. Need to think about the effects of changing the naming conventions again for other aspects. Fixed in CWS tlapi2. Files changed: - parse.cxx 1.24.100.1 See ========== A_2n " " A_n2 " " A_2n2 " " A_n2n newline n34.5 n.m345 newline 23nh 34.6nh newline n34.5 34.6nh 46.8 ========== for example. Now numbers followed immediately by (or being mixed up with) characters as in "2n" will not be broken up in number and text but will remain intact and handled as like an identifier. I.e. especially "2n" will now (as per default settings for variables) be written cursive whereas "2" as number will not. But that seems more fitting when used in subscripts as now the slant of "A_n2" will have the same slant as "A_2n". Having "2n" still treated as number (and thus displayed straight up) seems not reasonable. . . TL->MRU: Please check in CWS tlapi2. checked fix with CWS tlapi2. Checked integration in 6809m32. |