head	1.7;
access;
symbols
	v2_0_0beta3:1.7
	v2_0_0beta2:1.4
	v2_0_0beta1:1.4
	v1_5_0:1.4
	v1_4_0:1.4
	gaim-doodle:1.4.0.6
	v1_3_1:1.4
	v1_3_0:1.4
	v1_2_1:1.4
	v1_2_0:1.4
	v1_1_4:1.4
	v1_1_3:1.4
	v1_1_2:1.4
	v1_1_1:1.4
	v1_1_0:1.4
	v1_0_3:1.4
	v1_0_2:1.4
	v1_0_1:1.4
	v1_0_0:1.4
	oldstatus:1.4.0.4
	v0_82:1.4
	v0_81:1.4
	v0_80:1.4
	v0_79:1.4
	v0_78:1.4
	v0_77:1.4
	v0_76:1.4
	v0_75:1.4
	v0_74:1.4
	v0_74-branch:1.4.0.2
	v0_73:1.4
	v0_72:1.4
	v0_71:1.4
	v0_70:1.3
	v0_69:1.3
	v0_68:1.3
	v0_67:1.3
	v0_65:1.2
	v0_64:1.2
	v0_63:1.1
	v0_62:1.1;
locks; strict;
comment	@# @;


1.7
date	2006.02.28.20.13.00;	author lschiere;	state Exp;
branches;
next	1.6;

1.6
date	2006.02.16.20.50.10;	author rlaager;	state Exp;
branches;
next	1.5;

1.5
date	2006.02.16.20.42.05;	author rlaager;	state Exp;
branches;
next	1.4;

1.4
date	2003.10.04.15.48.40;	author eblanton;	state Exp;
branches;
next	1.3;

1.3
date	2003.08.10.17.46.22;	author thekingant;	state Exp;
branches;
next	1.2;

1.2
date	2003.05.27.03.38.51;	author thekingant;	state Exp;
branches;
next	1.1;

1.1
date	2003.04.19.23.19.49;	author chipx86;	state Exp;
branches;
next	;


desc
@@


1.7
log
@reverse merge
@
text
@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.
@


1.6
log
@Rework this file a bit to please Bleeter.
@
text
@d1 1
a1 1
Translation README
d3 1
a3 2
To supply a new translation, you first need a copy of gaim.pot.
This can be built by typing:
d5 22
a26 1
intltool-update --pot
a27 1
from the gaim/po/ directory.
a28 30
To update an exsting translation, type:

intltool-update -m LANG

where LANG is the language code to update, such as fr or ja.  This will build
a new gaim.pot and update the translation with the changes.  You may then
begin editing the updated file.

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.

New or updated translations should be sent to the translation tracker:
https://sourceforge.net/tracker/?group_id=235&atid=713922

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.

Before submitting updated or new translations, please run the following 
command to ensure the file does not contain errors:
> msgfmt -c --statistics xx.po

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.
#
@


1.5
log
@(14:40:44) Peter Lawler (Bleeter): LSchiere2: there's no po/update.pl (as per the po/README)?
@
text
@a2 12
Updated: 04-October-2003
------------------

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.



Updated: 19-April-2003
------------------

d14 2
a15 2
where LANG is the language code to update, such as fr or ja. This will build
a new gaim.pot and update the translation with the changes. You may then
d18 6
a23 2
New or updated translations should be sent to the gaim-devel listserv
(see http://lists.sourceforge.net/lists/listinfo/gaim-devel)
d25 1
a25 1
Please check your translations carefully. Make sure you have the same
d27 1
a27 6
you have in the original.



Updated: 05-August-2003
------------------
@


1.4
log
@Clarify the charset status of po files
@
text
@d18 1
a18 1
./update.pl --pot
d24 1
a24 1
./update.pl LANG
@


1.3
log
@I updated po/README, and the headers for all the .po files...
@
text
@d3 7
a40 4

All translations should be in UTF-8.  You can use the following command to 
convert from one encoding to another, if needed:
> iconv -f iso-8859-1 -t utf-8 xx.po > xx.po.new
@


1.2
log
@This is:
-AIM over OSCAR use Christian's new, kick ass
  gaim_notify_email stuff for new mail notification.  This
  should be good, but it's kind of a pain to test.  Let me
  know if you have any problems

-Minor fix to the translation README

-2 minor changes to the doxygen of 2 major header files
  (this means you'll have to recompile a lot of files :-) )

-If your global proxy setting is "No Proxy" and your global
  proxy host is empty, but $http_proxy is set to something,
  gaim used to switch your global proxy setting to "HTTP."  It
  no longer does this.  This makes more sense to me.  If you
  disagree, please let me know--this is open to debate, and
  what not.  Also, the use of environmental proxy settings
  will be changed a bit in the next day or two
@
text
@d3 2
d29 23
@


1.1
log
@This is the wave of the future! Or something like that.

Imma go eat cake later! Yay happy Easter!! Oh crap, I'm probably
going to get in a lot of trouble now. Holiday references, y'know. They're
illegal'n stuff. Or something like that. Personally, I like Christmas, but
it's just too near my birthday, you know? The presents should be spread
out. Birthdays are cool, sometimes. Halloween can be fun. Free candy!
Society says I can't trick-or-treat anymore though, so I take my little
sister around and get candy. Mmm.. Like stealing candy from a baby, except
we share it. So it's not stealing, really. Voluntary. On her part, not
mine, because it'd be stealing if it was my volunteering to take her candy.
@
text
@d15 1
a15 1
./update.pl LANG.po
@

