Mailinglist Archive: opensuse-translation (72 mails)

< Previous Next >
Re: [opensuse-translation] SVN Branching, Online Update, and a small warning (suse-i18n)
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
  • Date: Tue, 6 Nov 2007 12:37:16 +0100 (CET)
  • Message-id: <alpine.LSU.0.9999.0711061223350.7184@xxxxxxxxxxxxxxxx>
Hash: SHA1

The Tuesday 2007-11-06 at 10:56 +0100, Karl Eichwalder wrote:

"Carlos E. R." <> writes:

Our doubt is what should we do when you create the 10.3 branch so as not
to loose our work in the trunk? I mean, to carry over the translated
messages from trunk to 10.3.

Submitting to the trunk is just fine.

a) We will build 11.0 from the trunk.

b) I will create the 10.3 branch from the trunk. We will use the 10.3
for maintenance updates, if any.

Or... perhaps you mean for the phase of moving from 10.3 back to trunk,
later on? That's a month or two in the future, I hope. I wasn't thinking
of that one yet.

Just make sure all the work is submitted to the trunk ASAP. I do not
see any problems, though.

I submitted 36 files this early morning (night).
I have also made a checkout of the new 10.3 branch (partial).

Now we have the problem I was afraid of: the new lcn branch does not contain our translations.

What procedure do we follow to move the translated messages, from say:

trunk/lcn/es/po/ ==>

and the rest of the files. That's the problem, because what our group is interested in is in finishing the 10.3 translation in order to eventually get the update in the servers.

In other projects in which I cooperate, I simply copy my current translated .po file over your one, then run "make update-po" and it's done, the new messages from the .pot file appears, stale ones disappear, and changed ones are marked fuzzy.

How do we do that here? Who does it?

[Worried] :-?

- -- Cheers,
Carlos E. R.

Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Made with pgp4pine 1.76


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

< Previous Next >
List Navigation
Follow Ups