Re: Trunk and Branch!

On woensdag 27 juni 2012 05:25:15 Khoem Sokhem wrote:
> Hello All,
>
> I just want to make sure about the committing translation to server.
>  From now on, Should commit my Khmer translations to only Branch or to
> both Trunk and Branch? because I do not want to work on the same messages.
>
> Thanks,
> Sokhem

When you use lokalize, you should have a lokalize project file with at least
the following entries:
BranchDir=<points to the <language code> folder of branch or trunk>
PoBaseDir=<points to the <language code> folder of trunk or branch>
PotBaseDir=<points to the templates folder of trunk or branch>

The project file for trunk has the branch folder in BranchDir and the other
two the trunk folder and vice versa.
Make sure the ProjectID= in these project files have the same name. In that
case the Translation Memory will have all the translations in branch and trunk
in one database.

When you have this and you work in either project and branch and trunk have
the same named files, and in those files the English text is the same,
including the context, the translation will be entered in both po files in
branch and trunk. So you don't need to worry about doing double work.
Obviously you need to commit your work both in branch and trunk.

Besides, TM is your friend here as well. In principle all translations are
stored in TM or you can force them in TM (F7 -> Rescan project files).
After opening a po file, press <Ctrl>+<Alt>+B and TM will be searched for
similar messages and the translations will be entered. Sometimes marked fuzzy,
when the English text has more than one translation in your language. You have
to press that combination immediately after opening, otherwise nothing will
happen. When done, you get a text balloon to show that, I have to press >Page
Down> otherwise <Ctrl>+<Shift>+<Page Down> or <Ctrl>+<Page Down>, to go to the
next not ready message or fuzzy message, will not work.

This is also an easy way to 'copy' translations between trunk and branch.

--
fr.gr.

Freek de Kruijf