Mailinglist Archive: opensuse-translation (75 mails)

< Previous Next >
Re: [opensuse-translation] Re: obsolete webyast pot files in openSUSE localization svn?
  • From: Guillaume Gardet <guillaume.gardet@xxxxxxx>
  • Date: Mon, 07 Mar 2011 11:05:00 +0100
  • Message-id: <4D74ADCC.7010201@free.fr>


Le 07/03/2011 10:08, Andrea Turrini a écrit :
2011/3/7 Karl Eichwalder<ke@xxxxxxx>:
Are you still busy with translating webyast? How much time do you need
for preparing this Update?

I'd like to submit the packages end of this week or early next week.
Karl, can you synchronize the Italian version? I tried using Carlos'
scripts but I have found some problem generating new po files from
pot.

Thanks,
Andrea

You can try this one I used. You must have the POT files in ./00-POT/ and the po files in
./$lang/po/. If not, you can download them with SVN. It merge the PO files with latest POT files
and create PO files for new POT files. You must change the lang (from "fr" to
"it" for example).

#!/bin/bash

lang=fr

POT_path=./00-pot/
PO_path=./$lang/po/

# Update all PO files with a POT file
for PO_file in `ls $PO_path/*.$lang.po`; do
echo $(basename $PO_file .$lang.po)
POT_file=$POT_path/$(basename $PO_file .$lang.po).pot
if [[ -e $POT_file ]]
then
# POT and PO files exist => update
echo "NOTE: $POT_file exist."
msgmerge --update $PO_file $POT_file
else
echo "WARNING: $POT_path/$(basename $PO_file .$lang.po).pot does not
exist!!"
fi

done

POT_file=""
PO_file=""

echo ""
echo ""

# Create PO files for new POT files
for POT_file in `ls $POT_path/*.pot`; do
echo $(basename $POT_file .pot)
PO_file=$PO_path/$(basename $POT_file .pot).$lang.po
if [[ -e $PO_file ]]
then
# POT and PO files exist => nothing to do
echo "NOTE: $PO_file exist. Nothing to do"
else
echo "NOTE: $PO_file does not exist. Creating PO file."
msginit --no-translator --locale=$lang --input=$POT_file
--output-file=$PO_file
fi

done

--
To unsubscribe, e-mail: opensuse-translation+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-translation+help@xxxxxxxxxxxx

< Previous Next >