Apache OpenOffice (AOO) Bugzilla – Issue 25613
StarBats + StarMath not displayed correctly. Regression : was OK in OOo 1.1.1a
Last modified: 2004-11-04 11:46:20 UTC
StarBats and StarMath fonts are not displayed using the right font in OOo 1.1.1b while it works fine with OOo 1.1.1a. This applies to all OOo applications.
Workaround (tested for StarBats): 1) Use OpenSymbol instead, or 2) Use "Insert / Special Character" and choose either StarBats or OpenSymbol After reboot in case 2), StarBats is then identified as StarSymbol, which is not present on my system, but is displayed correctly. Strange!
os->lpsolit: This is not a P1. I've changed prio to 3 os->hdu: Do you have an idea?
Please attach a min document showing the problem and a small screenshot of the problem. Do StarMath and StarBats show up in the "Insert Special Character" dialog? Are they also visible in the Writer's font list?
Created attachment 13261 [details] screenshot
Created attachment 13262 [details] original file
I attached a doc and a screenshot of the problem. Using OOo 1.1.1a, setting the font to StarBats and typing "3" and "4" led to the two symbols shown in the screenshot. Using OOo 1.1.1b, the same operation writes numbers 3 and 4 instead of the two expected symbols. Both StarBats and StarMath are visible and usable in the "Insert Special Character" dialog. Both are also visible in the Writer's font list but are unusable!
HDU->US: can you help me to reproduce this?
Is it Windows or Linux you are working on? Because the issues states Linux but the screenshot looks more like windows.
I am working on Linux. I did not try on Windows. The problem is still present with OOo 1.1.1 RC3.
Looks like typing numbers as e.g. 3 or 4 results in 3 or 4 (although a special character font is set). Looks like a glyphfallback feature. US->HDU: WFM (aka works as designed)? Anyway, I wouldn't recommend to change the current state until this issue got lots of votes (you remember? we talked about votes lately. Maybe set to WFM, LATER or REMIND).
I cannot believe it worked in <=1.1.1a. Anyway, the problem is that when StarBats is not installed but is used anyway, OpenSymbol/StarSymbol is used and the symbols are translated accordingly. Now, since the unicodes for '123' are not symbol unicodes, they do not get translated, but are left as is. If StarSymbol is installed, it has the unicodes there, if not the glyph fallback comes to the rescue... For backward compatibility I'll add "symbol unicode aliasing to 0x0020..0x00FF" to the conversion tables...
Because of limited resources for the next product udpate on OOo1.1.x we have to re-target this issue to OOo1.1.4.
Fixed in CWS vclppbugs4 for target PP4. For testing instructions please see issue 30018.
reopening for reassignment
reassigning for verification
HDU->US: please verify
Verified. Pls. refer to issue 30987 for a follow-up on this topic.
consolidation of "please help" indicators: removing "easy2dev" keyword, formerly known as "todo". This issue never deserved it.
target
Verified in master m52.