Re: updating intltool on damned-lies
Hi, On Mon, 2008-07-07 at 20:18 +0200, Sven Neumann wrote: > Would it be possible to update the version of intltool that is being > used on l10n.gnome.org? Please, can someone at least tell me who I should contact to make this happen? Sven ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Gimp traslations
Hi, On Tue, 2008-07-08 at 08:39 +0700, Khoem Sokhem wrote: > On the other hand, till now I still do not have commit access to maintain the > gimp translations for Khmer. every after finished translating gimp I have to > send to the list to ask someone (Sven Neumann) commit for me. > > Could anyone please help to consider about my commit right? You are the official coordinator of the Khmer translation team. How can it be possible that you still don't have commit access? Someone on this list, please explain this to me (and Khoem). Sven ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Subversion plugin on gtranslator
O Mér, 09-07-2008 ás 01:56 +0300, Gil Forcada escribiu: > El dt 08 de 07 de 2008 a les 21:07 +0200, en/na Jorge González González > va escriure: > > El mar, 08-07-2008 a las 20:59 +0200, Nacho escribió: > > > Hi, > > > > > > right now I am working in a subversion plugin for gtranslator. > > > Which options do you think should have a subversion client for > > > a translation tool? > > > For now I am working in: Add (svn add), Update (svn update) and Commit > > > (svn ci). > > > Do you want anything else? (Maybe diff?) > > yup! diff would be awesome, even if it launches an external app such as > > meld. (meld rocks for svn). > > > > > +1000 to just launch meld, it's my more treasured app while reviewing > translations :) > > Don't know if it can be in gtranslator's interface (like any other > plugin) For now it is not possible. We need python bindings, but as soon as we make them, I'll do the plugin for meld. Regards. > > Cheers and keep up with this great work! > > > > > Regards. > > Many thanks Nacho. > > > > > ___ > > > gnome-i18n mailing list > > > gnome-i18n@gnome.org > > > http://mail.gnome.org/mailman/listinfo/gnome-i18n signature.asc Description: Esta é unha parte de mensaxe asinada dixitalmente ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Subversion plugin on gtranslator
El dt 08 de 07 de 2008 a les 21:07 +0200, en/na Jorge González González va escriure: > El mar, 08-07-2008 a las 20:59 +0200, Nacho escribió: > > Hi, > > > > right now I am working in a subversion plugin for gtranslator. > > Which options do you think should have a subversion client for > > a translation tool? > > For now I am working in: Add (svn add), Update (svn update) and Commit > > (svn ci). > > Do you want anything else? (Maybe diff?) > yup! diff would be awesome, even if it launches an external app such as > meld. (meld rocks for svn). > > +1000 to just launch meld, it's my more treasured app while reviewing translations :) Don't know if it can be in gtranslator's interface (like any other plugin) Cheers and keep up with this great work! > > Regards. > Many thanks Nacho. > > > ___ > > gnome-i18n mailing list > > gnome-i18n@gnome.org > > http://mail.gnome.org/mailman/listinfo/gnome-i18n -- gil forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Subversion plugin on gtranslator
2008/7/8 Ignacio Casal Quinteiro <[EMAIL PROTECTED]>: > Ok, I was thinking and you're right. A checkout option would be great. > But maybe in the future. Hey Ignacio, Here's the use case: User Og just installed gTranslator and now wants to work on the translation of empathy. He clicks on the SVN plugin interface, inputs the proper information and credentials (assuming Og has commit access) and performs the checkout. Cheers, -- Og B. Maciel [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Keys: D5CFC202 http://www.ogmaciel.com (en_US) http://blog.ogmaciel.com (pt_BR) ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Subversion plugin on gtranslator
O Mar, 08-07-2008 ás 22:04 +0200, Ignacio Casal Quinteiro escribiu: > O Mar, 08-07-2008 ás 16:01 -0400, Og Maciel escribiu: > > 2008/7/8 Nacho <[EMAIL PROTECTED]>: > > > For now I am working in: Add (svn add), Update (svn update) and Commit > > > (svn > > > ci). > > > Do you want anything else? (Maybe diff?) > > > > Checkout? :) > It is supposed that when you are using gtranslator and the subversion > plugin you already have the po file opened. So I think checkout is > not neccessary in this case. > Ok, I was thinking and you're right. A checkout option would be great. But maybe in the future. signature.asc Description: Esta é unha parte de mensaxe asinada dixitalmente ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Subversion plugin on gtranslator
O Mar, 08-07-2008 ás 16:01 -0400, Og Maciel escribiu: > 2008/7/8 Nacho <[EMAIL PROTECTED]>: > > For now I am working in: Add (svn add), Update (svn update) and Commit (svn > > ci). > > Do you want anything else? (Maybe diff?) > > Checkout? :) It is supposed that when you are using gtranslator and the subversion plugin you already have the po file opened. So I think checkout is not neccessary in this case. signature.asc Description: Esta é unha parte de mensaxe asinada dixitalmente ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Subversion plugin on gtranslator
2008/7/8 Nacho <[EMAIL PROTECTED]>: > For now I am working in: Add (svn add), Update (svn update) and Commit (svn > ci). > Do you want anything else? (Maybe diff?) Checkout? :) -- Og B. Maciel [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Keys: D5CFC202 http://www.ogmaciel.com (en_US) http://blog.ogmaciel.com (pt_BR) ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Subversion plugin on gtranslator
El mar, 08-07-2008 a las 20:59 +0200, Nacho escribió: > Hi, > > right now I am working in a subversion plugin for gtranslator. > Which options do you think should have a subversion client for > a translation tool? > For now I am working in: Add (svn add), Update (svn update) and Commit > (svn ci). > Do you want anything else? (Maybe diff?) yup! diff would be awesome, even if it launches an external app such as meld. (meld rocks for svn). > > Regards. Many thanks Nacho. > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n -- Jorge González González <[EMAIL PROTECTED]> Weblog: http://aloriel.no-ip.org Fotolog: http://www.flickr.com/photos/aloriel ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Subversion plugin on gtranslator
Hi, right now I am working in a subversion plugin for gtranslator. Which options do you think should have a subversion client for a translation tool? For now I am working in: Add (svn add), Update (svn update) and Commit (svn ci). Do you want anything else? (Maybe diff?) Regards. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Missing language teams from Mango
Olav Vitters wrote: On Tue, Jul 08, 2008 at 11:12:57AM +0530, Runa Bhattacharjee wrote: Hi, Christian Rose wrote: On 7/4/08, Ankit Patel <[EMAIL PROTECTED]> wrote: Runa Bhattacharjee wrote: Ankit Patel wrote: [snip] I added http://bugzilla.gnome.org/show_bug.cgi?id=541665 as a request for solving this catch-22 in Mango. Needs some Mango love; I hope that Olav will have time to look at it... Thanks Christian for filing the bug. The conversation in there however, still does not clarify what are the steps a team has to take to ensure that they eventually get commit rights. There is no mention of documentation (or any impending ones) about the LDAP account process, and whether existing Mango doesn't do that yet. So without being able to do stuff, it is pointless to have documentation. teams listed in Mango would be reviewed to ensure that they conform to the requirements. Often, teams go through changes in leadership and may have to What requirements? go through the entire process, irrespective of the maturity/trust of the existing account holders from the language team. How would such a situation be handled? Mango doesn't handle that at the moment. The solution plan as described in: http://bugzilla.gnome.org/show_bug.cgi?id=541505 does not have any time line about the change in process and does not talk about how the *existing* languages would be re-instated into Mango (assuming, the current mandatory rule of I don't get 'reinstated'. Nobody's account has been revoked. The discussion here is not about "account revocation". But about languages missing from the Mango list. And that definitely is a bug. Either on Mango or due to a flaw in the GTP account system or due to some missing bits on the part of the language team. And that bit needs to be documented. There are some specific scenarios here which would require separate handlers. : 1. New Team just starting off, without any kind of accounts (coordinator or team member) - Where is the account request for the first account to be sent and what are the checklist items that need to be completed to get the account? e.g. Pashto 2. Existing Team with translations, without co-ordinator account due to a change in co-ordinator - Where is the account request for the first account to be sent and what are the checklist items that need to be completed to get the account? e.g. Marathi 3. Existing Team with translations, with co-ordinator account, not listed in Mango - Where does a team member send the request for an account? e.g. Gujarati, Bengali-India None of these above cases can be handled by the only documentation available to the GTP volunteers at present, which are: http://live.gnome.org/TranslationProject/RequestingAnAccount http://live.gnome.org/TranslationProject/AccountFAQ Languages teams are right now hitting a blind alley at the New Accounts interface on Mango if any of the above 3 conditions exist. "team-gets-listed-if-svn-account-exists-for-coordinators" is still in Timeline? I don't get paid to work on GNOME. So I can't give a timeline. Especially as I still have to learn Django, LDAP schema stuff, etc. If more people help, it will go faster. Of course, ideally I'd like it to be finished in a few months. But that is not a promise plus it might be fixed faster (no idea). place). Some of these language teams have been around for nearly 5-6 years, highly active, have a larger group of volunteers and have also gone through changes in coordinatorship. Most of the individual language team bugs have been closed with an outright NOTABUG resolution, without any clarification of what we are doing wrong and/or what is to be done next. I think I explained everything. The Mango component is for bugs in Mango. Not about getting people an account. If you want to help, ask me what is needed and submit patches. Discussion won't speed anything up. If someone is at GUADEC, just talk to me. That'll be much easier and faster. In short: Mango is a tool to make the [EMAIL PROTECTED] queue handling automated. If Mango doesn't do something, there always is the email address (which currently is even handled every weekend or so). Currently people will be pretty much lost if they're forgot their Mango password etc, I have ideas about solving that. But don't have time, I work on more stuff on GNOME than Mango, etc. Irrespective of what happens beyond the abstracted layer for the accounts queue handling/admininstration, the translation teams can only meet specific instructions as per whatever is the current process as determined and documented by the GTP to get an account. regards Runa -- blog: http://runab.livejournal.com irc: mishti or runa_b on Freenode ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Lao Team
On 7/2/08, Anousak Souphavanh <[EMAIL PROTECTED]> wrote: > Hi Christian, > > I am Anousak Souphavanh, am a Lead for lao GNOME localization. > Apparently Lao was registered last year and now it is gone. Please > tell me how to proceed or to instate or put the Lao team back. Thanks. > > -- > Anousak (Anthony) Souphavanh > "Small can make a big impact" Hi, please see the "Teams cleanup" thread at http://mail.gnome.org/archives/gnome-i18n/2008-June/msg00065.html and the http://live.gnome.org/TranslationProject/TeamBrainstorm page. Christian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
How can I apply for an SVN account?
Hello everyone, I am a translator in GNOME's Pashto team. I have translated several packages and others have commited them for me. I want to know that how can I apply for a SVN account so that I am able to commit my files myself? Our coordinator Muhammad Khalid also doesn't have any SVN account. Zabeeh ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Missing language teams from Mango
On Tue, Jul 08, 2008 at 11:12:57AM +0530, Runa Bhattacharjee wrote: > Hi, > > Christian Rose wrote: >> On 7/4/08, Ankit Patel <[EMAIL PROTECTED]> wrote: >> >>> Runa Bhattacharjee wrote: >>> Ankit Patel wrote: >>> >>> >>> > [snip] >> >> I added http://bugzilla.gnome.org/show_bug.cgi?id=541665 as a request >> for solving this catch-22 in Mango. Needs some Mango love; I hope that >> Olav will have time to look at it... > Thanks Christian for filing the bug. The conversation in there however, > still does not clarify what are the steps a team has to take to ensure that > they eventually get commit rights. There is no mention of documentation (or > any impending ones) about the LDAP account process, and whether existing Mango doesn't do that yet. So without being able to do stuff, it is pointless to have documentation. > teams listed in Mango would be reviewed to ensure that they conform to the > requirements. Often, teams go through changes in leadership and may have to What requirements? > go through the entire process, irrespective of the maturity/trust of the > existing account holders from the language team. How would such a situation > be handled? Mango doesn't handle that at the moment. > The solution plan as described in: > > http://bugzilla.gnome.org/show_bug.cgi?id=541505 > > does not have any time line about the change in process and does not talk > about how the *existing* languages would be re-instated into Mango > (assuming, the current mandatory rule of I don't get 'reinstated'. Nobody's account has been revoked. > "team-gets-listed-if-svn-account-exists-for-coordinators" is still in Timeline? I don't get paid to work on GNOME. So I can't give a timeline. Especially as I still have to learn Django, LDAP schema stuff, etc. If more people help, it will go faster. Of course, ideally I'd like it to be finished in a few months. But that is not a promise plus it might be fixed faster (no idea). > place). Some of these language teams have been around for nearly 5-6 years, > highly active, have a larger group of volunteers and have also gone through > changes in coordinatorship. Most of the individual language team bugs have > been closed with an outright NOTABUG resolution, without any clarification > of what we are doing wrong and/or what is to be done next. I think I explained everything. The Mango component is for bugs in Mango. Not about getting people an account. If you want to help, ask me what is needed and submit patches. Discussion won't speed anything up. If someone is at GUADEC, just talk to me. That'll be much easier and faster. In short: Mango is a tool to make the [EMAIL PROTECTED] queue handling automated. If Mango doesn't do something, there always is the email address (which currently is even handled every weekend or so). Currently people will be pretty much lost if they're forgot their Mango password etc, I have ideas about solving that. But don't have time, I work on more stuff on GNOME than Mango, etc. -- Regards, Olav ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New team for [Persian] ([fa]
On Mon, 2008-07-07 at 22:29 +0430, mo mo wrote: > Hi > > Please read the whole message. > > My name is: Mohammad Moulai > > My Bugzilla account is: [EMAIL PROTECTED] > > My language is: Persian ( پارسی ). The ISO 639 code of Persian > language is: fa > > I wanna start a new team to translate gnome in persian > > I have send this message before and I got this: > > > Please read the history of this mailing list. > > It is very difficult to replace translation coordinator, if > you don't have > history of translation work. Call it bad karma or lack of > reputation. > > If you want to improve Persian translations, start translating > things and > file bug reports with your translations or send translation to > translation > coordinator. You might not like current coordinator, but by > attacking him > you won't reach your goals. > > Translate things, build up reputation. Complain if you have > something > translated and it is not added to Gnome software repository in > reasonable > time frame. > > > If we create a petition on http://www.petitiononline.com would that be > helpful? To show every one that we are not joking. > We are not looking for reputation. > We just want to improve translations of our language ( Persian ) in > next Gnome releases. > That's all As you can see in the history, there was a long discussion about this problem. I am optimistic about the progress and think there is no need for new fight. You can start translating and post them to bugzilla and wait for submission. Depending on the result (of course after a reasonable time) we can take new decisions. > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
