GNOME Bugzilla – Bug 657761
Several strings need review
Last modified: 2013-03-12 13:52:49 UTC
I've been translating the module and if you want non technical users to understand the UI this needs some work: All the errors concerning JSON; if they are gonna be visible, the normal-average user doesn't know whats JSON. guid, token, access_token, access_token_secret, request_token, request_token_secret, screen_name, id_str, ensure_credentials_sync I don't even know what they are, and I have to translate all of them, if I get that error, I will stare at the screen and close the program, then blame someone.
Could you list a few of the strings that are troubling you?
(In reply to comment #1) > Could you list a few of the strings that are troubling you? "All the errors concerning JSON; if they are gonna be visible, the normal-average user doesn't know whats JSON." grep JSON es.po |grep -v "#" |grep msgid msgid "Error parsing response as JSON: " msgid "Didn't find id member in JSON data" msgid "Didn't find email member in JSON data" msgid "Didn't find data member in JSON data" msgid "Didn't find account email member in JSON data" msgid "Didn't find access_token in non-JSON data" msgid "Didn't find access_token in JSON data" msgid "Didn't find id_str member in JSON data" msgid "Didn't find screen_name member in JSON data" msgid "Didn't find guid member in JSON data" msgid "Didn't find value member in JSON data" msgid "Error parsing usercard response as JSON: " msgid "Didn't find profile member in JSON data" msgid "Didn't find nickname member in JSON data" msgid "Missing request_token or request_token_secret headers in response" msgid "Credentials do not contain access_token or access_token_secret" You can keep doing the grep with the pointed strings and you'll get the full list. Easy.
Thanks. I think I was grepping for "json". :-/ Lack of sleep.
Created attachment 238608 [details] [review] Don't use technical jargon in user visible strings I replaced all those strings with this one: - "Couldn't parse response" As you pointed out, there is no need to crowd the UI with all the details because it is basically our inability to parse the response. The more detailed technical strings are now sent to the logs instead of the UI. This is what will end up in the UI: - "Error getting identity: Couldn't parse response" What do you think?
Created attachment 238680 [details] [review] Don't use technical jargon in user visible strings
Just a small tweak: "Couldn't" -> "Could not"
Hi! (In reply to comment #6) > Just a small tweak: "Couldn't" -> "Could not" Thanks for the tweak!
Looks good!