> There are several others around the 50-70% complete mark for F16, too, I > just cut off at 67%. It's a fairly long list of languages for which we > previously had tolerably complete translation coverage, but we now have > a level which isn't really usable: basically these languages have gone > from 'covered' in at least F16 (probably F17 too) to 'not covered' in > F18. I want to stress I'm not blaming anyone for this: I don't see how > it could be otherwise, the problem is the huge amount of string churn > caused by newUI, I'm actually more amazed at how many languages _do_ > have close-to-100% translations for F18 than how many _don't_, given the > conditions. It's just an unfortunate thing. Keep in mind that translations for a lot of these languages are completely a volunteer effort, and there's no guarantee that volunteers have the time or even interest to step up and do a whole new set of translations. It was always going to be this way, unless we found or hired some very motivated people to do all the translations, and we've explained that. You're comparing years of maintainence effort on a pretty stagnant UI with something that's not even been in a released product yet. > anaconda does not list every available translation for the user to > choose from, but I cannot figure out for the life of me how the decision > about which to display is made: it's not that very incomplete > translations are left out, as plenty of very incomplete translations > (including most of the above) are shown. If we filtered out very > incomplete translations we might at least look a bit less silly, but we > don't seem to be doing that. Our language selection screen is definitely > writing checks that our translations can't cash :) The details are in pyanaconda/localization.py, but basically we're displaying every language for which we have a .mo file. We'd talked about ordering things on the language screen such that very incomplete translations are sorted to the bottom or perhaps even hidden, but: (1) there's no time, and plenty of serious bugs to fix; (2) partial translations could be better than no translation at all, depending on what's missing and what's not. > 1. In the short term, is the combination of all these factors enough for > us to want to delay F18 further to try and make things suck less? No. > 2. If not, do we want to engage in some Messaging around the F18 release > to emphasize that we know there are all these issues and we'll try to > smooth things out for F19? We can only do so much for translations. What we need is a way to motivate speakers of a lot of these incomplete languages to join up and help out. That's the main messaging tactic I think we should take. > 3. In the longer term, how can we get anaconda, i18n, systemd, GNOME etc > folks all pointed in the same direction and working so that there's far > less suckage and far more smooth interaction going on here? Should we > try and run some sort of session at FUDCon? Perhaps. >From the anaconda perspective, we don't want to know a lot of this. We'd really prefer to not have knowledge about keyboard layouts and languages. We just want to grab the data from somewhere else and use it, but for whatever reason it seems like there's a lot of problems and a lot of components moving in different directions. - Chris _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
