Mailinglist Archive: yast-devel (211 mails)

< Previous Next >
Re: [yast-devel] new translation server and YaST
Dne 13.10.2015 v 16:53 Karl Eichwalder napsal(a):
Lukas Ocilka <lukas.ocilka@xxxxxxxx> writes:

Someone still needs to run `create pot file for $this repository`, but
this can be automated quite "easily", for instance, in Jenkins.

I already have a script that can generate all pot files for all Yast
repositories at once, also considering that not all Yast repositories
need to have the "latest" branch, especially SLE 11 might have, e.g.
only `SP2` branch, and nothing "younger".

I'm fine with changing, but I'm not fine with changing procedures that
affects products already done (only if behlert would approve it).

This means that SLE 11 SPx and SLE 12 (SP0) translation updates -- if
needed -- should be done as usual (submitting pot files to the SVN,
translating, and then packaging yast2-trans). The same applies for SLE
12 SP1.

There is no plan to migrate in SLE11 and SLE12SP < 2.

It is unsure even in case of future SLE12 SP2.

openSUSE Leap 42 will probably inherit translations from SLE12 (GA or SP1), probably with exception of Release Notes, which are already migrated, and its Leap version never appeared in LCN SVN.

It depends on result of future translation merge. Whichever it will be, it will surely bring some changes in translations, possibly including terminology change. I am not sure, whether we will want it for SLE12 SP2. Managers will decide in future, depending on feedback of the new translations and processes.

But we would like to get it to SLE13.

--
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o. e-mail: sbrabec@xxxxxxxx
Lihovarsk√° 1060/12 tel: +49 911 7405384547
190 00 Praha 9 fax: +420 284 084 001
Czech Republic http://www.suse.cz/
PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >