On Wednesday 24 October 2007, Christian Perrier wrote: > - criterion for downgrading to prospective: > - below 98% for sublevel 1
It probably won't surprise you that I have a problem with this 98% criterium. My main argument is of course that having 2% of your strings untranslated can make the installer completely unusable for people who don't understand the fall-back language if that 2% happens to include key strings. For Beta releases some missing translation updates is fine with me. But for _RC_ releases IMO all translations should be at 100% for at least sublevel1, and preferably for most of the "optional" and "expert" components from sublevel2. Exceptions for sublevel1 can be made, but would explicitly have to be judged on a case-by-case basis, taking into account exactly _which_ strings are fuzzy/missing. An additional method you could consider implementing to further reduce the size of sublevel1 is to "tag" strings as less important (e.g. because they are architecture specific) and split individual strings out based on that. This would allow a lot more fine-grained split than the current component based split and allow more sublevels. For bonus points: specify in the tag the sublevel a string should be in . Cheers, FJP
signature.asc
Description: This is a digitally signed message part.
