Apache OpenOffice (AOO) Bugzilla – Issue 15407
Display bug underbrace & overbrace
Last modified: 2003-09-08 16:53:10 UTC
See issue 15405 (Formula Command Reference) for example. In a large document with may tables and many cells containing formula entries, a display bug occurs when the underbrace or overbrace command are used. The bug may cause trouble in adjacent table cells which contain text only. The bug can be fixed by cutting out the offending table, and copying it into an empty document. The bug reapears if this new document is added back in to the original document. This issue has been reproduced in Ooo 1.0.3 Windows and 1.1 Beta Build Linux Hardware / software description Windows system is MSWindows98 Second Edition Build 4.10.2222A Running on PC, AMD K-6 (TM), 3D processor. 128MB Ram Linux is Mandrake 9.0 i586 Stock kernal Running on PC, Pentium MMX 233Mhz w/ 64MB Ram Print drivers: cups - Common Unix Printing System - Server package version 1.1.16-0.4mdk Display drivers Xfree86 version 4.2.1-3mdk PostScript interpreter - name ghostscript version 7.05-25mdk
TL->MRU: Please check
MRU->fksaalbach: We need the the file, where the problem occurs, in order to reproduce (and fix) this. It looks like a very complex problem, so it would save us many time. Please attach your offending file to this issue (or send it directly to mru@openoffice.org for the case it contains confidential data) and give a short hint, where to find the wrong object in the document (e.g. on page X). Feel free to reopen this issue when you've done so. Thank you very much!
Created attachment 7430 [details] Draft command reference & how to for calc.
document, the problem did not ocurr, so it perhaps the best route is to leave the issue closed, and recheck it on the next release, to make sure it is reallly gone. The trouble was observed when I was in the process of editing the document, so it is possible that the editing has somthing to do with the issue. The part of the file that contains the offending underbrace and overbrace commands is located on page 26 in table 27. I am going to leave the bug closed unless I observe it in the future.
I can also not reproduce the problem with the document. So this issue remains closed at first.