Re: [opensuse-translation] Problem with update-desktop-file.fr.po
MjAwNy8xMi81LCBBZHJpYW4gU2NocsO2dGVyIDxhZHJpYW5Ac3VzZS5kZT46Cj4gT24gV2VkbmVzZGF5IDA1IERlY2VtYmVyIDIwMDcgMTQ6MjM6NTQgd3JvdGUgTGFkaXNsYXYgTWljaG5vdmnEjToKPiA+IDIwMDcvMTIvNSwgS2FybCBFaWNod2FsZGVyIDxrZUBzdXNlLmRlPjoKPiA+ID4gPiBZb3UgY2FuIGluc3RhbGwgUG9lZGl0IDEuMy44cHJlMSBmcm9tIG15IGhvbWUgcHJvamVjdCBpbiBCdWlsZCBTZXJ2aWNlLgo+ID4gPiA+ICBodHRwOi8vZG93bmxvYWQub3BlbnN1c2Uub3JnL3JlcG9zaXRvcmllcy9ob21lOi9sbWljaC9vcGVuU1VTRV8xMC4zLwo+ID4gPiA+Cj4gPiA+ID4gQlRXLiBJcyB0aGVyZSBhIG1vcmUgYXBwcm9wcmlhdGUgcGxhY2UgaW4gQnVpbGQgU2VydmljZSBmb3Igc3VjaAo+ID4gPiA+IHBhY2thZ2U/Cj4gPiA+Cj4gPiA+IEluIHRoZSBwYXN0LCB0aGVyZSB3YXMgYSAidHJhbnNsYXRpb24iIEJTIHByb2plY3QuICBTb21lIHdlZWtzIGFnbywgSQo+ID4gPiBhZ3JlZWQgdG8gZGVsZXRlIGl0IGJlY2F1c2Ugb25seSBhIGxvbmxleSBnZXR0ZXh0IHBhY2thZ2UgKGZvciAxMC4yKSB3YXMKPiA+ID4gaGFuZ2luZyBhcm91bmQuCj4gPiA+Cj4gPiA+IEl0IGlzIHByb2JhYmx5IHRpbWUgdG8gY3JlYXRlIGl0IGFnYWluIDopCj4gPgo+ID4gQ2FuIHlvdSBjcmVhdGUgaXQsIG9yIHNob3VsZCB3ZSBwbGVhc2UgQWRyaWFuPwo+Cj4gSSBzdXBwb3NlLCBJIGhhdmUgdG8gZG8gaXQgZHVlIHRvIHRoZSBwZXJtaXNzaW9ucy4KPgo+IElzIGRldmVsOnRyYW5zYWxhdGlvbiBva2F5IHdpdGggeW91ID8KCkZvciBtZSBpcyBkZXZlbDp0cmFuc2xhdGlvbiAoKiB5b3Ugd3JvdGUgaXQgd2l0aCBhIHR5cG8gOy0pIE8uSy4KSSB3b3VsZCB3YWl0IGZvciBLYXJsJ3Mgb3Bpbmlvbi4KVGhhbmsgeW91LgogUmVnYXJkcyBMYWRpc2xhdi4K---------------------------------------------------------------------To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.orgFor additional commands, e-mail: opensuse-translation+help@opensuse.org
"Ladislav Michnovič" <ladislav.michnovic@gmail.com> writes:
Is devel:transalation okay with you ?
For me is devel:translation (* you wrote it with a typo ;-) O.K. I would wait for Karl's opinion.
Yes, devel:translation is fine. If we actually want to distribute translations or translation update via BS, we should register a project on its own. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2007-12-05 at 15:27 +0100, Karl Eichwalder wrote:
Yes, devel:translation is fine. If we actually want to distribute translations or translation update via BS, we should register a project on its own.
Well, we (the Spanish group) are thinking on how could we make an rpm of the translations we made, so that we can test them. Creating the rpm locally for our own use would be fine, but the possibility of distributing it is also interesting. But we do not know how to create the rpm. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHVsmwtTMYHG2NR9URApWaAJ9hgRNM0Zk+vf40J2uXLTCZ2WRoTACgkWdz /gs0Bkn0PFilxPVw5Mo8TYs= =fzFV -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
2007/12/5, Carlos E. R. <robin.listas@telefonica.net>:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Wednesday 2007-12-05 at 15:27 +0100, Karl Eichwalder wrote:
Yes, devel:translation is fine. If we actually want to distribute translations or translation update via BS, we should register a project on its own.
Well, we (the Spanish group) are thinking on how could we make an rpm of the translations we made, so that we can test them.
Creating the rpm locally for our own use would be fine, but the possibility of distributing it is also interesting.
But we do not know how to create the rpm.
I think , I can write an automated update from svn for YaST translation (all languages) to push it every week into Build Service. Just add me to project in BS. We should decide a name for it first, should'nt we? For LCN it would be harder, because the translations are distributed in various packages. Regards Ladislav. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2007-12-05 at 17:04 +0100, Ladislav Michnovič wrote:
Well, we (the Spanish group) are thinking on how could we make an rpm of the translations we made, so that we can test them.
Creating the rpm locally for our own use would be fine, but the possibility of distributing it is also interesting.
But we do not know how to create the rpm.
I think , I can write an automated update from svn for YaST translation (all languages) to push it every week into Build Service. Just add me to project in BS. We should decide a name for it first, should'nt we?
That would be very nice :-)
For LCN it would be harder, because the translations are distributed in various packages.
Ah... Pity. Anyway, how would a translator go about building/installing the translation to his local machine, for testing? Would that be simple/possible? I haven't studied it much yet, that's true. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHVwevtTMYHG2NR9URAsySAKCSmAcBVDmvuOaDVLFsNAltuzvyoACfeZkv dCSQ4P1ddUMvJh3MjEg+NtE= =eKQB -----END PGP SIGNATURE-----
"Ladislav Michnovič" <ladislav.michnovic@gmail.com> writes:
For LCN it would be harder, because the translations are distributed in various packages.
This could be done using the overload strategy with the shadow directory for the .mo files. We did those things for SLED10. The package name is translation-update. The tough part is to get rid of the package if you update from 10.3 to 11.0. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2007-12-06 at 10:46 +0100, Karl Eichwalder wrote:
For LCN it would be harder, because the translations are distributed in various packages.
This could be done using the overload strategy with the shadow directory for the .mo files. We did those things for SLED10. The package name is translation-update.
The tough part is to get rid of the package if you update from 10.3 to 11.0.
Ouch. It has to be an optional package, with a warning to the user; and then try to remind whoever does that in Yast development to remove the package on upgrade... not a clean solution, it can backfire. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHV+u8tTMYHG2NR9URAkZ+AJ9W5bYUaeN0FVmLJ3Vt2nNUIdCDSgCfas33 o1YRyqWYs5HTahELLaK0Vp0= =om8B -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
2007/12/6, Carlos E. R. <robin.listas@telefonica.net>:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Thursday 2007-12-06 at 10:46 +0100, Karl Eichwalder wrote:
For LCN it would be harder, because the translations are distributed in various packages.
This could be done using the overload strategy with the shadow directory for the .mo files. We did those things for SLED10. The package name is translation-update.
The tough part is to get rid of the package if you update from 10.3 to 11.0.
Ouch.
It has to be an optional package, with a warning to the user; and then try to remind whoever does that in Yast development to remove the package on upgrade... not a clean solution, it can backfire.
I have an idea how to solve it. Create this package within Suse and do a proper numbering. For example 10.3.x.y, which shows, that it is connected to openSUSE Linux 10.3. Release translation updates as often as needed, but when next SuSE release comes, renumber it to 11.0.x.y and make this package empty. This package will come within installation media and it would be without any files, only README for some information. If somebody will do an update, YaST, zypper, rpm can handle this and will erase all files which was installed on the system by that package in previous version. One thing is needed, to make some dependency on some basic package or Pattern which will ensure, that this package will be always installed. Ask YaST2 maintainers for details. Regards Ladislav. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
participants (3)
-
Carlos E. R. -
Karl Eichwalder -
Ladislav Michnovič