gtg-contributors team mailing list archive

[Izidor Matušov <izidor.matusov@xxxxxxxxx>]

Hi,

I started working on a branch to apply you string modifications. It's 
late here, I would finish it tomorrow or after weekend. I am sharing my 
few suggestions bellow.

Am 23.03.2012 03:24, schrieb Radina Matic:
> 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!

It seems that according official pages [0], it is written as D-Bus. I 
would use D-Bus or DBus, but not DBUS because it feels like shouting.


0: http://www.freedesktop.org/wiki/Software/dbus


> ------------------------
>
> 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.

I updated the string to be:

message_format = _("%s 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.") % self.software.title()

It should produce strings:
 "Tomboy seems to be ..."
 "Gnote seems to be ..."

Is that what you asked for?

> 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... ;)

I don't want to be nitpicking but there are also just import or 
read-only backends: fetch the list of bugs assigned to me, import unread 
e-mails, import articles from RSS and so on => just one way.

Synchronization means both ways: I get some tasks, modify them and send 
them away. Although it wouldn't be correct, probably everybody would use 
just synchronization backends... ehm.. services.

> 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.

Software is evolving over the time. Maybe somebody added a new menu item 
and didn't check the capitalization, used a synonym, etc. If you find 
any other glitch, just report it - I am willing to correct it.


>  > 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?

Yes, it is unused code. Thanks for pointing it out.

Izidor