Re: [Gaim-i18n] help, i was translating old file

[Luke S. <lsc...@us...>]

On Sat, Sep 10, 2005 at 12:12:04AM +0600, Jamil Ahmed wrote:
> Hello Luke,
> 
> I am from Dhaka, Bangladesh. We [http://www.ankurbangla.org/] is doing 
> l10n for Bengali/Bangla.
> We want to l10n Gaim for Bangla language.
> 
> Should we start with, http://gaim.sourceforge.net/i18n/gaim.pot
> or
> Download Gaim thru CVS and generate PO file?
> 
> And where should we submit our translation?
> 
> Thanks,
> `Jamil

At this point in time, using the gaim.pot on the website is (now)
equivalent to checking out cvs.  It really comes down to a choice of
how you prefer to manage your translation after it gets committed.
Some translators prefer one, others prefer the other.

when you go to submit it, there is a translations tracker at
http://sourceforge.net/tracker/?atid=713922&group_id=235&func=browse

I need the po itself (can be compressed), the two letter language
code (xx.po) or the two letter language code with two letter country
code (xx_YY.po) to use, as well as the name (can be a group name) and
email address (can be a personal or list email address) for the
help->about dialog.

luke

> 
> 
> Luke Schierer wrote:
> 
> >gaim.sf.net/i18n has been changed to track cvs head.  this should
> >simplify matters when we do string freeze.
> >
> >luke
> >
> >On Mon, Aug 22, 2005 at 11:08:57AM -0400, Luke Schierer wrote:
> > 
> >
> >>On Mon, Aug 22, 2005 at 05:07:56PM +0200, Richard Golier wrote:
> >>   
> >>
> >>>On Monday 22 August 2005 16:10, Funda Wang wrote:
> >>>     
> >>>
> >>>>Forget 1.50 away. There won't be any 1.x versions according to the
> >>>>developers.
> >>>>       
> >>>>
> >>>Ok, so is translating of this version useless? Any info about when the 
> >>>new version will come out?
> >>>-- 
> >>>
> >>>--pholie
> >>>     
> >>>
> >>I'd forgotten when I told you to look at the i18n page that Sean had
> >>announced an end to the oldstatus series.  We don't currently have an
> >>eta on when exactly 2.0.0 will come out yet though, it depends on how
> >>fast we can finish its status ui and work out the bugs and
> >>inconsistencies we have introduced.  We have (finally) reached the
> >>point where 2.0.0 should not get any *more* broken than it currently
> >>is, but it now remains to pull all the loose ends together.
> >>
> >>luke
> >>
> >>   
> >>