Opened 9 years ago

Closed 5 years ago

#1282 closed improve feature (fixed)

In Gallery, there's no link to translate "add description"

Reported by: tonchi Owned by: shevek
Priority: major Milestone: 2.1
Component: BW Internationalization Keywords: translation
Cc:

Description

BW Rox version: user agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath?.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30) request uri: http://www.bewelcome.org/gallery/show/sets/322?sidTB=BVF9JJ4BMl9mN9Uqi9SWsAa8Q6a

In Gallery, there's no link to translate "add description" It says: <SPAN class=tr_span><A class="tr_link missing_translation" title="translate GalleryAddDescription? in hr" href="http://www.bewelcome.org/bw/admin/adminwords_edit.php?lang=hr&amp;code=GalleryAddDescription" target=new>Add Description</A></SPAN>

Change History (17)

comment:1 Changed 9 years ago by globetrotter_tt

  • Component changed from unknown to BW Internationalization

comment:2 Changed 7 years ago by globetrotter_tt

  • Summary changed from bug report to In Gallery, there's no link to translate "add description"

comment:3 Changed 6 years ago by TimLoal

  • Priority changed from minor to major
  • Type changed from unknown to improve feature

comment:4 Changed 6 years ago by TimLoal

  • Milestone changed from Future to 1.0

Move to milestone 1.3 or 1.1 if not suitable on 1.0

LnP

comment:5 Changed 6 years ago by crumbking

@ Tim: I appreciate your willingness to help out and reorganize our bug tracker. But why is this a major ticket? This is a missing translation string. So it's minor/trivial.

I suppose you will work on all this tickets you added to milestone 1.0? If not please stop to add new tickets. If developers will work on an issue they will pick a ticket. And if a ticket is ready we add it to the milestone. Thanks you.

comment:6 Changed 6 years ago by TimLoal

@Crumking Thanks for your appreciation.

You are confusing severity with priority. The severity field has been disabled or removed and priority is now incorrectly used as you suggest. This should be corrected, so that the TWO bits of information can be clearly and separately identified per ticket. If you don't like using the priority field for the ticket priority, in preference to its severity, then, please open a ticket to correct this confusion. I have set it to major, because it is a low hanging fruit UX bug, that I believe can be resolved, before 1.5, so should be of high priority on the list.

I would love to close all these tickets, but i suppose too much cheap sarcasm is what needs to be stopped around here. I would have created milestone tickets 1.2 and 1.3 for these quick fixes, but rather than contacting me, helping me or responding to requests, one of the trac admins has restricted access to modify milestones and reports, without saying anything. Are there people that don't want bW to get better? Or at least not by their doing? I sometimes wonder.

There is no clear way to know the progress without reading its updates. I have elected a number of hopefully easy and quick tasks, and commented on most of them that if they are not suitable for 1.0 to move them to 1.2 or 1.3. Electing tickets in this way is an easy and clear way to focus on a set of tickets or do you think people will trawl through 270 tickets, to see which ones are ready or easy? I have worked many large corporate helpdesks, with a higher user base than bW has members, it is not like i'm jumping in without having a clue.

LnP

comment:7 Changed 6 years ago by crumbking

@Tim: I got hundreds of trac mails in the recent days in my inbox. Every time you change a setting from minor to major or milestone x to whatever etc. sends a mail to all trac users. So I fully understand the trac admin. He stops the flood of mails you are generating while reorganizing trac.

Back to the ticket: This ticket is minor, as it does not break anything on the page. We are volunteers here who work in there free time and I appreciate that you wanna show up some easy and quick tasks but this is not the way to do it. We discussed some tickets for the next milestone in the dev list. If nobody picks some easy tasks than we can't change that.

The process is simple: Pick a ticket, fix it locally speak with one of the release guys if you can add it to the next milestone and push to develop. That's it ;-)

comment:8 follow-up: Changed 6 years ago by TimLoal

If you got an email for every update you probably got at least 1000 emails. Thats is part of the reason I have paused this work for a while and look for quieter ways to tidy up the remainder of the list.

It entertains me in a perverse way that someone who is a user of such a messy list, which seems to have no one running it or even caring(the state of this list speaks volumes about the attitude on this project), is more bothered about a few emails, which can easily be deleted, rather than the 2 days of work someone has put in to sort out that list.

Restricting the modification to the reports and milestones has no effect on re assigning tickets or correctly tagging them, it just means that someone else has to help me or that i'm obstructed from doing the job, which speaks even more about the priorities of the project.

I won't get into a slanging match about priority, over what i said in the last ticket, if this confuses you, please raise a ticket for the severity field to be restored so that it can be used for the purpose you prefer.

Unfortunately, I can get to the easy stage, as you suggest, becuase I am still waiting for help on the other easy stage on installing a local build, which is failing on my computer, due to space i believe, but like i say i'm still waiting on more information on that. This is partly why I went to work on something that I could do, housekeeping Trac.

Rather than sarcasm, is there any chance you could spend you time and energy just on imporving bW?

LnP

comment:9 in reply to: ↑ 8 Changed 6 years ago by crumbking

Replying to TimLoal:

Rather than sarcasm, is there any chance you could spend you time and energy just on imporving bW?

Sure! Doing since a while. But as this is totally not ticket related by both of us - let's discuss a bit via mail.

comment:10 Changed 6 years ago by jsfan

  • Milestone changed from 1.0 to unassigned

comment:11 Changed 6 years ago by TimLoal

  • Milestone changed from unassigned to 1.0

comment:12 Changed 6 years ago by jsfan

  • Milestone changed from 1.0 to unassigned

comment:13 Changed 6 years ago by shevek

Several languages contain a translation nevertheless. Question is when were these made?

comment:14 Changed 5 years ago by shevek

  • Milestone changed from unassigned to 2.1
  • Owner set to shevek
  • Status changed from new to assigned

There was an echo missing in front of the flushBuffer. Fixed.

comment:15 Changed 5 years ago by shevek

  • Status changed from assigned to to_alpha

comment:16 Changed 5 years ago by shevek

  • Status changed from to_alpha to testing

comment:17 Changed 5 years ago by crumbking

  • Resolution set to fixed
  • Status changed from testing to closed

works for me

Note: See TracTickets for help on using tickets.