view po/README @ 13914:3ae8a3935406

[gaim-migrate @ 16414] First stab at trying to fix the MSN http connect method. It still doesn't work, and I'm not sure why, but it gets a lot farther in the signon process now. For those unfamiliar with the issue, the MSN http connect method stopped working after all the non-blocking I/O changes. The http connect method is apparently used by lots of people behind silly firewalls and stuff, and therefore we really shouldn't release Gaim 2.0.0 without it working, because people will complain. The two main problems were 1. The outgoing message queue was removed in favor of buffering all data to one large buffer. This sounds good in theory... but apparently each message sent to and from the server has a "SessionID" in the HTTP header. Every message we send should use the same SessionID as the last packet we received from the server. So basically you can't put two messages into the outgoing buffer at the same time because you don't have the correct SessionID to use for the second message. You have to wait until you get the reply from the server. 2. There were some strange buffer problems with using the wrong variable when trying to combine the header+body into one buffer before sending the message. I also fixed a small memleak or two, added some comments, and tried to clean up the code a little. committer: Tailor Script <[e-mail]>

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 [e-mail] 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 <[e-mail]>
                     # Copyright (C) 2003, Your Name <[e-mail]>
                     #
                     # 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.