gtg-contributors team mailing list archive

[Bertrand Rousseau <bertrand.rousseau@xxxxxxxxx>]

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 <didinomade@xxxxxxxxx> 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):
>
>
> 5. A simple Web page (nicely printable)
>     A simple Web page that can be easily printed.
>
>
> 6.  A template to create a simple HTML page with some tasks. It can be
> printed nicely.
>      A template to create a simple HTML page with some tasks that can be
> easily printed.
>
>
> 14.   Could not generate the document: %s           (Comment: Subject of the
> phase is not clear.)
>         GTG could not generate the document: %s
>
>
> 39.  was found on the system, but it doesn't provide a dbus interface. the
> Tomboy/Gnote plugin will not work with it.
>
> Comments:
>  - Phrase is unclear: What is "it" exactly, the missing dbus interface or
> whatever that is not providing it?

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.

>  - dbus is written in capital letters (DBUS) in other strings, we should
> choose one for the consistency and coherency and stick with it

I agree. DBUS in capital seems better.

>  - Capital T at the beginning of the second phrase

Indeed, nice catch!

>
> was found on the system, but it does not provide a DBUS interface which is
> required by the Tomboy/Gnote plugin.

This is perfect!

>
>
> 50.    This backend can synchronize all or part of your Gnote notes in GTG.
> If you decide it would be handy to have one of your notes in your TODO list,
> just tag it with the tag you have chosen (you'll configure it later), and it
> will appear in GTG.
>
> Comments:
>  - usage of the word "backend" does not seem clear here, but that could just
> be me... What should it represent: a plugin? a web service? If it is
> something that the regular end user sees and needs to configure, I believe
> the term "backend" (which can be pretty generic - see for example the
> Wikipedia page) should be defined more precisely, rephrased or renamed to
> something more suitable for non-geek users.

I agree, but this is then a policy that must be decided for the whole
application.

I filled a bug for this: https://bugs.launchpad.net/gtg/+bug/962642

>
> - tag the note with the chosen tag that you will only configure later? I am
> scratching my head...

Wow, that's a hard one. Here's the deal: in GTG you can synchronize
task with other services. To identify those tasks, you tag with a
specific tag (that you can chose). I gues this phrase is trying to
explain this.

> - what is the "TODO list", list of tasks in GTG window? It is not called
> that way anywhere else in the GTG interface and it may confuse the user. On
> the other hand, the informer of the [Bug 955728] has a point there because I
> tried to do a search in Fedora Software Sources for "to do list" or "task
> manager" and GTG was nowhere to be found. So maybe the description of the
> GTG should include these keywords otherwise the potential users will not be
> able to find it easily...

Ok, two things there, thus:

 - the text should not mention a "TODO" list. In GTG, it is more
conventional to speak about the "task list".
 - we definitely should include "to-do list" somewhere in our description.

I have filled a bug for the second point:
https://bugs.launchpad.net/gtg/+bug/962649

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

>
>
> 56.    Same comments as nº 50 (Tomboy)
>
> 58.   Comment:
>           - usage of the word "backend" again
>           - Mantis should begin with a capital letter
>           - I find "reverted changes of an issue" unclear, but since the
> 0.2.4 version that I have does not have that                 implemented, I
> may be missing something obvious.
>
> 67.    Same comments as nº 50 (Launchpad)
>
> 75.    dbus - capital letters or not?
>
> 77.    dbus - capital letters or not?
>
> 82.  Small edits for clarity:
>
> Welcome to Getting Things Gnome!, your new task manager.
> In GTG, everything is a task. From building a bridge over the Pacific Ocean
> to changing a light bulb or organizing a party. Task is automatically saved
> while you are editing.
> Once you are done with a specific task, you can push the &quot;Mark as
> done&quot; button. If the task is not relevant anymore, simply press the
> &quot;Dismiss&quot; button.
> A task might be composed of multiple subtasks that appear as links in the
> task description. Simply click on the following link to open the subtask:
>
>
> 83.  Small edits for clarity:
>
> Once you've read the above subtask, mark it as Done. If you decide not to do
> the task, mark it as Dismissed. Tasks that you marked as Done and Dismissed
> are stored in the Closed Tasks Pane which is hidden by default, but you can
> easily enable it in the View menu.
> If you choose to close this current task, its subtasks will be automatically
> closed too. GTG considers that if you have completed a given task, you don't
> need to do the subtasks anymore.
> Other stuff you should read:
>
> 86.   Edited for clarity:
>
> &quot;Subtask&quot; is something that you need to do first in order to
> accomplish your task. To insert a subtask in the task description (this
> window), begin a line with &quot;-&quot;, write the subtask title and press
> Enter. Try inserting one subtask below.
> You can also use the &quot;Insert subtask&quot; button.
> Tasks and subtasks can be reorganized by drag-n-drop in the tasks list.
> Subtasks have certain rules: for example, a subtask's due date can never be
> after its parent's due date and when you mark a parent task as done, its
> subtasks will also be marked as done.
>
>
> 96. Comments:
>
> - "Quick Add Entry" as a feature name sounds a bit redundant to me given
> that "add" and "entry" are practically synonyms. According to the GNOME
> Desktop Terms "entry" is more of the qualifier for the term "field" and I am
> not sure if it should be part of the feature/option name...
> - the average user might find the term "syntax" too technical
> - not sure if this is a bug or not, but a tag beginning with an @ will
> appear in the task title
>
> Edited for clarity and added some examples:
>
> The Quick Add Entry is the fastest way to create a new task. Use the check
> box in the View menu to enable and disable the entry field.
> To add a task simply type its title in the entry filed and press Enter. The
> task will be created and selected in the task browser. If a tag is selected
> in the Tags Pane, it will be applied to the task you created.
> You can also create a task in the Quick Add Entry and at the same time
> specify its tags, due and defer date. Follow these format rules:
>
> tags:tag1,tag2,tag3
> - This way you can apply as many tags as you wish using comma as separator
> - Any word that begins with &quot;@&quot; will be interpreted as a tag
>
> due:date
> defer:date
> - This way you can apply a due date or a defer date. Dates can be formated
> as yyyy-mm-dd (for example 2009-04-01), yyyymmdd (20090401), mmdd (0401 -
> the year being implicitly the current one) or today, tomorrow or a weekday
> name (due:monday means due next Monday). Dates which are added in this way
> will be not appear in the task title.
>
> Examples:
> <b>buy stationary tags:purchases,office due:20120330 defer:tuesday</b>
>
> - The above example tells GTG to create a new task with the title "buy
> stationary", under the tags "purchases" and "office", with the due date
> March 30, 2012 and the start date next Tuesday.
> <b>call mum tags:family,calls due:sunday defer:tomorrow</b>
> - The above example tells GTG to create a new task with the title "call
> mum", under the tags "family" and "calls", with the due date next Sunday and
> the start date tomorrow.
>
>
> 125. gtg or GTG?

GTG

>
> 148. There is no task tagged %s
>
> 152. - usage of the word "backend"
>
> 168.  Deleting a task cannot be undone. Are you sure that you want to delete
> the following task?
>
> 173.  Click on the plugin name to view its description here.
>
> 174. - usage of the word "backend"
>
> 175. - usage of the word "backend"
>
>        GTG could not contact backend <b>%s</b> due to a network problem.
>
>
> 176. - usage of the word "backend"
>        - DBUS or dbus?
>
>        GTG disabled the backend <b>%s</b> because of the failed connection
> to DBUS.
>
> 177. - usage of the word "backend"
>
> 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.

>
> 204.  Workview or workview or "Work View"?
>
> 224-230, 274. Capitalization is inconsistent throughout the main menu,
> contextual menus and the app window: "Mark as Done" or "Mark as done" or
> "Mark Done"?

Is should be "Mark As Done" I think. That's what other apps do.

>
> 267. "Make a Task" - is this different from "New Task"?

I can't seem to find where this string is used...

>
> 273. Comment: I suggest we differentiate the verbs - "to insert" for tasks
> and subtasks, and "to apply" or "to add" for tags
>
>  Add a tag to this task
>
>
>
> I am sorry if all this seems a bit anal, but the consistency of the GUI
> terminology is a big part of the usability and the user experience. Original
> strings should also be polished as much as possible to avoid the unnecessary
> future corrections of the translations in other languages...

You're totally right. Thanks again for spending time doing that. You
can't imagine how valuable it is!

>
> Rgds,
> Radina
>
>
>
>
>
>
>



-- 
Bertrand Rousseau