To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112228
------- Additional comments from a...@openoffice.org Thu Jun 10 10:19:08 +0000 2010 ------- AW: I agree that this is a problem for people who have no idea how to solve the problem; OTOH OOo cannot stand in for every problem caused by HW- or SW-base. We already try to do as much as possible and often work around issues which are not ours, but there is a border not to cross; errors have to be fixed where they emerge; else You will often see the inverse error when 'worked around' in OOo and suddenly fixed in the root cause system part. For this task, it would mean that the user's system is capable of fast AA one day, but will still show non-AAed since it was switched off by the user. Don't tell me that a standard user will try to switch it on again from time to time. We still have the possibility o swich AA completely off in that case; why did we left in that option, though? As an application on the end of the food chain You often get tasks 'it's not working' and when looking why the rason is not OOo at all; nonetheless people blame OOo for it. Sometimes i just wish people would more often write tasks to the source of the problem (after identifying or being told). Maybe it's just easier to write a task for OOo... --------------------------------------------------------------------- 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...@gsl.openoffice.org For additional commands, e-mail: issues-h...@gsl.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
