-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-09-18 11:00, Karl Eichwalder wrote:
"Carlos E. R." <> writes:
If you do that, I will have to undo it on my files. Otherwise, I'd have to manually check every string to locate which are the strings imported from SLES.
If you merge the strings as fuzzy, that's acceptable, though.
Setting them just to would not help that much for what we (SUSE) want to achieve.
Why the hurry? According to the official timetable: +++····················· openSUSE 13.2 translation finish Milestone: Last fixes for localization found during testing incorporated. Milestone: Drop of Release Notes to Localization Thu, 30 Oct 2014 14:00:00 GMT ·····················++- So we have a month to fully translate the files. And those you are interested in (es): snapper one single string non translated zypp it is not in the yast directory, but it is 98% done. zypper 90% done. You could delay the merge from SLES till that date, and leave us time to work.
I now propose to do the following (for snapper, zypp, and zypper only):
1/ I'll not touch translated strings.
2/ I'll flag strings added from the SLE12 branch with a special comment:
#. SLE12
This way it should be easy for you to locate the imports.
I'll treat all languages the same.
You can do that 30 Oct 2014. If you do it now, the "go to next not ready string" in lokalize would not work, and you would also overwrite our previous fuzzy string if they existed. Forcing the SLES translations on us makes me feel my work is not wanted/appreciated. I may then simply take a backup from older translations and overwrite what you do... - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEUEARECAAYFAlQaznYACgkQtTMYHG2NR9Wm7wCeMx4VlSNm8QpDq/BMMufYllaH MVEAmLQHhS5iT63YZq5xVlMF/+3xsrY= =vd6O -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org