Mercurial > pidgin.yaz
view po/README @ 22891:43233dc1d40b
applied changes from 4c5110037671f84e3e775214c32692b5b23c11e1
through ae37fe6b64c30704715a369df88bd76674a39b1a
applied changes from 4c5110037671f84e3e775214c32692b5b23c11e1
through ae37fe6b64c30704715a369df88bd76674a39b1a
applied changes from b28057d6ade7c221b0616c3b02e86659e2d8b10b
through 52c0efb045580dac7b6f5e40c91002e917e0cae3
Plucked changes for the chat-join-failed signal and associated server.c
function from im.pidgin.pidgin, as these necessitate a minor version bump.
author | Evan Schoenberg <evan.s@dreskin.net> |
---|---|
date | Tue, 29 Apr 2008 03:59:28 +0000 |
parents | 5538762c5ca7 |
children | da5c044a2437 |
line wrap: on
line source
Translation HowTo We are currently very informal and very hands-off when it comes to translating Gaim. What follows is a collection of notes for those who wish to assist. * We try to accept tanslations for a given language only from a single person, the person we are most familiar with getting translations from. If you feel a translation is wrong, produces strings that are too long, or is badly out of date, contact the existing translator first. Work with him or her if possible. If this is not possible, mention this to us as you submit your patch or new translation. * Translations to new languages are always welcome. 1. Get the po template (.pot) file from here. Alternately run intltool-update --pot in the gaim/po/ directory. 2. Find the two letter language code for your language. If translating to a regional dialect, append the two letter region or country code. Rename the file to match this. For example, Protuguese is pt.po, and Brazilian Portuguese is pt_BR.po. 3. Subscribe to gaim-i18n@lists.sf.net via the SF subscribe page 4. Open the translation file you downloaded in a text editor 5. translate the strings o Translated .po files may be submitted in whatever native encoding is most convenient (and hopefully canonical). Please ensure that the Content-type: line reflects the proper character set. o Please check your translations carefully. Make sure you have the same number of newlines and %s or other formatting codes in the translation as you have in the original. The po/check_po.pl script can help with this. o Before submitting updated or new translations, please run the following command to ensure the file does not contain errors: msgfmt -c --statistics xx.po o The comments at the top of each .po file should appear as follows: # Gaim Xxxxx translation # Copyright (C) 2002, Another Name <email@something.com> # Copyright (C) 2003, Your Name <email@whatever.com> # # This file is distributed under the same license as the Gaim package. # 6. Post partial or completed files to the Translations Tracker 7. Along with your first submission, note what name(s) and email address(es) should be put in help->about. * String freezes are announced on gaim-i18n Thank you for flying Valu-Jet.