gnome-menu-editor release imminent
I'd like to do a gnome-menu-editor release this weekend. You may want to update/add your translations now. Thanks for your efforts! :) -- Christian Neumair [EMAIL PROTECTED] ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: System Tools Backends have been moved to FreeDesktop
Hi Carlos, Yesterday at 17:56, Carlos Garnacho wrote: NOTE FOR TRANSLATORS: As soon as the backends have new translatable strings, I'll contact the Translation Project [2] and mail gnome-i18n for anyone interested This is related to any developers wishing to move their modules to FreeDesktop. Must project CVS be switched over to FDo in order for it to be considered FreeDesktop project (fwiw, you say that CVSROOT is cvs.gnome.org:..., which would imply that you haven't moved CVS)? If not, I'd strongly suggest to keep using Gnome CVS, if for nothing else, for GTP contributions. And I'd also suggest to *NOT* use both Translation Project and GTP at the same time, because of possible collisions (and my preference lies with GTP: it's better for both translators and maintainers). Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[Bug 173165] New: [ko] epiphany: translation inconsistency
Please DO NOT reply to this by email. All additional comments should be made in the comments box of this bug report. http://bugzilla.gnome.org/show_bug.cgi?id=173165 l10n | other | Ver: GNOME HEAD Summary: [ko] epiphany: translation inconsistency Product: l10n Version: GNOME HEAD Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: Normal Component: other AssignedTo: gnome-i18n@gnome.org ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] (There appears to be no component for Korean [ko] in l10n, so filing in other component.) The toolbar style names in Epiphany's toolbar editor are translated wrong. They should be the same as the same strings in GNOME Control Centre --- and the translator comment says as much! --- but they're not. (Note that the string has |-context in Epiphany but not in GNOME Control Centre). The following strings are affected: String: toolbar style|Text below icons Control Centre: 아이콘 아래 글자 Epiphany : 텍스트 밑에 아이콘 String: toolbar style|Text beside icons Control Centre: 아이콘 옆에 글자 Epiphany : 텍스트 옆에 아이콘 String: toolbar style|Text only Control Centre: 글자만 Epiphany : 텍스트만 --- You are receiving this mail because: --- You are the assignee for the bug. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Is the Korean team dead?
mn 2003-05-05 klockan 01:31 +0900 skrev Changwoo Ryu: 2003-05-02 06:54, Christian Rose() : Hi! Do you know if the Korean GNOME translation team is dead? I've tried several times to contact the current Korean coordinator, Noh Woo Kyong [EMAIL PROTECTED], but so far without success. I also sent the attached mail to the gnome-i18n@gnome.org mailing list with request for a new Korean coordinator almost a month ago but so far without a single response regarding anything Korean. Do you know anything about the Korean team situation? In that case, please clarify it on the gnome-i18n@gnome.org list. Otherwise I'll delete the Korean translation team listing soon. I have not seen him for a while. AFAIK Korean translators have never worked as a 'team'. He volunteered the coordinator, but did nothing. Though the Korean translators did their jobs without any team effort. anyway I'll try to contact Woo Kyong anyway and to find a new coordinator if possible. It seems I never got a reply on this, and this was left unresolved. So the Korean team has lacked a functional coordinator for almost two years now! If the Korean coordinatorship issue cannot be resolved because of lack of coordinator volunteers, then I will simply demand that no Korean translations are committed to CVS any longer, since we in the GTP cannot have people committing ko.po files at random without knowing who is the Korean coordinator who can authorize those things. So I hope that any Korean translators reading this will consider if they want to step up as Korean coordinators. If noone wants to be the Korean coordinator, then we simply shouldn't allow ko.po files to be committed to CVS any longer. So what does it take to be the Korean coordinator? Basically, a coordinator acts as a contact person to both the GTP and any new Korean translator volunteers, and hopefully also does some coordination so that duplicate efforts are avoided. That's basically all there is to it. Because of the lack of a Korean coordinator, we haven't got a Korean component in Bugzilla, so the recent bug report about Korean translations is basically orphaned and was sent here. Is there really *noone* that wants to be the Korean coordinator? Christian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
gthumb branched for 2.6 series
Hi, the gthumb 2.6.x series is in the gthumb-2-6 branch now. Regards, Paolo. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Is the Korean team dead?
sn 2005-04-10 klockan 07:52 +0900 skrev Changwoo Ryu: 2005-04-09 (), 17:36 +0200, Christian Rose : mn 2003-05-05 klockan 01:31 +0900 skrev Changwoo Ryu: 2003-05-02 06:54, Christian Rose() : Hi! Do you know if the Korean GNOME translation team is dead? I've tried several times to contact the current Korean coordinator, Noh Woo Kyong [EMAIL PROTECTED], but so far without success. I also sent the attached mail to the gnome-i18n@gnome.org mailing list with request for a new Korean coordinator almost a month ago but so far without a single response regarding anything Korean. Do you know anything about the Korean team situation? In that case, please clarify it on the gnome-i18n@gnome.org list. Otherwise I'll delete the Korean translation team listing soon. I have not seen him for a while. AFAIK Korean translators have never worked as a 'team'. He volunteered the coordinator, but did nothing. Though the Korean translators did their jobs without any team effort. anyway I'll try to contact Woo Kyong anyway and to find a new coordinator if possible. It seems I never got a reply on this, and this was left unresolved. So the Korean team has lacked a functional coordinator for almost two years now! Well, since I'm probably only one commiting ko.po files, I hereby volunteer as the Korean coordinator. Excellent! As the previous Korean coordinator is unreachable (bouncing mail address) and hasn't been heard from for years, you're the new Korean coordinator as of now. I've added your name to the http://developer.gnome.org/projects/gtp/teams.html teams page. Please make sure the listing is correct. Please use [EMAIL PROTECTED] if any team mail address is required. We unfortunately don't have a field for translation mailing list, but we do on the other hand have a field for a team web page. Perhaps you can add a simple team web page? Such a team web page is not mandatory however, but it might be a help for new translation volunteers. A team web page can then link to the actual mailing list. If the Korean coordinatorship issue cannot be resolved because of lack of coordinator volunteers, then I will simply demand that no Korean translations are committed to CVS any longer, since we in the GTP cannot have people committing ko.po files at random without knowing who is the Korean coordinator who can authorize those things. So I hope that any Korean translators reading this will consider if they want to step up as Korean coordinators. If noone wants to be the Korean coordinator, then we simply shouldn't allow ko.po files to be committed to CVS any longer. I think we should not reject contributions by such a reason. People often disappear, some lost their interests and some people don't follow our way. But it does not make the contributions useless. Of course, rejecting contributions would only be the very last measure, unless we had not been able to resolve the Korean coordinator issue any other way. I agree that it all comes down to a thing: the actual contributions. The surrounding administrativia, where it exists, should be and only be an aid to achieve that goal. So it would seem stupid to reject contributions based on an administrative formality. However, on the other hand, translator volunteers who have been interested in translating GNOME into Korean have, for the past years, been directed to a long missing Korean coordinator and a bouncing mail address. So, in practice, translation volunteers have been directed to /dev/null. I don't think that's healthy for a project to do such a thing with volunteers, at least not in the long run. So, seen from that point of view, I think it's fairly reasonable to temporarily block Korean translation contributions should there be *no* other way to get pressure to resolve a status quo situation with a team where any new volunteers are directed to /dev/null and noone knows whom to contact. I think that long-term, the benefits of resolving such a situation would clearly outweigh any drawbacks of temporarily blocking some contributions. So what does it take to be the Korean coordinator? Basically, a coordinator acts as a contact person to both the GTP and any new Korean translator volunteers, and hopefully also does some coordination so that duplicate efforts are avoided. That's basically all there is to it. Because of the lack of a Korean coordinator, we haven't got a Korean component in Bugzilla, so the recent bug report about Korean translations is basically orphaned and was sent here. I think most Korean users won't file translation bugs to the bugzilla (the bugzilla is another language barrier). Has there really been any Korean translation related bugs in the bugzilla? Yes, very recently, and that bug report notice was copied to this list as well: http://mail.gnome.org/archives/gnome-i18n/2005-April/msg00046.html It is important to
