Now we have the first (and the last?) slide-show update and a small patterns enhancement. For savefty reasons I also merged all the other files. It would be great, if you could take a final look because we are heading towards beta4.
Later the day, I'll remind the developers to update their package with the PO files from the lcn on Friday.
cheers, Karl
Onsdag 22 oktober 2008 12:07:04 skrev Karl Eichwalder:
Now we have the first (and the last?) slide-show update and a small patterns enhancement. For savefty reasons I also merged all the other files. It would be great, if you could take a final look because we are heading towards beta4.
Later the day, I'll remind the developers to update their package with the PO files from the lcn on Friday.
Hrm.. ~250 untranslated/fuzzy strings in gnome-packagekit. Is it really necessary that we still maintain our own fork of these translations? Shouldn't it be mature enough to be translated upstream by the gnome project by now?
This practice should really be kept to a minimum, and only happen temporarily when absolutely necessary.
Martin Schlander martin.schlander@gmail.com writes:
Hrm.. ~250 untranslated/fuzzy strings in gnome-packagekit. Is it really necessary that we still maintain our own fork of these translations? Shouldn't it be mature enough to be translated upstream by the gnome project by now?
Agreed.
This practice should really be kept to a minimum, and only happen temporarily when absolutely necessary.
Yes, but obviously it is not that easy to make all involved parties happy. It's a general problem. Upstream packages are often imcompletely translated when we add them to openSUSE. If more translations are available upstream, we probably should pull them in--wondering whether upstream translations should always win unconditionally?
IIRC, we still have such a feature request open, and thus far we did not dare to enable it.
On Wed, Oct 22, 2008 at 11:05 AM, Karl Eichwalder ke@suse.de wrote:
Martin Schlander martin.schlander@gmail.com writes:
Hrm.. ~250 untranslated/fuzzy strings in gnome-packagekit. Is it really necessary that we still maintain our own fork of these translations? Shouldn't it be mature enough to be translated upstream by the gnome project by now?
Agreed.
This practice should really be kept to a minimum, and only happen temporarily when absolutely necessary.
Yes, but obviously it is not that easy to make all involved parties happy. It's a general problem. Upstream packages are often imcompletely translated when we add them to openSUSE. If more translations are available upstream, we probably should pull them in--wondering whether upstream translations should always win unconditionally?
Agreed too, although if we will still maintaining this file, IMHO our translation should win over upstream.
Onsdag 22 oktober 2008 15:05:57 skrev Karl Eichwalder:
Yes, but obviously it is not that easy to make all involved parties happy. It's a general problem. Upstream packages are often imcompletely translated when we add them to openSUSE. If more translations are available upstream, we probably should pull them in--wondering whether upstream translations should always win unconditionally?
I say yes.
- Upstream know their own rules and guidelines best - Different translations for the same things across distros, makes cross- distro user support more difficult - Our forking of translations should be a temporary thing, so 1-2 releases later opensuse-users would be switched to upstream translations anyway
If openSUSE translators are unhappy with upstream translations they should take their gripes there, instead of forking it in opensuse svn.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday, 2008-10-22 at 15:36 +0200, Martin Schlander wrote:
Onsdag 22 oktober 2008 15:05:57 skrev Karl Eichwalder:
Yes, but obviously it is not that easy to make all involved parties happy. It's a general problem. Upstream packages are often imcompletely translated when we add them to openSUSE. If more translations are available upstream, we probably should pull them in--wondering whether upstream translations should always win unconditionally?
I say yes.
- Upstream know their own rules and guidelines best
- Different translations for the same things across distros, makes cross-
distro user support more difficult
- Our forking of translations should be a temporary thing, so 1-2 releases
later opensuse-users would be switched to upstream translations anyway
If openSUSE translators are unhappy with upstream translations they should take their gripes there, instead of forking it in opensuse svn.
Yes, but:
- If the file is on out ./po directory, then we translate it complete and we are boss, and I don't care what upstream think. - If the upstream translation is the one that should keep, then the file should be removed completeley from our tree.
Choose! >:-)
My vote: remove.
- -- Cheers, Carlos E. R.
"Carlos E. R." carlos.e.r@opensuse.org writes:
Yes, but:
- If the file is on out ./po directory, then we translate it complete and we are boss, and I don't care what upstream think.
- If the upstream translation is the one that should keep, then the file should be removed completeley from our tree.
We'd probably need an indirection layer. I'm inclined to consider upstream translations as memory files and entries from memories should be approved before usage.
Something along these lines we must add to the lcn-merge resp. y2-prep-package script anyway.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday, 2008-10-22 at 16:34 +0200, Karl Eichwalder wrote:
"Carlos E. R." <> writes:
Yes, but:
- If the file is on out ./po directory, then we translate it complete and we are boss, and I don't care what upstream think.
- If the upstream translation is the one that should keep, then the file should be removed completeley from our tree.
We'd probably need an indirection layer. I'm inclined to consider upstream translations as memory files and entries from memories should be approved before usage.
Something along these lines we must add to the lcn-merge resp. y2-prep-package script anyway.
Yes, translations from memory should always be marked "fuzzy". Not only in this case, but in all cases.
- -- Cheers, Carlos E. R.
Am Mittwoch, 22. Oktober 2008 14:56:30 schrieb Martin Schlander:
Hrm.. ~250 untranslated/fuzzy strings in gnome-packagekit. Is it really necessary that we still maintain our own fork of these translations? Shouldn't it be mature enough to be translated upstream by the gnome project by now?
This practice should really be kept to a minimum, and only happen temporarily when absolutely necessary.
I agree too. Also I wonder how many of those strings are actually visible?
Greetings Michael
Karl Eichwalder ke@suse.de writes:
Now we have the first (and the last?) slide-show update and a small patterns enhancement. For savefty reasons I also merged all the other files. It would be great, if you could take a final look because we are heading towards beta4.
The final yast files arrived; I'll start the merge within the next minute. Note, 'wagon' is new. We will ship it as a "technology preview" and translations are not necessarily required.
translation@lists.opensuse.org
-
Carlos E. R. -
Gabriel -
Karl Eichwalder -
Martin Schlander -
Michael Skiba