Bug : Leakage of messages into text translation pool

Yeah, I've been locking these down as well since day one. Geni is well aware of this bug but it's evidently very low on their priories list.

There're 27 of them currently :)
http://www.geni.com/tr8n/phrases?page=1&phrase_status=any&p...=
And in Estonian some of them have more than one translation!

I translate these for FUN! Every friday night! It's clearly 10 extra points for having more than one translation on these :)

@Olav So that's how you got to the top of the list!

@Victar "...but it's evidently very low on their priorities list."

Facetious, bordering on negative, comment coming up....You are making an assumption that Geni has such a list....

Seriously; if such a list was communicated, most of the frustration would be alleviated. It's the deafening radio silence/lack of communication that puzzles me. I see Noah on the list of Translation project Followers but he hasn't used the "speak" button on the radio handset yet....;-)

Best regards Oddbjørn
(middle name = frustrated, last name = annoyed)

Noah said he was going to us join us in the forums this week.

OK. Sounds good. I'm continuing to use translate@geni.com to report errors/omissions and the project discussion for, well, discussions.

Anyone have any suggestions as to how we (creatively) could use the project structure to post missing translation string images (screen captures)? A profile for each language with the US Geni being a single parent and images hooked up to the parent (for missing strings) and to the "child" for stuff that misbehaves per language (rules related issues); using the document feature?

As the various languages are nearing 100% translation status of the user interface, I assume these will be the ones that we will focus on towards the end of this first iteration of translations.

These "Deleted Topics" phrases shall all
A) firstly replaced by phrase withn token (currently missing): "The topic {topic} has been removed"
B) only then deleted.

Oddbjørn, if i might suggest, do both and be sure to post the ticket number here as well.

@victar As to your last post; Why the double effort? I fail to see the logic in doing double volunteer work; once should suffice. Geni needs to tell us what category of communication should go into what channel. Life's just too short to waste time on double effort.....;-)

The advantage of posting bugs here is that the same bug doesn't get reported 87 times by 87 people.

Geni is a commercial company, heavily based on software developed by their own staff. Software companies typically have a self service portal where customers report bugs. Once a bug is verified, the paying customer can follow progress on the matter through the self service portal. If the bug is of a nature that it must be expected that other users will encounter the same issue, the symptoms of the bug, work-arounds and ideally, plan for a fix, is communicated to the user base through a known-error-database part of the self service portal.

I have documented bugs found, sent them through to the service provider (Geni), using the channel of communication that Geni has made available (translate@geni.com). If they have changed their mind and now want this communication to go an alternate route, they should have a clear statement on what-goes-where and how it is being handled.

If it is of importance to duplicate tickets, then Geni should do it themselves.
I feel I have held up my end of the deal, now I expect Geni to do their part.