view po/README @ 14999:82d1a2fc6d25

[gaim-migrate @ 17778] SF Patch #1598994 from lexande Fixes SF Bug #1581999 Original Description: "The gaim 2.0.0beta5 log reader plugin uses the "Date" XML field in MSN logs, the format of which varies between locales, leading to logs being displayed on incorrect/future dates in locales that do not use the MM/DD/YYYY format. This patch fixes the plugin to use the "DateTime" field which has YYYY-MM-DD date in all locales." I totally Warmenhovened this patch. My approach: "I'm using the Date, Time, and DateTime fields. If I can determine that the log matches the current timezone, it'll display 100% properly in the log viewer. If it has a reasonable offset, it'll display as the original time, sort in the right place, but not have a timezone abbreviation. If the offset is bogus or I can't parse the Date or Time field, it'll display in UTC, but still sort properly. I think this is as ideal as is possible, given the data we have to work with." You don't have to understand this. ;) committer: Tailor Script <tailor@pidgin.im>
author Richard Laager <rlaager@wiktel.com>
date Sun, 19 Nov 2006 06:54:38 +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.