A few suggested improvements for the UE when someone encounters a problem with the Software Update system: - most of the software update error messages include the string "(Contact Your Administrator)". Most of our users don't have one of those, and the message ends up being unneccessarily confusing. - the capitalization of the error messages should be sentence-style, not book-style (ie: "Proxy server not found" vs. "Proxy Server not Found") - *boldface* draws the user's eye to the error message which, for the majority of our users, isn't as important as the workaround. I'd suggest reverting to normal typeface.

This patch contains the string changes without changing the names which I'll do after the error string have been reviewed.

Comment on attachment 337711 [details] [diff] [review] string patch in progress rev1 I think we should consider removing the AUS: prefix... does having this provide any real value in comparison to giving the user something else to wonder about?

(In reply to comment #3) > (From update of attachment 337711 [details] [diff] [review]) > I think we should consider removing the AUS: prefix... does having this provide > any real value in comparison to giving the user something else to wonder about? Can't imagine AUS adds much value. Do the error codes, such as (404), add value? If they do, I'm wondering why they're on some strings and not others.

(In reply to comment #4) > (In reply to comment #3) > > (From update of attachment 337711 [details] [diff] [review] [details]) > > I think we should consider removing the AUS: prefix... does having this provide > > any real value in comparison to giving the user something else to wonder about? > > Can't imagine AUS adds much value. Do the error codes, such as (404), add > value? If they do, I'm wondering why they're on some strings and not others. They are standard error codes used while browsing so there are quite a few people that do understand them (e.g. 404 - page not found). These codes are also displayed in the browser's error page. I am tempted to have the error code for all errors available as it is in the browser's error page for debugging purposes but I'm not convinced this would be a good thing.

> I am tempted to have the error code for all errors available as it is in the > browser's error page for debugging purposes but I'm not convinced this would be > a good thing. Yeah... I'm trying to think of the use casse for using one vs not needing one. The ones that are displaying now seem to be some of the most common error codes, but other than that I'm not sure how they were selected. I'm guessing argument is that if you have the code it's easier to look online for more information about the error... but if that's the case, why are they only on some? Maybe we should have them on all or none, unless there's another factor here.

I think the majority of people don't care one way or the other about the error code but when reporting a bug for app update it does simplify things a bit. As long as the report contains the exact text then we should be ok without the error message.

Comment on attachment 337738 [details] strings without AUS or error codes, update not capitalized Let's ask beltzner

Fixed by the checkin of bug 324121