Translating tokens

one small example - the heding of tis page contains the phrase "Public Discussions"
when I want to translate it,I get :" {category_name} Discussions "
the category_name is untranslateable token

any help from other translators of Geni?

Hey Ya'acov! I'm a fellow translator, but for the Swedish language.

I take it that you are not a 'language administrator' as well as 'language translator'? As I have come to understand it, only language administrators get access to modify the actual tokens themselves, the rest of us can only apply them.

I'm myself a regular translator without any language administration rights so I've been having the exact same problem as you with the {category_name} - it worked fine up until a couple of months ago but then some site update probably messed it up. Why it was changed at all - who knows? I asked someone about it & got the reply that everything was working as intended (which is obviously not the case at all). There are most likely several more of these 'kinks' lurking about in the system.

As a side note, I have also requested for language administration rights - to be able to construct/modify some necessary Swedish tokens - but over a month has passed by since the request was made with no further communication but an initial reply of "thanks for showing interest" ... So .., I guess I'm either labeled as a "persona non grata" or the Geni-guys are so busy elsewhere that refining the translations further is not a priority at the moment.

It basically boils down to patience & faith that someone eventually starts caring about getting the translations done again.

Regards,
Olav

Hey Olav,
Thanks for the answer.
I really want to be upgraded to be Hebrew Administrator. And I'm ready to invest my time in it. Who is in charge of it?

Is there a translation "Master" for each language?

Ya'akov

In an old query re translation of tokens, I was told by Geni staff NOT TO TRANSLATE any phrase within these brackets { } as these phrases are so far untranslateable tokens. If it works - I would not attempt to change it.

Translations of pairs (2 days, 2 weeks, 2 months, 2 years, etc.), commonly used in proper Hebrew must unfortunately fall into the "not_1" category (so far). We could live with it. I believe it would be a common problem for translation of Geni to other Semite languages as well.

Shalom Yigal
The problem is not only the 2 days= yomayim
one small example - the heading of tis page contains the phrase "Public Discussions"
when I want to translate it,I get :" {category_name} Discussions "
the category_name is untranslateable token
Do you know about any user (not Geni programmers) that can translate tokens?
I really don't want to fix things that work. I'm trying to fix those things that don't
:)

1. I don't know anyone who is authorized to translate tokens.
2. I left it as is, and when the translation does not make sense or the Hebrew is not accepted - I open a help ticket - and eventually get a reply.
3. Many phrases - tokens are not in the translation list or only partially in it, also some of the gender-linked phrases to not conform to the Hebrew grammar. Either we leave them or translate them, including a non-gender translation.

Maybe we need a language curators as well.
I vote for Yigal
:-)

I guess the main point here would be that no language will be able to become 100% grammar correct if authorizations to modify tokens - or the ability to build specific language rules - are denied.

Until that day comes, most other languages besides English will stay being incomplete gimmicks, just simple tools to enable pushing more targeted emails & help marketing efforts.

I do hope there is a consensus to provide a 100% product & service that does not only pay lip service to "Geni is now available in X and {count} other languages".

To continiue Olav's words - we can translate "Geni is now available..." into "Geni is now available in {language} mixed with Jibrish, Wouid you like to try?"
:-)

Yaacov Glezer and Olav Linno Poëll

Even Language Manager can not currently add some special rules if they are not foreseen by Geni.
I don't know who is your Hebrew manager and I can not predict is the main language page configured accordingly to your language rules (i.e. the count and gender can be used simultaneously etc.). I just know that there are still limitations for Language Cases at Geni...

BR

Lauri Kreen
- one of the language administrators for Estonian

Lauri,
Please tell us the secret...
How did you became Language Admin?

The initial translators was automatically language managers, and I am sure Shmuel-Aharon Kam (Kahn / שמואל-אהרן קם (קאן is the manager for Hebrew. He can probably ask Noah to promoter you to a language manager if he have the opinion that you needs it.

I will however warn about playing with the values available in the language console. If you change a rule already in use all translation attached to that rule has to be reentered again, so I would not recommend to keep the number of people who have access to a minimum.

This is a fresh snapshot of the language console wit some extra rules temporary expanded:
http://i632.photobucket.com/albums/uu41/bpbrox/Translations/Languag...

Bjorn - thank you
Shmuel - what do you think?

Ya'acov,
I have sent a message to Noah. You HAVE done an impressive amount of work. Please try and not break the system.If you do, Yigal and me will come and get you! ;-)

Dear Shmuel,
If you and Yigal come and get me, give me prior notice - I'll buy Mehadrin cake and put water for coffee.

Yaacov Glezer - I wanted to say the same as Private User already did - to contact your Hebrew Curator - Shmuel-Aharon Kam (Kahn / שמואל-אהרן קם (קאן the Curators are usully language administrators and can give this rights also to others - or organize it somehow.

Private User - Did somebody used the Language Cases thing? Any examples - Swedish, Finnish, Russian, German, Hungarian etc..

Lauri

Lauri - I saw some phrases in Russian that has laguage cases. but I cannot see the rules inside
change your language to Russian and search for a phrase containing "give" - you'll find a lot of them.

I shall probably ask examples from Private User or from Private User. They are not PROs nor Curators... I don't know who is Admiinistrator for Russian - only he/she can send me required screenshot or other examples.

Private User - "Translations of pairs (2 days, 2 weeks, 2 months, 2 years, etc.), commonly used in proper Hebrew must unfortunately fall into the "not_1" category (so far)."
Geni software engineers shall do something...

At least they can understand this problem as in English they have also non-regular situations: 1st, 21st, 31st .... 2nd, 22nd, 32nd..., 3rd, 23rd, 33rd..., but 4th, 5th, 6th, 8th, 9th, 10th, 11th, 12th, 13th, 14th, 15th, 16th, 17th, 18th, 19th, 20th, 24th...

If I want currently create similar rule/logic for other language - this is not possible.

Lauri (how do make a link to user name?) - as shown by Bjorn -
a language manager can add more cases to number token
it will do well for the Hebrew phrases I've mentioned earlier. about adding the nd to 2 and rd to 3 in english - as far as I understand the logic of GENI - it should in the token itself, and that's done by a progammer and not by translator or managaer.
a good suggestion is to add these numbering pattern abilities to language managers.

Yaacov Glezer - link to profile/user: [[ GENI ID Number ]] (without spaces).

I know that there are some limited possibilities to add cases to number etc... Without examples (Private User's one was nearly empty) I don't know how to do it.
In Estonian we have 14 Language Cases (for nouns etc) with word changing ends (post-positions like in Latin) + also plural version from each. I just cant understood how to define them in Geni with language tools. For verbs the situation is even more problematical...

Lauri

-I know Russian and I understand the complexity. In Hebrew it's not relevant for now.
I'm waiting for a tool to activate language cases on every possible token.

I am totally out of my league here. Have you contacted

geni help <help@geni.com>? They have been very receptive to my inquiries in the past.