So you say that an error message containing some technical information is worse than one with almost no information at all? I'm sure I disagree for myself, as I find an error message like 'No Symbols named "mac_nodeadkeys" in the include file "macintosh_vndr/de"' (from bug #327963) to be both understandable and useful, and to be a good description of the cause of the error, not a mere "technical detail". But I have to concede that I'm no average user, and my ideas of how they would react to such a message might be completely wrong.
Of course, I agree that it would be even better if such error messages would not occur in the first place, and bug #327963 is aiming at avoiding the error message I just quoted. That might not be the only possible error, though.
So you say that an error message containing some technical information is worse than one with almost no information at all? I'm sure I disagree for myself, as I find an error message like 'No Symbols named "mac_nodeadkeys" in the include file "macintosh_ vndr/de" ' (from bug #327963) to be both understandable and useful, and to be a good description of the cause of the error, not a mere "technical detail". But I have to concede that I'm no average user, and my ideas of how they would react to such a message might be completely wrong.
Of course, I agree that it would be even better if such error messages would not occur in the first place, and bug #327963 is aiming at avoiding the error message I just quoted. That might not be the only possible error, though.