Michael Skiba <mailinglist@michael-skiba.de> writes:
The advantage would be that it should be pretty easy to determine which language meets a requirement and which doesn't - on the other hand do we really want to throw away an 50-percent translation? I doesn't look perfect, but for some 50% is better than nothing...?! (last sentence also applies to unmaintained languages)
It is easy to count numbers and base a decision on it. But sometimes, it does not make a difference whether 100% or just 80% are translated if the missing translations belong to seldom used software pieces (this, of course, depends on the user).
Maybe they should be marked as incomplete or opt-in only (but bare in mind that for some people it will be difficult to apply the opt-in-process if it's not in their native language).
Something similar already exists in yast. If the user selects an incompletely translated language, yast will warn if a certain amount of messages in not translated (it is configurable). This is only about yast messages (85 or 90%?); taking other desktop components into account would be an interesting exercise. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org