Bertrand, I am glad that my comments will make GTG more usable :) These details are easier to catch for somebody with less programming knowledge like me, as I am closer to the point of view of the ordinary user...
To make the my replies clearer (replying on mailing lists often gets so messy) I'll strip the text to just the important bits: --------------------------------- > 39. Actually the subject of this phrase is automatically added with "self.software.title()" in the code. It should thus read something like: "Tomboy was found on the system, but it (...)". So I guess this string is ok. > was found on the system, but it does not provide a DBUS interface which is > required by the Tomboy/Gnote plugin. This is perfect! ------------------------ Ok, now that I know that "self.software.title()" in the code will result in app name (Tomboy in this case) then I would rephrase the string again: program seems to be installed on your system, but it does not provide a DBUS interface which is required by the Tomboy/Gnote plugin in GTG. If I can make another general suggestion which applies to all the error messages presented to the user: whenever possible, the message that informs of a certain error that occurred should include (at least) the suggestion of what can be done to correct the situation. You guys may know what to do to fix the missing DBUS interface, but the ordinary user may not even know what a DBUS is, and is left there thinking "Oh great, now what do I do to make this thing work...?" I know it is not always possible, and that sometimes it can go far beyond the scope of a simple error message, but I recommend to make the effort of assessing each error case, and whenever possible, structure the messages for users in 2 parts like this: 1. Error X has occurred. 2. Try doing Y to correct the situation. ---------------------------------------------- > 52. This backend synchronizes your tasks with the web service > RememberTheMilk: > > Comment: > - usage of the word "backend" - Here it seems to be used as a synonym for > plugin, why not call it that way directly? It's actually more of a synchronization service. It's a specific category of optional features that are kind of distinct of plugins. But I agree that this might be confusing. That would certainly require some discussion. This could be done during the ongoing redesign effort. Right now, for the sake of consistency, I'd leave it that way. If we were to adopt "plugins" for instance, then we would also have to change the UI a bit (right now those features have separate UI spaces). -------------------- I understand, and I am not proposing to necessarily get rid of it altogether, just to explain it better. So, if it is kind of a synchronization service (which is fairly understandable), why not call it "*backend **synchronization service*". It may be long, but it is clearer. I know that KISS is mantra, but sometimes longer is better... ;) ----------------------------------------------------------------- > 203. Workview or workview or "Work View"? I'd say "Work View", but I'm no native English speaker, so I may not be aware of the subtle difference in meaning. ---------------------------------------------------------------- Then "lo tenemos chungo" as they say in Spanish, as most of us are not English native speakers either... :)))))) Anyway, I do not think there is any significant difference in meaning, and the point is to choose one way of calling a certain feature and stick with it everywhere: main menu, contextual menus and the app window. -------------------------------------------------------------- > > 267. "Make a Task" - is this different from "New Task"? I can't seem to find where this string is used... --------------------------------------------------------------- I couldn't either, maybe it is an obsolete part of the code? I know that that the GTG redesign is an ongoing process and I am glad to be part of it! To be continued... ;) Rgds, Radina On Fri, Mar 23, 2012 at 00:37, Bertrand Rousseau < [email protected]> wrote: > Hi Radina, > > Thanks for your contribution!. This is an impressive work you've done here! > > I guess you'd like to have some feedback on your suggestion. > Personally, I find your suggestions really good, and I'm ok with most > of them. When I felt some discussion were needed or when I could > answer to your comment, I inlined my answer. > > Bertrand > > On Wed, Mar 21, 2012 at 10:40 PM, Radina Matic <[email protected]> > wrote: > > > > Hello everybody, > > > > During the last few days I have been updating the translations in > Spanish, > > Italian and Catalan and I would like to propose some improvements for the > > original (English) strings for GTG (original is bold, my suggestions are > in > > blue): > > >
_______________________________________________ Mailing list: https://launchpad.net/~gtg-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~gtg-contributors More help : https://help.launchpad.net/ListHelp
