Re: New teams for Gong (kdm), Hyam (jab), Jju (kaj), Tyap (tya)

[Uchenna <nnemanwu yahoo com>]

Christian,

No errors on your part.

Ngwai (Thanks),

Uchenna

--- Christian Rose <menthos gnome org> wrote:

> ons 2005-06-22 klockan 11:02 -0700 skrev nne mmanwu:
> > Hello,
> > 
> > I would like to announce the following new teams:
> > 
> > Gong (kdm)
> > Hyam (jab)
> > Jju (kaj)
> > Tyap (kcg)
> 
> I assume these are the ISO 639-3 codes
> (http://www.sil.org/iso639-3/)
> you mentioned. ISO 639-3 appears to still be a draft
> international
> standard though... and changing to use other
> language codes later when
> we have already incorporated translations into CVS
> would be painful.
> 
> However, using these codes is probably the safest
> option right now, and
> they seem at least semi-reliable to use for
> identifying the languages.
> So you should probably use those codes if you want
> to contribute
> translations.
> 
> ISO 639-3 appears to use the following names for
> these languages:
> 
> kdm	Kagoma
>
http://www.sil.org/iso639-3/documentation.asp?code=kdm
> jab	Hyam
>
http://www.sil.org/iso639-3/documentation.asp?code=jab
> kaj	Jju
>
http://www.sil.org/iso639-3/documentation.asp?code=kaj
> kcg	Tyap
>
http://www.sil.org/iso639-3/documentation.asp?code=kcg
> 
> I'm going to use those language names in the
> translation status pages
> (i.e. I will use "Kagoma", not "Gong"). If you're
> not happy with that,
> please try to convince the registration authority to
> change the name,
> and then we can change it in GNOME as well after
> that has happened.
> 
> 
> Anyway, support for Kagoma [kdm], Hyam [jab], Jju
> [kaj], and Tyap [kcg]
> is most welcome in GNOME. I've added your name and
> e-mail address to the
> teams page at
> http://developer.gnome.org/projects/gtp/teams.html
> now.
> Please verify that this listing is correct.
> 
> I've also sent a mail in private to you with a
> request for Bugzilla
> details. Bugzilla is our bug tracker that we use for
> tracking bug
> reports in software, and, in this case also
> translations. Please reply
> to that mail as soon as possible. 
> 
> Other than that, please ask around on this mailing
> list or at the IRC
> channel #i18n on irc.gnome.org if you need help
> getting started. An
> introduction to the translation process can be found
> at
> http://developer.gnome.org/projects/gtp/l10n-guide/.
> 
> 
> I'd recommend starting with translating GNOME 2.12.
> You can find a list of included software in GNOME
> 2.12 at the
> translation status pages on
> http://l10n-status.gnome.org/gnome-2.12/
> under the "desktop" and "developer-libs" sections.
> Those are the things
> to translate for full support of the official GNOME
> release. Note that
> GNOME 2.12 is not final yet; modules and messages
> may still be added
> and/or changed. You can see the GNOME 2.12
> development schedule at
>
http://live.gnome.org/ReleasePlanning/TwoPointEleven.
> 
> You can get the potfiles to translate for GNOME
> 2.12, as an example,
> from the
>
http://l10n-status.gnome.org/gnome-2.12/ku/developer-libs/
> and
> http://l10n-status.gnome.org/gnome-2.12/ku/desktop/
> pages.
> 
> You'll get your own translation status pages as soon
> as the first
> kdm.po, jab.po, kaj.po, and kcg.po is committed to
> the GNOME cvs
> repository, respectively. From that point on, you
> can use those
> translation status pages alone. The translation
> status pages will then
> be availiable at the following addresses:
> 
>
http://l10n-status.gnome.org/gnome-2.12/kdm/developer-libs/
> http://l10n-status.gnome.org/gnome-2.12/kdm/desktop/
> 
>
http://l10n-status.gnome.org/gnome-2.12/jab/developer-libs/
> http://l10n-status.gnome.org/gnome-2.12/jab/desktop/
> 
>
http://l10n-status.gnome.org/gnome-2.12/kaj/developer-libs/
> http://l10n-status.gnome.org/gnome-2.12/kaj/desktop/
> 
>
http://l10n-status.gnome.org/gnome-2.12/kcg/developer-libs/
> http://l10n-status.gnome.org/gnome-2.12/kcg/desktop/
> 
> Once you have translated some of the pot files
> referenced above, you can
> send the resulting po files to me (or someone else
> with cvs access
> willing to commit the files) and we'll try to put
> them into cvs for you.
> Just make sure that the po files pass a test with
> "msgfmt -cvv
> filename.po" without errors or warnings, that
> they're encoded in UTF-8,
> and that you compress them using gzip before
> attaching them to the mail.
> Or you can put the files on a web page somewhere,
> and we can fetch them
> from there.
> 
> Once you've contributed a few translations this way,
> you can apply for a
> cvs account of your own at
> http://developer.gnome.org/doc/policies/accounts/,
> so that you can put
> translations directly into cvs later on.
> 
> Don't hesitate to ask if you have any questions!
> 
> Thanks, and welcome,
> 
> Christian
> 
> 



		
____________________________________________________ 
Yahoo! Sports 
Rekindle the Rivalries. Sign up for Fantasy Football 
http://football.fantasysports.yahoo.com