To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=43393
------- Additional comments from [EMAIL PROTECTED] Thu Feb 24 02:32:06 -0800 2005 ------- Well it clearly showed up in the CWS on Unix (and still does in the CWS!), but as SJ claimed it would be the same problem he was always facing with MWSes via ReflectionX, CGU decided to approve the CWS (although he should have known better). On the other hand almost no one in that CWS group knew that substantial changes had been made to the GlyphFallBack and what that means. My expectation is (and we will nail this down in the respective process groups) that such substantial changes should: 1. not be done any more in a phase close to a release 2. should result in an explicit request for testing of a certain module along with the required information what specifically to look for (e.g. on the EIS status page) or in a seperate QA-Child-Task (which is already common practice in QA when core changes apply to all applications). The remaining and AFAIK not yet understood font problem is what SJ claims to have with the MWSes via remote ReflectionX connection from a Win32 to a Linux host. Not sure whether this still remains. @SJ: can you still reproduce and if so, would you mind to open up a follow-up issue. --------------------------------------------------------------------- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
