To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99029
------- Additional comments from c...@openoffice.org Thu Feb 12 18:09:59 +0000 2009 ------- "The font was gedit's default font (gedit simply says Monospace), and was an ordinary text font. That seems to eliminate the problem of not being able to draw the font. The culprit appears to be the string itself, or in it." Not really, it doesn't always quite work that way, i.e. its just "raw text" when copied from gedit, the font doesn't come with it so if there was a missing glyph there could be two different fonts, and two different font-replacement technology stacks in operation, the gedit one (which doesn't crash) and the OOo one (which did). Anyway, its probably not that issue, I only mentioned it as a example. If you have a text file which reproduces this then just attach it here and we can have a look at it. If its confidential, and you trust us :-), then you can send it to either myself (c...@openoffice.org) or I'm sure m...@openoffice.org would also be willing to test it out-of-band --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
