2008/10/31 Stephan Kulow <coolo@suse.de>
Am Donnerstag 30 Oktober 2008 schrieb Alberto Passalacqua:
The strings were added after a translator testing the beta asked for the strings to become translatable. Only a very small part of it is KDE 4.2
I think I know who asked for that. ;-)
It's me who asked that, did you guess right ;-)
Still, I think it should be refused because that translator gave more work to everyone else in the translation teams without consulting them.
This is something I don't understand. It would have been english without the bug and if it's english without the work done. So why bother? Is your goal a "100%" string somewhere or an italian desktop?
I agree with that. I doesn't make chage as it is added strings and it doesn't change anything but statistics. What is anoying is when you change dozen of strings to fuzzy (for changes such as minor typos) very late in the stage. I think (but not sure) that is was what happened last relaese with knetworkmanager. For small team, when we cannot goal to 100% translation due to lack of translators, we try to focus first to the user experience. So we have to make choices and we skip for later things such as yast modules to make servers or other very advanced features to focus on the desktop. So for us it's a very bad thing if proeminents thing in the Desktop are shown in English such as "Destkop folder" on the deskop's folder view or things similars. I think the error was not to add these strings earlier (if it was possible). Greetings, Djan
E.g. we could branch out yast now and freeze it for openSUSE, but then we would also lack all the fixes done now. So basically we decided to go for more fixes and a possible lack of translations at some points. But as we did with past releases, we'll ship translation updates where it makes sense.
I admit 11.1 has a very long freeze period, so it is a sort of exception. However, I tend to think that a branch at a certain point (not the last week of the development) would improve things. Of course this would require a different planning of the development phases.
For example, in the years I spent around openSUSE, I always noticed that changes are done from the middle of the alpha stage to the beginning of the beta stage, while the first alpha's are relatively unchanged. Shifting this back would allow more changes and fixes in the "second part" of alpha stage, and the beginning of beta stage, allowing for a real hard feature freeze at some point in beta phase. I would also stop
Well, alphas see a lot of underlying changes that make it very often even impossible to develop against them. And usually the developers are blocked with other products during the alpha phase. But beta1 is really the point in time where the developers submit new features to the build, adding the strings. Then someone actually tests the beta and we find reasons to add more strings (just read opensuse-factory to spot 'well, just add a checkbox or a popup - it's just beta4').
The problem is, as said earlier, easy to fix if all you care for are translations: just don't change anything. But I'm afraid, for me, it's just one aspect out of many. We're trying constantly (and when I say we I mainly mean Karl and me I'm afraid :) to find ways to make it as easy as possile for the translators. But if you then complain that we make strings translatable that weren't in earlier betas, I fail to understand what you're up to.
I'm open to a discussion on how to improve things, but I'm afraid the things are not as easy as you may think. There are cases where I don't understand why they are still done either, but we will clarify them. PackageKit and yast2-support are two cases that souldn't be in lcn by now IMO (but then again, I was offline for 9 weeks).
Greetings, Stephan -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org