Re: Camel and i18n




Ok thanks for the clarification, i slightly misread the original mail, i thought one or the other was required but neither would be complete.

JPR, we should do this soon i guess.

Camel also needs to be changed to use the lib stuff, if it doesn't pick that up implicitly by being in eds.

Michael

On Mon, 2004-12-20 at 01:37 +0100, Danilo Šegan wrote:
Hi Michael,

Today at 1:08, Michael Zucchi wrote:

> Hmm, so would the first script update all the translations and new
> strings?  Or does it do something less than that?

The following would *update* all existing translations in e-d-s with
Camel translations from Evolution:

>>   cd ~/cvs/e-d-s/po
>>   intltool-update -p
>>   for i in *.po; do
>>     msgmerge -C ~/cvs/evolution/po/$i evolution-data-server.pot $i
>>   done

The following would copy all the translations from evolution which
didn't exist in e-d-s at all, and you could simply intltool-update
them to get updated translations (and you should probably remove
obsoleted entries, but that's not too big a deal):

>>   cd ~/cvs/evolution/po
>>   for i in *.po; do
>>     if [ ! -f ~/cvs/e-d-s/po/$i ]; then 
>>        cp $i ~/cvs/e-d-s/po/
>>     fi
>>   done

So, you need to do *both* to completely migrate translations from evo
to e-d-s.

Cheers,
Danilo
--
Michael Zucchi <notzed ximian com>
"Ride, Work, Sleep. Beer."
Novell's Evolution and Free Software Developer

Attachment: zed-48.small.jpg
Description: Binary data



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]